Windows 10: Log Collector Fails Solved

Page 3 of 4 FirstFirst 1234 LastLast
  1.    11 Oct 2017 #21
      My ComputerSystem Spec

  2. philc43's Avatar
    Posts : 3,561
    64bit Win 10 Pro ver 1803 Build 17134.285 and W10 Insider Build 18234
       12 Oct 2017 #22

    jeffsun13 said: View Post
    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.
      My ComputersSystem Spec

  3.    12 Oct 2017 #23

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

  4. philc43's Avatar
    Posts : 3,561
    64bit Win 10 Pro ver 1803 Build 17134.285 and W10 Insider Build 18234
       12 Oct 2017 #24

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

  5.    12 Oct 2017 #25

    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.
      My ComputerSystem Spec


  6. Posts : 20,131
    windows 10 professional version 1607 build 14393.969 64 bit
       12 Oct 2017 #26

    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.
      My ComputerSystem Spec

  7.    12 Oct 2017 #27

    Click image for larger version. 

Name:	Capture.PNG 
Views:	3 
Size:	23.2 KB 
ID:	157721Click image for larger version. 

Name:	Capture2.PNG 
Views:	3 
Size:	25.6 KB 
ID:	157722
      My ComputerSystem Spec

  8. philc43's Avatar
    Posts : 3,561
    64bit Win 10 Pro ver 1803 Build 17134.285 and W10 Insider Build 18234
       12 Oct 2017 #28

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


  9. Posts : 20,131
    windows 10 professional version 1607 build 14393.969 64 bit
       12 Oct 2017 #29

    For the virtual memory on the above image click change > post an image into the thread then click cancel.

    Please un-check automatically restart.
    Change active memory dump to kernal memory dump.
    Then reboot.

    In the past 24 hours what has been the frequency of bsod?
    How many crashes were there without bsod?

    Open device manager > click view > click show hidden devices > expand all that display a yellow icon > for any that have a yellow triangle with a black exclamation or for any listing that displays unknown please post images into the thread.


    BSOD Finding and fixing them - Microsoft Community
      My ComputerSystem Spec

  10.    12 Oct 2017 #30

    Click image for larger version. 

Name:	Capture.PNG 
Views:	2 
Size:	24.4 KB 
ID:	157725There have been 2 BSODs in the past 24 hours, no crashes without BSOD
      My ComputerSystem Spec


 
Page 3 of 4 FirstFirst 1234 LastLast

Related Threads
Solved Cannot run DM log Collector Tool in BSOD Crashes and Debugging
Hi I have had a BSOD and want to run the DM Log Collector tool as instructed in the BSOD forum, so I can post on that forum, however when I try to run the tool I get this message "This app can't run on your PC. (see attached Picture) Any ideas...
Disk usage spikes to 100% all the time with only FF browser open - and even with nothing open. Already disabled Windows Search and Superfetch. Resource Monitor shows "WPR_Initiated_DiagTrackAotLogger_WPR System Collector.etl" using 900K B/Sec: ...
Not cause by virus .. this just started today. I tried a restore point of yesterday .. nothing. I have tried several suggestions from the web but nothing seems to do it? I know it would be better if i could name them but can't remember the exact...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 12:15.
Find Us