Windows 10: Getting "Dump file creation failed due to error during dump creation." error along with...

Hi All,I am running Windows 10 version 20H2 and the OS build is 19042.1415. For the past couple of weeks my system is facing blue screen error and rebooting repeatedly. The Event viewer provides the "Dump file creation failed due to error during dump creation." error before a Critical error of The system has rebooted without cleanly shutting down first. I have followed various posts to deal with the BSOD but none helped. Recently did a fresh Windows install with formatting the drives. But the issue is still persistent. Any help would be really appreciate

:)

 

Hard Locks and BSODs on boot (with no dumps)

The question is why the dumps are not written. Since the OS was reinstalled a few times, I dont think its an OS problem. In most cases different bugcheck codes point to hardware problems.

The windows eventlog is showing that the dumps cannot be written:
Code:

Because the system cannot write dumps at crash time, it could be also possible that there is an problem with disk, disk controller or controller drivers.

1)
There is an Firmware Update from Dell exactly for you Notebook model and SSD model:
Toshiba THNSN5256GPUK/THNSN5512GPUK/THNSN51T02DUK non-SED Solid State Drive Firmware Update | Dell US

2)
Check if there are firmware updates for your Toshiba SSD:
https://ssd.toshiba-memory.com/downl...70_Windows.zip

 

Hard Locks and BSODs on boot (with no dumps)

Yeah, I've seen that a lot. Unfortunately, the hardware tests I've tried don't surface anything useful:

- FutureMark full suite (do all the things, make it hot, make it sweaty)
- Memtest (went 26 cycles without issue)
- PowerShell to write massive 100GB files to the disk in a row within Windows, delete, repeat several times (something like 10TB in total over a couple hours). Nothing. While not the best idea to burn down the SSD like that with writes, I had to rule it out.

If I knew what I could stress to make it fall over, I'd have a much easier time with Dell because it's under warranty with their "Pro" (LOL) support package; if I tell them "I found evidence X is bad," I send them my evidence and they send me a box. That was how I got the SSD replaced–I used event logs that complained about not being able to write to the disk.

Since it can't write the dump, I keep pondering if I could hook it up and have it in debug mode, if it crashes on boot, I might be successful in catching the crash on another system. Problem is, my "other system" would be a MacBook Pro running Windows in Bootcamp. (don't judge; I haven't been a Windows user myself for years).

If there's any other sorts of tests I can run that'll press the pedal down or replicate whatever the heck is happening (besides just restarting it a ton of times), I'm all ears.

Update: Ironically, it crashed on the desktop to a BSOD (CRITICAL_PROCESS_DIED) right after boot.

 

Intermittent BSODs with no dump file created

My PC has had occasional blue screens for several months. Each time one happens, no dump file is created even though I have configured Windows to do so. The event log contains a volmgr error at the time of the blue screen, with text "Dump file creation failed due to error during dump creation." The EventData for this is:\Device\HarddiskVolume8 000000000100000000000000A10004C042000400010000C000000000000000000000000000000000Some investigation shows that HarddiskVolume8 is my C: drive (Samsung 950 PRO NVMe). I actually have the dump file configured to write to a different drive, but this doesn't seem to make a difference. Does this suggest that the C: drive is physically on its way out? The Samsung analysis tool doesn't find any errors with the drive data, but I suppose that I might just have got unlucky and it's going bad before its time. If this is indicative of any other error condition I'd like to hear about it too!