Kmode_exception_not_handled on shutdown, Blue Screen shown

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

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

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
Sincerely,

Dyari Barham
Independent Advisor & Microsoft Community Member

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

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

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

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.

Make a new restore point:

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.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi,

Thanks for updating me.

Have you disabled the Driver Verifier after enabling it?

Because running Driver Verifier could cause the computer to crash.
Sincerely,

Dyari Barham
Independent Advisor & Microsoft Community Member

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

The V2 log collector report and the verifier /querysettings result are added: https://1drv.ms/u/s!AhlHvKlF5_txgkWe5W0ElNrM_m7I

There wasn't a BSOD after enabling the two DDI compliance checking settings.

Setting the option Color Format to YCBCR_444 instead of RGB in the Intel Graphics Command Center -> Display seems to have fixed the brightness. I adjusted it a bit more in the Color menu with the Brightness and Contrast sliders.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Yes, I disabled the Driver Verifier after running the tests.

Running the command kd> ln fffff800207bf37c for the Minidump file returns:

(fffff800`207bf34c) nt!BiSpacesUpdatePhysicalDevicePath+0x30 | (fffff800`207bf5ac) nt!BgDisplaySafeToPowerOffScreen

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Restart WDV using only:

[ ] 0x00000004 Randomized low resources simulation.

Run this overnight or for at least 12 hours > post a new V2 log collector

After posting a new V2 open administrative command prompt and copy and paste:

chkdsk /r /v

C:\WINDOWS\system32>chkdsk /r /v

The type of the file system is NTFS.

Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another

process. Would you like to schedule this volume to be

checked the next time the system restarts? (Y/N)

Type: Y

Run these chkdsk switches on all disk drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: or chkdsk /r /v E:

Run the windows drive overnight.

The other drives can run while windows in in use.

When all drives have completed chkdsk testing run:

Run:

HD Tune (free or trial version) (test all drives)

Post images or share links for results on these tabs:

a) Health

b) Benchmark

c) Full error scan

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi,

I want to follow up, is your computer encounters any BSOD?

Thank you
Sincerely,

Dyari Barham
Independent Advisor & Microsoft Community Member

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Yes, it encounters SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M on shutdown. The OS is cloned from another PC with Macrium Reflect. I will try the other steps with chkdsk, but that requires more time, and the PC to not be in use.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi DMinovski,

Thanks for updating me and mentioning the information that it is cloned from another PC. Cloning OS from one PC to another sometimes gets driver incompatibility issues since the hardware parts of both computers are different even if it is exactly the same model.

Therefore, I would suggest performing an in-place upgrade:
https://www.tenforums.com/tutorials/16397-repai...

If it did not help, you can perform a clean install as a last resort.


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

Have a nice day
____________________________________________________________
Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.
Sincerely,

Dyari Barham
Independent Advisor & Microsoft Community Member

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated November 5, 2022 Views 634 Applies to: