Question is my motherboard still okay?

[Nvious]

Hi guys,
I recently changed my CMOS battery on my motherboard but while doing so i accidentally knock my gpu over and it fall and hit the motherboard (about 5-6 inches drop) after that i tried booting and running benchmark the pc seems find the only thing im start noticing lately is how it will produces sound stuttering randomly when im playing games, which didn't happen before (except in one game but that is more likely the game fault) now it's happen all across the board. could this be my motherboard going bad? how can i check if i did actually done any damage to the board?

 

[Dj0gany]

first of course check phisycally.Any scratch can hurt your motherboard (it dependes how tough the mobo is).But i am sorry to tell you this but if you dropped your gpu from 5-6 inches that is... that is a pretty bad fall both for the gpu and the mobo.In a worse case scenario buy a new mobo,but until then stick with the current one until it either dies or until you decide to swap it.I have a friend who dropped his chargeg accidentally on the mobo and it scratched his pci-e slot and i remember him straight up shaking until he found ot he had to buy a new mobo because when he turned it up he had no signal from his gpu.

Good luck man

 

[Nvious]

wait, does this mean i have to worry that the gpu is going to die soon too? :S

 

[Dj0gany]

no,in my personal experience the only reason gpu die is either they are faulty right from the begging or the psu killed them.You pci-e slot might die,but im sure the mobo cant kill it

 

[Nvious]

no i meant, u said the drop from that height is pretty bad for both motherboard and gpu... i'm wondering does that mean my gpu is now also likely damaged? :S if so is there a way for me to test for damage on gpus so i can have a peace of mind that at worst i just need to replace motherboard and not both? , thanks again for ur help tho.

 

[Dj0gany]

gpus are phisycally stronger than the motherboard (motherbords are ussually a thin layer of composed cooper which is embeeded inbetween the layers of fiberglass) or they are just weak.On the other hand the gpu should be fine unless you drooped it at 30km/h.If the gpu felt on the metal peace that thightens it to the pc case you are fine,i could only imagine actually riping the mobo of the gpu but to do that you need extra force so i think that the gpu is fine.My only concern is that the pointy egdes of the gpus have damaged the motherboard when it fell.Again your gpu should be fine,i am only worried about the mobo.

 

[Nvious]

okay thanks so much for this, soo now i will know at the most it's just motherboard replacement :/

 

[Dj0gany]

yeah probably.
Good luck

 

[Nvious]

so im still experiencing sound stuttering , so i tried latencymon and this is the result i got
_
CONCLUSION
_
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:05:33 (h🇲🇲ss) on all processors.


_
SYSTEM INFORMATION
_
Computer name: DESKTOP-DB4DBVD
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: B150M-HD3, Gigabyte Technology Co., Ltd., B150M-HD3-CF
CPU: GenuineIntel Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
Logical processors: 8
Processor groups: 1
RAM: 16342 MB total


_
CPU SPEED
_
Reported CPU speed: 3408 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.



_
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 1811.80
Average measured interrupt to process latency (µs): 5.691356

Highest measured interrupt to DPC latency (µs): 1805.40
Average measured interrupt to DPC latency (µs): 2.004276


_
REPORTED ISRs
_
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 175.97770
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0.147980
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0.178129

ISR count (execution time <250 µs): 374968
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
ISR count (execution time >=4000 µs): 0


_
REPORTED DPCs
_
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 2999.167840
Driver with highest DPC routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total DPC routine time (%): 0.095365
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 0.254088

DPC count (execution time <250 µs): 1076921
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 185
DPC count (execution time 1000-1999 µs): 14
DPC count (execution time 2000-3999 µs): 4
DPC count (execution time >=4000 µs): 0


_
REPORTED HARD PAGEFAULTS
_
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: avp.exe

Total number of hard pagefaults 4711
Hard pagefault count of hardest hit process: 1647
Number of processes hit: 146


_
PER CPU DATA
_
CPU 0 Interrupt cycle time (s): 20.791046
CPU 0 ISR highest execution time (µs): 175.97770
CPU 0 ISR total execution time (s): 4.640355
CPU 0 ISR count: 362717
CPU 0 DPC highest execution time (µs): 2999.167840
CPU 0 DPC total execution time (s): 5.937142
CPU 0 DPC count: 985829
_
CPU 1 Interrupt cycle time (s): 7.747633
CPU 1 ISR highest execution time (µs): 124.598592
CPU 1 ISR total execution time (s): 0.112366
CPU 1 ISR count: 12251
CPU 1 DPC highest execution time (µs): 888.154930
CPU 1 DPC total execution time (s): 0.288045
CPU 1 DPC count: 18757
_
CPU 2 Interrupt cycle time (s): 6.976354
CPU 2 ISR highest execution time (µs): 0.0
CPU 2 ISR total execution time (s): 0.0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 344.774648
CPU 2 DPC total execution time (s): 0.152484
CPU 2 DPC count: 20365
_
CPU 3 Interrupt cycle time (s): 7.284515
CPU 3 ISR highest execution time (µs): 0.0
CPU 3 ISR total execution time (s): 0.0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 197.802817
CPU 3 DPC total execution time (s): 0.032816
CPU 3 DPC count: 4851
_
CPU 4 Interrupt cycle time (s): 6.085680
CPU 4 ISR highest execution time (µs): 0.0
CPU 4 ISR total execution time (s): 0.0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 223.517019
CPU 4 DPC total execution time (s): 0.127723
CPU 4 DPC count: 18001
_
CPU 5 Interrupt cycle time (s): 6.357986
CPU 5 ISR highest execution time (µs): 0.0
CPU 5 ISR total execution time (s): 0.0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 377.656103
CPU 5 DPC total execution time (s): 0.041269
CPU 5 DPC count: 5951
_
CPU 6 Interrupt cycle time (s): 6.732884
CPU 6 ISR highest execution time (µs): 0.0
CPU 6 ISR total execution time (s): 0.0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 198.221831
CPU 6 DPC total execution time (s): 0.104081
CPU 6 DPC count: 13493
_
CPU 7 Interrupt cycle time (s): 6.727136
CPU 7 ISR highest execution time (µs): 0.0
CPU 7 ISR total execution time (s): 0.0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 344.109742
CPU 7 DPC total execution time (s): 0.095838
CPU 7 DPC count: 9877
_

do you happened to know how to interpret any of that result? :S and if so what could possibly be causing this stuttering/popping sound ? thanks in advance againn

 

[Dj0gany]

i mean...i dunno