Kernel mode heap corruption error on startup

[uhCrypto]

Hello, I was wondering if anyone could assist me with this issue then I have been getting on my gaming desktop.

I bought this computer from HP in November 2025

Over the past few weeks, on most start-ups, I have been receiving a black screen of death before I get to the lock screen of my computer.

It gets to the windows loading screen and then freezes and black screen of death appears saying 'KERNEL_MODE_HEAP_CORRUPTION' with either '0x013' or '0x015' appearing next to it.

It then automatically restarts my computer and then usually the screen appears again and then it performs Windows Automatic repair which results in windows saying the computer couldn't be repaired.

I have tried various ways of trying to fix it (not in order as shown), see below;

1. Using DDU to completely reinstall all graphic drivers on the computer (nvidia and integrated)
2. Completely reinstalling windows and wiping all data on both disks.
3. Running verifier - this came back with an error with a realtek audio driver which made me do the next one.
4. Using DDU to remove realtek audio drivers.
5. Use HP Support Assistant to update drivers
6. Use HP PC Hardware Diagnostics Windows 3.0.0.0 and performed every test available on there. (all passed)
7. Windows memory test (passed)
8. BIOS update
9. Running the following commands: 

sfc /scannow​

chkdsk /f /r
DISM /Online /Cleanup-image /Scanhealth

Anyone else got any idea of what could be the issue and how I could fix it or does this look like something I would have to send the computer to HP to look at themselves?

Many thanks!

[Bill_To]

Greetings @uhCrypto 

That BSOD is usually caused by:

1. memory corruption

2. Corrupted drivers

3. Hardware

It looks like your troubleshooting has isolated a possible Realtek audio problem. You have uninstalled/reinstalled the audio drivers but the problem persists.

Remove the Realtek audio drivers again. Then try disabling Realtek audio in the BIOS to see what happens.

The Realtek audio chipset may have a problem requiring a MB replacement.

You could also run MemTest86 (free) to double check system memory.

Regards