MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .thread ; .cxr ; kb FOLLOWUP_IP: nvlddmkm+1a2b3f
Arguments: Arg1: 00000000c0000005, Exception code = access violation Arg2: fffff8002e4a2b3f, Address of instruction that caused exception windows 11 dump file viewer
If the image name is ntoskrnl.exe , the crash may be due to hardware, corrupted system files, or buggy filter drivers; run !analyze -v and check the stack for third‑party drivers below nt!KeBugCheckEx . Despite enabling dumps, Windows 11 sometimes fails to write them. Common reasons and solutions: MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm
| Symptom | Likely Cause | Fix | |-----------------------------------------|--------------------------------------|--------------------------------------------------------------| | No MEMORY.DMP after BSOD | Paging file too small | Set paging file to “System managed” or >2 GB. | | Minidump folder empty | Disabled by Group Policy | Check gpedit.msc → Computer Config → Admin Templates → System → “Write debugging information”. | | Dump file exists but viewer says corrupt | Disk error or interrupted write | Run chkdsk /f /r . Disable fast startup (Power Options). | | WinDbg shows “No symbols loaded” | Missing symbol path | Set _NT_SYMBOL_PATH environment variable or use .symfix . | | | Minidump folder empty | Disabled by
nvlddmkm.sys (NVIDIA driver) caused an access violation. Update GPU drivers.