Windows 10: BSOD : Dump file creation failed due to error during dump creation.

[COLOR=rgba0, 0, 0, 1]Hello All,[/COLOR]


[COLOR=rgba0, 0, 0, 1]BSOD I got this errorcontinuously. Even when I post this I got two time. I try all solution which Ifind in Google. [/COLOR]

[COLOR=rgba0, 0, 0, 1]I run command like “sfc /scannow” I did disc check.[/COLOR]

also this DISM[COLOR=rgba32, 33, 36, 1] /[/COLOR]Online[COLOR=rgba32, 33, 36, 1] /[/COLOR]Cleanup[COLOR=rgba32, 33, 36, 1]-[/COLOR]Image[COLOR=rgba32, 33, 36, 1] /[/COLOR]RestoreHealth[COLOR=rgba32, 33, 36, 1].[/COLOR]

[COLOR=rgba0, 0, 0, 1]I don’t have any cleaningsoftware like ‘ccleaner’.[/COLOR]


[COLOR=rgba0, 0, 0, 1]I did reset my PC from “local”as well as “cloud download and reinstall windows” option. But cloud downloadoption not working for me after download, When system reset show some error“Something went wrong” and cancel this reset and then I must try localreinstall.[/COLOR]

[COLOR=rgba0, 0, 0, 1] [/COLOR]

When I search “*.dmp” in my system nothing i found











Please check this link

System information link : https://1drv.ms/u/s!AqezH_HBtc3GiBQf0AJKnj6mbBR4?e=ndgzUJ

Windows system log : https://1drv.ms/u/s!AqezH_HBtc3GiBK8bI48C8XYGqlW?e=YRETo7

windows Application log : https://1drv.ms/u/s!AqezH_HBtc3GiBMYi27AwubPDEE7?e=4KFfjj


please help me fix this problem

:)

 

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.

 

Windows is not following the setting for the dump file location!

I chose "Small memory dump (256KB). The next BSOD had the same result (no dump files).
As it has happened some times (but not always), the BSOD froze at 100% and I had to press reset to reboot the pc.

Why is Windows trying to create a dump file on K instead of %SystemRoot%?

- - - Updated - - -

I caused a MANUALLY_INITIATED_CRASH, the system rebooted by itself but again no dump files.
But now Event Viewer does NOT contain the event "Dump file creation failed due to error during dump creation".

- - - Updated - - -

I disconnected the drive with the K partition, caused a MANUALLY_INITIATED_CRASH and the result was the same.

- - - Updated - - -

I just got a new BSOD. The Event Viewer shows the following (event "Dump file creation failed due to error during dump creation."), despite the fact that there is no Volume 9 anymore (since I disconnected the drive)!
\Device\HarddiskVolume9
000000000100000000000000A10004C063000000010000C000000000000000000000000000000000

- - - Updated - - -

I disabled Avira's real time protection, caused a MANUALLY_INITIATED_CRASH and a small memory dump was successfully created! I will wait for a real BSOD to see real results.

- - - Updated - - -

I tried with kernel memory dump. I uninstalled Avira, caused a MANUALLY_INITIATED_CRASH and a kernel memory dump was successfully created! Still waiting for a real BSOD.