Windows 10: MACHINE_CHECK_EXCEPTION caused by hal.dll

  1.    27 Apr 2018 #1

    MACHINE_CHECK_EXCEPTION caused by hal.dll


    Hi! What should I do with this BSOD?
    MACHINE_CHECK_EXCEPTION caused by hal.dll Attached Files
      My ComputerSystem Spec


  2. Posts : 20,917
    windows 10 professional version 1607 build 14393.969 64 bit
       27 Apr 2018 #2

    The logs were in a foreign language and were not able to be scanned or read.
    Please change the default language to English and post a new zip so that the logs can be troubleshooted:
    Language - Add, Remove, and Change in Windows 10 Windows 10 Tutorials


    Run the beta log collector for the BSOD:
    https://www.tenforums.com/attachment...-v2-beta10.zip
    If there are problems running the beta log collector use the text and images in this link: (post #5)
    DM Log tool problem Solved - Windows 10 Forums


    Update the system 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
      My ComputerSystem Spec

  3. philc43's Avatar
    Posts : 3,591
    64bit Win 10 Pro ver 1809 Build 17763.1 and W10 Insider Build 18252
       27 Apr 2018 #3

    The symbols are not yet available for this new build of W10 (pre release of the April 2018 update) so we can't do any debugging on the crash dumps.
      My ComputersSystem Spec

  4.    27 Apr 2018 #4

    Sorry for wasting your time. I did proper logs.
    philc43 said: View Post
    The symbols are not yet available for this new build of W10 (pre release of the April 2018 update) so we can't do any debugging on the crash dumps.
    So you can't help me?
    MACHINE_CHECK_EXCEPTION caused by hal.dll Attached Files
      My ComputerSystem Spec

  5. philc43's Avatar
    Posts : 3,591
    64bit Win 10 Pro ver 1809 Build 17763.1 and W10 Insider Build 18252
       27 Apr 2018 #5

    Rambo1 said: View Post
    Sorry for wasting your time. I did proper logs.

    So you can't help me?
    We can't debug the crash dump files yet but @zbook will be able to explore the logs and may find some answers for you.
      My ComputersSystem Spec


  6. Posts : 20,917
    windows 10 professional version 1607 build 14393.969 64 bit
       27 Apr 2018 #6

    The BSOD mini dump files displayed bugchecks:
    9C
    101

    9C is now WHEA 0x124
    The WHEA 0x124 often indicates malfunctioning hardware.

    The RAM is mismatched.
    In general the RAM should be used with identical SKU.
    How long have the different RAM modules been in use?

    Ideally the BSOD mini dump files are debugged to display misbehaving drivers or malfunctioning hardware.

    As philc43 commented the symbols currently are not up to date for debugging the mini dump files.

    Perform the following steps:

    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) Make sure that there is no over clocking while troubleshooting.

    7) Sometimes there are problems in the bios that produce bsod.
    The BIOS: BIOS Version/Date American Megatrends Inc. P2.60, 12/17/2015 SMBIOS Version 2.7
    8) Please check to see if this is the most up to date version.
    9) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

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

    14) 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

    15) Open Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

    16) 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

    17) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
    Speccy - Free Download - Piriform: Speccy - System Information - Free
    Download Speccy | Find your computer specs, free!
    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
    HWMONITOR | Softwares | CPUID
    SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
    SpeedFan - Access temperature sensor in your computer

    18) Run HD Tune: (free version)
    Post images into the thread for the test results on these tabs:
    a) Health (SMART)
    b) Benchmark
    c) Full error scan

    19) 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 6 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

    20) Uninstall everything AMD using Display driver uninstaller and install new drivers from the AMD website.
    21) On the AMD web site be sure the "clean install" box is checked and only install the graphics driver.
    Official Display Driver Uninstaller DDU Download
    Display Driver Uninstaller Download version 17.0.8.2 (or a newer version if available)
    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    AMD Support and Radeon Software Driver Download

    AMD Graphics Drivers - Install Without Catalyst Install Manager - Windows 7 Help Forums
    Older AMD drivers: Previous

    After updating the AMD GPU:
    22) Measure the GPU's temperatures at idle and under load
    23) Ensure the GPU is free from dust build up and that the fan is working correctly
    24) Reseat the GPU and check all connections are securely made
    25) Check PSU voltages in BIOS
    What are the BIOS 3.3, 5 and 12 voltage values?
    What are the CPU voltage and frequency?

    26) 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 the thread
    Crash dump found at C:\WINDOWS\MEMORY.DMP
    Creation date: 04/27/2018 19:33:42
    Size on disk: 640 MB

    27) Open file explorer > this PC > C: > in the right upper corner search for:
    win32k.sys and
    win32k.sys-20180411-0021.dmp
    4/11/2018 5:49:55 PM 928.9 MB
    zip the file > post a one drive or drop box share link into the thread

    Code:
    4/27/2018 5:35 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Niedostępny
    Cab Id: 0
    
    Problem signature:
    P1: 101
    P2: 60
    P3: 0
    P4: fffff803c4fc4180
    P5: 0
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\042718-20625-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-117437-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1FE2.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2021.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER207E.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER209E.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_101_a63b56d55657b9993fb07f696f78432984eeb8c_00000000_cab_026a209d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e92d4df1-e9cc-44f1-801b-49b364bcdb8e
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    4/27/2018 2:17 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Niedostępny
    Cab Id: 0
    
    Problem signature:
    P1: 9c
    P2: 0
    P3: ffff8480b840bc00
    P4: 0
    P5: 0
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\042718-18218-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-171125-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF8DD.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF95B.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF9A8.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF9B9.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9c_8db883e8c6ac74663760f664eeac0ed79cf477e_00000000_cab_0276f9b8
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 15f28d45-6a91-4fcc-a17e-c438016e7b16
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    4/27/2018 4:33 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Niedostępny
    Cab Id: 0
    
    Problem signature:
    P1: 9c
    P2: 0
    P3: ffff9e00d460bc00
    P4: 0
    P5: 0
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\042718-21640-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-132515-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER64AB.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER650A.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6596.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER65B6.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9c_87b61f4b14afbf3081bc13b037429b3ad94dc62e_00000000_cab_027265b5
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 5389974b-2612-4a68-81f7-735bb1aa5eb1
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    4/27/2018 1:56 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Niedostępny
    Cab Id: 0
    
    Problem signature:
    P1: 9c
    P2: 0
    P3: ffffa1003b20bc00
    P4: 0
    P5: 0
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\042718-18640-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-230125-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREBC8.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREBF8.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREC45.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREC56.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9c_e647f3d7bbf5dda62f559d749832f1c93247b6_00000000_cab_027fec65
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 39bcb03a-a188-49a1-8d72-5ee48b4b6388
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    4/27/2018 4:26 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Niedostępny
    Cab Id: 0
    
    Problem signature:
    P1: 9c
    P2: 0
    P3: ffffb9016440bc00
    P4: 0
    P5: 0
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\042718-20937-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-172578-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFBBB.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFC0A.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFC96.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFCB6.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9c_8e4c5afff23af7edc2f21b3484a6f249e681c3_00000000_cab_0272fce4
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: c70bbf1b-09dc-46b3-a8f3-1ff87e919f29
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    4/24/2018 9:11 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Niedostępny
    Cab Id: 0
    
    Problem signature:
    P1: 9c
    P2: 0
    P3: ffffc3816ce64c00
    P4: 0
    P5: 0
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\042418-17890-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-177859-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER18A9.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1918.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1955.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1976.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9c_5f6c569fdd1d0589315fa4654687d5b7173bc6_00000000_cab_028f1975
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: a7061d2c-7496-408a-bf85-26be6b473e0a
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    Code:
    4/27/2018 2:17 PM    Windows Error Reporting    Fault bucket 0x9C_GenuineIntel, type 0
    Event Name: BlueScreen
    Response: Niedostępny
    Cab Id: 1c219dda-1e4f-4cf4-87c2-e1487e82d8a7
    
    Problem signature:
    P1: 9c
    P2: 0
    P3: ffff8480b840bc00
    P4: 0
    P5: 0
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\042718-18218-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-171125-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF8DD.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF95B.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF9A8.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF9B9.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9c_8db883e8c6ac74663760f664eeac0ed79cf477e_00000000_cab_07536989
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 15f28d45-6a91-4fcc-a17e-c438016e7b16
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
    4/27/2018 4:34 PM    Windows Error Reporting    Fault bucket 0x9C_GenuineIntel, type 0
    Event Name: BlueScreen
    Response: Niedostępny
    Cab Id: 372e78a1-da78-4564-8be5-527ebfaafc98
    
    Problem signature:
    P1: 9c
    P2: 0
    P3: ffff9e00d460bc00
    P4: 0
    P5: 0
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\042718-21640-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-132515-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER64AB.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER650A.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6596.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER65B6.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9c_87b61f4b14afbf3081bc13b037429b3ad94dc62e_00000000_cab_180a8998
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 5389974b-2612-4a68-81f7-735bb1aa5eb1
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
    4/24/2018 9:11 PM    Windows Error Reporting    Fault bucket 0x9C_GenuineIntel, type 0
    Event Name: BlueScreen
    Response: Niedostępny
    Cab Id: 47437b79-02f1-4ce5-b43b-9abd18e195be
    
    Problem signature:
    P1: 9c
    P2: 0
    P3: ffffc3816ce64c00
    P4: 0
    P5: 0
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\042418-17890-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-177859-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER18A9.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1918.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1955.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1976.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9c_5f6c569fdd1d0589315fa4654687d5b7173bc6_00000000_cab_15bb3c9d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: a7061d2c-7496-408a-bf85-26be6b473e0a
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
    4/27/2018 1:56 PM    Windows Error Reporting    Fault bucket 0x9C_GenuineIntel, type 0
    Event Name: BlueScreen
    Response: Niedostępny
    Cab Id: 4e5118df-56a0-4e0a-8795-090d08cf47e9
    
    Problem signature:
    P1: 9c
    P2: 0
    P3: ffffa1003b20bc00
    P4: 0
    P5: 0
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\042718-18640-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-230125-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREBC8.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREBF8.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREC45.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREC56.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9c_e647f3d7bbf5dda62f559d749832f1c93247b6_00000000_cab_09700fac
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 39bcb03a-a188-49a1-8d72-5ee48b4b6388
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
    4/27/2018 4:27 PM    Windows Error Reporting    Fault bucket 0x9C_GenuineIntel, type 0
    Event Name: BlueScreen
    Response: Niedostępny
    Cab Id: d54bb00e-8fb7-4a99-8eb1-d5c60734a613
    
    Problem signature:
    P1: 9c
    P2: 0
    P3: ffffb9016440bc00
    P4: 0
    P5: 0
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\042718-20937-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-172578-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFBBB.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFC0A.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFC96.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFCB6.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9c_8e4c5afff23af7edc2f21b3484a6f249e681c3_00000000_cab_119b31b0
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: c70bbf1b-09dc-46b3-a8f3-1ff87e919f29
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
    Code:
    4/27/2018 5:35 PM    Windows Error Reporting    Fault bucket CLOCK_WATCHDOG_TIMEOUT_2_PROC, type 0
    Event Name: BlueScreen
    Response: Niedostępny
    Cab Id: 6e081a1c-ecc8-43a9-9699-937f8f7d4a09
    
    Problem signature:
    P1: 101
    P2: 60
    P3: 0
    P4: fffff803c4fc4180
    P5: 0
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\042718-20625-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-117437-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1FE2.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2021.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER207E.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER209E.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_101_a63b56d55657b9993fb07f696f78432984eeb8c_00000000_cab_05565673
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e92d4df1-e9cc-44f1-801b-49b364bcdb8e
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
    Code:
    4/27/2018 2:11 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niedostępny
    Cab Id: 7822ce28-194b-455d-87b2-95e1ff88931e
    
    Problem signature:
    P1: 141
    P2: ffffb483a27de4a0
    P3: fffff80cdf4df9cc
    P4: 0
    P5: 1d8c
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180427-1608.dmp
    \\?\C:\WINDOWS\TEMP\WER-1000328-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER91E6.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9216.tmp.xml
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_231ef9817c8f73fca9f1319bd0479efdbdac3c_00000000_cab_01ff930f\WPR_initiated_DiagTrackMiniLogger_One Trace User Logger_20180425 Event Collector_0_inject.etl
    \\?\C:\Windows\Temp\WER92E2.tmp.etl
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_231ef9817c8f73fca9f1319bd0479efdbdac3c_00000000_cab_01ff930f\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
    \\?\C:\Windows\Temp\WER92E3.tmp.etl
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER92E4.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9304.tmp.txt
    \\?\C:\Windows\Temp\WERE67A.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_231ef9817c8f73fca9f1319bd0479efdbdac3c_00000000_cab_1e01ed1c
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 487fabab-ff8a-4ef6-a456-b9a6386b29e5
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
    4/27/2018 2:10 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niedostępny
    Cab Id: b7bb7daf-dc54-4bdb-b57e-e5f300010e1e
    
    Problem signature:
    P1: 141
    P2: ffffb483a0a624a0
    P3: fffff80cdf4df9cc
    P4: 0
    P5: 1d8c
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180427-1607.dmp
    \\?\C:\WINDOWS\TEMP\WER-929359-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER83A3.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER83B3.tmp.xml
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_a9f1d1cc77f038764c9d28a1ff5f1788a4c9bcf_00000000_cab_0cc28549\WPR_initiated_DiagTrackMiniLogger_One Trace User Logger_20180425 Event Collector_0_inject.etl
    \\?\C:\Windows\Temp\WER850C.tmp.etl
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_a9f1d1cc77f038764c9d28a1ff5f1788a4c9bcf_00000000_cab_0cc28549\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
    \\?\C:\Windows\Temp\WER850D.tmp.etl
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER851A.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER852A.tmp.txt
    \\?\C:\Windows\Temp\WER4942.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_a9f1d1cc77f038764c9d28a1ff5f1788a4c9bcf_00000000_cab_1e006f46
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: d24ebd4b-a70f-49ff-8e79-aadbc76c9cee
    Report Status: 268435556
    Hashed bucket: 
    Cab Guid: 0
      My ComputerSystem Spec


 

