Windows 10: BSOD when I try and run sfc/scannow

Discus and support BSOD when I try and run sfc/scannow in Windows 10 BSOD Crashes and Debugging to solve the problem; Great. The major problems were found and there are no more BSOD. See if you can complete all of the steps in post #2 so that you have tested the... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by zbook, Apr 5, 2018.

  1. zbook New Member

    BSOD when I try and run sfc/scannow


    Great.
    The major problems were found and there are no more BSOD.
    See if you can complete all of the steps in post #2 so that you have tested the other computer components.
    When replacing RAM always use pairs of matching SKU.
    This website is useful for finding RAM replacement options as it has a system scanner:
    Crucial System Scanner | Crucial.com
    Let us know if you need any help in the future.
     
    zbook, Apr 5, 2018
    #1
  2. jag213 Win User

    I have had this computer for over 5 years now and its been relatively issue free in that time (different comp. from one in my specs). However over the past couple weeks Ive been getting BSOD with increasing frequency.

    I tried running driver verifier to see if its a outdated driver and after enabling it a driver for Intel HD 3000 graphics triggered a BSOD. I then disabled the intel graphics since I have a standalone graphics card and ran driver verfier again.

    The next time I got a BSOD from npf.sys and from googling it said to run sfc/scannow. However, I am finding my computer blue screens during the scannow process and have hit a snag.

    :)
     
    jag213, Apr 21, 2018
    #2
  3. Wilson T Win User
    Run CCleaner and sfc /scannow?

    Can System File Checker preform registry scan?
     
    Wilson T, Apr 21, 2018
    #3
  4. Wilson T Win User

    BSOD when I try and run sfc/scannow

    Run CCleaner and sfc /scannow?

    I think there are some spyware in my system.

    Does Microsoft recommends Malwarebytes Anti-Malware?
     
    Wilson T, Apr 21, 2018
    #4
  5. zbook New Member
    Hi jag213,

    Welcome to the the Ten Forums BSOD forum.

    For all tests/steps please post images into the thread.
    If there are any problems posting images please use one drive or drop box share links.
    Share OneDrive files and folders - Office Support
    Upload photos and files to OneDrive - OneDrive
    Share OneDrive files and folders - Office Support
    Upload photos and files to OneDrive - OneDrive

    There were 5 BSOD mini dump files collected with bugchecks:
    C4
    BE
    1A

    The logs also displayed bugchecks:
    109
    1C7
    4E
    A

    1) The logs displayed RAM with differing SKU. How long have you been using RAM with differing manufacturers and part numbers?

    2) Run the BETA log collector on the bottom of this web page and post a zip into this thread:
    (extract > open)
    BSOD - Posting Instructions - Windows 10 Forums
    In case there are problems running the beta log collector use the text and images in post #5 in this link:
    DM Log tool problem Solved - Windows 10 Forums

    3) For any new BSOD please use the beta log collector > post a zip into the newest post. And post a new zipped memory dump into the thread.

    4) Open file explorer > this PC > C: > in the right upper corner search for: C:\windows\memory.dmp > zip > post a one drive or drop box share link into this thread

    5) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

    6) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
    b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

    7) Open administrative command prompt and type or copy and paste:
    a) powercfg.exe /hibernate off
    b) chkdsk /x /f /r
    This may take many hours so plan to run overnight
    Run chkdsk /x /f /r on all partitions/drives using the syntax: chkdsk /x /f /r C: or chkdsk /x /f /r D: (change the drive letter to the applicable partition/drive)

    C:\Windows\system32>chkdsk /x /f /r
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot

    8) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste > notepad > post a one drive or drop box share link into the thread.
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Tutorials

    9) Run HD Tune (free edition) on all disks/drives
    HD Tune website
    Post images into the thread for the test results on these tabs:
    a) Health (SMART)
    b) Benchmark
    c) Full error scan

    10) Run memtest86+ version 5.01 for at least 8 passes. Memtest86+ - Advanced Memory Diagnostic Tool
    This may take hours so plan to run it overnight.
    a) Please make sure you use the Memtest86+ version 5.01 with the link below.
    Memtest86+ - Advanced Memory Diagnostic Tool
    The testing is done not by time but by passes.
    The more passes the better.
    There are a significant number of false negatives if fewer than 8 passes are made.
    A false negative is a test pass when there is malfunctioning RAM.
    There is 12 GB of RAM on the computer.
    Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
    Just 1 error is a fail and you can abort testing.
    Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
    b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
    Memory problems. - Microsoft Community
    MemTest86+ - Test RAM Windows 10 Tutorials

    11) Make sure that there is no over clocking while troubleshooting.


    12) Sometimes there are problems in the bios that produce bsod.
    13) To ensure that there are no improper bios settings please reset the bios.
    14) Sometimes there can be failure to boot after resetting the bios.
    15) Backup the computer files to another drive or to the cloud.
    16) Make a backup image using Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Macrium Reflect Free


    17) And please create a brand new restore point.


    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computers CMOS to Reset BIOS Settings
    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow

    18) The BIOS: BIOS Version/Date American Megatrends Inc. P1.30, 11/22/2011 SMBIOS Version 2.7
    Upgrade the BIOS: 1.3 > 2,3
    ASRock > Z68 Extreme3 Gen3






    Code: Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64 ROOT\NET\0000 This device is disabled.[/quote] Code: Intel(R) HD Graphics 3000 PCI\VEN_8086&DEV_0112&SUBSYS_01121849&REV_09\3&11583659&0&10 This device is disabled.[/quote] Code: 3/7/2018 4:47 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 109 P2: a3a012db39cfa548 P3: b3b71f618c50aa13 P4: fffff80a720526a0 P5: 1 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\030718-13828-01.dmp \\?\C:\WINDOWS\TEMP\WER-16218-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BEB.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BFA.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C2A.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_109_68d1a437f40597725407e88f85b3dac812474b9_00000000_cab_02c05c29 Analysis symbol: Rechecking for solution: 0 Report Id: 8852d6d2-b043-4f8e-a4a7-6edb31bf378f Report Status: 4 Hashed bucket:4/21/2018 4:47 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1a P2: 403 P3: fffff400e575eb48 P4: 800000002603a967 P5: fffff400e5765148 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\042118-29125-01.dmp \\?\C:\WINDOWS\TEMP\WER-31781-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA076.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA0A5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA0B5.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_e99db48e734377a4816877d443242c8885850b9_00000000_cab_02c4a0c4 Analysis symbol: Rechecking for solution: 0 Report Id: 8ff7b8e3-8528-43bb-bfe5-c10f21a08d32 Report Status: 4 Hashed bucket: 4/19/2018 2:22 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1a P2: 404 P3: ffffff520fe38b48 P4: 8a0000002a483863 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\041818-12593-01.dmp \\?\C:\WINDOWS\TEMP\WER-15281-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A64.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A83.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A94.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_7220466050edf571399c7f3f17abd949a198f7b_00000000_cab_02cc5a93 Analysis symbol: Rechecking for solution: 0 Report Id: 073c0869-e130-43f1-bff8-eb094067ec20 Report Status: 4 Hashed bucket: 4/21/2018 9:14 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1a P2: 41792 P3: ffff9c813514cb48 P4: 40000 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\042118-12203-01.dmp \\?\C:\WINDOWS\TEMP\WER-14484-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER630F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER632E.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER633F.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_8772e4d1e120882de10579e40ceb0d88d93f229_00000000_cab_02bc633e Analysis symbol: Rechecking for solution: 0 Report Id: a5e4de32-7da5-4630-93b7-290d4a866f54 Report Status: 4 Hashed bucket: 4/21/2018 9:06 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1a P2: 41793 P3: ffffe980c5ae6ff8 P4: 200 P5: 1ff P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\042118-14921-01.dmp \\?\C:\WINDOWS\TEMP\WER-22906-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER783D.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER784C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER786D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_a3f814b3f9944b34f2b9fdd2fd6fede17da1f57_00000000_cab_02c4786c Analysis symbol: Rechecking for solution: 0 Report Id: ffa04a0a-3abb-46b9-9272-e547497455c9 Report Status: 4 Hashed bucket: 4/21/2018 9:29 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1a P2: 41793 P3: ffffef00eb813b48 P4: 2 P5: 1 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\042118-12281-01.dmp \\?\C:\WINDOWS\TEMP\WER-14625-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7D3E.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7D6D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7D8D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_87d3ac3fdb63cab5a5d38cb6a6e22fe134209_00000000_cab_02c87d9c Analysis symbol: Rechecking for solution: 0 Report Id: 01040524-7ae1-458b-823e-8102b9890317 Report Status: 4 Hashed bucket: 4/15/2018 10:21 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1c7 P2: 0 P3: ffffd4877969b000 P4: 848207ad P5: 311cf P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\041518-33343-01.dmp \\?\C:\WINDOWS\TEMP\WER-37421-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB640.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB65F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB69F.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1c7_463c495e68b83ade6dc1c790b84dc7647a0bd_00000000_cab_02c4b69e Analysis symbol: Rechecking for solution: 0 Report Id: 455a0bf8-5cc5-41ef-8720-5b08b770a5c6 Report Status: 4 Hashed bucket: 4/18/2018 1:31 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 4e P2: 99 P3: 1b185b P4: 2 P5: e0001b0001b285d P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\041718-27703-01.dmp \\?\C:\WINDOWS\TEMP\WER-30281-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER97AC.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER97CB.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER97DC.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_4e_151b1eda7d7097d3e2bc1f4a60583d4282a5bbf8_00000000_cab_02c897db Analysis symbol: Rechecking for solution: 0 Report Id: d0156e76-ed46-460a-ae75-3b16c1919ae5 Report Status: 4 Hashed bucket: 4/21/2018 8:43 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 4e P2: 99 P3: 2c850c P4: 2 P5: 60002500025b60b P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\042118-12109-01.dmp \\?\C:\WINDOWS\TEMP\WER-14687-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C39.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C58.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C98.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_4e_e417efbbf814bf3d7c959d10394c80dd6695ba29_00000000_cab_02c05ca6 Analysis symbol: Rechecking for solution: 0 Report Id: c5629059-378f-46bd-8388-33fe43a26972 Report Status: 4 Hashed bucket: 4/19/2018 12:45 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: a P2: 34 P3: 2 P4: 0 P5: fffff800b6301671 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\041818-14390-01.dmp \\?\C:\WINDOWS\TEMP\WER-16953-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6F05.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6F25.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6F35.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_f2d52468de5e7bf95439bf471f294e9389b8b7d_00000000_cab_02c46f34 Analysis symbol: Rechecking for solution: 0 Report Id: 29e1011d-11f6-473f-abda-18ff38982dcc Report Status: 4 Hashed bucket: 4/21/2018 9:39 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: be P2: ffff9e0017ddbc18 P3: 8a00000004300021 P4: ffffb584f8d94f70 P5: a P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\042118-12718-01.dmp \\?\C:\WINDOWS\TEMP\WER-16671-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER84C0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER853D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER854E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_be_7894459c9510bab04a3798d8d8d1067b38aea2c_00000000_cab_02bc855c Analysis symbol: Rechecking for solution: 0 Report Id: bf46086c-f4d3-497a-908c-1d4c145634f6 Report Status: 4 Hashed bucket: 4/21/2018 8:52 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c4 P2: 2000 P3: fffff8072fff18ff P4: 0 P5: 33505741 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\042118-24640-01.dmp \\?\C:\WINDOWS\TEMP\WER-26828-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER86C4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8712.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8732.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_b19a1a2a3ad02e65f29de4a0261a49f72148ad_00000000_cab_02cc8731 Analysis symbol: Rechecking for solution: 0 Report Id: 8094c9fb-3a15-4923-9cef-24386a82d5ef Report Status: 4 Hashed bucket: 4/21/2018 4:55 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c4 P2: 2004 P3: ffff988e8c477e38 P4: fffff80facee0218 P5: ffffe28ea84370c8 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\042118-7750-01.dmp \\?\C:\WINDOWS\TEMP\WER-10140-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER43EE.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER442D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER443D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_8a49ebf63c5adf9511cf7b2b71ddc2858e1b64cf_00000000_cab_02c8443c Analysis symbol: Rechecking for solution: 0 Report Id: c0ca7e56-2e25-4414-87e0-d815b4d7f2d5 Report Status: 4 Hashed bucket:[/quote] Code: 4/21/2018 4:55 PM Windows Error Reporting Fault bucket 0x1a_403_nt!MiDeletePteRun, type 0 Event Name: BlueScreen Response: Not available Cab Id: ce742775-214a-4ab2-95a3-3d6a9d4bd4fc Problem signature: P1: 1a P2: 403 P3: fffff400e575eb48 P4: 800000002603a967 P5: fffff400e5765148 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\042118-29125-01.dmp \\?\C:\WINDOWS\TEMP\WER-31781-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA076.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA0A5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA0B5.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_e99db48e734377a4816877d443242c8885850b9_00000000_cab_09c0aece Analysis symbol: Rechecking for solution: 0 Report Id: 8ff7b8e3-8528-43bb-bfe5-c10f21a08d32 Report Status: 268435456 Hashed bucket:4/19/2018 1:45 PM Windows Error Reporting Fault bucket 0x1a_404_nt!ExFreePoolWithTag, type 0 Event Name: BlueScreen Response: Not available Cab Id: 0de8af39-ccaa-4f49-9094-cf73c5cc6061 Problem signature: P1: 1a P2: 404 P3: ffffff520fe38b48 P4: 8a0000002a483863 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\041818-12593-01.dmp \\?\C:\WINDOWS\TEMP\WER-15281-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A64.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A83.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A94.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_7220466050edf571399c7f3f17abd949a198f7b_00000000_cab_0a95c8ce Analysis symbol: Rechecking for solution: 0 Report Id: 073c0869-e130-43f1-bff8-eb094067ec20 Report Status: 268435456 Hashed bucket: 4/21/2018 9:06 PM Windows Error Reporting Fault bucket 0x1a_41793_nt!MiDeleteVirtualAddresses, type 0 Event Name: BlueScreen Response: Not available Cab Id: 889bbefc-8304-4841-8e62-b88bfaa3f179 Problem signature: P1: 1a P2: 41793 P3: ffffe980c5ae6ff8 P4: 200 P5: 1ff P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\042118-14921-01.dmp \\?\C:\WINDOWS\TEMP\WER-22906-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER783D.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER784C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER786D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_a3f814b3f9944b34f2b9fdd2fd6fede17da1f57_00000000_cab_23209a0d Analysis symbol: Rechecking for solution: 0 Report Id: ffa04a0a-3abb-46b9-9272-e547497455c9 Report Status: 268435456 Hashed bucket: 4/21/2018 9:31 PM Windows Error Reporting Fault bucket 0x1a_41793_nt!MiDeleteVirtualAddresses, type 0 Event Name: BlueScreen Response: Not available Cab Id: ceb34302-d07e-483b-b716-56ddd390284c Problem signature: P1: 1a P2: 41793 P3: ffffef00eb813b48 P4: 2 P5: 1 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\042118-12281-01.dmp \\?\C:\WINDOWS\TEMP\WER-14625-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7D3E.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7D6D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7D8D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_87d3ac3fdb63cab5a5d38cb6a6e22fe134209_00000000_cab_27a650c6 Analysis symbol: Rechecking for solution: 0 Report Id: 01040524-7ae1-458b-823e-8102b9890317 Report Status: 268435456 Hashed bucket: 4/15/2018 11:14 PM Windows Error Reporting Fault bucket 0x1C7_0_nt!SmHpBufferProtectEx, type 0 Event Name: BlueScreen Response: Not available Cab Id: d9110b5f-d6c1-4aeb-8bc4-b4e23793733a Problem signature: P1: 1c7 P2: 0 P3: ffffd4877969b000 P4: 848207ad P5: 311cf P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\041518-33343-01.dmp \\?\C:\WINDOWS\TEMP\WER-37421-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB640.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB65F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB69F.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1c7_463c495e68b83ade6dc1c790b84dc7647a0bd_00000000_cab_0fbcec98 Analysis symbol: Rechecking for solution: 0 Report Id: 455a0bf8-5cc5-41ef-8720-5b08b770a5c6 Report Status: 268435456 Hashed bucket: 4/18/2018 1:31 PM Windows Error Reporting Fault bucket 0x4E_99_nt!MiBadShareCount, type 0 Event Name: BlueScreen Response: Not available Cab Id: ea9aa784-efab-4a47-8b03-576c83df3466 Problem signature: P1: 4e P2: 99 P3: 1b185b P4: 2 P5: e0001b0001b285d P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\041718-27703-01.dmp \\?\C:\WINDOWS\TEMP\WER-30281-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER97AC.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER97CB.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER97DC.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_4e_151b1eda7d7097d3e2bc1f4a60583d4282a5bbf8_00000000_cab_1a7bc7cf Analysis symbol: Rechecking for solution: 0 Report Id: d0156e76-ed46-460a-ae75-3b16c1919ae5 Report Status: 268435456 Hashed bucket: 4/21/2018 8:53 PM Windows Error Reporting Fault bucket 0x4E_99_nt!MiDeletePteRun, type 0 Event Name: BlueScreen Response: Not available Cab Id: c9fa680a-2167-4d3e-a603-0bb60a94cba2 Problem signature: P1: 4e P2: 99 P3: 2c850c P4: 2 P5: 60002500025b60b P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\042118-12109-01.dmp \\?\C:\WINDOWS\TEMP\WER-14687-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C39.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C58.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C98.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_4e_e417efbbf814bf3d7c959d10394c80dd6695ba29_00000000_cab_0b10e5db Analysis symbol: Rechecking for solution: 0 Report Id: c5629059-378f-46bd-8388-33fe43a26972 Report Status: 268435456 Hashed bucket: 4/21/2018 9:42 PM Windows Error Reporting Fault bucket 0xBE_nt!MiSetPfnBlink, type 0 Event Name: BlueScreen Response: Not available Cab Id: edf835a7-2935-4b33-9a86-0445207c5d2c Problem signature: P1: be P2: ffff9e0017ddbc18 P3: 8a00000004300021 P4: ffffb584f8d94f70 P5: a P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\042118-12718-01.dmp \\?\C:\WINDOWS\TEMP\WER-16671-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER84C0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER853D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER854E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_be_7894459c9510bab04a3798d8d8d1067b38aea2c_00000000_cab_1e0e677a Analysis symbol: Rechecking for solution: 0 Report Id: bf46086c-f4d3-497a-908c-1d4c145634f6 Report Status: 268435456 Hashed bucket: 4/21/2018 8:54 PM Windows Error Reporting Fault bucket 0xc4_2000_VRF_npf!unknown_function, type 0 Event Name: BlueScreen Response: Not available Cab Id: d25884b2-ac68-4ff1-ab26-881ec5938265 Problem signature: P1: c4 P2: 2000 P3: fffff8072fff18ff P4: 0 P5: 33505741 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\042118-24640-01.dmp \\?\C:\WINDOWS\TEMP\WER-26828-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER86C4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8712.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8732.tmp.txt \\?\C:\Windows\Temp\WER1039.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_b19a1a2a3ad02e65f29de4a0261a49f72148ad_00000000_cab_0b127555 Analysis symbol: Rechecking for solution: 0 Report Id: 8094c9fb-3a15-4923-9cef-24386a82d5ef Report Status: 268435456 Hashed bucket: 4/21/2018 4:56 PM Windows Error Reporting Fault bucket 0xc4_2004_VRF_nt!MmLoadSystemImageEx, type 0 Event Name: BlueScreen Response: Not available Cab Id: 0cd09c9f-ae44-420e-8171-dc571ce30d5e Problem signature: P1: c4 P2: 2004 P3: ffff988e8c477e38 P4: fffff80facee0218 P5: ffffe28ea84370c8 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\042118-7750-01.dmp \\?\C:\WINDOWS\TEMP\WER-10140-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER43EE.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER442D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER443D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_8a49ebf63c5adf9511cf7b2b71ddc2858e1b64cf_00000000_cab_09c10308 Analysis symbol: Rechecking for solution: 0 Report Id: c0ca7e56-2e25-4414-87e0-d815b4d7f2d5 Report Status: 268435456 Hashed bucket:[/quote] Code: 4/19/2018 1:22 AM Windows Error Reporting Fault bucket AV_nt!MiGetImageProtoProtection, type 0 Event Name: BlueScreen Response: Not available Cab Id: 9a5fabf7-0836-48bc-9044-2679282f222b Problem signature: P1: a P2: 34 P3: 2 P4: 0 P5: fffff800b6301671 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\041818-14390-01.dmp \\?\C:\WINDOWS\TEMP\WER-16953-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6F05.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6F25.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6F35.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_f2d52468de5e7bf95439bf471f294e9389b8b7d_00000000_cab_0765c459 Analysis symbol: Rechecking for solution: 0 Report Id: 29e1011d-11f6-473f-abda-18ff38982dcc Report Status: 268435456 Hashed bucket:12/14/2017 7:45 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 01f2dde3-b776-4995-bfc1-119900f7de80 Problem signature: P1: 141 P2: ffffc380c1bd0010 P3: fffff8070971f948 P4: 0 P5: 22f4 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171214-0145.dmp \\?\C:\WINDOWS\TEMP\WER-28773031-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER19CA.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER19CA.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER19EA.tmp.txt \\?\C:\Windows\Temp\WER3AA1.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_fa26bb1bd53ae68ba972ef2e181e4e07ca8cbfc_00000000_cab_20fb3c36 Analysis symbol: Rechecking for solution: 0 Report Id: 21493d48-cae6-4254-9b44-acc986f2ae48 Report Status: 268435456 Hashed bucket: 12/16/2017 10:54 PM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0359478d-245e-4fc9-b4ca-9cc63b457c2a Problem signature: P1: 141 P2: ffffc380c0d35210 P3: fffff8070971f948 P4: 0 P5: 518 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171216-1653.dmp \\?\C:\WINDOWS\TEMP\WER-256087609-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA443.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA452.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA463.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_43176ccff7d78826b534f6d3994e4d24fa10d0_00000000_cab_2383dc79 Analysis symbol: Rechecking for solution: 0 Report Id: bbb3d8ae-7754-4adb-ba77-a686fa51fc6c Report Status: 268435456 Hashed bucket: 12/13/2017 2:00 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 08489171-e2d0-492c-a397-97a9000441c5 Problem signature: P1: 141 P2: ffffc309ae1e82c0 P3: fffff8091cc6f948 P4: 0 P5: 1ad8 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171212-1959.dmp \\?\C:\WINDOWS\TEMP\WER-472853640-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D03.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D13.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D23.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_612b74e1d1e18278401637426e39f24bde177d65_00000000_cab_23cf600c Analysis symbol: Rechecking for solution: 0 Report Id: 9fcfb75c-fea9-4452-9d8f-5d374de0ebf5 Report Status: 268435456 Hashed bucket: 12/16/2017 10:54 PM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0b00b1f9-0f8e-40b0-9c30-598b88a57a31 Problem signature: P1: 141 P2: ffffc380c0d35210 P3: fffff8070971f948 P4: 0 P5: acc P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171216-1654.dmp \\?\C:\WINDOWS\TEMP\WER-256109046-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF418.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF41A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF42B.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_50e60b4e25deeefa6b41eab2622c19e69da954c_00000000_cab_24d005eb Analysis symbol: Rechecking for solution: 0 Report Id: 482070e8-eb3e-4679-9062-d70ade2a1096 Report Status: 268435456 Hashed bucket: 1/25/2018 4:04 PM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 179d74d8-2c39-4f1b-ba3e-620bc19242d9 Problem signature: P1: 141 P2: ffff9f8587d6f010 P3: fffff80ec9edf948 P4: 0 P5: 2f8c P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180125-1004.dmp \\?\C:\WINDOWS\TEMP\WER-556906812-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC8FB.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC8FB.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC91C.tmp.txt \\?\C:\Windows\Temp\WERE742.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_80afc62c62d4b5cd4654d83ee143a279671c46ce_00000000_cab_0e69e8b8 Analysis symbol: Rechecking for solution: 0 Report Id: 863163eb-8809-4a35-b01b-d239dcd4598a Report Status: 268435456 Hashed bucket: 12/20/2017 2:49 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 33bf85be-9e08-406d-855f-c2147181f763 Problem signature: P1: 141 P2: ffffc380c41104a0 P3: fffff8070971f948 P4: 0 P5: 930 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171219-2048.dmp \\?\C:\WINDOWS\TEMP\WER-529394375-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFCD8.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFCD8.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFCF8.tmp.txt \\?\C:\Windows\Temp\WER117A.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_56767639a7fb13df4b0dd5cd15611cf1f57bea3_00000000_cab_36a2131f Analysis symbol: Rechecking for solution: 0 Report Id: 92d788f7-2300-417f-bc99-163829e073c7 Report Status: 268435456 Hashed bucket: 12/16/2017 12:45 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 36344d1e-01b5-4970-9622-a314743977c6 Problem signature: P1: 141 P2: ffffc380bff3e4a0 P3: fffff8070971f948 P4: 0 P5: 28f4 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171215-1845.dmp \\?\C:\WINDOWS\TEMP\WER-176376031-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER537E.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5382.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER53A2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_df4a9721845ea9d9587fb47e99d698b4f77df2e5_00000000_cab_201b704d Analysis symbol: Rechecking for solution: 0 Report Id: c18a865a-5b9a-47cf-9363-43e235556c15 Report Status: 268435456 Hashed bucket: 12/17/2017 8:37 PM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 4b78f209-902f-4220-a1e0-0a375a19047b Problem signature: P1: 141 P2: ffffc380bd9b84a0 P3: fffff8070971f948 P4: 0 P5: 2df8 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171217-1437.dmp \\?\C:\WINDOWS\TEMP\WER-334273046-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA5A0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA5A0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA5C0.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_2248d62f1972866cf3ee858d30cbe3f49269fa_00000000_cab_0bc0fd84 Analysis symbol: Rechecking for solution: 0 Report Id: e2c6b856-00c2-4092-acc1-9a5afdc5d338 Report Status: 268435456 Hashed bucket: 2/10/2018 12:35 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 76787bff-a584-442e-914c-2482da49ffc4 Problem signature: P1: 141 P2: ffff9f8591c96010 P3: fffff80ec9edf948 P4: 0 P5: 563c P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180209-1834.dmp \\?\C:\WINDOWS\TEMP\WER-1883545781-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB0F1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB0F1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB111.tmp.txt \\?\C:\Windows\Temp\WER89.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_a0dfac29cd0b572a3fb5d6b82e27ebae8f938_00000000_cab_22a50395 Analysis symbol: Rechecking for solution: 0 Report Id: 111dc6a5-f8c1-4ddb-95f3-cbcb7684fce4 Report Status: 268435456 Hashed bucket: 12/16/2017 12:45 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 7ffb333f-6ed0-48b2-874c-abf64ccd62dd Problem signature: P1: 141 P2: ffffc380bff3e4a0 P3: fffff8070971f948 P4: 0 P5: 28f4 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171215-1845.dmp \\?\C:\WINDOWS\TEMP\WER-176370015-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C9A.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C9C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CAD.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_df4a9721845ea9d9587fb47e99d698b4f77df2e5_00000000_cab_38a35255 Analysis symbol: Rechecking for solution: 0 Report Id: 75c714ca-6d27-4227-93f2-ed4e53da9bc7 Report Status: 268435456 Hashed bucket: 2/11/2018 5:23 PM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 80ba623f-bece-4a34-9d9f-6c9e4591e143 Problem signature: P1: 141 P2: ffff9f8587217220 P3: fffff80ec9edf948 P4: 0 P5: 3a88 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180211-1122.dmp \\?\C:\WINDOWS\TEMP\WER-2030441640-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2439.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2439.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2449.tmp.txt \\?\C:\Windows\Temp\WER68A5.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_2d5a4087662215835ec0bf161736cb3cfc424cd9_00000000_cab_603a6c0f Analysis symbol: Rechecking for solution: 0 Report Id: 75ce07bd-d8ff-48c1-9e93-b69687c9a0be Report Status: 268435456 Hashed bucket: 12/2/2017 8:06 PM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 940aaba6-6e1f-47d2-875f-dc7db3784587 Problem signature: P1: 141 P2: ffffa282742644a0 P3: fffff80158f7f818 P4: 0 P5: 238 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171202-1406.dmp \\?\C:\WINDOWS\TEMP\WER-72985187-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA32.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA42.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA52.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_73c780985494d61f4319669314bcc8c587124f56_00000000_cab_1f29e808 Analysis symbol: Rechecking for solution: 0 Report Id: ed2c8d59-6819-4cc0-81f7-4cbcba7bbad1 Report Status: 268435456 Hashed bucket: 12/16/2017 10:54 PM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: d83621ec-4a8a-4502-b0ac-24539660234d Problem signature: P1: 141 P2: ffffc380c0d35210 P3: fffff8070971f948 P4: 0 P5: acc P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171216-1654.dmp \\?\C:\WINDOWS\TEMP\WER-256118312-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER17BD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER17C3.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER17E3.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_50e60b4e25deeefa6b41eab2622c19e69da954c_00000000_cab_0eac3f89 Analysis symbol: Rechecking for solution: 0 Report Id: ec6e4542-cc82-4a76-a39c-3d29b559c0b3 Report Status: 268435456 Hashed bucket: 12/16/2017 12:45 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: eb202c53-e25e-4c37-a7f2-35dfc1d3caff Problem signature: P1: 141 P2: ffffc380bff3e4a0 P3: fffff8070971f948 P4: 0 P5: 28f4 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171215-1845.dmp \\?\C:\WINDOWS\TEMP\WER-176357140-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC62.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC62.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC83.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_df4a9721845ea9d9587fb47e99d698b4f77df2e5_00000000_cab_1b2b1db8 Analysis symbol: Rechecking for solution: 0 Report Id: d11d43bd-1213-4ce8-8795-6a36c171e2de Report Status: 268435456 Hashed bucket: 12/16/2017 12:45 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: f595532c-d4f5-40c1-af7e-8244c05367fc Problem signature: P1: 141 P2: ffffc380bff3e4a0 P3: fffff8070971f948 P4: 0 P5: 28f4 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171215-1845.dmp \\?\C:\WINDOWS\TEMP\WER-176379078-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E5B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E70.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E81.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_df4a9721845ea9d9587fb47e99d698b4f77df2e5_00000000_cab_201b829c Analysis symbol: Rechecking for solution: 0 Report Id: fdaddfcb-d5d9-4dca-8ef1-f10293231a74 Report Status: 268435456 Hashed bucket: 12/16/2017 10:54 PM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: f6bf772c-1ab0-401e-b552-8b603b4c0179 Problem signature: P1: 141 P2: ffffc380c0d35210 P3: fffff8070971f948 P4: 0 P5: acc P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171216-1654.dmp \\?\C:\WINDOWS\TEMP\WER-256115046-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBF6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBFA.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC1A.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_50e60b4e25deeefa6b41eab2622c19e69da954c_00000000_cab_0eac2dd5 Analysis symbol: Rechecking for solution: 0 Report Id: 349cf9d6-c1d7-4305-8951-fabcabc8f918 Report Status: 268435456 Hashed bucket: 4/21/2018 9:16 PM Windows Error Reporting Fault bucket MEMORY_CORRUPTION_ONE_BIT, type 0 Event Name: BlueScreen Response: Not available Cab Id: 416d0fa7-55b1-43b0-b770-030970bd81d4 Problem signature: P1: 1a P2: 41792 P3: ffff9c813514cb48 P4: 40000 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\042118-12203-01.dmp \\?\C:\WINDOWS\TEMP\WER-14484-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER630F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER632E.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER633F.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_8772e4d1e120882de10579e40ceb0d88d93f229_00000000_cab_16a28f94 Analysis symbol: Rechecking for solution: 0 Report Id: a5e4de32-7da5-4630-93b7-290d4a866f54 Report Status: 268435456 Hashed bucket: 3/7/2018 11:45 PM Windows Error Reporting Fault bucket MEMORY_CORRUPTION_ONE_BIT, type 0 Event Name: BlueScreen Response: Not available Cab Id: c3f03c26-26b7-4eb5-a064-af52ab2e1f2e Problem signature: P1: 109 P2: a3a012db39cfa548 P3: b3b71f618c50aa13 P4: fffff80a720526a0 P5: 1 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\030718-13828-01.dmp \\?\C:\WINDOWS\TEMP\WER-16218-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BEB.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BFA.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C2A.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_109_68d1a437f40597725407e88f85b3dac812474b9_00000000_cab_13829642 Analysis symbol: Rechecking for solution: 0 Report Id: 8852d6d2-b043-4f8e-a4a7-6edb31bf378f Report Status: 268435456 Hashed bucket:[/quote] Code: Event[6837]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2018-04-21T11:47:17.198 Event ID: 5 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-O2K3A7A Description: {Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\SOFTWARE' was corrupted and it has been recovered. Some data might have been lost.[/quote] Code: Event[6442]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2018-04-17T20:31:06.666 Event ID: 16 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-O2K3A7A Description: Windows failed to resume from hibernate with error status 0xC0000001.[/quote] Code: Event[3461]: Log Name: System Source: Display Date: 2018-02-11T11:22:57.195 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-O2K3A7A Description: Display driver amdkmdap stopped responding and has successfully recovered.[/quote] Code: npf NetGroup Packet Filter Driver \??\c:\windows\system32\drivers\npf.sys Kernel Driver Yes Auto Running OK Normal No Yes[/quote]
     
    zbook, Apr 21, 2018
    #5
  6. jag213 Win User
    I posted 1) using the debug collect, did it not make it through?
     
    jag213, Apr 21, 2018
    #6
  7. zbook New Member
    There are 2 log collectors.
    Over time the beta log collector is being tested and will replace the DM log collector.
    The beta log collector will collect more useful information.
     
    zbook, Apr 21, 2018
    #7
  8. zbook New Member

    BSOD when I try and run sfc/scannow

    Please update the specs in the "My Computer" section:
    System Specs - Fill in at Ten Forums:
    System Specs - Fill in at Ten Forums Windows 10 Tutorials
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums


    Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)
    https://www.tenforums.com/profile.php?do=extra
     
    zbook, Apr 21, 2018
    #8
  9. jag213 Win User
    I have two computers and my specs are for the other one. Is there a way to have two sets of specs?
     
    jag213, Apr 21, 2018
    #9
  10. zbook New Member
    In the left lower corner of each of your posts you can click on "My Computer" > there should be 2 choices:
    a) Update your System Spec
    b) Add 2nd System
     
    zbook, Apr 21, 2018
    #10
  11. jag213 Win User
    Added 2nd specs thanks for directions
     
    jag213, Apr 21, 2018
    #11
  12. jag213 Win User
    Memtest showed two of my ram sticks giving errors right away. Removed them and haven't had any issues in the past hour or so. Scannow also seems to complete, so I will mark this as resolved. Thanks for your help
     
    jag213, Apr 21, 2018
    #12
