Log Collector Fails

I would say Critical Process Died definitely makes up most of the BSODs, although I get Unexpected Store Exception once in a while and I think I've seen one other statement. I've never used Bluetooth on this computer, so I have no idea about that.
I've called in to Dell Support a number of times, but they just always run the same tests and the computer passes everything, so they request that I send it in.

Most of the BSODs show Critical Process Died, but I also get Unexpected Store Exception and I think I've seen one other one. I have never used Bluetooth before on this computer, so I cannot tell.

Edit: Thought first message didn't get posted

The critical process died was seen within the logs.

Open administrative command prompt and type or copy and paste:
1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) chkdsk /scan
4) 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

4) msconfig (in the pop up system configuration > move the dot from normal startup to selective startup > uncheck load startup items > click service tab > in left lower corner check hide all Microsoft services > in the lower right side click disable all > click apply or ok > do not reboot)


5) taskmgr (in the pop up task manager > click on the start up tab > click on status so that the column sorts with enable rising to the top > right click on each row with enable and change to disable)

https://support.microsoft.com/en-us/...oot-in-windows

How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

6) shutdown /r (you will reboot the computer so that it is in clean boot)

When you have completed all of the above commands please run the log collector again and post a new zip into the thread.


There have been numerous crash dump failures:

Code:

Event[4996]:  Log Name: System
  Source: volmgr
  Date: 2017-10-09T08:53:10.789
  Event ID: 161
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-3B05JDE
  Description: 
Dump file creation failed due to error during dump creation.

Code:

Event[5495]:  Log Name: System
  Source: volmgr
  Date: 2017-10-10T13:16:47.463
  Event ID: 49
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-3B05JDE
  Description: 
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.

If your computer blue screens again, upload another set of logs, and also compress and upload C:\Windows\memory.dmp to dropbox/google drive/onedrive and post a link here.

Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\Windows\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\Windows\system32>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 709632 file records processed.File verification completed. 7442 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 831302 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.Stage 3: Examining security descriptors ...Security descriptor verification completed. 60836 data files processed.CHKDSK is verifying Usn Journal... 39888808 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 124454911 KB total disk space. 64531636 KB in 604290 files. 303204 KB in 60837 indexes. 0 KB in bad sectors. 821511 KB in use by the system. 65536 KB occupied by the log file. 58798560 KB available on disk. 4096 bytes in each allocation unit. 31113727 total allocation units on disk. 14699640 allocation units available on disk.C:\Windows\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\Windows\system32>

Attachment 157612

In post #10 there was a link on updating the startup and recovery settings:
Configure Windows 10 to Create Minidump on BSOD BSOD Tutorials

Once you have made changes please check to see that you are able to create and analyze dumps using Whocrashed:
Above analyze click tools > crash dump test > type: ACCEPT
Click analyze > view results for dead
Create another zip and see if there is a new mini dump in the zip

Should I set it to small dump or active dump, which someone said earlier in the thread because there wasn't enough info in the minidumps

Start with active and make sure you can create a dump using Whocrashed.
If Whocrased is able to analyze a dump then check to see that a mini dump has been collected by the zip.
Then post a memory dump:
memory dump file: %SystemRoot%\MEMORY.DMP or C:\Windows\MEMORY.DMP

Use file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.

As in post #14 use one drive or drop box to post a share link into the thread.

Minidumps are created alongside the larger memory.dmp when you generate an Active, Full, or Kernel crash dump. I'd suggest you use an Active dump.