Random BSOD only on first start.


  1. Posts : 2
    Windows 10 Pro
       #1

    Random BSOD only on first start.


    Hi, I have been having this BSOD problem for about 6 months. The BSOD only happens the 1st start and when it gives me the error the bsod code is different every time. Playing games makes the bsod happen quicker usually around 10-20 min. But the thing is once i restart it, it doesn't happen for the rest of the day. But the next morning it's the same process. p.s I have checked all the drivers.
      My Computer


  2. Posts : 41,462
    windows 10 professional version 1607 build 14393.969 64 bit
       #2

    Hi Durply

    Welcome to Ten Forums BSOD forum.

    The log files indicated corruption of the drive file system and a misbehaving hardware driver.
    There was only 1 BSOD mini dump file.

    For the tests /steps please post images into the thread.
    If there are problem posting images please use one drive or drop box share links.

    1) open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /restorehealth
    4) 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
    5) chkdsk /x /f /r
    This may take many hours so plan to run overnight.
    6) Use the information in this link to find the chkdsk report in the event viewer then copy and paste the report into the thread:
    Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials
    7) In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings > under startup and recovery click settings > post an image into the thread
    8) backup all files to another drive or to the cloud
    8) create a backup image using Macrium:
    Macrium Software | Macrium Reflect Free
    9) Place the backup image onto another drive or into the cloud
    10) read this information on windows driver verifier:

    Use this link for the test settings:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
    Use this link to learn the 3 methods to turn off windows driver verifier:
    Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

    Code:
    Event[1342]:  Log Name: System  Source: Volsnap  Date: 2017-12-30T12:45:45.445  Event ID: 30  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-9IK74FA  Description: An unfinished create of a shadow copy of volume C: was deleted.
    Code:
    Event[1223]:  Log Name: System  Source: Ntfs  Date: 2017-12-29T12:38:30.829  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: N/A  User Name: N/A  Computer: DESKTOP-9IK74FA  Description: A corruption was discovered in the file system structure on volume C:.The exact nature of the corruption is unknown.  The file system structures need to be scanned online.
    Code:
    12/27/2017 3:40 AM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 139
    P2: 0
    P3: 0
    P4: 0
    P5: 1401000000000000
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\122617-19296-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-38656-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE213.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE2CE.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE2DF.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_a9b99b9b7ba20adee723efdd99216adadbd4fd4_00000000_cab_0328e2de
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 51d0329f-ee40-4caf-93c3-94f324ff76d0
    Report Status: 4
    Hashed bucket:1/2/2018 5:15 AM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1a
    P2: 41201
    P3: ffffeb80d2493030
    P4: 81000001ebe10047
    P5: ffff9d0fd23ea7d0
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010118-23890-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-55406-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC128.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC166.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC177.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_6d06e55b499cb22a3a99e6e5b3845c9978b981_00000000_cab_033dc176
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 86b56d61-0ad1-4c18-bcbe-1f83c69af69f
    Report Status: 4
    Hashed bucket:1/2/2018 9:38 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1a
    P2: 41792
    P3: fffff980fcf43390
    P4: 1c7400000004
    P5: 0
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010218-20953-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-44781-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F75.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FB3.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FC4.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_a5e1be79f097fb121c9dfdbff3353b24b2bf8a6_00000000_cab_03393fd3
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 4f272ce8-ea12-4cc9-a1d1-8b9a0196dbda
    Report Status: 4
    Hashed bucket:12/30/2017 8:52 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1e
    P2: ffffffffc0000005
    P3: fffff802c6ea1b04
    P4: ffffc20d037aee68
    P5: ffffc20d037ae6b0
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\123017-23781-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-398125-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F16.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F54.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F74.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_dffd372b24534549be182d3eb09c43148167d9_00000000_cab_033e7f73
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 3f518ed7-b962-49e9-ab3c-c8a1dc975086
    Report Status: 4
    Hashed bucket:1/4/2018 1:46 AM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1e
    P2: ffffffffc0000005
    P3: fffff80ec274ae6a
    P4: 0
    P5: ffffffffffffffff
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010318-25453-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-40640-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER41F5.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4234.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4245.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_dbba2b6d45de285dc74bb84d9893e7e1affc732_00000000_cab_033d4263
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: dcd53604-53d4-4866-a77e-296731f11af1
    Report Status: 4
    Hashed bucket:1/3/2018 7:21 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 3b
    P2: c0000005
    P3: fffff809e9980b5b
    P4: ffff9282f3f88730
    P5: 0
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010318-22203-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-43921-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREBD7.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREC15.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREC16.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_df93f4c88457a55896a6237b804ac785f597832_00000000_cab_0344ec25
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: b6b81a3b-1eb9-4bed-a6ee-80beb12f1b2a
    Report Status: 4
    Hashed bucket:12/27/2017 3:10 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: a
    P2: 319a8
    P3: 2
    P4: 0
    P5: fffff80230ab2cfb
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\122717-21015-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-42484-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER79DE.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B07.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B37.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_a32aab697a4442f95cf3a5bc41eb42fa3b1631d_00000000_cab_03297b45
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: c091f298-1c8a-446c-9f95-ddb3513e8664
    Report Status: 4
    Hashed bucket:12/27/2017 10:42 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: d1
    P2: b2
    P3: 2
    P4: 0
    P5: fffff80c72bd0ef5
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\122717-20859-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-134984-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4982.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A4D.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A5E.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_aaeaf8791d3d3ec283aac58f4ebad25690a4aa1a_00000000_cab_03324a6d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 3df28220-9009-4353-9a05-ec3b3d93eaa4
    Report Status: 4
    Hashed bucket:12/27/2017 11:03 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: f7
    P2: 63bcdcba2732
    P3: 63bcdcba0f32
    P4: ffff9c432345f0cd
    P5: 0
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\122717-19156-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-66875-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5985.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A7F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A9F.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_f7_13cfa2bec0922165ac88141896f55dedb1e1818b_00000000_cab_03355a9e
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: ee22b2cf-b292-49c6-876c-ede4a1fd4369
    Report Status: 4
    Hashed bucket:12/27/2017 3:11 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: f6eac91f-496e-4dc9-a1ae-c30474285b6a
    
    Problem signature:
    P1: a
    P2: 319a8
    P3: 2
    P4: 0
    P5: fffff80230ab2cfb
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\122717-21015-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-42484-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER79DE.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B07.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B37.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_a32aab697a4442f95cf3a5bc41eb42fa3b1631d_00000000_cab_03297b45
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: c091f298-1c8a-446c-9f95-ddb3513e8664
    Report Status: 4
    Hashed bucket:
    Code:
    12/27/2017 3:40 AM    Windows Error Reporting    Fault bucket 0x139_0_LEGACY_GS_VIOLATION_nt!_guard_icall_bugcheck, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: aa970af9-93b4-48b5-afd7-070914fc6e1f
    
    Problem signature:
    P1: 139
    P2: 0
    P3: 0
    P4: 0
    P5: 1401000000000000
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\122617-19296-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-38656-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE213.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE2CE.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE2DF.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_a9b99b9b7ba20adee723efdd99216adadbd4fd4_00000000_cab_13b90460
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 51d0329f-ee40-4caf-93c3-94f324ff76d0
    Report Status: 268435456
    Hashed bucket:1/2/2018 5:15 AM    Windows Error Reporting    Fault bucket 0x1a_41201_nt!MiGetPageProtection, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 7f0929ce-3767-4946-840e-b381943b2992
    
    Problem signature:
    P1: 1a
    P2: 41201
    P3: ffffeb80d2493030
    P4: 81000001ebe10047
    P5: ffff9d0fd23ea7d0
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010118-23890-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-55406-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC128.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC166.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC177.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_6d06e55b499cb22a3a99e6e5b3845c9978b981_00000000_cab_20aa0833
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 86b56d61-0ad1-4c18-bcbe-1f83c69af69f
    Report Status: 268435456
    Hashed bucket:1/2/2018 9:46 PM    Windows Error Reporting    Fault bucket 0x1a_41792_nt!MiDeleteVirtualAddresses, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 8e5c8c41-65b2-466c-a446-ef17eade16d9
    
    Problem signature:
    P1: 1a
    P2: 41792
    P3: fffff980fcf43390
    P4: 1c7400000004
    P5: 0
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010218-20953-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-44781-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F75.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FB3.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FC4.tmp.txt
    \\?\C:\Windows\Temp\WER6EC3.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_a5e1be79f097fb121c9dfdbff3353b24b2bf8a6_00000000_cab_20f8409c
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 4f272ce8-ea12-4cc9-a1d1-8b9a0196dbda
    Report Status: 268435456
    Hashed bucket:12/30/2017 9:00 PM    Windows Error Reporting    Fault bucket 0x1E_c0000005_ntfs!NtfsCoherencyFlushAndPurgeCache, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 58cc6d3e-7911-41d7-b523-505374623bc0
    
    Problem signature:
    P1: 1e
    P2: ffffffffc0000005
    P3: fffff802c6ea1b04
    P4: ffffc20d037aee68
    P5: ffffc20d037ae6b0
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\123017-23781-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-398125-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F16.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F54.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F74.tmp.txt
    \\?\C:\Windows\Temp\WERB672.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_dffd372b24534549be182d3eb09c43148167d9_00000000_cab_18e9db6c
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 3f518ed7-b962-49e9-ab3c-c8a1dc975086
    Report Status: 268435456
    Hashed bucket:1/4/2018 1:46 AM    Windows Error Reporting    Fault bucket 0x1E_c0000005_R_ntfs!NtfsFindPrefix, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: a0e64e61-e6d6-43db-9d6b-55c84f715e5b
    
    Problem signature:
    P1: 1e
    P2: ffffffffc0000005
    P3: fffff80ec274ae6a
    P4: 0
    P5: ffffffffffffffff
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010318-25453-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-40640-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER41F5.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4234.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4245.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_dbba2b6d45de285dc74bb84d9893e7e1affc732_00000000_cab_1e7987e8
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: dcd53604-53d4-4866-a77e-296731f11af1
    Report Status: 268435456
    Hashed bucket:1/3/2018 7:28 PM    Windows Error Reporting    Fault bucket 0x3B_nvlddmkm!_deleteFixup, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: efe651c5-4296-4e69-bae9-f998ceacc257
    
    Problem signature:
    P1: 3b
    P2: c0000005
    P3: fffff809e9980b5b
    P4: ffff9282f3f88730
    P5: 0
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010318-22203-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-43921-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREBD7.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREC15.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREC16.tmp.txt
    \\?\C:\Windows\Temp\WER24AA.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_df93f4c88457a55896a6237b804ac785f597832_00000000_cab_157f8e15
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: b6b81a3b-1eb9-4bed-a6ee-80beb12f1b2a
    Report Status: 268435456
    Hashed bucket:12/27/2017 11:05 PM    Windows Error Reporting    Fault bucket 0xF7_TWO_BIT_nt!KiSwapThread, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 981c3137-e566-46f3-b9b3-bbcbe34f3076
    
    Problem signature:
    P1: f7
    P2: 63bcdcba2732
    P3: 63bcdcba0f32
    P4: ffff9c432345f0cd
    P5: 0
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\122717-19156-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-66875-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5985.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A7F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A9F.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_f7_13cfa2bec0922165ac88141896f55dedb1e1818b_00000000_cab_0938d6d8
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: ee22b2cf-b292-49c6-876c-ede4a1fd4369
    Report Status: 268435456
    Hashed bucket:

    Code:
    12/27/2017 10:58 PM    Windows Error Reporting    Fault bucket AV_afd!AfdIndicatePollEvent, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: a7fa6ac6-233f-4822-bece-4cf04666b9aa
    
    Problem signature:
    P1: d1
    P2: b2
    P3: 2
    P4: 0
    P5: fffff80c72bd0ef5
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\122717-20859-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-134984-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4982.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A4D.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A5E.tmp.txt
    \\?\C:\Windows\Temp\WERD821.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_aaeaf8791d3d3ec283aac58f4ebad25690a4aa1a_00000000_cab_083edfe3
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 3df28220-9009-4353-9a05-ec3b3d93eaa4
    Report Status: 268435456
    Hashed bucket:12/27/2017 3:16 PM    Windows Error Reporting    Fault bucket AV_nt!MiResolveMappedFileFault, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: f6eac91f-496e-4dc9-a1ae-c30474285b6a
    
    Problem signature:
    P1: a
    P2: 319a8
    P3: 2
    P4: 0
    P5: fffff80230ab2cfb
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\122717-21015-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-42484-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER79DE.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B07.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B37.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_a32aab697a4442f95cf3a5bc41eb42fa3b1631d_00000000_cab_1096c41d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: c091f298-1c8a-446c-9f95-ddb3513e8664
    Report Status: 268435460
    Hashed bucket:
      My Computer


  3. Posts : 2
    Windows 10 Pro
    Thread Starter
       #3

    I will do this all tonight and get back to you tomorrow with everything @zbook .
    ​Thanks for the help!
      My Computer


  4. Posts : 41,462
    windows 10 professional version 1607 build 14393.969 64 bit
       #4

    To turn off windows driver verifier you must be comfortable with the windows advanced troubleshooting menu and make a brand new restore point.
    The menu can be opened by these steps:
    1) open administrative command prompt and type or copy and paste: shutdown /r /o /f /t 00
    The menu will open when the computer reboots.
    2) click the left lower corner windows icon
    3) click the power button
    4) hold down the shift key
    5) click restart while holding down the shift key
    The computer should boot to the windows advanced troubleshooting menu.

    The methods to turn off Windows driver verifier should be done in sequence and only if the prior method fails to turn off the tool.
    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
    Using system restore typically leads to a loss of the BSOD dump file and little progress is made in the troubleshooting.

    Please do not use Windows driver verifier until it is communicated in the thread.
    And please be sure that you create a brand new restore point before using the tool.

    The tool will be used for 48 hours. After the last BSOD the tool will be used for an additional 36 hours with typical computer use. While windows verifier is running the computer may become sluggish.

    After the 36 hours of no BSOD the windows driver verifier troubleshooting will be completed.

    After each BSOD please post a new zip into the thread for troubleshooting.

    As misbehaving drivers are found they will be updated, uninstalled and reinstalled or uninstalled.
      My Computer


 

  Related Discussions
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 20:31.
Find Us




Windows 10 Forums