Thema:

BSOD when I try and run sfc/scannow

Loading...
  1. BSOD when I try and run sfc/scannow - Similar Threads - BSOD try run

  2. sfc\scannow was just run.

    in Windows 10 Gaming
    sfc\scannow was just run.: i ran sfc /scannow after it say windows resource protection found corrupt files and successfully repaired them for online Repairs details are included in the CBS log file located at windir\logs\CBS\CBS.logs. for example c:\windowns\logs\CBS.log for oflinerapirs details are...
  3. sfc\scannow was just run.

    in Windows 10 Software and Apps
    sfc\scannow was just run.: i ran sfc /scannow after it say windows resource protection found corrupt files and successfully repaired them for online Repairs details are included in the CBS log file located at windir\logs\CBS\CBS.logs. for example c:\windowns\logs\CBS.log for oflinerapirs details are...
  4. Cannot run sfc /scannow

    in Windows 10 Gaming
    Cannot run sfc /scannow: Hi,Believing my Windows installation had some missing or corrupted files, I tried to run sfc /scannow in my command prompt. But I got the error message: Windows Resource Protection could not start the repair service.I already tried to:- Run the command prompt as...
  5. Cannot run sfc /scannow

    in Windows 10 Software and Apps
    Cannot run sfc /scannow: Hi,Believing my Windows installation had some missing or corrupted files, I tried to run sfc /scannow in my command prompt. But I got the error message: Windows Resource Protection could not start the repair service.I already tried to:- Run the command prompt as...
  6. Cannot run sfc /scannow

    in Windows 10 BSOD Crashes and Debugging
    Cannot run sfc /scannow: Hi,Believing my Windows installation had some missing or corrupted files, I tried to run sfc /scannow in my command prompt. But I got the error message: Windows Resource Protection could not start the repair service.I already tried to:- Run the command prompt as...
  7. cannot run sfc / scannow

    in Windows 10 Gaming
    cannot run sfc / scannow: In cmd prompt I get this message when attempting to run sfc/scannow:"you must be an administrator running a console session in order to use sfc/scannnow"How do I resolve this?...
  8. cannot run sfc / scannow

    in Windows 10 Software and Apps
    cannot run sfc / scannow: In cmd prompt I get this message when attempting to run sfc/scannow:"you must be an administrator running a console session in order to use sfc/scannnow"How do I resolve this?...
  9. Cannot run SFC/scannow

    in Windows 10 Installation and Upgrade
    Cannot run SFC/scannow: Dear all, Tried all sorts of remedies for above problem, nothing seems to work. Thank you. https://answers.microsoft.com/en-us/windows/forum/all/cannot-run-sfcscannow/85432df1-6503-4753-bdd6-932c282071ca
  10. Error message when running sfc /scannow

    in Windows 10 BSOD Crashes and Debugging
    Error message when running sfc /scannow: I get an error message when running scannow saying that some files are corrupt and could not be fixed. How do I fix them? My laptop seems to be in an unstable state. Thanks for your help...

Users found this page by searching for:

  1. 0x1C7_0_nt!SmHpBufferProtectEx

    ,
  2. migetimageprotoprotection