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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2025-01-07T09:58:04+00:00

    Uhoh. That isn't good. A hyper-V error.

    A hyper-V memory error essentially. That is really not good.

    You have the latest bios update? and the latest chipset drivers?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-01-07T10:24:13+00:00

    This really now looks like a solid hardware defect on RAM, or RAM misconfiguration on mainboard. It could also be the CPU, and third, the mainboard. The most likely is the RAM, not placed in the exact right combination proposed by the mainboard manual, or a defect.

    @edit: it can also happen naturally under extreme stress but must never happen when not under heavy stress.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-01-07T10:27:40+00:00

    This is not a BSOD due to software fault... it is a BSOD due to hardware fault.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-01-07T11:14:58+00:00

    Hello All,

    My laptop CPU does not support Intel Control-flow Enforcement Technology (CET) - I don't know what percentage of CPUs currently in use support this feature. Security in depth is a "good thing", but stopping malware being deployed to a system is always the better option. Since I sleep well without CET, I am not reluctant to suggest disabling it as a work-around for irritating problems.

    I think that the Windows kernel naming prefix "Hv" refers to routines related to "hives" (where registry information is stored); I believe that "Hvl" (Hypervisor Library?) is the prefix used for hypervisor related functions.

    There are a few hits when searching for crashes where an exception occurs in the routine HvpGetCellPaged (as is the case for the 1st January crash) but, as usual, there is no information about the cause. I would regard the crash as "unexplained" and not necessarily hardware related.

    Gary

    Was this answer helpful?

    0 comments
  5. Anonymous
    2025-01-07T17:31:52+00:00

    Hi all,
    yeah, Gary is right. I thought it was a hyper-v and missed the p :D, but it's a registry-related function. And I should have seen that the process was Registry. So, unexplained crash. Not necessarily a hardware fault. Good that Gary was paying attention. That's why it's better to have multiple persons looking it over. :-)

    Was this answer helpful?

    0 comments