DPC latency issue (crackling audio) dxgkrnl.sys - Windows 7 x86 SP1

So i left out the kicker, which is that last week out of nowhere (I didn't do anything and the computer was already running) The crackling and rubberbanding went away for 2 days until i accidentally restarted my computer which i didn't want to do. So if its a hardware issue would it be the video card itself? or could it be the mobo? the card runs at a cool temp so does my cpu. Would it be worth doing a clean install of windows? Or should i just go exchange the card first?
 
satrow said:
Tomas, there may be further clues here: DPC latency issue (crackling audio) dxgkrnl.sys - MajorGeeks Support Forums

My feeling is that it's a physical connection problem, possibly damaged GPU card (reflow it?) or GPU/motherboard connection/damage.

I'd want to test the graphics card in a known good PC, feels like little point in a clean install until all the hardware has been proven good.
Click to expand...

Yea i wish i could test the gpu in a different comp but i have no way of doing this right now. Im headed off to get a can of compressed air actually to see if that does anything.
 
Ok so i exchanged the video card for a new one and its still happening. Guessing its something with my computer, any ideas? and what would of caused the audio to work fine randomly without me doing anything those couple days
 
Still happening in Chrome? Tomas pointed out the following back in #20
The problem is that Chrome is talking almost all CPU time, resulting into 100% CPU usage, which cause audio glitches. To be more specific, I see that pepflashplayer.dll component is responsible for that CPU usage inside Chrome. This can probably be explain by the fact that you are using a built-in GPU, which does not support hardware video decoding inside Flash, putting all the load to the CPU.
Click to expand...
I suggest you try alternative browsers, IE, Firefox, Opera etc., to see if you still have the same problems.

If it's really a hardware issue and you have changed the graphics card, then the motherboard GPU slot, broken motherboard traces/cracked motherboard, bad connection (almost anywhere), faulty PSU, ... could be to blame. They're all close to impossible to diagnose remotely.
 
the high latency with chrome open was without the video card installed. which when its not installed my audio is about perfect and dpc is low. something happens when the card is installed and it doesnt start happening until the card is actually being used with proper drivers. if i uninstall the card in device manager then restart with the card still connected everything is fine, its not till i install it with drivers then restart that the audio goes bad. If it is a motherboard issue it must be something that's not completely damaged cause as i said i couple times the high latency went away on its own. unfortunately I dont have the means to test parts in a working computer so for now I guess i just have to wait it out.
 
doesnt start happening until the card is actually being used with proper drivers.
Click to expand...
This might indicate that the PSU is involved, or that there's an issue with the Power (-saving?) settings within Windows, perhaps the settings in the graphics card software?

the high latency went away on its own
Click to expand...
Could be a sign of a bad connection, a crack or broken trace on the 'board, maybe PSU -related?
 
Could you please generate a new XPERF trace, while using a new VGA and still experiencing audio issues? Please use the following command this time:

Code: 
xperf -on PROC_THREAD+LOADER+PROFILE+INTERRUPT+DPC+DRIVERS+POWER+IDLE_STATES -stackwalk Profile -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 256 -FileMode Circular

Thank you.
 
Lasty said:
TomasD said:
Thanks.

I might have something, but I need some additional information about your system first. Could you please do the following?
  1. Download and run Sysnative jcgriff2 BSOD File Collection app. Attach the report it generates here.
  2. Download and run Speccy. Click File->Save Snapshot. Attach it here.
Click to expand...

doing this asap
Click to expand...

Thanks. In addition, please open Elevated (Run As Administrator) command prompt, type FLTMC and paste the results here.
 
Filter Name Num Instances Altitude Frame
--------------------- ----------------- ----------- --------
Mpfilter 10 328000 0
luafv 1 135000 0
FileInfo 10 45000 0
 
Thanks.

Let's do two more things:

  1. Install NVIDIA drivers that were released three days ago
  2. Generate one more XPERF trace, but use the following command this time:
    Code: 
    xperf -on PROC_THREAD+LOADER+PROFILE+INTERRUPT+DPC+DRIVERS+POWER+IDLE_STATES+FLT_IO_INIT+FLT_IO+FLT_FASTIO+FLT_IO_FAILURE+FILENAME -stackwalk Profile+MiniFilterPreOpInit+MiniFilterPostOpInit -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 256 -FileMode Circular
 
TomasD said:
Thanks.

Let's do two more things:

  1. Install NVIDIA drivers that were released three days ago
  2. Generate one more XPERF trace, but use the following command this time:
    Code: 
    xperf -on PROC_THREAD+LOADER+PROFILE+INTERRUPT+DPC+DRIVERS+POWER+IDLE_STATES+FLT_IO_INIT+FLT_IO+FLT_FASTIO+FLT_IO_FAILURE+FILENAME -stackwalk Profile+MiniFilterPreOpInit+MiniFilterPostOpInit -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 256 -FileMode Circular
Click to expand...

will do, ive just been testing different drivers thats why i didnt have the most current for those logs
 
Lasty said:
Lasty said:
hmmm that driver keeps failing to initiate
gonna try again
Click to expand...
nevermind that i was spacing out
heres the IDLE xperf
https://onedrive.live.com/redir?resid=DC3F3B0E548F933!110
Click to expand...

Are you sure you used the following command for this trace?

Code: 
xperf -on PROC_THREAD+LOADER+PROFILE+INTERRUPT+DPC+DRIVERS+POWER+IDLE_STATES+FLT_IO_INIT+FLT_IO+FLT_FASTIO+FLT_IO_FAILURE+FILENAME -stackwalk Profile+MiniFilterPreOpInit+MiniFilterPostOpInit -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 256 -FileMode Circular
 
Yea im pretty sure i used it, just copy pasted it.
and i used xperf -stop -d C:\CPU.etl to end the log
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top