Kernel mode heap corruption

[AI_Princess]

was playing siege and suddenly had a BSOD and it showed the reason KERNAL_MODE_HEAP_CORRUPTION.

what does it mean? ive checked online it's says to update the drivers but all of my drivers are up-to-date.

After that BSOD, PC started normally. And was playing like before. This is the first time ive seen this while playing R6.

[crunchyfrog]

Well as a general rule BSODs are hardware related. As it hasn't reutned yet, all you can really do is keep an eye on it.

If it doesn't happen again, then it's probably just a blip. It can happen.

But if it happens more take note of when and where it happened - note as many details as you can, as far as what game, when, how long you've been playing, temperatures, etc.

[AI_Princess]

Originally posted by crunchyfrog:

Well as a general rule BSODs are hardware related. As it hasn't reutned yet, all you can really do is keep an eye on it.

If it doesn't happen again, then it's probably just a blip. It can happen.

But if it happens more take note of when and where it happened - note as many details as you can, as far as what game, when, how long you've been playing, temperatures, etc.

I'll be keeping an eye on it. As far as temps go, everything is under 60c. Checked using the event viewer and it showed one warning bout low on virtual memory, R6S and Spotify were using a lot of it.

Idk why I'd be having that issue cuz I've 16GB ram. And never saw ram uses over 11GB.

[crunchyfrog]

Originally posted by ANAアナ:

Originally posted by crunchyfrog:

Well as a general rule BSODs are hardware related. As it hasn't reutned yet, all you can really do is keep an eye on it.

If it doesn't happen again, then it's probably just a blip. It can happen.

But if it happens more take note of when and where it happened - note as many details as you can, as far as what game, when, how long you've been playing, temperatures, etc.

I'll be keeping an eye on it. As far as temps go, everything is under 60c. Checked using the event viewer and it showed one warning bout low on virtual memory, R6S and Spotify were using a lot of it.

Idk why I'd be having that issue cuz I've 16GB ram. And never saw ram uses over 11GB.

