Page 10 of 19 FirstFirst ... 89101112 ... LastLast
  1.    2 Weeks Ago #91
    Join Date : Oct 2017
    Posts : 115
    Microsoft Windows 10 Pro 64-bit - Version 1709 - Build 16299.19
    Thread Starter



    What should I do at this point?
      My ComputerSystem Spec
  2.    2 Weeks Ago #92
    Join Date : Oct 2017
    Posts : 115
    Microsoft Windows 10 Pro 64-bit - Version 1709 - Build 16299.19
    Thread Starter

    Wait, I think I understand...

    Make sure automatic restart is unticked, then run Driver Verifier? Or was just using who crashed enough?

    Just wondering if I should restart and post Minidumps again or whether I missed a step
      My ComputerSystem Spec
  3.    2 Weeks Ago #93
    Join Date : Apr 2017
    Posts : 8,607
    windows 10 professional version 1607 build 14393.969 64 bit

    Having automatic restart un-checked will be useful for all dumps as you will have time to view the bsod windows. If there is a misbehaving driver displayed you then have the immediate analysis.

    The Whocrashed is a software tool that can be used to confirm that dumps are properly set to record with the crash dump test.

    The Whocrashed and Bluescreenview are able to perform preliminary analysis and sometimes the preliminary analysis displays the misbehaving driver. More often Windbg is needed to debug the dumps and find the misbehaving drivers.

    If you get the dead confirmation with whocrashed you then know that the dumps are configured so that they are created. Then any of the above analyzing software can be used to process the dump.

    Windows driver verifier is useful in finding misbehaving drivers and if you replace a misbehaving driver you can immediately test the replacement. Sometimes the newest driver also misbehaves and a roll back driver could end up being the most stable driver.

    So you have the option to wait and see if there are spontaneous misbehaving drivers or use Windows driver verifier to find misbehaving drivers. With your experience and prior use of Windows driver verifier it may be useful in finding other misbehaving drivers.

    If there are only WHEA 0x124 bugchecks then the removal or swap of problematic hardware could eliminate the bsod and confirm the problematic hardware. Also if the WHEA errors in the event log disappear this would add an additional confirmation to the problematic hardware.
      My ComputerSystem Spec
  4.    2 Weeks Ago #94
    Join Date : Oct 2017
    Posts : 115
    Microsoft Windows 10 Pro 64-bit - Version 1709 - Build 16299.19
    Thread Starter

    DAN-PC-Thu_11_02_2017_150810_18.zip

    Here's the latest from using WhoCrashed
      My ComputerSystem Spec
  5.    2 Weeks Ago #95
    Join Date : Oct 2017
    Posts : 115
    Microsoft Windows 10 Pro 64-bit - Version 1709 - Build 16299.19
    Thread Starter

    Click image for larger version. 

