Error encountered: kmode exception not handled
Error encountered: kmode exception not handled
My computer unexpectedly began showing a blue screen when I tried to open a game. It tends to happen roughly 3 to 5 minutes after startup. This issue also appears without the Kmode exception error. Notably, it doesn’t occur in safe mode.
Besides the Kmode exception, I experienced this problem once just before the blue screen during the second occurrence. The error message read:
"c:\windows\system32\nvspcap64.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support."
This error code is oxc000012f and appears only once among several blue screens.
I own a RTX 3080, a Ryzen 9 5900x, and 16GB of RAM. I suspect these are the relevant diagnostic files:
https://files.catbox.moe/6bwtr2.dmp
I have tried cleaning the installation of Nvidia drivers using DDU and installing drivers via the device manager. Windows memory diagnostics found no problems. I also ran chkdsk, which reported errors but fixed them. However, the issue persists.
I uninstalled Gigabyte RGB, as it’s rumored to cause instability. I performed a full malware scan. I executed sfc /scannow in the admin command prompt—it initially detected and resolved some issues, but the problem remains. I ran Dism /Online /Cleanup-image /RestoreHealth, checked drive health, and confirmed all drivers are up to date.
I do have an available Windows update, though updating it isn’t possible because of the blue screen and I can’t update in safe mode.
Any assistance would be very much appreciated.
Welcome to the forums, newcomer!
This began when I tried to launch a game.
Which game was it? Where did you get the installer for?
Also odd is that it doesn’t blue screen in safe mode—this might point to a driver problem.
I’ve tried cleaning the Nvidia drivers with DDU and installing them from the device manager.
In Safe Mode, I use DDU to remove all GPU drivers (Intel, AMD, Nvidia), then manually install the latest driver from Nvidia’s support site in an elevated command, like right-clicking the installer and selecting Run as Administrator.
I have a RTX 3080, a Ryzen 9 5900x, and 16GB of RAM.
When sharing a troubleshooting thread, it’s helpful to list your full system specifications. Please include details such as:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
Also mention the age of the PSU, along with its make and model.
BIOS version for your motherboard at this time.
Using WinDBG, I noticed WindowsUpdateBox.exe could be a trigger. What version are you running?
I really appreciate the response, but I'm still struggling and haven't found any assistance elsewhere.
I started The finals from Steam, having played it for several months before. It seems unrelated to that particular game.
Yes, I reinstalled using DDU in safe mode and then installed the driver. I'm not sure if I ran it with admin privileges, so I'll try that again and follow up.
I'm unsure about all my components; what I know is the details:
CPU: Amd ryzen 9 5900x
CPU cooler: Corsair h150
Boards: MSi b550-A pro
RAM: Corsair vengeance 2x16 ddr4 3600mhz
SSD: multiple, but I think the boot drive is WD_black SN770 1tb?
GPU: GIGABYTE 3080 10gb
Power supply: be quiet! Direct power 1200w
Operating system: win 11 version 23H2 build 22631.4890
Setting up new Nvidia drivers via admin in safe mode after DDU failed. MSI Dragon mentions an old AMD chipset driver might be the issue, but installing AMD drivers in safe mode is proving challenging due to the installer's restrictions.
I also think I've successfully obtained a full dump file by adjusting the paging file size. Here it is:
https://files.catbox.moe/kk1qrn.zip
Even though the file size matches others, I'm still a bit uncertain.
The system is using identical overclock drivers from two different locations, which could cause instability. Each driver modifies the CPU voltage settings. A new overclock driver was not installed after updating the BIOS. Additionally, multiple copies of this driver are present, such as CorsairLLAccess64.sys and its variants. It is recommended to remove and re-test the installation. You may run Microsoft autoruns64.exe with admin privileges and clear any conflicting entries. Extra kernel addresses appear when drivers conflict. An old driver named inpoutx64.sys was found on October 17, 2008, indicating persistent legacy software. Memory corruption issues were reported in 2013, resolved by updating the firmware. There is a mix of outdated VB-Audio drivers from previous years, and memory access violations were observed. Consider uninstalling these and cleaning up before retesting. Also, ensure the RTKVHD64.sys driver matches your current BIOS version.