So, I don’t really do event’s that much so I decided to start doing The Hunt event. I was trying to play Pressure but my game just kept closing on itself without messages (Like Oh no, Roblox quit because of an unexpected error). No biggie, open it back up. I did this about 15 to 16 times and then BOOM. I get a BSOD saying:
KERNAL_MODE_HEAP_CORRUPTION
By the way. It can’t be my hardware. Roblox was running fine all day playing with friends until it updated tonight. Now I’m just crashing over and over. Plus I’ve been playing Rainbow Six and it still has not crashed or BSOD.
The only Information I could find for the BSOD was in the Reliability Monitor on Windows 11. This is IN ORDER.
RobloxPlayerBeta.exe : Stopped Working
Faulting application name: RobloxPlayerBeta.exe, version: 0.664.0.21577, time stamp: 0xe3b08458
Faulting module name: RobloxPlayerBeta.exe, version: 0.664.0.21577, time stamp: 0xe3b08458
Exception code: 0xc0000409
Fault offset: 0x0000000003f21ff8
Faulting process id: 0x2A88
Faulting application start time: 0x1DB9588CAB12E5E
Faulting application path: MOVED TO STAFF-ONLY FOR PRIVACY.
Faulting module path: MOVED TO STAFF-ONLY FOR PRIVACY.
Report Id: MOVED TO STAFF-ONLY FOR PRIVACY.
Faulting package full name:
Faulting package-relative application ID:
Windows : Stopped Working
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000013a (0x0000000000000017, 0xffffe7026e100380, 0xffffe70296996720, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\031525-13328-01.dmp. Report Id: MOVED TO STAFF-ONLY FOR PRIVACY.
Windows : Windows was not properly shut down
The previous system shutdown at 3:55:47 AM on 3/15/2025 was unexpected.
I run these Specs
- Board: ROG Strix B550-F (BIOS VERSION 3611)
- CPU: Ryzen 7 3700X (Stock Clocks, Firmware installed)
- GPU: RTX 3060 (Stock Clocks, Driver Version: 572.16)
- Memory: 32GB CORSAIR Vengeance LPX (8x4)
If yall need more info just let me know.
Expected behavior
No messageless crashes (Or at least crashes with a message), no BSOD’s whatsoever.
A private message is associated with this bug report