Discussion: NVIDIA Display Driver (nvlddmkm.sys) DPC Latency

Status
Not open for further replies.
Can someone help me out please. I'm really flustered right now and not thinking straight. This crap method Microsoft published for getting into safe mode by shutting down 3 times over and over is not working, and it's just going to fry my hardware with all this power surging (who's brilliant idea was this).

I think my only option is to take my default W10 install usb and do the shift+f10 trick to open cmd prompt. Now I have X:\ to work with. I can't change directory into C:\Windows\System32 so that I can run bcdedit /set {current} safeboot minimal since it gives me the error "The system cannot find the path specified". Hopefully I'm just overlooking something simple...I'm on my chromebook at the moment...
 
Last edited:
Windows can't load for me to use winaero :p It immediately goes to black screen and fails to load the OS right after the bios loads. My display works in windows setup when I boot from usb because it automatically uses microsoft's basic display driver instead.
 
got room to create a test install? from there load the hives from the bricked partition, compare, export from current and import on bricked.
Nirsoft got 2 tools that could do that(i think). Leaving 100gb or less for a quick rescue install can get you out of crap creek :cool:
 
F***. Why won't someone tell me why it's broken?? I didn't touch anything!!

Hahahahahaha. Everyone ignore this little reply, it's just a funny inside joke I'm directing at Garlin because it sooooo applies here, and right now humor is the way I am keeping my sanity :p
 
I think I'm in the clear now, managed to get into safeboot desktop...Well I guess it's a damn good thing W10 has given me so much grief, because all the crap I learned in the last 12 months paid off immensely just now. I'll walk everyone through what I did soon so if anyone ever bricks like this again in the future we can direct them on what to do.
 
Hellbovine said:
I think I'm in the clear now, managed to get into safeboot desktop...Well I guess it's a damn good thing W10 has given me so much grief, because all the crap I learned in the last 12 months paid off immensely just now. I'll walk everyone through what I did soon so if anyone ever bricks like this again in the future we can direct them on what to do.
Click to expand...
Heres what i have learned, leave a partition that is big enough to install a recovery install for your OS of choice, even if it is to just grab user profile folders for your programs like Firefox :cool:. Once you have grabbed all the critical data you can reinstall.

One lesson that you havnt learned is to test test test first, not use your main install. Guess that one slipped by you, well it wont next time :p
 
I wrote up a small guide on a last resort method to get into safe mode (link) that I had to use for my bricked computer because nothing else would work. Taosd was right on the money in his thought process, what happens is that when you boot to Windows Setup it loads that stuff into a temporary X:\ drive, and all of your other drives are assigned letters that don't match what we see on a live Windows in the File Explorer. We have to use diskpart's list command to figure out what letter our Windows drive has, then change directory to the bcdedit location so that we can use that command and tell Windows to boot into safemode on the next restart. Also the bcdedit {current} didn't work, it had to be {default} instead.
 
Last edited:
Hello everyone. I apologize for possible mistakes, I write helping myself through the translator. After reading kilometers of text from forums and trying a million different ways to fix this problem, I was able to personally identify my "one of the pains in the ass", which is the driver/device - M-Audio 192 4. While the sound goes through it, the number of ISR and DPC is just off the scale. And it affects - nvlddmkm.sys , dxgkrnl.sys and wdf01000.sys . When using regular headphones connected to the front panel, without a sound card, wdf01000.sys behaves more or less normally, significantly reducing the number of ISRs and DPCs. The same thing happens with nvlddmkm.sys , the delay time decreases, but there are still moments of peaks. I noticed an interesting detail that in my case, if you disable the video card as a device in the device manager and connect the sound through the sound card, then there is no delay at all (maybe I don't understand something, because I'm not very strong in such matters, but I found it even a little funny, at 19 o'clock continuous search for a solution to the problem). As I understand it, the video card driver somehow conflicts with the sound card drivers? If yes, then why does the number of ISRs and DCP grow when the sound card is disabled? My hands are already dropping. There is not even anything to cling to in order to understand where to move to deal with this problem.
 
glxxmybxy said:
Hello everyone. I apologize for possible mistakes, I write helping myself through the translator. After reading kilometers of text from forums and trying a million different ways to fix this problem, I was able to personally identify my "one of the pains in the ass", which is the driver/device - M-Audio 192 4. While the sound goes through it, the number of ISR and DPC is just off the scale. And it affects - nvlddmkm.sys , dxgkrnl.sys and wdf01000.sys . When using regular headphones connected to the front panel, without a sound card, wdf01000.sys behaves more or less normally, significantly reducing the number of ISRs and DPCs. The same thing happens with nvlddmkm.sys , the delay time decreases, but there are still moments of peaks. I noticed an interesting detail that in my case, if you disable the video card as a device in the device manager and connect the sound through the sound card, then there is no delay at all (maybe I don't understand something, because I'm not very strong in such matters, but I found it even a little funny, at 19 o'clock continuous search for a solution to the problem). As I understand it, the video card driver somehow conflicts with the sound card drivers? If yes, then why does the number of ISRs and DCP grow when the sound card is disabled? My hands are already dropping. There is not even anything to cling to in order to understand where to move to deal with this problem.
Click to expand...

Hellbovine i think we may be seeing the pattern become more too common with the nvlddmkm.sys, dxkrnl.sys and the wdf01000.sys

glxxmybxy what cpu and graphics card do you use ?
 
If I'm understanding correctly, it sounds like the issue glxxmybxy is having is coming from his audio driver. But that his Nvidia driver also still has some spikes when he doesn't use the sound driver? If so that does make sense. It's possible to have 2 drivers with DPC issues and for them to affect each other, making the whole issue worse. Does uninstalling the sound driver put your overall DPC into decent ranges, even though Nvidia is still spiking when the audio driver is uninstalled? How high are the spikes before and after?
 
Last edited:
Taosd said:
that may be even better, if you don't mind. thanks
Click to expand...
NZXT H7 Elite
Gigabyte z690 Aorus Elite DDR4 rev. 1.0
I9 12900k
ASUS ROG Ryujin II 360 ARGB EVA Edition
Samsung 980 Pro 1tb
Corsair Dominator Platinum 4x8 (CMT16GX4M2C3600C18)
Colorful Vulcan RTX 3090
Super Flower Leadex SE Platinum 1000w
 
it has to be some sort of issue still between MS and NVid

Personally i don't find any issues when gaming at the moment, but who knows if i can say the same tomorrow
 
Hellbovine said:
If I'm understanding correctly, it sounds like the issue glxxmybxy is having is coming from his audio driver. But that his Nvidia driver also still has some spikes when he doesn't use the sound driver? If so that does make sense. It's possible to have 2 drivers with DPC issues and for them to affect each other, making the whole issue worse. Does uninstalling the sound driver put your overall DPC into decent ranges, even though Nvidia is still spiking when the audio driver is uninstalled are we looking at spikes of 200us or what?
Click to expand...
I tried deleting audio drivers. Reinstall them. Old or new, it does not matter in principle. The spikes are still at the level of 550-1600us. But these are not stable values, which puts me in a stupor. Now, for example, I have nothing turned on except the browser and Spotify and Latencymon. The value is around 150-450 us.
 
Status
Not open for further replies.
Back
Top