Virtual memory is NOT RAM. Virtual memory is disk space, that's why it's called "virtual". It's really a kind of cache for stuff that doesn't need immediate recall (and doesn't need to sit in RAM) but needs it enough to be regular.

So you can try adjusting your Virtual memory in Windows. Normally it does it automatically so it may have already adjusted. And as you point out, if you have lots of things open that can cause these issues.

[AI_Princess]

Originally posted by crunchyfrog:

Originally posted by ANAアナ:

I'll be keeping an eye on it. As far as temps go, everything is under 60c. Checked using the event viewer and it showed one warning bout low on virtual memory, R6S and Spotify were using a lot of it.

Idk why I'd be having that issue cuz I've 16GB ram. And never saw ram uses over 11GB.

Virtual memory is NOT RAM. Virtual memory is disk space, that's why it's called "virtual". It's really a kind of cache for stuff that doesn't need immediate recall (and doesn't need to sit in RAM) but needs it enough to be regular.

So you can try adjusting your Virtual memory in Windows. Normally it does it automatically so it may have already adjusted. And as you point out, if you have lots of things open that can cause these issues.

It's set to 2.9GB as default, virtual memory. I was kinda worried today when I saw that error, though might have some prob with my 1650 but I've checked everything and everything seems to be working just fine. Thanks for the info tho.

[Carlsberg]

Update all your drivers, (consider a bios update first).

Update Chipset first, reboot then sound, usb, network and any others you may need. after final reboot update/reinstall gpu. Get the drivers from whoever makes your machine or mainboard, do not rely on windows for them because you may not get the correct ones just a microsoft generic.

Then make sure windows is fully updated. Note; google how to prevent windows from updating your drivers and disable it because win update will replace them with microsoft ones and put you right back where you are now.

[AI_Princess]

Originally posted by Carlsberg:

Update all your drivers, (consider a bios update first).

Update Chipset first, reboot then sound, usb, network and any others you may need. after final reboot update/reinstall gpu. Get the drivers from whoever makes your machine or mainboard, do not rely on windows for them because you may not get the correct ones just a microsoft generic.

Then make sure windows is fully updated. Note; google how to prevent windows from updating your drivers and disable it because win update will replace them with microsoft ones and put you right back where you are now.

All of those above mentioned things are done also as I stated above, everything is up to date. And for bios, my mobo doesn't have a new bios, it's a 7th gen board. I've the latest bios to that point. But thanks.

[Elucidator]

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x13a--kernel-mode-heap-corruption
here it says what it means

do you want tips on how to fix it?

[AI_Princess]

Originally posted by Elucidator:

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x13a--kernel-mode-heap-corruption
here it says what it means

do you want tips on how to fix it?

I read the article but idk really. Cuz after the BSOD the pc started normally, didn't do any repair attempt or something like that.

[Elucidator]

I recommend looking at the dmp file or the minidump file at least, figure out what exactly triggered it.
Like others said, usually updating helps (drivers included)
there is a link in that article that takes you to microsoft's official BSOD troubleshoot page for users, which can resolve most common issues, but to be honest this specific bsod in't common.

edit: (you can use bluescreenview or windbg to analyse bsod errors. windbg gives most info)

[AI_Princess]

Originally posted by Elucidator:

I recommend looking at the dmp file or the minidump file at least, figure out what exactly triggered it.
Like others said, usually updating helps (drivers included)
there is a link in that article that takes you to microsoft's official BSOD troubleshoot page for users, which can resolve most common issues, but to be honest this specific bsod in't common.

edit: (you can use bluescreenview or windbg to analyse bsod errors. windbg gives most info)

Thanks for the info. Sadly there's no dmp file generated. I'll DDU and reinstall the Nvidia drivers.

[Crashed]

More than likely it was a hardware related glitch causing one of the memory structures in the Windows kernel to get corrupted. Try running Windows Memory Diagnostic to check for issues with your memory.

[AI_Princess]

Originally posted by Crashed:

More than likely it was a hardware related glitch causing one of the memory structures in the Windows kernel to get corrupted. Try running Windows Memory Diagnostic to check for issues with your memory.

Ok, I've done a test. Filling up my RAM, so when it gets near 15.8GB, the system shuts off and reset. Although I didn't see any error. Maybe this is a one off. And according to the diagnostic, nothing seems to be wrong. Although i recall my Ram acts weird sometimes when I set it 3000bus with XMP. Prolly that's what causing it. I should set it back to 2666.

[Crashed]

Originally posted by ANAアナ:

Originally posted by Crashed:

More than likely it was a hardware related glitch causing one of the memory structures in the Windows kernel to get corrupted. Try running Windows Memory Diagnostic to check for issues with your memory.

Ok, I've done a test. Filling up my RAM, so when it gets near 15.8GB, the system shuts off and reset. Although I didn't see any error. Maybe this is a one off. And according to the diagnostic, nothing seems to be wrong. Although i recall my Ram acts weird sometimes when I set it 3000bus with XMP. Prolly that's what causing it. I should set it back to 2666.

Windows Memory Diagnostic is a low-level check, and there is also MemTest86+ however the current release requires CSM to be turned on, though there is a version in development that will support UEFI.

[AI_Princess]

Originally posted by Crashed:

Originally posted by ANAアナ:

Ok, I've done a test. Filling up my RAM, so when it gets near 15.8GB, the system shuts off and reset. Although I didn't see any error. Maybe this is a one off. And according to the diagnostic, nothing seems to be wrong. Although i recall my Ram acts weird sometimes when I set it 3000bus with XMP. Prolly that's what causing it. I should set it back to 2666.

Windows Memory Diagnostic is a low-level check, and there is also MemTest86+ however the current release requires CSM to be turned on, though there is a version in development that will support UEFI.

Gotcha