Windows 10: Unexpected BSOD - Clean Install of W10 - BSOD's still Reoccurring.

Page 2 of 2 FirstFirst 12

  1. Posts : 14,238
    windows 10 professional version 1607 build 14393.969 64 bit
       3 Weeks Ago #11

    1) For startup and recovery > un-check automatically restart
    2) When disk cleanup is opened click ok on one of the drives that is not C: then scroll up and down and post images of the checked and un-checked boxes.
    3) Download and install: Whocrashed:
    http://www.resplendence.com/whocrashed
    4) Open Whocrashed:
    5) Above analyze click on tools > click crash dump test > type: ACCEPT
    6) Click analyze > post the result into the thread
    7) Run this version of the zip after the above steps and post a new zip into the thread:
    log collector v2-beta08.zip
      My ComputerSystem Spec


  2. Posts : 14,238
    windows 10 professional version 1607 build 14393.969 64 bit
       3 Weeks Ago #12

    The debugging of 2 mini dumps did not display a definitive misbehaving driver.
    Bugchecks were 1A and 50.

    1) open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /restorehealth
    4) chkdsk /scan
    5) 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
    6) Backup all files to another drive or to the cloud
    7) Make a backup image using Macrium:
    Macrium Software | Macrium Reflect Free
    8) Place the backup image onto another drive or into the cloud
    9) Make a brand new restore point
    10) Windows driver verifier is a tool which stimulates drivers and misbehaving will repetitively produce BSOD until they are fixed or until the tool is turned off.
    When using the tool you must know the 3 methods to turn off the tool so that you can return to the desktop and fix the misbehaving driver. Then restart the tool and fix the next misbehaving driver. Replacement drivers can be reinstalled either as soon as drivers are unistalled or after all misbehaving drivers have been uninstalled. The end result should be the same.

    To turn off windows driver verifier all of the methods are done using the windows advanced troubleshooting menu.
    1) startup options (not startup repair) > click restart > select #6 safe mode with command prompt > type:
    verifier /reset
    2) command prompt > Administrator: X:\windows\system32\cmd.exe > X:\Sources >
    type: verifier /bootmode resetonbootfail
    3) system restore
    The methods to turn off windows driver verifier should be done in order and only if the prior method failed. When system restore is used the mini dump is often lost and little progress is made in the troubleshooting.

    When using windows driver verifier it sometimes can be hard to boot or the computer can be sluggish.
    If this becomes problematic the test settings can be changed.
    The tool will be used for approximately 48 hours.
    After the last BSOD the tool will be used for an additional 36 hours of typical computer use.
    If there are no more BSOD the tool will be turned off the this troubleshooting step will be completed.

    Use this link for the test settings:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    Use this link for the methods to turn off Windows driver verifier:
    Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials



    Code:
    Event[733]:  Log Name: System  Source: Microsoft-Windows-USB-USBXHCI  Date: 2018-01-22T23:21:39.471  Event ID: 14  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-IBP1DSC  Description: Windows failed to start the USB xHCI Compliant Host Controller for the following reason:Controller reset timed out. Check with your computer manufacturer for an updated firmware for the controller.
    Code:
    Event[2190]:  Log Name: System  Source: Microsoft-Windows-DNS-Client  Date: 2018-01-29T22:26:52.629  Event ID: 1012  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-20  User Name: NT AUTHORITY\NETWORK SERVICE  Computer: Haylee  Description: There was an error while attempting to read the local hosts file.
    Code:
    23/01/2018 08:13    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1a
    P2: 41201
    P3: fffff7000f851158
    P4: 80000001fabf1967
    P5: ffffb9848f978880
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\012318-10468-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-19109-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER567D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER568E.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER568F.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_aeec92f336c616645e811ecdd63a4ea23ee2dbb6_00000000_cab_02b8569b
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 2c224843-12a7-4ed8-af86-b6092a327d67
    Report Status: 4
    Hashed bucket:27/01/2018 13:52    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1a
    P2: 41792
    P3: ffff8900000903f0
    P4: 1000000
    P5: 0
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\012718-13015-02.dmp
    \\?\C:\WINDOWS\TEMP\WER-20000-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER605F.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER607F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER608F.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_b9aef515f6df179e34ff1f1e8fbc5c2bd53f78bb_00000000_cab_02c0608e
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 6a3a2e99-25fb-44f1-aaad-c6b1216eae8d
    Report Status: 4
    Hashed bucket:27/01/2018 13:04    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 50
    P2: ffffa1816299bec0
    P3: 0
    P4: fffff800ed155593
    P5: 2
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\012718-12828-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-19546-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C4C.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C4F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C5F.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_ee3ba3758980fbbc1ee1ed344d3b3b173ea2068_00000000_cab_02bc5c68
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 728bfee3-cd52-4d73-94da-df7012139668
    Report Status: 4
    Hashed bucket:
    Code:
    23/01/2018 08:13    Windows Error Reporting    Fault bucket 0x1a_41201_nt!MiGetPageProtection, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 5880fa83-d199-46dc-9cca-7823e6ff376e
    
    Problem signature:
    P1: 1a
    P2: 41201
    P3: fffff7000f851158
    P4: 80000001fabf1967
    P5: ffffb9848f978880
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\012318-10468-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-19109-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER567D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER568E.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER568F.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_aeec92f336c616645e811ecdd63a4ea23ee2dbb6_00000000_cab_1834783d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 2c224843-12a7-4ed8-af86-b6092a327d67
    Report Status: 268435456
    Hashed bucket:
    Code:
    27/01/2018 13:04    Windows Error Reporting    Fault bucket AV_R_INVALID_nt!ObWaitForMultipleObjects, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 570bdccf-f141-4822-bad8-96a0eccbfbc7
    
    Problem signature:
    P1: 50
    P2: ffffa1816299bec0
    P3: 0
    P4: fffff800ed155593
    P5: 2
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\012718-12828-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-19546-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C4C.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C4F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C5F.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_ee3ba3758980fbbc1ee1ed344d3b3b173ea2068_00000000_cab_1b848e26
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 728bfee3-cd52-4d73-94da-df7012139668
    Report Status: 268435456
    Hashed bucket:27/01/2018 13:52    Windows Error Reporting    Fault bucket MEMORY_CORRUPTION_ONE_BIT, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: ad621068-78d3-4ec9-8e1a-129563b14f07
    
    Problem signature:
    P1: 1a
    P2: 41792
    P3: ffff8900000903f0
    P4: 1000000
    P5: 0
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\012718-13015-02.dmp
    \\?\C:\WINDOWS\TEMP\WER-20000-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER605F.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER607F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER608F.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_b9aef515f6df179e34ff1f1e8fbc5c2bd53f78bb_00000000_cab_1cf8bf77
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 6a3a2e99-25fb-44f1-aaad-c6b1216eae8d
    Report Status: 268435456
    Hashed bucket:
      My ComputerSystem Spec


 
