Page 2 of 3 FirstFirst 123 LastLast
  1.    28 Aug 2017 #11
    Join Date : Apr 2017
    Posts : 8,658
    windows 10 professional version 1607 build 14393.969 64 bit

    Hi Arodes ,

    There were 8 bsod mini dump files debugged.
    There was 1 misbehaving hardware driver identified.
    The event logs had numerous entries indicating drive corruption.



    Open administrative command prompt and type or copy and paste these commands:

    1) sfc /scannow
    2) dism /online /cleanup-image /restorehealth

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

    4) For all testing please post images into the thread:
    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
    For RAM / DIMM /Motherboard testing using Memtest86+ please use a camera or smart phone camera to take pictures and post images into the thread.

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

    Sometimes there are problems in the bios that produce bsod.

    The bios in your computer: BIOS Version/Date American Megatrends Inc. 2203, 18/12/2015

    6) Please check to see if this is the most up to date version.

    7) To ensure that there are no improper bios settings please reset the bios.

    Sometimes there can be failure to boot after resetting the bios.

    8) So please make sure your files are backed up.

    9) Please make a backup image with Macrium:

    Macrium Software | Macrium Reflect Free:
    Macrium Software | Your Image is Everything

    10) And please create a 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

    11) Run memtest86+ version 5.01 for at least 8 passes on each RAM module in 1 DIMM.

    This may take many hours so plan to run it overnight.

    Memtest86+ - Advanced Memory Diagnostic Tool

    When Memtest86+ has completed 8 or more runs use a camera or smart phone camera to take a picture and post an image into the thread.

    Microsoft Community
    MemTest86+ - Test RAM Windows 10 BSOD Tutorials

    12) Run HDTune on all drives:

    http://www.hdtune.com/

    to check the health of the drive,
    scan for errors, no quick scan but full scan
    run a benchmark.

    It may take some time, but please take the time you need to perform it properly.

    When above is done please make screenshots of the following
    the health,
    the error scan,
    the benchmark incl. following
    transfer rate,
    access time,
    burst rate,
    cpu usage.
    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials

    13) Run Sea tools for windows on your drive using SMART, short and long generic tests on all HD:

    How to use SeaTools for Windows
    http://www.seagate.com/support/downl...ls-win-master/
    How to use SeaTools for Windows
    http://www.seagate.com/support/downloads/seatools/

    14) Please update the system specifications:
    How To Fill Out Your System Specs
    How To Fill Out Your System Specs
    System Specs - Fill in at Ten Forums:
    System Specs - Fill in at Ten Forums Windows 10 General Tips 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

    15) In the system specifications please include information on PSU cooler, case, peripherals (mouse, keyboard, joystick). And also make sure to include anything attached to the computer by wireless or wired connection (printer, headset, xbox, etc)

    16) The best way to fix the misbehaving graphics driver is to uninstall everything AMD using Display Driver Uninstaller and install new drivers from AMD. Be sure to ONLY install the drivers using custom/advanced options.

    Official Display Driver Uninstaller DDU Download

    Display Driver Uninstaller Download version 17.0.7.2

    Display Driver Uninstaller: How to use - Windows 7 Help Forums

    17) Open administrative command prompt and type or copy and paste: chkdsk /x /f /r
    This may take many hours so plan to run over night.
    18) Post the results of the chkdsk scan into the thread:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials

    19) For all tests please make sure that you post images into the thread and for memtest86+ testing please use a camera or smart phone camera to take pictures and then post images into the thread.







    atikmpag.sys ATI Video driver (remove the Catalyst Control Center and only install the Display Driver) http://support.amd.com/us/Pages/AMDSupportHub.aspx
    Get from OEM for laptops

    Code:
    A corruption was discovered in the file system structure on volume C:.De exacte beschadiging is onbekend.  De bestandssysteemstructuren moeten online worden gescand.
    Code:
    Event[7329]:  Log Name: System  Source: Ntfs  Date: 2017-08-27T17:35:39.290  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Michael  Description: A corruption was discovered in the file system structure on volume C:.De exacte beschadiging is onbekend.  De bestandssysteemstructuren moeten online worden gescand.
    Code:
    Event[8417]:  Log Name: System  Source: Ntfs  Date: 2017-08-28T14:28:36.369  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Michael  Description: A corruption was discovered in the file system structure on volume C:.
    Code:
    Event[1346]:  Log Name: System  Source: BROWSER  Date: 2017-07-18T05:21:36.765  Event ID: 8032  Task: N/A  Level: Information  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: The browser service has failed to retrieve the backup list too many times on transport \Device\NetBT_Tcpip_{0CC98A27-8B7E-4EC3-BB4A-F3E3FB1712F2}. The backup browser is stopping.
    Code:
    Event[5369]:  Log Name: System  Source: Microsoft-Windows-Diagnostics-Networking  Date: 2017-08-22T23:58:28.729  Event ID: 5100  Task: Validation Failure  Level: Information  Opcode: Info  Keyword: Core Events  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: Michael  Description: The Network Diagnostics Framework (NDF) has completed the repair phase of operation. The following repair option or work-around was executed: Helper Class Name: AddressAcquisition Repair option: Stel adapter voor Ethernet opnieuw inDit kan soms een onregelmatig probleem oplossen. RepairGuid: {07D37F7B-FA5E-4443-BDA7-AB107B29AFB9} The repair option appears to have successfully fixed the diagnosed problem. But NDF has detected the existence of other network problems. NDF should be re-run to diagnose these problems.
    Code:
    Event[6988]:  Log Name: System  Source: Microsoft-Windows-StartupRepair  Date: 2017-08-27T14:41:44.495  Event ID: 1002  Task: N/A  Level: Information  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Michael  Description: Start-up Repair failed.
    Code:
    Event[8467]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-08-28T15:58:38.403  Event ID: 98  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Michael  Description: Volume C: (\Device\HarddiskVolume4) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.
    Code:
    Event[8424]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-08-28T14:47:26.786  Event ID: 98  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Michael  Description: Volume C: (\Device\HarddiskVolume4) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.
    Code:
    Event[8340]:  Log Name: System  Source: Disk  Date: 2017-08-28T06:23:55.419  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: An error was detected on device \Device\Harddisk3\DR4 during a paging operation.
    Code:
    Event[7819]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-08-27T18:35:22.297 Event ID: 98 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Michael Description: Volume C: (\Device\HarddiskVolume4) requires an Online Scan. An Online Scan will automatically run as part of the next scheduled maintenance task. Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
    Code:
    Event[2548]:  Log Name: System  Source: Display  Date: 2017-07-30T07:41:35.152  Event ID: 4109  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: Application ShellExperienc has been blocked from accessing Graphics hardware.

    Code:
    Event[5335]:  Log Name: System  Source: Display  Date: 2017-08-22T13:38:42.525  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[5336]:  Log Name: System  Source: Display  Date: 2017-08-22T13:38:42.530  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[5337]:  Log Name: System  Source: Display  Date: 2017-08-22T13:39:13.433  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[5338]:  Log Name: System  Source: Display  Date: 2017-08-22T13:39:33.599  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[5339]:  Log Name: System  Source: Display  Date: 2017-08-22T13:39:36.686  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[5340]:  Log Name: System  Source: Display  Date: 2017-08-22T13:39:40.472  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[5341]:  Log Name: System  Source: Display  Date: 2017-08-22T13:39:41.486  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: Display driver amdkmdap stopped responding and has successfully recovered.
    Code:
    Event[4379]:  Log Name: System  Source: Microsoft-Windows-Wininit  Date: 2017-08-13T22:47:30.583  Event ID: 11  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Michael  Description: Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications. Please visit http://support.microsoft.com/kb/197571 for more information.
    Code:
    Event[3250]:  Log Name: System  Source: Microsoft-Windows-Smartcard-Server  Date: 2017-08-05T18:38:06.941  Event ID: 610  Task: N/A  Level: Error  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: Smart Card Reader 'ACS CCID USB Reader 0' rejected IOCTL 0x313520: Onjuiste functie.  If this error persists, your smart card or reader may not be functioning correctly.Command Header: XX XX XX XXEvent[3251]:  Log Name: System  Source: Microsoft-Windows-Smartcard-Server  Date: 2017-08-05T18:38:07.556  Event ID: 610  Task: N/A  Level: Error  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: Smart Card Reader 'ACS CCID USB Reader 0' rejected IOCTL 0x313520: Onjuiste functie.  If this error persists, your smart card or reader may not be functioning correctly.Command Header: XX XX XX XXEvent[3252]:  Log Name: System  Source: Microsoft-Windows-Smartcard-Server  Date: 2017-08-05T18:38:08.449  Event ID: 610  Task: N/A  Level: Error  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: Smart Card Reader 'ACS CCID USB Reader 0' rejected IOCTL 0x313520: Onjuiste functie.  If this error persists, your smart card or reader may not be functioning correctly.Command Header: XX XX XX XXEvent[3253]:  Log Name: System  Source: Microsoft-Windows-Smartcard-Server  Date: 2017-08-05T18:38:23.779  Event ID: 610  Task: N/A  Level: Error  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: Smart Card Reader 'ACS CCID USB Reader 0' rejected IOCTL 0x313520: Onjuiste functie.  If this error persists, your smart card or reader may not be functioning correctly.Command Header: 00 XX XX XXEvent[3254]:  Log Name: System  Source: Microsoft-Windows-Smartcard-Server  Date: 2017-08-05T18:38:28.933  Event ID: 623  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: The card in Smart Card Reader 'ACS CCID USB Reader 0' has been reset because an application held an exclusive transaction on the card for 5 seconds without activity.  If this error persists, the application may not be functioning correctly.Process ID: 5624Event[3255]:  Log Name: System  Source: Microsoft-Windows-Smartcard-Server  Date: 2017-08-05T18:39:41.118  Event ID: 610  Task: N/A  Level: Error  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: Smart Card Reader 'ACS CCID USB Reader 0' rejected IOCTL 0x313520: Onjuiste functie.  If this error persists, your smart card or reader may not be functioning correctly.
    Code:
    Event[2547]:  Log Name: System  Source: Display  Date: 2017-07-30T07:41:30.007  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Michael  Description: Display driver amdkmdap stopped responding and has successfully recovered.
    Code:
    27/08/2017 16:57    Windows Error Reporting    Fault bucket 0x139_3_CORRUPT_LIST_ENTRY_nt!CmpDelayCloseWorker, type 0
    Event Name: BlueScreen
    Response: Niet beschikbaar
    Cab Id: ac2ec482-346b-4849-b205-0b765e52d28a
    
    Problem signature:
    P1: 139
    P2: 3
    P3: ffffca809d216920
    P4: ffffca809d216878
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\082717-5312-01.dmp
    \\?\C:\Windows\Temp\WER-6828-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER251C.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER254A.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER258A.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_6444cb7952821e947d764747bb8aa8fa671f8_00000000_cab_1d5b0ef5
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 94cf9cf0-2abf-4904-be8b-333571f58608
    Report Status: 268435556
    Hashed bucket:27/08/2017 19:17    Windows Error Reporting    Fault bucket 0x139_3_CORRUPT_LIST_ENTRY_nt!KiSignalThread, type 0
    Event Name: BlueScreen
    Response: Niet beschikbaar
    Cab Id: 33133a65-edcc-4008-8d44-a1f5d33d907b
    
    Problem signature:
    P1: 139
    P2: 3
    P3: ffffe181d747c700
    P4: ffffe181d747c658
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\082717-5750-01.dmp
    \\?\C:\Windows\Temp\WER-7281-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2644.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2664.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2674.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_f5867ccbfdf668fc353ddf8301f21738bfc_00000000_cab_0d16fb6d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 2bdd55cc-0c7b-45ea-9b07-3799d20f5f28
    Report Status: 268435556
    Hashed bucket:27/08/2017 17:09    Windows Error Reporting    Fault bucket 0x1a_41201_dxgmms2!VIDMM_RECYCLE_RANGE::Commit, type 0
    Event Name: BlueScreen
    Response: Niet beschikbaar
    Cab Id: ad97d103-3a70-4fc4-bc04-2f73c4ff48b6
    
    Problem signature:
    P1: 1a
    P2: 41201
    P3: ffffb300e201af80
    P4: ffffffffffffffff
    P5: ffff9181a4e2b340
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\082717-5546-01.dmp
    \\?\C:\Windows\Temp\WER-7078-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2617.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2618.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2619.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_4f6b3afdc88c4e52fb754d5f169dac72a3c56c9_00000000_cab_337b6c09
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 4eede536-2e06-433f-a93f-d0420403de40
    Report Status: 268435556
    Hashed bucket:15/08/2017 11:29    Windows Error Reporting    Fault bucket 0x1a_41792_nt!MiDeleteVirtualAddresses, type 0
    Event Name: BlueScreen
    Response: Niet beschikbaar
    Cab Id: e2a535bc-ffeb-46e8-a0b5-dd3655b6e357
    
    Problem signature:
    P1: 1a
    P2: 41792
    P3: ffffec000035ae80
    P4: ff000000ff000000
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\081517-6609-01.dmp
    \\?\C:\Windows\Temp\WER-8140-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CAE.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CBF.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CC0.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_382691b959aef24f214836904e50255d1d6cb0d5_00000000_cab_210cec25
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 3c01fef1-16ab-46da-bf0d-fde680441df5
    Report Status: 268435556
    Hashed bucket:

    Code:
    09/07/2017 08:47    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 003d0bf1-cd24-439e-91d2-f036c117e765
    
    Problem signature:
    P1: 141
    P2: ffffd4043653f210
    P3: fffff808b08bed90
    P4: 0
    P5: 2980
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170709-1046.dmp
    \\?\C:\Windows\Temp\WER-108140-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAC0A.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAC0C.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAC1C.tmp.txt
    \\?\C:\Windows\Temp\WERE8C6.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_2f5b7466170a341151e3de6589def01ff5fc7_00000000_cab_0c4dec8d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 6d2a0267-432b-495e-babc-5af06a3c241c
    Report Status: 268435456
    Hashed bucket:17/08/2017 10:26    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 0285aba3-38fc-4988-a995-d1234e95e123
    
    Problem signature:
    P1: 141
    P2: ffffc30136488220
    P3: fffff809909ff7f8
    P4: 0
    P5: 2618
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170817-1220.dmp
    \\?\C:\Windows\Temp\WER-12162484-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9AA6.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9AA8.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9AB8.tmp.txt
    \\?\C:\Windows\Temp\WER7781.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_993056d02de26b559dad7d4bec07afda67122_00000000_cab_26337aad
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 2474edbf-d7a9-41f4-b370-002657fc9330
    Report Status: 268435456
    Hashed bucket:09/07/2017 08:48    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 03bacc38-ab1d-4bbb-8705-34e44f00ad95
    
    Problem signature:
    P1: 141
    P2: ffffd4043653f210
    P3: fffff808b08bed90
    P4: 0
    P5: 2980
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170709-1046.dmp
    \\?\C:\Windows\Temp\WER-119093-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD9F0.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDA07.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDA18.tmp.txt
    \\?\C:\Windows\Temp\WERF331.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_2f5b7466170a341151e3de6589def01ff5fc7_00000000_cab_0efef795
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: e01b7afb-e5b2-4f89-89c3-ac68b4a9a5a1
    Report Status: 268435456
    Hashed bucket:30/07/2017 05:42    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 0d508ab1-e952-4786-8748-77e521ead46c
    
    Problem signature:
    P1: 141
    P2: ffffc30f4d2294a0
    P3: fffff80d97ddf7f8
    P4: 0
    P5: 1c10
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170730-0741.dmp
    \\?\C:\Windows\Temp\WER-34248640-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C83.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C8B.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C9C.tmp.txt
    \\?\C:\Windows\Temp\WER33B6.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_50653493be64622bcdf8487e6bf80fb358df06b_00000000_cab_1e2f3921
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 4056b059-63df-4512-ade9-0d178b0db8b4
    Report Status: 268435456
    Hashed bucket:22/08/2017 11:40    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 0fd3a192-b49b-42f3-82f7-da3659d152c2
    
    Problem signature:
    P1: 141
    P2: ffffac004c49a010
    P3: fffff80533bbf7f8
    P4: 0
    P5: c24
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170822-1339.dmp
    \\?\C:\Windows\Temp\WER-2224109-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF636.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF640.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF651.tmp.txt
    \\?\C:\Windows\Temp\WER4B8E.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_8fc9805367c0d192727e63d4a819b13de0fc77_00000000_cab_26124f05
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 82f35b16-c55b-4738-b947-a70d309339cc
    Report Status: 268435456
    Hashed bucket:30/07/2017 16:05    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 118d4b41-61c2-4ef7-8d6b-971f6800bc2f
    
    Problem signature:
    P1: 141
    P2: ffffc30f4d2294a0
    P3: fffff80d97ddf7f8
    P4: 0
    P5: 1c10
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170730-0741.dmp
    \\?\C:\Windows\Temp\WER-34272593-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA14.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA24.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA44.tmp.txt
    \\?\C:\Windows\Temp\WER2E49.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_50653493be64622bcdf8487e6bf80fb358df06b_00000000_cab_2e5f353a
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: f8fcf581-47c5-4892-ba58-a2ed552a0141
    Report Status: 268435456
    Hashed bucket:13/08/2017 20:50    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 1379b63e-3ba5-4b91-8f1f-cbca6143d2fd
    
    Problem signature:
    P1: 141
    P2: ffffb5019ca61010
    P3: fffff807f28ef7f8
    P4: 0
    P5: 23cc
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170813-1242.dmp
    \\?\C:\Windows\Temp\WER-945484-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER725D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7278.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7279.tmp.txt
    \\?\C:\Windows\Temp\WERA43.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_7f566fe1e37fefbae6afcff6fe5e0b7369928e9_00000000_cab_1a370ddc
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 92c26393-fb58-4eef-bd90-737466669aa8
    Report Status: 268435456
    Hashed bucket:30/07/2017 05:41    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 199c2a9e-4898-48a9-802a-1bd20226557b
    
    Problem signature:
    P1: 141
    P2: ffffc30f4d2294a0
    P3: fffff80d97ddf7f8
    P4: 0
    P5: 1c10
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170730-0741.dmp
    \\?\C:\Windows\Temp\WER-34242218-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER839C.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER83A0.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER83B1.tmp.txt
    \\?\C:\Windows\Temp\WERBB79.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_50653493be64622bcdf8487e6bf80fb358df06b_00000000_cab_090abf3e
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 90a3f692-55d8-46e1-83f0-109b904e6fe1
    Report Status: 268435456
    Hashed bucket:15/08/2017 11:29    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 2d808303-fb23-4b48-a73a-a9805057e326
    
    Problem signature:
    P1: 141
    P2: ffffa1083528e4a0
    P3: fffff809a807f7f8
    P4: 0
    P5: 190
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170815-1320.dmp
    \\?\C:\Windows\Temp\WER-8140-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C40.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C5F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CAE.tmp.txt
    \\?\C:\Windows\Temp\WERD13F.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_54de4446f14b33723eee417283568fc3f24136a2_00000000_cab_210cd4d4
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 42076030-e1bd-4347-af03-524785eb380e
    Report Status: 268435556
    Hashed bucket:30/07/2017 05:42    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 34d5e0bb-93a1-4e4d-af17-5b23a7a617b7
    
    Problem signature:
    P1: 141
    P2: ffffc30f4d2294a0
    P3: fffff80d97ddf7f8
    P4: 0
    P5: 1c10
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170730-0741.dmp
    \\?\C:\Windows\Temp\WER-34253781-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB0B7.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB0C1.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB0D1.tmp.txt
    \\?\C:\Windows\Temp\WER52CA.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_50653493be64622bcdf8487e6bf80fb358df06b_00000000_cab_1e2f5861
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: c1e874b2-f33c-4e03-90d1-3c61cd1c5187
    Report Status: 268435456
    Hashed bucket:30/07/2017 16:05    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 4279afb3-7c60-448a-a710-8885b283deeb
    
    Problem signature:
    P1: 141
    P2: ffffc30f4d2294a0
    P3: fffff80d97ddf7f8
    P4: 0
    P5: 1c10
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170730-0741.dmp
    \\?\C:\Windows\Temp\WER-34269718-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREEE9.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREEF7.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREF07.tmp.txt
    \\?\C:\Windows\Temp\WERFD91.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_50653493be64622bcdf8487e6bf80fb358df06b_00000000_cab_2e5f03e9
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 6264a3aa-d934-4c8c-9521-c8a2377b1cb9
    Report Status: 268435456
    Hashed bucket:13/08/2017 10:42    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 43ced786-9833-45ac-ae57-475f5d285818
    
    Problem signature:
    P1: 141
    P2: ffffb5019df9c010
    P3: fffff807f28ef7f8
    P4: 0
    P5: 27a4
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170813-1241.dmp
    \\?\C:\Windows\Temp\WER-908593-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE213.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE229.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE23A.tmp.txt
    \\?\C:\Windows\Temp\WER7E35.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_5ced289d860da5bdede195e59b93e7b1e1c8c27_00000000_cab_15e282d8
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: ea0ffecf-27d5-4bed-84e8-c4fee25111ed
    Report Status: 268435456
    Hashed bucket:13/08/2017 10:43    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 5554f892-ac08-4054-bf46-ad296b3e74fc
    
    Problem signature:
    P1: 141
    P2: ffffb5019ca61010
    P3: fffff807f28ef7f8
    P4: 0
    P5: 23cc
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170813-1242.dmp
    \\?\C:\Windows\Temp\WER-942484-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER66D4.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER66DE.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER66EE.tmp.txt
    \\?\C:\Windows\Temp\WER1432.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_7f566fe1e37fefbae6afcff6fe5e0b7369928e9_00000000_cab_15e317a5
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 4ccceacf-ad3e-4f7a-ad99-a48ddd099199
    Report Status: 268435456
    Hashed bucket:30/07/2017 05:42    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 55b05694-db10-426a-8e6a-ff6474952994
    
    Problem signature:
    P1: 141
    P2: ffffc30f4d2294a0
    P3: fffff80d97ddf7f8
    P4: 0
    P5: 1c10
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170730-0741.dmp
    \\?\C:\Windows\Temp\WER-34266812-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE39E.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE3AA.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE3BB.tmp.txt
    \\?\C:\Windows\Temp\WER770E.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_50653493be64622bcdf8487e6bf80fb358df06b_00000000_cab_1e2f7abe
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: ab5896a0-5b02-433f-a03f-8aae1648b149
    Report Status: 268435456
    Hashed bucket:30/07/2017 05:41    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 5608ef49-2b2d-4300-89a8-b45baee60a71
    
    Problem signature:
    P1: 141
    P2: ffffc30f53bef0f0
    P3: fffff80d97ddf7f8
    P4: 0
    P5: 2510
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170730-0740.dmp
    \\?\C:\Windows\Temp\WER-34217000-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER20FA.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER20FC.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER210D.tmp.txt
    \\?\C:\Windows\Temp\WER9EB6.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_76e1c35fad265924fa0bf93f34a9e859cf75b5a_00000000_cab_090aa27e
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: ecbee414-68b0-486c-896f-280f827f372d
    Report Status: 268435456
    Hashed bucket:13/08/2017 10:41    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 60206638-cdc7-40de-a8fa-4fb8063e805e
    
    Problem signature:
    P1: 141
    P2: ffffb50198b3f4a0
    P3: fffff807f28ef7f8
    P4: 0
    P5: 28a8
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170813-1240.dmp
    \\?\C:\Windows\Temp\WER-861203-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BB4.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BC3.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BD4.tmp.txt
    \\?\C:\Windows\Temp\WER5AE3.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_395acd3edf437b2b9adbc657881fc2acfaaf8_00000000_cab_0c655e5d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 7b3f6b1c-6c59-4ff1-8f8e-29c788492426
    Report Status: 268435456
    Hashed bucket:27/08/2017 17:09    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 63bc8afa-a92d-44de-a356-e09192b04d1b
    
    Problem signature:
    P1: 141
    P2: ffff9181a6f5b4a0
    P3: fffff802f0f0f818
    P4: 0
    P5: 2bc0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170827-1905.dmp
    \\?\C:\Windows\Temp\WER-693921-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B64.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B64.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B75.tmp.txt
    \\?\C:\Windows\Temp\WERF83.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_cebc75958ad29f8272de2f250e15a294eea8653_00000000_cab_337b12fc
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 1a0ac3d7-3a46-4167-995b-1c1d716a8f84
    Report Status: 268435556
    Hashed bucket:22/08/2017 11:39    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 65557e4e-1b35-4de9-b401-cf1f4c8ee7af
    
    Problem signature:
    P1: 141
    P2: ffffac004c49a010
    P3: fffff80533bbf7f8
    P4: 0
    P5: c24
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170822-1339.dmp
    \\?\C:\Windows\Temp\WER-2197078-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8BD4.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8BD8.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8BE9.tmp.txt
    \\?\C:\Windows\Temp\WERBAE4.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_8fc9805367c0d192727e63d4a819b13de0fc77_00000000_cab_25f5be5d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 9a9829f6-14e0-408c-84dd-95b644d8b800
    Report Status: 268435456
    Hashed bucket:17/08/2017 10:27    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 74f6507f-6f4a-4a41-b64d-6dea2524afe8
    
    Problem signature:
    P1: 141
    P2: ffffc3013777a010
    P3: fffff809909ff7f8
    P4: 0
    P5: 19d4
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170817-1226.dmp
    \\?\C:\Windows\Temp\WER-12537828-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5572.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5572.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5582.tmp.txt
    \\?\C:\Windows\Temp\WERD864.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_ea6d22edee7f926f8a5c94856349d5d81ed7273a_00000000_cab_2633db7a
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 4231471d-877c-4e5f-9258-0e45e113f61d
    Report Status: 268435456
    Hashed bucket:27/08/2017 17:09    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 7813161c-0fc8-4678-88f3-d1e839bae873
    
    Problem signature:
    P1: 141
    P2: ffff9181a6f5b4a0
    P3: fffff802f0f0f818
    P4: 0
    P5: 2bc0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170827-1905.dmp
    \\?\C:\Windows\Temp\WER-7078-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER25D7.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER25F6.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2607.tmp.txt
    \\?\C:\Windows\Temp\WER44C0.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_cebc75958ad29f8272de2f250e15a294eea8653_00000000_cab_337b4900
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 7971d0ce-bfd3-4338-b91b-8c2387bc3fea
    Report Status: 268435556
    Hashed bucket:15/08/2017 11:19    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 93feef56-bc69-4d3e-accf-31b8499501fc
    
    Problem signature:
    P1: 141
    P2: ffffa108347d24a0
    P3: fffff809a807f7f8
    P4: 0
    P5: 1848
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170815-1319.dmp
    \\?\C:\Windows\Temp\WER-4672734-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER52CA.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER52CA.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER52DA.tmp.txt
    \\?\C:\Windows\Temp\WER7835.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_c3dc9d705aefee11f97780461019363e8852cc86_00000000_cab_2e577bae
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 19f38238-91cf-4f17-993b-db091a962c93
    Report Status: 268435456
    Hashed bucket:30/07/2017 05:41    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 949b428d-0439-4be0-a9fb-18d012eceaae
    
    Problem signature:
    P1: 141
    P2: ffffc30f4d2294a0
    P3: fffff80d97ddf7f8
    P4: 0
    P5: 1c10
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170730-0741.dmp
    \\?\C:\Windows\Temp\WER-34245203-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F25.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F2B.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F3C.tmp.txt
    \\?\C:\Windows\Temp\WERADE.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_50653493be64622bcdf8487e6bf80fb358df06b_00000000_cab_1e2f0e96
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 88adaa6f-6034-4e92-bef4-704a28e8419e
    Report Status: 268435456
    Hashed bucket:17/08/2017 10:18    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: addfe956-d441-4582-834a-99af31380a4d
    
    Problem signature:
    P1: 141
    P2: ffffc3013cbb0010
    P3: fffff809909ff7f8
    P4: 0
    P5: 2244
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170817-1217.dmp
    \\?\C:\Windows\Temp\WER-12008968-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4711.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4730.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4741.tmp.txt
    \\?\C:\Windows\Temp\WER61FC.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_dc8989d5f91d09a1635dd8fbae68e6548462c2_00000000_cab_1a936595
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 96da501e-cba0-4da1-8f2f-01861be51de7
    Report Status: 268435456
    Hashed bucket:17/08/2017 10:20    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: b6f9c4cd-467c-467a-b21e-0d64f2ed350c
    
    Problem signature:
    P1: 141
    P2: ffffc30136488220
    P3: fffff809909ff7f8
    P4: 0
    P5: 2618
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170817-1220.dmp
    \\?\C:\Windows\Temp\WER-12159593-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F7A.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F7A.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F8B.tmp.txt
    \\?\C:\Windows\Temp\WER80A.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_993056d02de26b559dad7d4bec07afda67122_00000000_cab_05fa0b80
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 4716c8b9-fc47-4aa0-a84f-3faf2aed79ca
    Report Status: 268435456
    Hashed bucket:15/08/2017 11:29    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: ba798d7a-b870-4d30-b93a-d56f24d71796
    
    Problem signature:
    P1: 141
    P2: ffffa1083528e4a0
    P3: fffff809a807f7f8
    P4: 0
    P5: 190
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170815-1320.dmp
    \\?\C:\Windows\Temp\WER-4746515-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER73AB.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER73C2.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER73D3.tmp.txt
    \\?\C:\Windows\Temp\WER9134.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_54de4446f14b33723eee417283568fc3f24136a2_00000000_cab_210c954a
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 33a94d5e-93ba-4fc8-8d3d-3cad345f6fe0
    Report Status: 268435556
    Hashed bucket:09/07/2017 08:46    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: bb6e51b2-32ca-482f-86ba-dc88576842f7
    
    Problem signature:
    P1: 141
    P2: ffffd4043653f210
    P3: fffff808b08bed90
    P4: 0
    P5: 2980
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170709-1046.dmp
    \\?\C:\Windows\Temp\WER-102375-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9834.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9834.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9844.tmp.txt
    \\?\C:\Windows\Temp\WERBF83.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_2f5b7466170a341151e3de6589def01ff5fc7_00000000_cab_1c41c34b
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: df822d2f-2178-4365-b4f4-336304b7920a
    Report Status: 268435456
    Hashed bucket:09/07/2017 08:47    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: bc10776e-0704-4bc0-baa0-b240a15e2ea1
    
    Problem signature:
    P1: 141
    P2: ffffd4043653f210
    P3: fffff808b08bed90
    P4: 0
    P5: 2980
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170709-1046.dmp
    \\?\C:\Windows\Temp\WER-111937-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAA0.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAA4.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAB5.tmp.txt
    \\?\C:\Windows\Temp\WER598.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_2f5b7466170a341151e3de6589def01ff5fc7_00000000_cab_0c4e096c
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 9f3b0af4-292e-4d8d-baf1-90b9400b475a
    Report Status: 268435456
    Hashed bucket:13/08/2017 10:42    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: be04ea30-5561-4cc4-9575-b7409d4c14aa
    
    Problem signature:
    P1: 141
    P2: ffffb5019df9c010
    P3: fffff807f28ef7f8
    P4: 0
    P5: 27a4
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170813-1241.dmp
    \\?\C:\Windows\Temp\WER-905515-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD60D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD611.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD622.tmp.txt
    \\?\C:\Windows\Temp\WER13A7.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_5ced289d860da5bdede195e59b93e7b1e1c8c27_00000000_cab_158e170e
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: eeea1143-a173-47b5-9ad5-84f3fdbe8728
    Report Status: 268435456
    Hashed bucket:17/08/2017 10:20    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: d7fed6cd-c7dc-4055-85ea-ae510c617af3
    
    Problem signature:
    P1: 141
    P2: ffffc3013cbb0010
    P3: fffff809909ff7f8
    P4: 0
    P5: 2244
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170817-1217.dmp
    \\?\C:\Windows\Temp\WER-12014937-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5AD7.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5AD9.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5AEA.tmp.txt
    \\?\C:\Windows\Temp\WEREDB8.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_dc8989d5f91d09a1635dd8fbae68e6548462c2_00000000_cab_05f9f170
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: bf11a1f9-aea0-4857-a3ec-1fbfc6cf785f
    Report Status: 268435456
    Hashed bucket:13/08/2017 20:50    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: db6100fd-c3de-4d72-a252-10d4df338eb1
    
    Problem signature:
    P1: 141
    P2: ffffb5019ca61010
    P3: fffff807f28ef7f8
    P4: 0
    P5: 23cc
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170813-1242.dmp
    \\?\C:\Windows\Temp\WER-949218-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8355.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8372.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8383.tmp.txt
    \\?\C:\Windows\Temp\WER30F8.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_7f566fe1e37fefbae6afcff6fe5e0b7369928e9_00000000_cab_1a37348e
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 0091ecab-329b-466b-b6a0-5b17c78af34b
    Report Status: 268435456
    Hashed bucket:22/08/2017 11:39    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: e770e88e-5906-4d55-a20e-534089c785a5
    
    Problem signature:
    P1: 141
    P2: ffffac004c49a010
    P3: fffff80533bbf7f8
    P4: 0
    P5: c24
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170822-1339.dmp
    \\?\C:\Windows\Temp\WER-2217234-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDA61.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDA67.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDA78.tmp.txt
    \\?\C:\Windows\Temp\WERF136.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_8fc9805367c0d192727e63d4a819b13de0fc77_00000000_cab_0a99f4b0
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 4ab160f7-f941-49e8-9367-c2c8c039ea24
    Report Status: 268435456
    Hashed bucket:22/08/2017 11:38    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: ea77edb8-1202-44d2-8e6a-e627f40a252b
    
    Problem signature:
    P1: 141
    P2: ffffac004c595010
    P3: fffff80533bbf7f8
    P4: 0
    P5: 1b28
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170822-1338.dmp
    \\?\C:\Windows\Temp\WER-2166812-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER18A8.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER18AA.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER18BA.tmp.txt
    \\?\C:\Windows\Temp\WER3161.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_2802a5bf9ffd68adebbd8ab99d38f3f2a516538_00000000_cab_1ad934ea
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: cd9211e7-0e94-4987-9770-49523cb5a2b5
    Report Status: 268435456
    Hashed bucket:09/07/2017 08:47    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: f0b3acf5-4778-48b2-b33b-b23510357e4c
    
    Problem signature:
    P1: 141
    P2: ffffd4043653f210
    P3: fffff808b08bed90
    P4: 0
    P5: 2980
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170709-1046.dmp
    \\?\C:\Windows\Temp\WER-115796-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC985.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC98B.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC99B.tmp.txt
    \\?\C:\Windows\Temp\WER225A.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_2f5b7466170a341151e3de6589def01ff5fc7_00000000_cab_0c4e261c
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: bcdcd9b9-7ee6-45de-bb0d-50086dea9075
    Report Status: 268435456
    Hashed bucket:13/08/2017 10:41    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: f298c7c4-5373-49cc-9cd9-b1c337c735ff
    
    Problem signature:
    P1: 141
    P2: ffffb5019df9c010
    P3: fffff807f28ef7f8
    P4: 0
    P5: 27a4
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170813-1241.dmp
    \\?\C:\Windows\Temp\WER-864578-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3672.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3674.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3684.tmp.txt
    \\?\C:\Windows\Temp\WERF927.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_5ced289d860da5bdede195e59b93e7b1e1c8c27_00000000_cab_158dfcb0
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 17e0b121-958a-4201-bcc3-4faefd62be23
    Report Status: 268435456
    Hashed bucket:13/08/2017 10:42    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: f2e96ebe-2e4f-4c17-8e40-bff55a677aa5
    
    Problem signature:
    P1: 141
    P2: ffffb5019df9c010
    P3: fffff807f28ef7f8
    P4: 0
    P5: 27a4
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170813-1241.dmp
    \\?\C:\Windows\Temp\WER-911468-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREE58.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREE60.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREE71.tmp.txt
    \\?\C:\Windows\Temp\WERBEBC.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_5ced289d860da5bdede195e59b93e7b1e1c8c27_00000000_cab_15e2c232
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 2d414e9d-f728-4c2a-9c0a-8313f0c0cdb3
    Report Status: 268435456
    Hashed bucket:30/07/2017 05:41    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: f6271885-3225-4e3f-9474-f7d624bfc897
    
    Problem signature:
    P1: 141
    P2: ffffc30f53bef0f0
    P3: fffff80d97ddf7f8
    P4: 0
    P5: 2510
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170730-0740.dmp
    \\?\C:\Windows\Temp\WER-34212109-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1419.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1429.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1439.tmp.txt
    \\?\C:\Windows\Temp\WER2F82.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_76e1c35fad265924fa0bf93f34a9e859cf75b5a_00000000_cab_1b8a333a
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: f145a3d5-8fd7-46e3-a2d2-5643f8635aab
    Report Status: 268435456
    Hashed bucket:22/08/2017 11:39    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: fb824fef-43be-49ff-8ae5-ef19bc96192f
    
    Problem signature:
    P1: 141
    P2: ffffac004c49a010
    P3: fffff80533bbf7f8
    P4: 0
    P5: c24
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170822-1339.dmp
    \\?\C:\Windows\Temp\WER-2220328-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE667.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE66F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE680.tmp.txt
    \\?\C:\Windows\Temp\WER2556.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_8fc9805367c0d192727e63d4a819b13de0fc77_00000000_cab_261228cf
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: cfed5603-595e-4356-b5d5-4bab98f446cc
    Report Status: 268435456
    Hashed bucket:17/08/2017 10:27    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: fd3471d5-f8df-49d3-b6dc-95d5ed3f8085
    
    Problem signature:
    P1: 141
    P2: ffffc30136488220
    P3: fffff809909ff7f8
    P4: 0
    P5: 2618
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170817-1220.dmp
    \\?\C:\Windows\Temp\WER-12165281-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA758.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA75C.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA76C.tmp.txt
    \\?\C:\Windows\Temp\WERA7CC.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_993056d02de26b559dad7d4bec07afda67122_00000000_cab_2633aaf4
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: feb60977-8b32-469a-b36c-e9f35cc6e1e2
    Report Status: 268435456
    Hashed bucket:

    Code:
    27/08/2017 12:20    Windows Error Reporting    Fault bucket AV_nt!NtWaitForWorkViaWorkerFactory, type 0
    Event Name: BlueScreen
    Response: Niet beschikbaar
    Cab Id: 0b5c7d16-e50f-400d-9e96-013e8a0d9a86
    
    Problem signature:
    P1: a
    P2: 0
    P3: 2
    P4: 1
    P5: fffff8008523dc2d
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\082717-5484-01.dmp
    \\?\C:\Windows\Temp\WER-7046-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2673.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2693.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26E2.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_c42e4062615567ea6ccfd6646093413cb175cee4_00000000_cab_2f8706a8
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: b9f95239-a759-4031-922c-5426d1bfd52d
    Report Status: 268435556
    Hashed bucket:15/08/2017 11:29    Windows Error Reporting    Fault bucket BAD_DUMPFILE, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 5964a785-7a31-472d-bf7d-34cd86ccb690
    
    Problem signature:
    P1: 141
    P2: ffffa1083528e4a0
    P3: fffff809a807f7f8
    P4: 0
    P5: 190
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170815-1320.dmp
    \\?\C:\Windows\Temp\WER-4749781-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8137.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8153.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8173.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_54de4446f14b33723eee417283568fc3f24136a2_00000000_cab_210cba57
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 001e2ef2-806f-414d-a88f-4dd63daaf462
    Report Status: 268435556
    Hashed bucket:27/08/2017 17:09    Windows Error Reporting    Fault bucket BAD_DUMPFILE, type 0
    Event Name: LiveKernelEvent
    Response: Niet beschikbaar
    Cab Id: 8792769f-9260-4955-a85b-099523546f10
    
    Problem signature:
    P1: 141
    P2: ffff9181a6f5b4a0
    P3: fffff802f0f0f818
    P4: 0
    P5: 2bc0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170827-1905.dmp
    \\?\C:\Windows\Temp\WER-697484-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA8E1.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA8F3.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA8F4.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_cebc75958ad29f8272de2f250e15a294eea8653_00000000_cab_337b27ec
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 45b22160-33f0-420c-b16b-2b90273f33aa
    Report Status: 268435556
    Hashed bucket:27/08/2017 14:52    Windows Error Reporting    Fault bucket IP_MISALIGNED_win32kbase.sys, type 0
    Event Name: BlueScreen
    Response: Niet beschikbaar
    Cab Id: 0647761a-b6e7-4632-b022-ec0dfad34e86
    
    Problem signature:
    P1: be
    P2: ffff995baf4533a2
    P3: 195ebf021
    P4: ffffbc00427a9710
    P5: b
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\082717-5296-01.dmp
    \\?\C:\Windows\Temp\WER-6859-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24FC.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER252B.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER253C.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_be_c483c8a4f058c176ff76a83c9adbc649e10ec6d_00000000_cab_294afc67
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: a6d1f2d0-6548-46e1-a934-8050d1a47296
    Report Status: 268435556
    Hashed bucket:


    Code:
    Name    AMD Radeon R9 200 SeriesPNP Device ID    PCI\VEN_1002&DEV_6798&SUBSYS_3001174B&REV_00\4&BAB4994&0&0008Adapter Type    AMD Radeon Graphics Processor (0x6798), Advanced Micro Devices, Inc. compatibleAdapter Description    AMD Radeon R9 200 SeriesAdapter RAM    (1,073,741,824) bytesInstalled Drivers    aticfx64.dll,aticfx64.dll,aticfx64.dll,amdxc64.dll,aticfx32,aticfx32,aticfx32,amdxc32,atiumd64,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64Driver Version    22.19.673.0INF File    oem54.inf (ati2mtag_R575DS section)Colour Planes    Not AvailableColour Table Entries    4294967296Resolution    1920 x 1080 x 60 hertzBits/Pixel    32Memory Address    0xE0000000-0xFEAFFFFFMemory Address    0xF7E00000-0xF7E3FFFFI/O Port    0x0000E000-0x0000E0FFIRQ Channel    IRQ 4294967292I/O Port    0x000003B0-0x000003BBI/O Port    0x000003C0-0x000003DFMemory Address    0xA0000-0xBFFFFDriver    c:\windows\system32\driverstore\filerepository\c0317359.inf_amd64_71db94a48cef0172\atikmpag.sys (22.19.673.0, 529.02 KB (541,720 bytes), 24/08/2017 19:41)
    Last edited by zbook; 28 Aug 2017 at 12:56.
      My ComputerSystem Spec
  2.    28 Aug 2017 #12
    Join Date : Aug 2017
    Posts : 11
    Windows 10 64 bit
    Thread Starter

    Alright I will go through your post step by step and post the results (I downloaded and installed the latest version of the BIOS yesterday. I did not change any settings or overclock anything so it shouldn't be causing any issues):

    1) Command prompt results
    Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.
    C:\WINDOWS\system32>sfc /scannow
    Beginning system scan. This process will take some time.
    Beginning verification phase of system scan.
    Verification 100% complete.Windows Resource Protection did not find any integrity violations.
    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0Image
    Version: 10.0.15063.0
    [==========================100.0%==========================]
    Error: 0x800f081f
    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see MSN.com - Hotmail, Outlook, Skype, Bing, Latest News, Photos Videos DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    C:\WINDOWS\system32>
    Last edited by Arodes; 28 Aug 2017 at 13:55.
      My ComputerSystem Spec
  3.    28 Aug 2017 #13
    Join Date : Apr 2017
    Posts : 8,658
    windows 10 professional version 1607 build 14393.969 64 bit

    The sfc /scannow did not find any integrity violations.
    So at this time the operating system is Okay.
    Sometimes the dism commands are needed when the scannow cannot complete or when it finds integrity violations that it cannot fix.
    So it is good to have a working command.

    Make sure that you are not on a metered connection.

    Do you have a bootable windows 10 iso? Download Windows 10
    Insert the flash drive into any USB port.

    See which of these DISM commands can and cannot complete:

    Open administrative command prompt and type or copy and paste these commands:
    1) dism /online /cleanup-image /checkhealth
    2) dism /online /cleanup-image /scanhealth
    3) dism /online /cleanup-image /RestoreHealth /limitaccess
    4) Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:\Sources\install.wim:1 /limitaccess
    ...................................................................................................D :\sources\install.wim:1 /limitaccess
    In the information above it should display wim: immediately followed by D:\sources\install.wim:1 /limitaccess
    The webpage is changing the to a smiley
    5) Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\Sources\Install.esd:1 /limitaccess
    6) Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:C:\$Windows.~BT\Sources\Install.esd:1 /limitaccess
    7) DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:L:\Windows /LimitAccess
    8) dism /Online /NoRestart /Cleanup-Image /StartComponentCleanup
    9) dism /Online /NoRestart /Cleanup-Image /RestoreHealth
      My ComputerSystem Spec
  4.    28 Aug 2017 #14
    Join Date : Aug 2017
    Posts : 11
    Windows 10 64 bit
    Thread Starter

    Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.
    C:\WINDOWS\system32>dism /online /cleanup-image /checkhealth
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    Image Version: 10.0.15063.0
    The component store is repairable.The operation completed successfully.
    C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    Image Version: 10.0.15063.0
    [==========================100.0%==========================]
    The component store is repairable.The operation completed successfully.
    C:\WINDOWS\system32>dism /online /cleanup-image /RestoreHealth /limitaccess
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    Image Version: 10.0.15063.0
    [===========================91.3%==================== ]
    Error: 0x800f081f
    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see MSN.com - Hotmail, Outlook, Skype, Bing, Latest News, Photos Videos DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    C:\WINDOWS\system32>dism /online /cleanup-image /restoreHealth /Source:wim :\sources\install.wim:1 /limitaccess
    Error: 87
    DISM doesn't recognize the command-line option ":\sources\install.wim:1".For more information, refer to the help by running DISM.exe /?.
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    C:\WINDOWS\system32>dism /online /Cleanup-image /RestoreHealth /Source:wim:\sources\install.wim:1 /limitaccess
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    Image Version: 10.0.15063.0
    [===========================91.4%==================== ]
    Error: 0x800f081f
    The source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see MSN.com - Hotmail, Outlook, Skype, Bing, Latest News, Photos Videos DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    C:\WINDOWS\system32>dism /online /Cleanup-image /RestoreHealth /Source:esd:E:\Sources\Install.esd:1 /limitaccess
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    Image Version: 10.0.15063.0
    [===========================91.4%==================== ]
    Error: 0x800f081f
    The source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see MSN.com - Hotmail, Outlook, Skype, Bing, Latest News, Photos Videos DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    C:\WINDOWS\system32>dism /online /Cleanup-image /RestoreHealth /Source:esd:C:\$Windows.~BT\Sources\Install.esd:1 /limitaccess
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    Image Version: 10.0.15063.0
    [===========================91.3%==================== ]
    Error: 0x800f081f
    The source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see MSN.com - Hotmail, Outlook, Skype, Bing, Latest News, Photos Videos DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    C:\WINDOWS\system32>DISM.exe /Online /Cleanup-image /RestoreHealth /Source:L:\Windows /LimitAccessDeployment Image Servicing and Management tool
    Version: 10.0.15063.0
    Image Version: 10.0.15063.0
    [===========================91.3%==================== ]
    Error: 0x800f081f
    The source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see MSN.com - Hotmail, Outlook, Skype, Bing, Latest News, Photos Videos DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    C:\WINDOWS\system32>dism /online /NoRestart /Cleanup-image /StartComponentCleanup
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    Image Version: 10.0.15063.0
    Error: 0x800f0806
    The operation could not be completed due to pending operations.The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    C:\WINDOWS\system32>dism /online /norestart /cleanup-image /restorehealth
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    Image Version: 10.0.15063.0
    [==========================100.0%==========================]
    Error: 0x800f081f
    The source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see MSN.com - Hotmail, Outlook, Skype, Bing, Latest News, Photos Videos DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.logC:\WINDOWS\system32>

    I am currently running the HD tune pro tests and once those are done I will post the results.
      My ComputerSystem Spec
  5.    28 Aug 2017 #15
    Join Date : Aug 2017
    Posts : 11
    Windows 10 64 bit
    Thread Starter

    The results of the HD tune tests: (1)

    Click image for larger version. 

