Kmode_exception_not_handled on shutdown, Blue Screen shown

Question

My PC crashes every time it shutdowns with the message Kmode_exception_not_handled. I checked the Minidump files with WinDbg, there were some messages that other threads suggest indicate problems with the graphic drivers. I deleted the graphic drivers from Device Manager. But, it still showed the error on shutdown, and the screen brightness is higher than normal, with or without these drivers. Previously I had to adjust the screen brightness in the Intel Control Center.

I activated Driver Verifier from this guide: https://answers.microsoft.com/en-us/windows/forum/all/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983, and after restarting, it showed an error with a message DRIVER_VERIFIED_DETECTED_VIOLATION but no driver name there on Startup. After that, it restarted again, and it showed the same error on Startup. I entered into Safe Mode and did /verifier reset. In Safe Mode, the screen brightness was normal.

The minidump and the MSInfo32 are uploaded, the file 043022-5250-01 is created after Driver Verifier is enabled, and it showed an error

DRIVER_VERIFIED_DETECTED_VIOLATION on startup.

The other 4 files are created after it showed an error Kmode_exception_not_handled on PC shutdown.

The link to One Drive: https://1drv.ms/u/s!AhlHvKlF5\_txgkArml9uoa-3wzO0

Answer 1

I upgraded to Windows 11 Pro. The BSOD on shutdown doesn't appear now.

Answer 2

Hi,

Thanks for updating me.

Have you disabled the Driver Verifier after enabling it?

Because running Driver Verifier could cause the computer to crash.

Answer 3

There were two new BSOD.

Only one was with WDV.

Run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive. https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

https://www.elevenforum.com/t/bsod-posting-instructions.103/

Make a new restore point: https://www.tenforums.com/tutorials/4571-create-system-restore-point-windows-10-a.html

Restart WDV using only these customized settings:

[ ] 0x00020000 DDI compliance checking.

[ ] 0x00080000 DDI compliance checking (additional).

If there is no immediate BSOD then open administrative command prompt and type or copy and paste:

verifier /querysettings

Post a share link into this thread using one drive, drop box, or google drive.

For any new BSOD run the V2 log collector and post a share link into the newest post.

Answer 4

Hi Dyari,

I uninstalled NordVPN, and after running Driver Verifier again, another app was also causing DRIVER_VERIFIED_DETECTED_VIOLATION at Startup. I uninstalled it and removed its driver with Autoruns for Windows https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns. Running Driver Verifier, the PC boots and it doesn't crash with a blue screen at Startup. But, on shutdown, it crashes with the error SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M.

I saw your answer for IMAGE_NAME: ntkrnlmp.exe, but the error message here is different: https://answers.microsoft.com/en-us/windows/forum/all/bsod-caused-by-ntkrnlmpexe/46437b26-5ed8-4e7a-9c4c-f4129efbe72e

I tried dism.exe /online /cleanup-image /restorehealth and sfc /scannow, but there is still an error on shutdown. The PC has all the updates including the optional installed, and Windows Defender as an antivirus. Uninstalling the Intel drivers causes them to be reinstalled if there is an internet connection. If there isn't, the basic drivers are installed, and after restarting the brightness is back to normal levels. But, shutting down the PC causes an error again.

The Minidumps are here: https://1drv.ms/u/s!AhlHvKlF5\_txgkS26iJuOEnkyKup

Answer 5

Hi DMinovski,

I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

The minidump files indicate nordlwf.sys as a cause of the crash which is related to NordVPN.

If you do have this VPN installed on your computer, uninstall it completely and check to see if your computer would be stable or not. After that, you can install a stable version of it.

If you do indeed of it, try updating your Network drivers to the latest or drivers that are compatible with your computer.

Please let me know if you need further assistance and keep me updated.

Stay safe