Related Threads
Hello, I've been troubleshooting trying to find the problem for ages, so I am seeking some more competent help. The stop core occurs randomly where for the most part it is when I browse and scroll with some media open (Youtube, banner adds). The...
Solved BSOD Under load MACHINE_CHECK_EXCEPTION in BSOD Crashes and Debugging
Hello, Been having a problem with PC lately, randomly crashes with abovementioned issue. Happens more often when PC is under load (ie games) but also randomly. Since I can't get windbg to work (won't load symbols from server) I'd appreciate...
Solved Machine_Check_Exception BSOD in BSOD Crashes and Debugging
For the past few days, playing Fallout 4 seems to invariably end in a BSOD usually with a MACHINE_CHECK_EXCEPTION error, but a few times the screen has simply frozen during play, sound crashed loudly, and the machine has not responded to any...
Bsod - machine_check_exception in BSOD Crashes and Debugging
Hello Ladies & Gents! I'm a SevenForums member, DreadStar/DreadStarX! It's been a long time since I've been on here, and found that SF/EF/TF is one of the best resources for OS Problems. So, here's the problem. When I boot up VMWare...
Hi, I've been getting random this random bsod every time I try to boot my laptop. It's been happening everyday after 2 weeks, since I updated from windows 7 to windows 10. Thanks in advance.
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 00:04.
Find Us