What is causing my computer to BSOD at random times?

Anonymous
2024-12-06T20:22:37+00:00

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

Windows for home | Windows 10 | Performance and system failures

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.

0 comments

84 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-12-09T10:42:22+00:00

    Hello Alex,

    The CRITICAL_STRUCTURE_CORRUPTION crash is related. In the first three crashes, it seems that preparations for patching the routine ndisOidPreAddWakeUpPattern failed; the reason for the failure was an attempt to clear the "Write Protect" bit in CR0 when the "Control-flow Enforcement Technology" bit in CR4 is set.

    In the fourth crash, the routine ndisOidPreAddWakeUpPattern has been modified and this modification has been detected by PatchGuard (Windows Kernel Patch Protection).

    There is not enough information in the minidumps for me to make any further progress. Did you change any settings between the first 3 crashes and the fourth crash?

    Gary

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-12-06T22:18:40+00:00

    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

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-12-06T22:09:45+00:00

    Hi Gary,

    There were no matches in any of the system files in those directories.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-12-06T21:59:12+00:00

    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

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-12-06T21:32:07+00:00

    Hi Gary,

    Thank you for your help. If there's any more information I can provide you please let me know.

    Was this answer helpful?

    0 comments