Windows 10: Log Collector Fails

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>

 

DESKTOP-3B05JDE (10-11-2017 11 22 PM).zip

 

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.

 

This is the MEMORY.DMP file on my computer

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

 

This memory dump is from the test that @zbook asked you to run, which has now overwritten the one we wanted. As we really need a memory dump that was triggered by a genuine BSOD crash, please post a new file when your system next crashes.

 

I had another BSOD, but according to event viewer, "Dump file creation failed due to error during dump creation."

 

Your pagefile may be too small to allow the active memory dump. Try setting it to a kernel memory dump instead.

 

The memory dump works when I initiate a crash through WhoCrashed, and the BSOD shows percentage values for completion. When the computer actually BSODs, the BSOD just disappears at 0% and the computer tries to reboot on its own, and gets stuck at the Dell Logo until I manually reboot.

 

These were in the very first event log from post #5:

Dump file creation failed due to error during dump creation.

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.

In the left lower corner search type: system > on the left pane click advanced system settings >
> performance click settings > click advance tab > post an image into the thread
> startup and recovery click settings > post an image into the thread.

 

Did you try setting it to Kernel memory dump like I suggested? It is still shown as Active memory dump in your screen shot.