Name:	image.png 
Views:	5 
Size:	131.2 KB 
ID:	161839
      My ComputerSystem Spec
  6.    2 Weeks Ago #96
    Join Date : Nov 2015
    Posts : 2,860
    64bit Win 10 Pro ver 1709 Build 16299.64

    There is not a lot more we can do now until you run your system normally for a while and monitor what happens. The last crash was caused deliberately by you following @zbook instructions and was simply to demonstrate that your system is reacting correctly in the event of a crash.

    When (or if) you have more BSOD events then you need to post a new set of files for us to analyse.
      My ComputersSystem Spec
  7.    2 Weeks Ago #97
    Join Date : Oct 2017
    Posts : 115
    Microsoft Windows 10 Pro 64-bit - Version 1709 - Build 16299.19
    Thread Starter

    Quote Originally Posted by zbook View Post
    Having automatic restart un-checked will be useful for all dumps as you will have time to view the bsod windows. If there is a misbehaving driver displayed you then have the immediate analysis.

    The Whocrashed is a software tool that can be used to confirm that dumps are properly set to record with the crash dump test.

    The Whocrashed and Bluescreenview are able to perform preliminary analysis and sometimes the preliminary analysis displays the misbehaving driver. More often Windbg is needed to debug the dumps and find the misbehaving drivers.

    If you get the dead confirmation with whocrashed you then know that the dumps are configured so that they are created. Then any of the above analyzing software can be used to process the dump.

    Windows driver verifier is useful in finding misbehaving drivers and if you replace a misbehaving driver you can immediately test the replacement. Sometimes the newest driver also misbehaves and a roll back driver could end up being the most stable driver.

    So you have the option to wait and see if there are spontaneous misbehaving drivers or use Windows driver verifier to find misbehaving drivers. With your experience and prior use of Windows driver verifier it may be useful in finding other misbehaving drivers.

    If there are only WHEA 0x124 bugchecks then the removal or swap of problematic hardware could eliminate the bsod and confirm the problematic hardware. Also if the WHEA errors in the event log disappear this would add an additional confirmation to the problematic hardware.
    Thank you, I understood about 85% of what you were mentioning, but still have little experience actually analyzing the results of the tests.

    Would you recommend I use Driver Verifier again and if/when I get I get a BSOD, take a picture and post it?
      My ComputerSystem Spec
  8.    2 Weeks Ago #98
    Join Date : Apr 2017
    Posts : 8,607
    windows 10 professional version 1607 build 14393.969 64 bit

    The bsod window and the windbg confirmed that whocrashed is working properly. We already knew that dumps were being properly created.
    Please make sure that you don't have software settings that remove dumps:
    If you use Ccleaner > click on windows tab > scroll down to system and advanced > for system make sure that memory dumps is unchecked. Also windows error reporting and logs are sometimes useful for troubleshooting so please un-check Windows log files and Windows error reporting.

    In the left lower corner search type clean > open disk cleanup > click ok > look for system error memory dumps files and system created Windows error reporting and make sure these boxes are un-checked.

    The latest DM log collector displayed the loss of most of the mini dumps.

    For the dumps we don't need the pictures but if you find something in the whocrashed analysis or bluescreen analysis that is useful you can post that. Again we usually have more in depth analysis with Windbg but some of the common commands are not working during this Windows upgrade period.
      My ComputerSystem Spec
  9.    2 Weeks Ago #99
    Join Date : Oct 2017
    Posts : 115
    Microsoft Windows 10 Pro 64-bit - Version 1709 - Build 16299.19
    Thread Starter

    Quote Originally Posted by zbook View Post
    The bsod window and the windbg confirmed that whocrashed is working properly. We already knew that dumps were being properly created.
    Please make sure that you don't have software settings that remove dumps:
    If you use Ccleaner > click on windows tab > scroll down to system and advanced > for system make sure that memory dumps is unchecked. Also windows error reporting and logs are sometimes useful for troubleshooting so please un-check Windows log files and Windows error reporting.

    In the left lower corner search type clean > open disk cleanup > click ok > look for system error memory dumps files and system created Windows error reporting and make sure these boxes are un-checked.

    The latest DM log collector displayed the loss of most of the mini dumps.

    For the dumps we don't need the pictures but if you find something in the whocrashed analysis or bluescreen analysis that is useful you can post that. Again we usually have more in depth analysis with Windbg but some of the common commands are not working during this Windows upgrade period.
    I did run CCleaner yesterday, but none of the Windows Log or Error Reporting options were selected or used:
    Click image for larger version. 

Name:	image.png 
Views:	3 
Size:	75.4 KB 
ID:	161844

    As to Disk Cleanup options, I only have Downloaded Program Files, Temporary Internet Files, Device Driver Packages, and Thumbnails selected. I don't recall when I last used this, but it may have been right before I installed my latest Samsung SSD ... maybe a month ago?

    I'm currently running Driver Verifier with automatic restart unticked.

    I have made a backup of SOME of my Minidump files... I can add these back to the Minidump folder under C:\Windows\Minidump if that is preferable.

    Thanks,
    diznanl
      My ComputerSystem Spec
  10.    2 Weeks Ago #100
    Join Date : Oct 2017
    Posts : 115
    Microsoft Windows 10 Pro 64-bit - Version 1709 - Build 16299.19
    Thread Starter

    Click image for larger version. 

Name:	image.png 
Views:	16 
Size:	32.1 KB 
ID:	161845 Click image for larger version. 

Name:	image.png 
Views:	16 
Size:	16.0 KB 
ID:	161846Click image for larger version. 

Name:	image.png 
Views:	16 
Size:	14.1 KB 
ID:	161847
      My ComputerSystem Spec

 
Page 10 of 19 FirstFirst ... 89101112 ... LastLast


Similar Threads
Thread Forum
Random reboots
Hello, I've been having an issue with my PC randomly rebooting. I never really notice a BSOD as the computer just reboots with no apparent error but a 'memory.dmp' file is generated every time. I've done chkdsk's and also ran memtest86 numerous...
BSOD Crashes and Debugging
Random WHEA_UNCORRECTABLE_ERROR
It's been a week. Happens about 5 times already. Randomly And don't even show the BSOD, PC just crashes with a White or Dark Gray screen. I just see after PC restart in the Minidump folder: WHEA_UNCORRECTABLE_ERROR 116734
BSOD Crashes and Debugging
BSOD 0x124 WHEA_UNCORRECTABLE_ERROR
i have had this error for like a month, tested all components on the Pc and none of them seems to be failing, so i started searching so i can figured out which component is failing according to minidump file according to minidump it say...
BSOD Crashes and Debugging
Solved Random Restarts with 0x124 Dump
Hi, and thanks in advance for any and all assistance, and sorry if this turns into a long post! I have a problem that has been infuriating me for the past month or so. I was away for studies for about 5 months, and once I returned, fired up my PC...
BSOD Crashes and Debugging
Bsod 0x124 whea_uncorrectable_error. Nothing works.
First sorry for creating a duplicate post. I am insider since before the build 10240, and always tried to resolve this error by myself. I researched a lot and found this forum, which even had posts about my problem. After trying all a bit...
BSOD Crashes and Debugging
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 18:14.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums