Exception in System_Thread_Exception_Not_Handled reported by nvlddmkm, crash dump noted in comments.
Exception in System_Thread_Exception_Not_Handled reported by nvlddmkm, crash dump noted in comments.
Hello once more! After finally getting a boot into BIOS, I’ve faced several obstacles when trying to launch Windows. I’ve been exploring various fixes online for a week and am hoping someone here can help me in the right direction. Right now, I’m stuck without clear guidance on what to try next. I’ll do my best to recount all the troubleshooting steps I attempted.
Installing Windows
When I first tried installing Windows, I consistently experienced random crashes during setup. I didn’t see a BSOD, but I had no idea why it would stop abruptly. I’ve repeated the installation process multiple times, but the only reliable way to reach the OS is via the iGPU and then the graphics card. While running Windows on the graphics card, my system would freeze and black screen unexpectedly. However, it remained stable when booting into safe mode.
I thought the problem might be with the graphics card itself. I tried using DDU in safe mode to install the latest drivers (which I downloaded onto a USB drive). This sometimes resolved the issue temporarily—it stopped working once I powered off and on again. Sometimes it would freeze when the Asus BIOS logo appeared, then restart.
Several Reddit threads suggested checking the Event Viewer for clues. I noticed an error message labeled “nvlddmkm” that kept appearing. The description for this event was unclear—either the hardware wasn’t installed properly or the installation was corrupted. I followed instructions to add the missing “nvlddmkm.sys” file to the drivers folder, but the errors persisted, often followed by “WHEA-Logger” messages.
Other attempts included booting into safe mode, running DDU, and reinstalling the graphics drivers all within safe mode. Occasionally, these steps fixed the problem, though not always.
I’ve also looked at articles like this one: https://ccm.net/computing/hardware/1975-...r-message/.
Despite my efforts, I’m still unsure what to do next. Please share any additional details you can provide—I’ve been working on this for most of my break and really wanted to get back up before work tomorrow. Thank you!
It seems there could be a disk failure. If an SSD experiences memory sector issues, it can use spare sectors to keep running while the faulty ones are replaced. However, the data in those failed sectors is lost permanently. I’d remove that M.2 drive and inspect it on another machine. DDR5 models have also faced similar problems—consider setting the speed to 4800 as a precautionary test.
Performed a diagnostic and SMART scan using Samsung's software; both confirmed SSD was clean. Downloaded Steam titles and ran them via iGPU without issues. Turning off XMP and resetting RAM clock to 4800 didn't resolve the problem. Tried several fixes: updated BIOS, re-seated GPU, RAM, and M.2 SSD. Decided to perform a fresh Windows install. After rebooting, device manager identified the GPU as Nvidia 3060ti. It seems the automatic driver update conflicted with manual installation attempts. Attempted safe mode, DDU, and a full reinstall via USB. Progress: Driver updated successfully on September 13, 2021. Next steps involve safe mode testing and a potential reboot for completion. Planning to try again tomorrow.
Discovered a discussion on the Windows Hardware forums recommending disabling hardware acceleration. No success with the suggested method. The Jayztwocents video also raised concerns, as it appeared to require a BIOS flash and still didn’t resolve the issue. I’m considering returning the GPU or switching brands if needed. It seems many sources mention Zotac GPUs in their configurations. I plan to perform a clean Windows install on the integrated graphics card, then update drivers via DDU, restart normally, and attempt driver installation again. I’ll also update this post’s title based on my suspicion that the graphics card is the root cause.
Continuing with the update, I managed to make some headway using the iGPU while keeping the 3060ti connected. The blue screen error appeared—great progress! I saved the three mini dumps and one full memory dump to Dropbox. If anyone can clarify what’s happening, it would mean a lot. After work, I plan to try a few more steps: install MSI Afterburner to reduce GPU clock speeds (possibly the OC Zotac is pushing too hard?) and upgrade to a much older GeForce driver (like 516.94).