The system is experiencing frequent crashes due to nvlddmkm.sys issues.
The system is experiencing frequent crashes due to nvlddmkm.sys issues.
Hello, welcome to the forum. I’m new here and trying to figure out a problem with my recent PC setup. The NVIDIA display driver keeps crashing without any clear reason. It happens at random times—sometimes I’m using it for just a few minutes, other times I’ve been on for hours. It doesn’t matter if I’m gaming, watching videos, or just idle. I’ve been experimenting with it for days and feel really confused. If you have any advice, I’d appreciate it.
I checked the Windows Event Viewer and found an error labeled “Spoiler” with ID c84b6412-45e4-4bbf-9e06-00a402ef2bf1. The dump was saved at C:\Windows\Minidump\110222-6687-01.dmp. When I opened it with WinDpg using the command “!analyze -v”, it pointed to a section indicating the driver stopped functioning. The details included in the dump file were labeled with specific codes and IDs.
I tried running the dump through a tool called WinDpg, but it led me to a part of the code suggesting the NVIDIA driver had stopped working. The system reported a failure with ID 0x133_ISR_nvlddmkm!unknown_function. The OS version was 10.0.22621.1, and it was running Windows 10.
I also looked into the Event ID 0 description, but it wasn’t found. It seems the issue might be related to a missing or corrupted component. I’ve tried several fixes: booting in safe mode with DDU to uninstall the driver, downloading a new one via GeForce Experience, and even reinstalling Windows. Still, the crashes persist.
Other attempts included updating to the latest driver fix, rolling back to an older version, and using a different case or cooler. The build details are noted, but the problem remains unresolved. If you have more insights or suggestions, I’d really value your help.
I should point out I am also seeking help from the Nvidia forums. One person over there suggested I take the GPU out and reseat it in the motherboard, and making sure all the power cables were connected. In doing so, I have completely disconnected the gpu from my system. Reseated it in the motherboard, made sure all the pins were plugged in, and reinstalled the drivers. Unfortunately I still have the crashing issue. Here is the minidump that windows created after the crash. Spoiler ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above. Arg2: 0000000000001e00, The watchdog period (in ticks). Arg3: fffff8051c51c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeout Arg4: 0000000000000000 Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: TickPeriods *** *** *** ************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 812 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2673 Key : Analysis.IO.Other.Mb Value: 12 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 31 Key : Analysis.Init.CPU.mSec Value: 92 Key : Analysis.Init.Elapsed.mSec Value: 32460 Key : Analysis.Memory.CommitPeak.Mb Value: 98 Key : Bugcheck.Code.DumpHeader Value: 0x133 Key : Bugcheck.Code.Register Value: 0x133 Key : Dump.Attributes.AsUlong Value: 1808 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 FILE_IN_CAB: 110322-6812-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x1808 Kernel Generated Triage Dump BUGCHECK_CODE: 133 BUGCHECK_P1: 1 BUGCHECK_P2: 1e00 BUGCHECK_P3: fffff8051c51c340 BUGCHECK_P4: 0 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED BLACKBOXBSD: 1 ( !blackboxbsd ) BLACKBOXNTFS: 1 ( !blackboxntfs ) BLACKBOXPNP: 1 ( !blackboxpnp ) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffd600`7c770c68 fffff805`1ba2413f : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`1c51c340 : nt!KeBugCheckEx ffffd600`7c770c70 fffff805`1ba22f74 : 000001d1`f803bb97 00000000`00000000 00000000`0000a345 00000000`00000000 : nt!KeAccumulateTicks+0x23f ffffd600`7c770cd0 fffff805`1ba21403 : fffff805`1c45fcd0 00000000`00000000 ffffd600`7c756180 ffff9786`e511ec40 : nt!KiUpdateRunTime+0xf4 ffffd600`7c770e90 fffff805`1ba2088a : fffff805`1c45fcd0 ffffab8f`1b54c950 ffffab8f`1b54c950 00000000`00000000 : nt!KeClockInterruptNotify+0x763 ffffd600`7c770f40 fffff805`1bb45f9e : 00000001`8549e86f ffffab8f`1b54c8a0 ffffd600`7c756180 00000000`00000000 : nt!HalpTimerClockInterrupt+0x10a ffffd600`7c770f70 fffff805`1bc29bea : ffff9786`e511ecc0 ffffab8f`1b54c8a0 ffffab8f`2e523ba8 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x19e ffffd600`7c770fb0 fffff805`1bc2a1b7 : ffffab8f`2e523000 ffff9786`e511ed00 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa ffff9786`e511ec40 fffff805`4d90a9ec : 00000000`00000000 00000000`000001d0 ffffab8f`2e534000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 ffff9786`e511edd0 00000000`00000000 : 00000000`000001d0 ffffab8f`2e534000 00000000`00000000 00000000`00000020 : nvlddmkm+0x9a9ec SYMBOL_NAME: nvlddmkm+9a9ec MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 9a9ec FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86} Followup: MachineOwner --------- I will be honest, I have no idea what any of it means. Any other ideas?
Before starting any actions, ensure you have a backup or restore point ready. If needed, you can revert to an earlier state to avoid further issues. Here are some possible solutions you might consider:
1. Update Graphics Drivers via Device Manager
Use the Windows Device Manager to inspect your hardware. To update drivers, open Run (Win + R), type "devmgmt.msc," and choose the best match. You can also search for "Device Manager" in the Start menu, expand Display Adapters, right-click your GPU, and select Update driver. Windows will then search for the newest versions online and install them. Restart your PC afterward.
2. Adjust GPU Settings
Sometimes changing the settings can resolve problems. You may try underclocking your GPU using tools like MSI Afterburner (download from the provided link). This can fix certain errors, though it may slightly reduce performance.
3. Remove and Reinstall Drivers
Open Device Manager, find your graphics card, right-click, and choose Uninstall device. Confirm the deletion in the confirmation dialog. Download the latest Nvidia drivers from the official site, reinstall them, and restart your computer. After rebooting, locate the nvlddmkm.sys file in C:\Windows\System32, rename it to nvlddmkm.sys.old, and move the new file into C:\Windows\System32.
If you follow these steps, you should be able to resolve the issue.
Windows indicated I already possessed the newest drivers.
2 - Reduce GPU Speed - It seems the adjustments only last briefly unless I keep power limits active. Keeping afterburner or Zotac's FireStorm on, lowering the GPU power cap. For example, when I open FireStorm and set the power to 60%, my idle core clock sits around 210, GPU memory clock near 400, and voltage hovers at about 875. However, after a crash, the Core clock jumps to 2535, Memory clock to 10501, and voltage spikes to 950. It appears the GPU is being overloaded before it fails.
3 - Erase and Reinstall Graphics Card Drivers - After restarting, go to C:\Windows\System32\Drivers and rename the nvlddmkm.sys file to nvlddmkm.sys.old. Then, access the Nvidia folder (typically C:\ProgramFiles\Nvidia), locate a file named nvlddmkm.sys_, and copy it to the System32 directory. Launch Command Prompt as admin and run EXPAND.exe nvlddmkm.sy_ nvlddmkm.sys. After completion, paste the newly created file into C:\Windows\System32\Driversfolder. I’m having trouble locating the nvlddmkm.sys file in those locations—it doesn’t seem to exist anywhere.
I connected my 3070 to the computer and it functions perfectly. When I tried the 4090 on my old machine, the same problem occurred. It seems the issue might be with the card itself. I plan to contact Zotac for their opinion.
Just set up an account here for +1 and encountered the same problem with a Zotac 4090 Trinity. I've tried several fixes but haven't found a solution yet. The issue seems to be resolved when switching the 4090 for a 2080ti. Here are the components I'm considering: CPU – AMD R9 7900x MOBO; GPU – Zotac Gefore RTX 4090 Trinity; PSU – ASUS ROG STRIX 1000 Watt 80 Plus Gold; RAM – TEAMGROUP FF4D532G6200HC38ADC01 (32GB DDR5, 6200MHz). I'm hoping this information helps with the return process.
Hi! new 4090 owner here with the same issue. Also tried every possible solution posted in forums. I can (more or less) consistently cause a crash just by executing the FIRE STRIKE 3dmark free test. For 20+ executions, only two of them finished. Here is one of them: https://www.3dmark.com/3dm/83805375 Did you find any solution? CPU: Intel i9 13900K MOBO: Asus PRIME Z790-P WIFI GPU: Zotac Gefore RTX 4090 Trinity PSU: Corsair RM1000e Watt 80 Plus Gold
Are you using the GPU driver that came with your graphics card or the newest version? Make sure to download only WHQL signed drivers, avoid betas, and verify compatibility with your applications. You'll be using the latest one, but it may not always be the best choice.
I tested all available drivers: 522.25, 526.47, 526.86, and 526.98. I also tried turning XMP on/off, HAGS on/off, and enabling/disabling performance mode at Nvidia Power settings. None of these combinations stopped the crash when Fire Strike 3dmark ran (likely Directx11 without ray tracing). The crashes happened in different runs sometimes. I couldn't get four consecutive failures.