Page 2 of 2 FirstFirst 12

Related Threads
can't boot windows after reoccurring bsod's in BSOD Crashes and Debugging
So I have a laptop (windows 10) and it was having performance problems, specifically 100% disk usage all the time. I tried everything to fix it but nothing worked. I then later started to get bsod all the time which I assume is related. About a week...
BSOD during clean install in BSOD Crashes and Debugging
Quick backstory: Had Windows 10 Pro running since it came out with relatively few problems. I decided it was time for a graphics upgrade so I threw in an EVGA GeForce 1060. Nvidia decided I needed new drivers and it has been all downhill since...
hey! i got a Lenovo yoga 3 pro 1370 with core -m CPU, Liteon L8H-256v2g SSD after a clean windows 10 -genuine installation, UEFI. i installed it cause there where BSODs before and though it may be because of corrupted file system. now i think its...
Multiple BSOD after clean install in BSOD Crashes and Debugging
Good afternoon, I started having a few BSOD crashes last month and after exhaustive attempts to solve this issue myself with no progress I did a clean install of windows 10. The issue remains, however, it is less frequent now. 86921
bsod win 10 clean install , old dell in BSOD Crashes and Debugging
hello, hope someone can help. upgraded a vista machine to win7, then updated to win10, then clean installed win 10. worked ok for a few days but now bsod every 20 minutes or so. I get watchdog violation. have updated bios and NVidia drivers plus...
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 15:53.
Find Us