Page 9 of 19 FirstFirst ... 7891011 ... LastLast
  1.    3 Weeks Ago #81
    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
    Were you previously using windows driver verifier?

    1) DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR: 0x139

    2) CLOCK_WATCHDOG_TIMEOUT (101)
    DEFAULT_BUCKET_ID: CODE_CORRUPTION
    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC

    3) BUGCHECK_STR: 0x124_GenuineIntel
    Yes, I did... but I wasn't sure how to verify what results came of it.

    I followed these instructions:
    Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials
      My ComputerSystem Spec
  2.    3 Weeks Ago #82
    Join Date : Oct 2017
    Posts : 115
    Microsoft Windows 10 Pro 64-bit - Version 1709 - Build 16299.19
    Thread Starter

    @zbook is there anything you can recommend I do next?


    • I hope to redo my CPU heatsink tonight or tomorrow then retry Prime95
    • I haven't been able to figure out what those mouse/keyboard yellow triangles are and not sure I will
    • I still need to reach out to Focusrite, but I'm not quite sure what to ask them now that I'm not getting BSODs (since 10/26)
    • I resolved the Windows Start Menu issue by creating a second admin account, logging out of that, then logging back into my main account and it worked just fine (as was suggested in many threads on fixing the Windows Start Menu)


    If you have other items you'd like me to address while my machine is on (need it on now for work), please let me know.

    Thanks!
      My ComputerSystem Spec
  3.    3 Weeks Ago #83
    Join Date : Apr 2017
    Posts : 8,854
    windows 10 professional version 1607 build 14393.969 64 bit

    With your recent use of Windows driver verifier you could test the Focusrite driver or wait to see if there are any bsod related problems.

    The device manager and msinfo32 indicated that there are problem devices.
    Standard PS/2 Keyboard ACPI\PNP0303\0 This device is not present, is not working properly, or does not have all its drivers installed.Microsoft PS/2 Mouse ACPI\PNP0F03\0 This device is not present, is not working properly, or does not have all its drivers installed.
    And they appear to be the device is not present.
    It's unclear with the troubleshooting steps that you have already done why the yellow triangles were not fixed.
    The CPU heat problem needs follow up and we'll await the test results.
      My ComputerSystem Spec
  4.    3 Weeks Ago #84
    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
    With your recent use of Windows driver verifier you could test the Focusrite driver or wait to see if there are any bsod related problems.

    The device manager and msinfo32 indicated that there are problem devices.
    Standard PS/2 Keyboard ACPI\PNP0303\0 This device is not present, is not working properly, or does not have all its drivers installed.Microsoft PS/2 Mouse ACPI\PNP0F03\0 This device is not present, is not working properly, or does not have all its drivers installed.
    And they appear to be the device is not present.
    It's unclear with the troubleshooting steps that you have already done why the yellow triangles were not fixed.
    The CPU heat problem needs follow up and we'll await the test results.
    Driver Verifier lead to a BSOD... it happened overnight while I was asleep. Latest dm_log_collection attached below:

    Attachment 161778

    Please have a look...! I appreciate it, again!
      My ComputerSystem Spec
  5.    3 Weeks Ago #85
    Join Date : Apr 2017
    Posts : 8,854
    windows 10 professional version 1607 build 14393.969 64 bit

    The Windbg has commands that are not working during this Windows upgrade period.
    On some BSOD the commands may work and others they don't so the more the dumps maybe there may be some useful information.
    With the commands that are working the BSOD indicated bugcheck A.
    No definitive misbehaving driver was identified.

    Download and install each:
    Blue screen of death (STOP error) information in dump files.
    http://www.resplendence.com/whocrashed

    Create a new restore point.
    If you have not already made a backup image please use Macrium and place the backup image onto another drive or into the cloud.
    Macrium Software | Macrium Reflect Free

    Turn on Windows driver verifier with the settings in this link:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    Post new zips into the thread with new BSOD:
    BSOD Crashes and Debugging - Windows 10 Forums
      My ComputerSystem Spec
  6.    3 Weeks Ago #86
    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 Windbg has commands that are not working during this Windows upgrade period.
    On some BSOD the commands may work and others they don't so the more the dumps maybe there may be some useful information.
    With the commands that are working the BSOD indicated bugcheck A.
    No definitive misbehaving driver was identified.

    Download and install each:
    Blue screen of death (STOP error) information in dump files.
    http://www.resplendence.com/whocrashed

    Create a new restore point.
    If you have not already made a backup image please use Macrium and place the backup image onto another drive or into the cloud.
    Macrium Software | Macrium Reflect Free

    Turn on Windows driver verifier with the settings in this link:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    Post new zips into the thread with new BSOD:
    BSOD Crashes and Debugging - Windows 10 Forums
    Click image for larger version. 

