Need Help - Make sense of my Dumpfile - KMODE_EXCEPTION_NOT_HANDLED - Random crashes

Hi everyone,

I’m experiencing random crashes on my computer with the error “KMODE_EXCEPTION_NOT_HANDLED.” Sometimes I can work all day without issues, but if I leave my computer idle, it restarts unexpectedly (example). I’ve analyzed the dump file using Microsoft’s recommended tool (WinDBG), but I don’t fully understand what to look for.

I have a high-performance PC that I rely on for work, and while I can still use it, these crashes are concerning, especially in terms of potential data loss. I’d appreciate any help in diagnosing the issue. I have been using this computer for a year now.

I have already done some tests:

  • Disabled Fast Startup

  • Run the memory diagnostic tool (no error

  • Disabled Antivirus Bitdefender

  • Checked corrupted files with command lines

Thanks in advance!

DUMPFILE (text)

Processor Intel(R) Core(TM) i9-14900K 3.20 GHz

Installed RAM 128 GB (128 GB usable)

Graphic Nvidia 4090 TUF 24GB

System type 64-bit operating system, x64-based processor

|

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hello,


The minidump you provided lead to ntkrnlmp.exe, which is part of the Windows kernel. This means that some other driver caused the BSOD. I would recommend running Driver Verifier to find the misbehaving driver.

Before launching Driver Verifier, create a Restore Point in case your PC might not be able to boot from Windows, and you can restore to a point before using Driver Verifier. To create a Restore Point, go to the Start Menu and type Restore Point and then click the entry that says, "Create a Restore Point".

Once you have created a Restore Point, go to the Start Menu and type verifier. If you are asked to allow the app to make changes to your device, click yes. In the window that pops up, asking you to select a few options, select "Create custom settings (for code developers)" and then select Next. Then, in the list of checkboxes, select "I/O Verification", "Force pending I/O requests", and "IRP Logging" and push Next.

Then, when asked to select which drivers to verify, click the heading "Provider" and select all non-Microsoft provided drivers, and then push OK and when asked to restart your PC, restart your PC.

Once your PC restarts, Driver Verifier will stress the drivers that you selected before in the background and cause the PC to crash and BSOD. If you see a degradation in performance, that’s normal.

Once you feel that you have had enough BSODs, or it has been more than 48 hours since you enabled Driver Verifier, take all of the minidumps and then upload it to Google Drive/OneDrive/Dropbox, and then turn off Driver Verifier by opening verifier from the Start Menu and then select "Delete existing settings".

Let me know how this goes.

Airbus A350 (Random_One0113's alt)

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.

Thanks a lot!

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.

I forgot to ask:

"take all of the minidumps and then upload it to Google Drive/OneDrive/Dropbox"

Does it mean you will have another look at the minidumps?

Thanks again.

Cheers,

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.

Hello,

Yes, I am trying to take a look at the minidumps again, since it seems as though you are missing some symbols for WinDbg.

This also makes it easier on my side since I can inspect the root cause better.

Hope to hear back from you.

Airbus A350 (Random_One0113's alt)

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 reaching out. My name is Bernard, a Windows fan like you. I'll be happy to help you out today, my timezone is UTC +8.

I understand the issue you have, there is nothing to worry I am here to assist, can you further check if you have more Minidump files on the PC? As per checking the Minidump logs, it is only displaying general errors, in addition, can you please check the System logs on the PC so that I can further examine the root cause of the issue?

To do this kindly follow the steps from this link:
https://www.yourwindowsguide.com/2017/12/how-to...

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

Then please upload it by following the steps from the link.


Let me know how it goes and I hope that helps.

Bernard

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.

I forgot to ask:

"take all of the minidumps and then upload it to Google Drive/OneDrive/Dropbox"

Does it mean you will have another look at the minidumps?

Thanks again.

Cheers,

So,

I did what you told me and I could not even log into windows but I was able to restore the box to an older point. I had 3 crashes between my previous reply and now. You were right. It looks like a driver issue but I can't tell which one.

Here is the dump file:

minidump

Let me know if that's enough crashes.

Thanks

Cheers,

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.

Ok it looks like a Blackmagic design IO issue.

"SYMBOL_NAME: BlackmagicIO+57f01 MODULE_NAME: BlackmagicIO IMAGE_NAME: BlackmagicIO.sys STACK_COMMAND: .cxr 0xffff8f802814e0e0 ; kb BUCKET_ID_FUNC_OFFSET: 57f01 FAILURE_BUCKET_ID: 0x7E_80000003_VRF_BlackmagicIO!unknown_function OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release"

I will uninstall/install the latest driver.

Let me know what you think.

Cheers,

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

It looks like we've pinpoint the issue.

See other replies.

Thank you very much.

Cheers,

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, thank you for your response. You are correct. Upon reviewing the new DMP file, it indicates an error with BlackmagicIO.sys. I recommend uninstalling the Blackmagic DeckLink driver, then monitoring the PC to see if the issue persists.

Since you have already completed all the previous steps, I hope this resolves the issue. If not, please try removing or uninstalling the driver without reinstalling it, and continue to observe the device.

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, thank you for your response. You are correct. Upon reviewing the new DMP file, it indicates an error with BlackmagicIO.sys. I recommend uninstalling the Blackmagic DeckLink driver, then monitoring the PC to see if the issue persists.

Since you have already completed all the previous steps, I hope this resolves the issue. If not, please try removing or uninstalling the driver without reinstalling it, and continue to observe the device.

Hey Bernard,

I've tried to uninstall/reinstall the driver but it crashes again while I was away from the computer. This driver should not be used when I am not working (display video on a external monitor). I'll try to uninstall it and see how it goes.

Thanks.

Kind regards,

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 April 18, 2025 Views 43 Applies to: