F5F Stay Refreshed Software Operating Systems Error occurred when attempting to generate crash dumps; system failed to start BSOD recovery.

Error occurred when attempting to generate crash dumps; system failed to start BSOD recovery.

Error occurred when attempting to generate crash dumps; system failed to start BSOD recovery.

M
M3xURxHUNTER
Junior Member
Find
14
07-31-2021, 11:00 PM
#1
This situation is really taxing on my mental energy. The main issue is this: My computer frequently freezes, a blue screen appears, yet it always ends up at 0% Completed, regardless of the dump type I use—whether Kernel Memory Dump, Complete Memory Dump, or Active Memory Dump. Even after a quick restart following the BSOD for a brief moment, it often restarts again. That’s why I have to manually turn it off (there’s a small reset button on my case). Occasionally, after pressing that button, the PC will power down completely before coming back online, with fans slowing and lights dimming before resuming. Once Windows loads normally, the Event Viewer shows a dump creation failure with error ID 161.

In some instances, if I press the reset button, the system shuts down entirely, then restarts without a full crash (you can spot this by the fans stopping and lights fading briefly before coming back). Usually it works fine afterward.

I’ve also tried overclocking, and there were a few BSODs linked to that. When I enabled XMP profiles during CPU overclocking, most crashes stopped, except when playing demanding games like Black Ops 4 with poorly optimized settings. My pagefile is set to an unusually large 64GB.

I’m asking why? To rule out a Pagefile problem. So I experienced another BSOD: the IRQL_UNEXPECTED_VALUE error pointed to ndis.sys, possibly a Windows network driver issue. It’s unclear if that was resolved. The crash dump creation problem still remains.

I’ve swapped out my motherboard several times—first from the old Gigabyte Z97 Gaming 3, then to MSI Z97 Gaming 5, and finally to an 8TB HDD (which turned out to be SMR). I’m now using a Samsung Evo 860 1TB SSD with the latest firmware. Still, nothing changed much.

Crash dumps are important because they can reveal unknown causes for the BSODs. This issue has been ongoing since my PC was built. My specs include an Intel Core i7 4790K (4.8GHz), GTX 1080 G1, 32GB RAM, and a MSI Z97 Gaming 5 motherboard with AeroCool X99. I’m using a 1000W PSU and have tried various diagnostics: SFC/Scannow, CHKDSK, DISM, BIOS reset to default, changing dump types, adjusting pagefile size, and even triggering a BSOD intentionally with WhoCrashed. Nothing seems to fix the problem.
Reply
Reply
M
M3xURxHUNTER
07-31-2021, 11:00 PM #1

This situation is really taxing on my mental energy. The main issue is this: My computer frequently freezes, a blue screen appears, yet it always ends up at 0% Completed, regardless of the dump type I use—whether Kernel Memory Dump, Complete Memory Dump, or Active Memory Dump. Even after a quick restart following the BSOD for a brief moment, it often restarts again. That’s why I have to manually turn it off (there’s a small reset button on my case). Occasionally, after pressing that button, the PC will power down completely before coming back online, with fans slowing and lights dimming before resuming. Once Windows loads normally, the Event Viewer shows a dump creation failure with error ID 161.

In some instances, if I press the reset button, the system shuts down entirely, then restarts without a full crash (you can spot this by the fans stopping and lights fading briefly before coming back). Usually it works fine afterward.

I’ve also tried overclocking, and there were a few BSODs linked to that. When I enabled XMP profiles during CPU overclocking, most crashes stopped, except when playing demanding games like Black Ops 4 with poorly optimized settings. My pagefile is set to an unusually large 64GB.

I’m asking why? To rule out a Pagefile problem. So I experienced another BSOD: the IRQL_UNEXPECTED_VALUE error pointed to ndis.sys, possibly a Windows network driver issue. It’s unclear if that was resolved. The crash dump creation problem still remains.

I’ve swapped out my motherboard several times—first from the old Gigabyte Z97 Gaming 3, then to MSI Z97 Gaming 5, and finally to an 8TB HDD (which turned out to be SMR). I’m now using a Samsung Evo 860 1TB SSD with the latest firmware. Still, nothing changed much.

Crash dumps are important because they can reveal unknown causes for the BSODs. This issue has been ongoing since my PC was built. My specs include an Intel Core i7 4790K (4.8GHz), GTX 1080 G1, 32GB RAM, and a MSI Z97 Gaming 5 motherboard with AeroCool X99. I’m using a 1000W PSU and have tried various diagnostics: SFC/Scannow, CHKDSK, DISM, BIOS reset to default, changing dump types, adjusting pagefile size, and even triggering a BSOD intentionally with WhoCrashed. Nothing seems to fix the problem.

Reply
Reply