nvlddmkm.sys problem
Hello everyone, how is it going?
Lately, I've been having some freezes while using Rider and sometimes I get the blue screen of death (0x00000133 DPC_WATCHDOG_VIOLATION). I'm a student but with the help of an AI I could open the memory DMP file and I got this:
The crash is associated with the nvlddmkm.sys driver.
- Symbol Name : nvlddmkm+dc233
- Image Name : nvlddmkm.sys
- This driver is part of the NVIDIA graphics driver stack.
- The crash occurred while the process rider64.exe was running.
- DPC Timeout Type: The timeout type is DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED, meaning the system spent too much time at DISPATCH_LEVEL or above.
- Hypervisor Flags: The system is running under a hypervisor (likely Hyper-V), as indicated by the Hypervisor.Flags.AnyHypervisorPresent flag being set to 1 (I checked and the Hyperv is disabled in the Windows features tool.
- Stack Trace: The stack trace shows that the crash originated in the NVIDIA driver (nvlddmkm.sys) during interrupt handling.
I know the problem could be with the Nvidia drivers, I'll post on the Nvidia forums, but I don't think Nvidia will even read my post.
Any idea what would be happening? Any suggestion?
Please sign in to leave a comment.
Hello,
Thank you for contacting Rider support. We are sorry to know that you experienced a BSOD error while using Rider.
Generally, no user-space program behavior could lead to BSOD, so in all cases this is either a hardware problem or a Windows problem.
We're not aware of any reasons Rider would cause the system to show BSOD. We wouldn't expect to see anything in Rider diagnostic files that would explain a BSOD error.
I recommend checking the hardware (perhaps starting from the RAM, using the Windows Memory Diagnostics utility, since Rider could use it extensively), and checking if Rider has any problems on another machine under similar circumstances (if possible).
I see you already have a stop code 0x00000133 DPC_WATCHDOG_VIOLATION. Typically, this is related to driver issues or hardware conflicts.
The next step you might consider following is to get crash minidump, then contact Microsoft and share the dump you collected together with the issue description. I found multiple complaints similar to your issue. (for ex.)
Have a nice day and good luck!
Thank you for responding. I was trying to fix the issue and realized that the problem was the new Nvidia driver. I installed an older one and the problem was fixed.