Name:	image.png 
Views:	1 
Size:	106.0 KB 
ID:	161826

    Running the Macrium Reflect Image backup of my C drive now.

    How would you like me to use WhoCrashed?
    I already have BlueScreenViewer available ... what can I post to show you?

    As to Driver Verifier -- I ran this last night, which is what gave me the latest Minidump. How will these differ from the ones I posted this morning?

    Thanks for explaining.
    diznanl
      My ComputerSystem Spec
  7.    3 Weeks Ago #87
    Join Date : Apr 2017
    Posts : 8,854
    windows 10 professional version 1607 build 14393.969 64 bit

    With the windbg working suboptimally during this upgrade period having these additional tools may be useful:
    1) bluescreenview
    2) whocrashed
    3) startup and recovery settings with automatic restart un-checked so that you have time to view the BSOD windows. Windows driver verifier will typically display the bugcheck driver verifier detected violation and sometimes the misbehaving driver may be displayed in the form *.sys
    In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings > on the advanced tab in startup and recovery > click settings > under system failure > un-check automatic restart
    4) For whocrashed above analyze click on tools > crash dump test > type: ACCEPT
    5) Click analyze > look for dead in the results
      My ComputerSystem Spec
  8.    3 Weeks Ago #88
    Join Date : Nov 2015
    Posts : 2,871
    64bit Win 10 Pro ver 1709 Build 16299.64

    Hi diznanl,

    I have looked at your most recent BSOD crash dump - as @zbook points out this was not a 0x124 hardware error and was not triggered by the Driver Verifier so it is pointing to something else on your system. The stack shows that there were a lot of network related activities and while it is unlikely to be the ndis.sys windows driver it could be due to the driver associated with your network card.

    Intel(R) Ethernet Connection (2) I219-V - current driver is c:\windows\system32\drivers\e1d65x64.sys (ver 12.15.23.7) dated: Tue Jul 26 17:48:21 2016

    If you can find a more recent driver either from Intel or your motherboard manufacturer I would suggest you update it.
      My ComputersSystem Spec
  9.    3 Weeks Ago #89
    Join Date : Oct 2017
    Posts : 115
    Microsoft Windows 10 Pro 64-bit - Version 1709 - Build 16299.19
    Thread Starter

    Quote Originally Posted by philc43 View Post
    Hi diznanl,

    I have looked at your most recent BSOD crash dump - as @zbook points out this was not a 0x124 hardware error and was not triggered by the Driver Verifier so it is pointing to something else on your system. The stack shows that there were a lot of network related activities and while it is unlikely to be the ndis.sys windows driver it could be due to the driver associated with your network card.

    Intel(R) Ethernet Connection (2) I219-V - current driver is c:\windows\system32\drivers\e1d65x64.sys (ver 12.15.23.7) dated: Tue Jul 26 17:48:21 2016

    If you can find a more recent driver either from Intel or your motherboard manufacturer I would suggest you update it.
    Thanks... I found this driver on Intel's website and installed it:
    Download Intel® Network Adapter Driver for Windows® 10

    Click image for larger version. 

Name:	image.png 
Views:	17 
Size:	104.1 KB 
ID:	161830
      My ComputerSystem Spec
  10.    3 Weeks Ago #90
    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
    With the windbg working suboptimally during this upgrade period having these additional tools may be useful:
    1) bluescreenview
    2) whocrashed
    3) startup and recovery settings with automatic restart un-checked so that you have time to view the BSOD windows. Windows driver verifier will typically display the bugcheck driver verifier detected violation and sometimes the misbehaving driver may be displayed in the form *.sys
    In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings > on the advanced tab in startup and recovery > click settings > under system failure > un-check automatic restart
    4) For whocrashed above analyze click on tools > crash dump test > type: ACCEPT
    5) Click analyze > look for dead in the results
    Backup Complete:
    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	45.5 KB 
ID:	161831

    I'll now go through the steps mentioned:

    • startup and recovery settings with automatic restart un-checked so that you have time to view the BSOD windows.....
    • In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings > on the advanced tab in startup and recovery > click settings > under system failure > un-check automatic restart
    • For whocrashed above analyze click on tools > crash dump test > type: ACCEPT
    • Click analyze > look for dead in the results
      My ComputerSystem Spec

 
Page 9 of 19 FirstFirst ... 7891011 ... 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 19:20.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums