Just for test, would you mind try boot into Clean boot and see if you are observing this behavior?
Have a look at How to perform a clean boot in Windows - Microsoft Support.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have a custom built gaming PC that has recently been blue screening randomly and it seems completely unprompted. It happens when I'm in the middle of a game, or when I'm working on a Word document with Spotify playing, or when I'm browsing google chrome with nothing else open. I don't know what could be causing it.
The error I get is always "KMODE_EXCEPTION_NOT_HANDLED"
I recently had an issue where my computer would BSOD with the same error every time I woke it up from sleep mode. I got a warranty replacement for my RAM and that fixed that issue. These BSODs seem to be caused by something else. This also means that I find it highly unlikely that there's something wrong with my RAM.
Here is a link to the dump files I've gathered so far. I will add more as my computer continues to crash. It happens once every few hours, it seems.
https://drive.google.com/drive/folders/1_QM2imGRMNnQtNsdU8W98a16JUMTyj0d?usp=sharing
Does anybody know what could be causing this issue? Do the dump files point to anything specifically that could be causing the crashes?
Thank you
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Just for test, would you mind try boot into Clean boot and see if you are observing this behavior?
Have a look at How to perform a clean boot in Windows - Microsoft Support.
Interesting. I have an update for you as well. Just a few minutes ago I was working on google chrome with music playing and got a BSOD, with a different error message this time. This time it was "CRITICAL_STRUCTURE_CORRUPTION". It also said "What failed: ndis.sys" below that.
I added the dump file this crash created to the same folder that the other 3 files are in, linked at the beginning of this thread. Maybe that will provide us with more information?
Thank you again for all your help.
Hello Alex,
Thanks. That might be good news or it might be bad news. If the code does originate from one of those .sys files but is obfuscated (not stored in plain text), then that would be rather suspicious...
Gary
Hi Gary,
There were no matches in any of the system files in those directories.
Hello Alex,
You could try the following three commands and let me know if any matches are found:
findstr /m E3.M..I..D9 \Windows\System32\*.sys
findstr /s /m E3.M..I..D9 \Windows\System32\drivers\*.sys
findstr /s /m E3.M..I..D9 \Windows\System32\DriverStore\FileRepository\*.sys
E3.M..I..D9 is a pattern in the mystery instruction sequence. That sequence is not present on my system, so there should not be too many false positives.
Gary