Windows 10: 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!

You seem to have plenty of space on drive c:\ so there is no need to have the dump files written elsewhere.

Can you verify that you do not have automatically restart selected in the event of a system failure (see below). If possible try to capture a photo of the blue screen next time it happens to record if there are any drivers indicated as the cause.

I've disabled automatic restart now, to see what happens. I actually just had a BSOD this evening with UNEXPECTED_STORE_EXCEPTION, but the progress indicator stayed at 0% for several minutes and eventually I just had to push the button myself. I have also seen CRITICAL_PROCESS_DIED. Neither type of error has any further detail on the screen. Just in case, I have reset the dump location to %SystemRoot%\MEMORY.DMP but it's now a waiting game for another crash to happen.

OK, when that happens just post a new set of logfiles and I'd recommend that you use the beta08 version of the logfile collector which is provided at the end of the BSOD posting instructions. Extract the files from the beta08 zip and then run the log collector and upload the folder that is eventually created on your desktop.

OK, I've had a repeat occurrence. I used the beta08 tool this time and have attached the results as JUPITER (2018-02-20 18 14).zip.

In case any hints can be gleaned from circumstance, the crash was UNEXPECTED_STORE_EXCEPTION. I was playing World of Warcraft and the WoW process froze, but everything else was responding as normal. About 5-10 seconds later I got the blue screen, again with no dump file.

There were 3 BSOD between 2/9/18 and 2/20/18 however all of the BSOD failed to create dump files.
Dump files are needed for the debugging.
The greater the number of dump files available the more the debugging that can be performed to find the causes of the BSOD.
The causes of BSOD could be misbehaving hardware or software drivers or malfunctioning hardware.

The logs displayed problems with low virtual memory and errors during dump creation.


Perform the following steps:

1) open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
6) In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings >
a) under performance click settings > on performance options click the advanced tab > under virtual memory click change > post an image into the thread of the virtual memory windows
b) under startup and recovery > click settings > post an image of the startup and recovery window into the thread
7) Download and install Whocrashed:
http://www.resplendence.com/whocrashed

Code:

Event[796]:  Log Name: System  Source: Microsoft-Windows-Resource-Exhaustion-Detector  Date: 2018-02-03T02:26:31.046  Event ID: 2004  Task: Resource Exhaustion Diagnosis Events  Level: Warning  Opcode: Contains the results of the diagnosis.  Keyword: Events related to exhaustion of system commit limit (virtual memory).  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: jupiter  Description: Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: StarCitizen.exe (10028) consumed 20535189504 bytes, chrome.exe (6272) consumed 489816064 bytes, and chrome.exe (528) consumed 273821696 bytes.

Code:

Event[2430]:  Log Name: System  Source: volmgr  Date: 2018-02-20T18:10:47.616  Event ID: 161  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: jupiter  Description: Dump file creation failed due to error during dump creation.

The command prompt output is at Microsoft Windows [Version 10.0.16299.248] (c) 2017 Microsoft Corporation. All - Pastebin.com. Requested images are https://puu.sh/zCIpW/f647ec48ab.png and https://puu.sh/zCIrt/23a209df93.png. I did a NVMe driver update and actually haven't had a BSoD since then, though it's not been long enough to be confident that the problem has gone. Many thanks for any insight you can glean from these pics/outputs.