Name:	Error scan 1.png 
Views:	16 
Size:	25.1 KB 
ID:	150871Click image for larger version. 

Name:	Error scan 2.png 
Views:	16 
Size:	25.0 KB 
ID:	150872Click image for larger version. 

Name:	Error scan 3.png 
Views:	16 
Size:	24.4 KB 
ID:	150873Click image for larger version. 

Name:	Health 1.png 
Views:	16 
Size:	40.6 KB 
ID:	150874Click image for larger version. 

Name:	Health 2.png 
Views:	16 
Size:	34.8 KB 
ID:	150875
      My ComputerSystem Spec
  6.    28 Aug 2017 #16
    Join Date : Aug 2017
    Posts : 11
    Windows 10 64 bit
    Thread Starter

    HD test results: (2)
    Click image for larger version. 

Name:	Benchmark 1.png 
Views:	16 
Size:	41.5 KB 
ID:	150878Click image for larger version. 

Name:	Benchmark 2.png 
Views:	16 
Size:	50.6 KB 
ID:	150879Click image for larger version. 

Name:	Benchmark 3.png 
Views:	16 
Size:	41.4 KB 
ID:	150880Click image for larger version. 

Name:	Health 3.png 
Views:	16 
Size:	51.1 KB 
ID:	150881
      My ComputerSystem Spec
  7.    28 Aug 2017 #17
    Join Date : Oct 2016
    Caledon, Ontario, Canada
    Posts : 4,005
    Windows 10 Pro Build 1703

    Hi Arodes. If I understand you correctly, you were not having BSOD's of any kind until you added memory.

    You removed memory and things ran fine.

    When you installed memory and ran memtest it reported millions of errors. You made a change in the BIOS, post #10 of this thread and your memory errors are gone.

    Are you now experiencing BSOD's with memory additional installed?


    Ken
      My ComputerSystem Spec
  8.    29 Aug 2017 #18
    Join Date : Aug 2017
    Posts : 11
    Windows 10 64 bit
    Thread Starter

    Quote Originally Posted by Caledon Ken View Post
    Hi Arodes. If I understand you correctly, you were not having BSOD's of any kind until you added memory.

    You removed memory and things ran fine.

    When you installed memory and ran memtest it reported millions of errors. You made a change in the BIOS, post #10 of this thread and your memory errors are gone.

    Are you now experiencing BSOD's with memory additional installed?


    Ken
    Hi, yesterday I did not experience a single BSOD with the new memory installed.
      My ComputerSystem Spec
  9.    29 Aug 2017 #19
    Join Date : Oct 2016
    Caledon, Ontario, Canada
    Posts : 4,005
    Windows 10 Pro Build 1703

    Then I think you are done.

    Maybe check your event viewer and see if you are getting any serious errors, red x's, they should be looked at.

    All your dumps were generated with "Shaky" memory installed.

    Ken
      My ComputerSystem Spec
  10.    29 Aug 2017 #20
    Join Date : Aug 2017
    Posts : 11
    Windows 10 64 bit
    Thread Starter

    Quote Originally Posted by Caledon Ken View Post
    Then I think you are done.

    Maybe check your event viewer and see if you are getting any serious errors, red x's, they should be looked at.

    All your dumps were generated with "Shaky" memory installed.

    Ken
    Alright, I hope you are right and I won't get any more issues I'd like to take the time to thank both you and zbook, you really helped me out & I appreciate it a lot so thank you!
      My ComputerSystem Spec

 
