Share via

Random BSOD errors (Kernel Mode Heap Corruption etc)

Anonymous
2024-06-10T10:37:16+00:00

Hello,

I've been getting a lot of BSODs lately, and most of them are kernel-related (some of the errors are KERNEL_MODE_HEAP_CORRUPTION).
I'm not sure what to do, as I've already tried resetting Windows with a clean install.
Also, I've noticed that most of the errors happen when I'm playing a game, like Forza Horizon 5, even though the last one was while in the desktop.
Is there anyone that can help me?
This is the zip file with all the dumps in C:\Windows\minidumps
Zip file

Thank you

Windows for home | Windows 11 | 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 No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2024-06-10T11:11:52+00:00

    Hi, I am Dave, I will help you with this.

    Your minidump files just indicate memory (RAM) corruption no specific driver is listed

    To try to force Windows 11 show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

    Before you run Driver Verifier, please create a new System Restore Point

    https://answers.microsoft.com/en-us/windows/for...


    Note, if you have any difficulty getting into Windows with Driver Verifier enabled:

    Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

    Do this twice

    On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

    Go to Troubleshoot - Advanced Option - Startup Settings and click Restart

    Upon restart, press 4 to enter Safe Mode

    Open Command Prompt as Administrator and run these two commands, then restart your PC.

    verifier /reset

    verifier /bootmode resetonbootfail

    Was this answer helpful?

    0 comments No comments