Page 2 of 3 FirstFirst 123 LastLast


Similar Threads
Thread Forum
Solved How can I repair or replace these two log files? (found by scannow)
Problem.: computer occasionally locks after some time running, regardless if browser running, etc. scannow found NO problems before System Refresh last week note: am admin, computer indicates it cannot locate CBS.log, etc. now > ...
Performance & Maintenance
Solved sfc /scannow: Can't fix corrupt files with a Repair Install
I have Windows 10 installed on top of Windows 7. When I ran sfc /scannow, I expected to be able to replace the corrupt files with good ones. However, I just did a Repair Install and I still get a message that I have corrupt files and Windows can't...
Performance & Maintenance
SFC /scannow ?? corrupt files? I'm lost...
I was bored and had been having some issues so after a little reading I decided to run "sfc /scannow". Got the message that couldn't fix some of the corrupt files so I followed the next step and then the next step till I got to the point that the...
Performance & Maintenance
Solved DISM Source files could not be found, sfc /scannow found corrupt files
Custom build for a friend. OS: Windows 10 Pro, 64-bit MB: MSI Z170-A Pro Graphics Card: GeForce GTX 680 CPU: Intel i5 6600K @ 3.50GHz RAM: 8g Installed OS through bootable USB, as the build has no CD drive. On completion of build I had...
Performance & Maintenance
Solved SFC scannow cannot fix corrupt files, Dism?
Hi guys. I know this may be old news to some of you guys, but posting anyway. So I installed a game which did some net framework installing and after that had a hang. Removed the game, did sfc and found corrupt files. ...
Performance & Maintenance
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 06:53.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums