Windows 10: WHEA errors, CLOCK_WATCHDOG_TIMEOUT and frozen screens...

  1.    11 Dec 2017 #1

    WHEA errors, CLOCK_WATCHDOG_TIMEOUT and frozen screens...


    ...since installing the Fall Creators Update. I've had similar problems after installing every (major) update. They appear to go away by themselves after a few weeks, but I'm getting worried now that this time, they won't.

    The problems often appear to be preceded by problems with my network adapter (Qualcomm Atheros AR956x) turning off, sometimes temporarily, sometimes until restart.

    I've found out today that some of the frozen screens can be 'fixed' with Ctrl+Alt+Del, but got a CLOCK_WATCHDOG_TIMEOUT somewhat later.

    Graphics drivers (Intel(R) HD Graphics 4000 and NVIDIA GeForce 820M) have been reinstalled from the file on my computer. So was the driver for the network adapter.

    Please find the dumpfile attached.

    Hope someone can help, many thanks in advance!

    Tim
    WHEA errors, CLOCK_WATCHDOG_TIMEOUT and frozen screens... Attached Files
      My ComputerSystem Spec


  2. Posts : 3,129
    64bit Win 10 Pro ver 1709 Build 16299.248 and W10 Insider Build 17101 and 17604
       11 Dec 2017 #2

    Hello ohno and welcome to TenForums

    It looks as if the Intel graphics driver you are using might be causing your BSOD problems. I would suggest you get the latest one directly from Intel and see if makes a difference.

    Code:
    Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for igdkmd64.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
    
    igdkmd64.sys Timestamp:        Mon Dec 21 19:46:50 2015
      My ComputersSystem Spec

  3.    11 Dec 2017 #3

    I just did, and I'll keep you posted!

    PS: Any idea what might be going on with my network adapter?

    Many many thanks,

    Tim
      My ComputerSystem Spec


  4. Posts : 14,111
    windows 10 professional version 1607 build 14393.969 64 bit
       11 Dec 2017 #4

    Please modify the C: so that there is > 25 GB free space.

    Drive: C:
    Free Space: 7.3 GB
    Total Space: 696.8 GB
    File System: NTFS
    Model: ST750LM022 HN-M750MBB

    Code:
    Event[3714]:  Log Name: System
      Source: Microsoft-Windows-WER-SystemErrorReporting
      Date: 2017-12-11T08:47:29.009
      Event ID: 1018
      Task: N/A
      Level: Informatie
      Opcode: N/A
      Keyword: Klassiek
      User: N/A
      User Name: N/A
      Computer: Tim
      Description: 
    Het dumpbestand in C:\WINDOWS\MEMORY.DMP is verwijderd omdat het schijfvolume minder dan 25 GB vrije ruimte heeft.
    Please change the default language to English so that the log files can be scanned and read.
    Language - Add, Remove, and Change in Windows 10 General Tips Tutorials
    Please re-post the zip:
    BSOD - Posting Instructions - Windows 10 Forums
    Last edited by zbook; 11 Dec 2017 at 08:20.
      My ComputerSystem Spec

  5.    26 Dec 2017 #5

    I've freed up disk space, but for some reason, I don't manage to download the language pack for English...

    New dump file attached.

    Thanks again!

    Tim
    WHEA errors, CLOCK_WATCHDOG_TIMEOUT and frozen screens... Attached Files
      My ComputerSystem Spec


  6. Posts : 14,111
    windows 10 professional version 1607 build 14393.969 64 bit
       26 Dec 2017 #6

    There is a lot of information in these files which we cannot scan or read:
    event viewer
    dxdiag
    msinfo32
    etc.
    The event log currently displays 6039 entries so it is not possible to translate all of the entries to be able to scan them.
    So we are handicapped in providing help without having the ability to scan or read the information.

    These are 2 drivers that should be updated or uninstalled and reinstalled:


    athw8x.sys Atheros Wireless LAN Driver Official site: http://www.qualcomm.com/drivers
    Unofficial site: https://www.ath-drivers.eu

    Updating a driver: Updating a driver. - Microsoft Community



    1) If you use Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread


    2) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread


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

    4) Open administrative command prompt and type or copy and paste:
    5) sfc /scannow
    6) dism /online /cleanup-image /restorehealth
    7) 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
    8) chkdsk /x /f /r
    This may take many hours so plan to run overnight.
    9) Use the information in this link to find the chkdsk report in the event viewer and post a one drive or drop box share link into the thread:
    Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

    10) Run HDTune:
    http://www.hdtune.com/
    to check the health,
    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 General Tips Tutorials

    11) 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.
    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 8 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.
    When Memtest86+ 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 BSOD Tutorials


    Code:
    Event[3439]:  Log Name: System
      Source: volmgr
      Date: 2017-12-10T17:32:04.746
      Event ID: 46
      Task: N/A
      Level: Fout
      Opcode: N/A
      Keyword: Klassiek
      User: N/A
      User Name: N/A
      Computer: Tim
      Description: 
    Crashdumpinitialisatie is mislukt!

    Code:
    11/12/2017 7:47    Windows Error Reporting    Foutbucket CLOCK_WATCHDOG_TIMEOUT_4_PROC, type 0
    Naam van gebeurtenis: BlueScreen
    Antwoord: Niet beschikbaar
    Id van CAB-bestand: 413dc95d-0da7-4aeb-b654-d5ad002324b5
    
    Handtekening van probleem:
    P1: 101
    P2: 30
    P3: 0
    P4: fffff800ea2ad180
    P5: 0
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Toegevoegde bestanden:
    \\?\C:\WINDOWS\Minidump\121117-62296-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-897421-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5DAC.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5DEC.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E2C.tmp.txt
    
    Deze bestanden zijn mogelijk hier beschikbaar:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_101_bc9a3063cf935b6f52665c728052cb66ee9838be_00000000_cab_190a9546
    
    Analysesymbool: 
    Opnieuw zoeken naar oplossing: 0
    Rapport-id: 69c12129-0eea-455a-b732-b767f411ce5d
    Rapportstatus: 268435456
    Opgedeelde bucket:8/12/2017 14:45    Windows Error Reporting    Foutbucket LKD_0x117_Tdr:3_TdrVTR:0_IMAGE_igdkmd64.sys_GEN7_0_BBHANG, type 0
    Naam van gebeurtenis: LiveKernelEvent
    Antwoord: Niet beschikbaar
    Id van CAB-bestand: e785951a-9a7e-48df-a8f7-ed29b35453d3
    
    Handtekening van probleem:
    P1: 117
    P2: ffff9480cb0a74a0
    P3: fffff801e83d5070
    P4: 0
    P5: 1b34
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Toegevoegde bestanden:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171208-1507.dmp
    \\?\C:\WINDOWS\TEMP\WER-2368578-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBBCF.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBC1F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBC4F.tmp.txt
    
    Deze bestanden zijn mogelijk hier beschikbaar:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_e27d486821afbfe915f5c1ab2996da233c5362a_00000000_cab_134f00d2
    
    Analysesymbool: 
    Opnieuw zoeken naar oplossing: 0
    Rapport-id: d91c09a3-c1b3-42b6-ab77-84bc2ad3320f
    Rapportstatus: 268435456
    Opgedeelde bucket:
    8/12/2017 14:46    Windows Error Reporting    Foutbucket LKD_0x117_Tdr:9_IMAGE_igdkmd64.sys_GEN7_0_BBHANG, type 0
    Naam van gebeurtenis: LiveKernelEvent
    Antwoord: Niet beschikbaar
    Id van CAB-bestand: 3500e5c7-5949-4660-a1fe-1fbe742f631b
    
    Handtekening van probleem:
    P1: 117
    P2: ffff9480cafb8010
    P3: fffff801e83d5070
    P4: 0
    P5: 0
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Toegevoegde bestanden:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171208-1510.dmp
    \\?\C:\WINDOWS\TEMP\WER-2551156-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40FE.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4111.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4132.tmp.txt
    
    Deze bestanden zijn mogelijk hier beschikbaar:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_aed5da99df181e633223ea2bb9d6553cc78dd32_00000000_cab_135083f7
    
    Analysesymbool: 
    Opnieuw zoeken naar oplossing: 0
    Rapport-id: 353a1370-3daf-4067-8aed-487ec634d029
    Rapportstatus: 268435456
    Opgedeelde bucket:
    8/12/2017 14:44    Windows Error Reporting    Foutbucket LKD_0x117_Tdr:9_IMAGE_igdkmd64.sys_GEN7_0_BBHANG, type 0
    Naam van gebeurtenis: LiveKernelEvent
    Antwoord: Niet beschikbaar
    Id van CAB-bestand: 65e3a3d3-407a-4616-a596-923acbc8257d
    
    Handtekening van probleem:
    P1: 117
    P2: ffff9480cb26e4a0
    P3: fffff801e83d5070
    P4: 0
    P5: 0
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Toegevoegde bestanden:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171208-1503.dmp
    \\?\C:\WINDOWS\TEMP\WER-2120640-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER20F5.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2106.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2126.tmp.txt
    
    Deze bestanden zijn mogelijk hier beschikbaar:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_8cb02ebaf67d93dc7d3669aac231c2c622264d3_00000000_cab_134e71e0
    
    Analysesymbool: 
    Opnieuw zoeken naar oplossing: 0
    Rapport-id: 4d866204-703a-4c48-8faa-8022056855ca
    Rapportstatus: 268435456
    Opgedeelde bucket:
    8/12/2017 14:46    Windows Error Reporting    Foutbucket LKD_0x141_Tdr:6_IMAGE_igdkmd64.sys_GEN7_0_BBHANG, type 0
    Naam van gebeurtenis: LiveKernelEvent
    Antwoord: Niet beschikbaar
    Id van CAB-bestand: 838ce2e9-e884-4793-be2c-8c8eb17146a4
    
    Handtekening van probleem:
    P1: 141
    P2: ffff9480cb0a74a0
    P3: fffff801e83d5070
    P4: 0
    P5: 2a0
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Toegevoegde bestanden:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171208-1509.dmp
    \\?\C:\WINDOWS\TEMP\WER-2538875-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD71D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD72F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD74F.tmp.txt
    
    Deze bestanden zijn mogelijk hier beschikbaar:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_7ac91e7a55efea466d9ffbcdef28ee419baf1a9_00000000_cab_134fcf9b
    
    Analysesymbool: 
    Opnieuw zoeken naar oplossing: 0
    Rapport-id: de1241cc-d9c6-41c7-b29d-4257fbfaf7a6
    Rapportstatus: 268435456
    Opgedeelde bucket:
    8/12/2017 14:45    Windows Error Reporting    Foutbucket LKD_0x141_Tdr:6_IMAGE_igdkmd64.sys_GEN7_0_BBHANG, type 0
    Naam van gebeurtenis: LiveKernelEvent
    Antwoord: Niet beschikbaar
    Id van CAB-bestand: a972afdc-0fdd-4c7b-b5d0-307b258ffccd
    
    Handtekening van probleem:
    P1: 141
    P2: ffff9480cb0a74a0
    P3: fffff801e83d5070
    P4: 0
    P5: 1b34
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Toegevoegde bestanden:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171208-1506.dmp
    \\?\C:\WINDOWS\TEMP\WER-2360437-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22AB.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2338.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2397.tmp.txt
    
    Deze bestanden zijn mogelijk hier beschikbaar:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_4fb284c0b9473750822ae892d2d6fed3744ce29_00000000_cab_134ebb8b
    
    Analysesymbool: 
    Opnieuw zoeken naar oplossing: 0
    Rapport-id: 65286a4e-496f-4472-8a6d-de3ce15af7bd
    Rapportstatus: 268435456
    Opgedeelde bucket:
    8/12/2017 14:43    Windows Error Reporting    Foutbucket LKD_0x141_Tdr:6_IMAGE_igdkmd64.sys_GEN7_0_BBHANG, type 0
    Naam van gebeurtenis: LiveKernelEvent
    Antwoord: Niet beschikbaar
    Id van CAB-bestand: f93532cb-0d25-43cf-af29-0d0f5a482c88
    
    Handtekening van probleem:
    P1: 141
    P2: ffff9480cebef010
    P3: fffff801e83d5070
    P4: 0
    P5: 2a0
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Toegevoegde bestanden:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171208-1502.dmp
    \\?\C:\WINDOWS\TEMP\WER-2106750-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E84.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3EC2.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F02.tmp.txt
    
    Deze bestanden zijn mogelijk hier beschikbaar:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_b65ceefc94285dc7a8d3cde27c9faee76d0851d_00000000_cab_134d6ad0
    
    Analysesymbool: 
    Opnieuw zoeken naar oplossing: 0
    Rapport-id: 9cf55bf9-796b-4398-a2a0-bef0778bdf17
    Rapportstatus: 268435456
    Opgedeelde bucket:
    8/12/2017 15:03    Windows Error Reporting    Foutbucket LKD_0x15E_MINI_StuckOID_D010310_athw8x!MPRequest, type 0
    Naam van gebeurtenis: LiveKernelEvent
    Antwoord: Niet beschikbaar
    Id van CAB-bestand: 7f0f7306-d77f-42bf-9ab3-7a4a5a1ca94f
    
    Handtekening van probleem:
    P1: 1000015e
    P2: 25
    P3: 23
    P4: ffff9480cb73a498
    P5: d010310
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Toegevoegde bestanden:
    \\?\C:\WINDOWS\LiveKernelReports\NDIS\NDIS-20171208-1457.dmp
    \\?\C:\WINDOWS\TEMP\WER-1879859-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCFE.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD2D.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD6C.tmp.txt
    
    Deze bestanden zijn mogelijk hier beschikbaar:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000015e_81e3781d7f11f78771f34234b333264f882292f0_00000000_cab_0f7f8fd5
    
    Analysesymbool: 
    Opnieuw zoeken naar oplossing: 0
    Rapport-id: 30c2b634-da1c-425b-9feb-b836dfb91b0e
    Rapportstatus: 268435556
    Opgedeelde bucket:
    25/12/2017 22:12    Windows Error Reporting    Foutbucket LKD_0x15E_PROT_NetPnPEvent_NetEventPause_tcpip!Fl48PnpEvent, type 0
    Naam van gebeurtenis: LiveKernelEvent
    Antwoord: Niet beschikbaar
    Id van CAB-bestand: 1c3f5ff2-5f32-4fbf-991a-5b5b52d7950f
    
    Handtekening van probleem:
    P1: 1000015e
    P2: 25
    P3: 2
    P4: ffffc70e2fb99fa8
    P5: 8
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Toegevoegde bestanden:
    \\?\C:\WINDOWS\LiveKernelReports\NDIS\NDIS-20171225-2129.dmp
    \\?\C:\WINDOWS\TEMP\WER-254820234-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER369C.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER36CB.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER370A.tmp.txt
    
    Deze bestanden zijn mogelijk hier beschikbaar:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000015e_d6f65d286185d55e6bc6f8db997c26fd41f4a2e3_00000000_cab_28dda295
    
    Analysesymbool: 
    Opnieuw zoeken naar oplossing: 0
    Rapport-id: e99125d3-fb80-4df9-9ecd-1bc87908ec42
    Rapportstatus: 268435556
    Opgedeelde bucket:
    6/12/2017 16:23    Windows Error Reporting    Foutbucket LKD_0x1A1_WIN32K_CALLOUT_WATCHDOG_nt!KiSwapContext, type 0
    Naam van gebeurtenis: LiveKernelEvent
    Antwoord: Niet beschikbaar
    Id van CAB-bestand: 901b7ab9-7a66-4f40-9261-58d54002316f
    
    Handtekening van probleem:
    P1: 1a1
    P2: ffff8d0d3c154040
    P3: 0
    P4: 0
    P5: 0
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Toegevoegde bestanden:
    \\?\C:\WINDOWS\LiveKernelReports\PoW32kWatchdog\PoW32kWatchdog-20171203-1058.dmp
    \\?\C:\WINDOWS\TEMP\WER-1562375-0.sysdata.xml
    \\?\C:\WINDOWS\LiveKernelReports\PoW32kWatchdog-20171203-1058.dmp
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC3B8.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC4A3.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC4E2.tmp.txt
    
    Deze bestanden zijn mogelijk hier beschikbaar:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a1_b7d847b4297561451f11bf973d3a2642198fac30_00000000_cab_0ebd1090
    
    Analysesymbool: 
    Opnieuw zoeken naar oplossing: 0
    Rapport-id: 1f10a588-9718-49d1-8f51-18f30bc226de
    Rapportstatus: 268435456
    Opgedeelde bucket:
    Code:
    13/12/2017 22:49    Windows Error Reporting    Foutbucket 0x124_GenuineIntel_PROCESSOR_MAE, type 0
    Naam van gebeurtenis: BlueScreen
    Antwoord: Niet beschikbaar
    Id van CAB-bestand: 8561140e-9be5-4a7d-a9c5-0c85ee783b6e
    
    Handtekening van probleem:
    P1: 124
    P2: 0
    P3: ffffcb89402db028
    P4: be000000
    P5: 800400
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Toegevoegde bestanden:
    \\?\C:\WINDOWS\Minidump\121317-101218-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-920750-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC213.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC290.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC2C0.tmp.txt
    \\?\C:\Windows\Temp\WERFC6E.tmp.WERDataCollectionStatus.txt
    
    Deze bestanden zijn mogelijk hier beschikbaar:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_e786a9108a7e175f26a1d44d350a6f18ab63ea_00000000_cab_15430268
    
    Analysesymbool: 
    Opnieuw zoeken naar oplossing: 0
    Rapport-id: 3368b830-ede3-4b7c-8ebb-c2603a220f45
    Rapportstatus: 268435456
    Opgedeelde bucket:6/12/2017 16:24    Windows Error Reporting    Foutbucket 0x124_GenuineIntel_PROCESSOR_MAE, type 0
    Naam van gebeurtenis: BlueScreen
    Antwoord: Niet beschikbaar
    Id van CAB-bestand: 913a68df-20ae-43b5-a586-ee0fb9a2e110
    
    Handtekening van probleem:
    P1: 124
    P2: 0
    P3: ffffad0c17e73028
    P4: be000000
    P5: 800400
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Toegevoegde bestanden:
    \\?\C:\WINDOWS\Minidump\120617-58625-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-1562375-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC61B.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC63B.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC66B.tmp.txt
    
    Deze bestanden zijn mogelijk hier beschikbaar:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_ab6168a069c89ccc97244c95aac173f4a3d4138_00000000_cab_0ebd8e3c
    
    Analysesymbool: 
    Opnieuw zoeken naar oplossing: 0
    Rapport-id: f3ad6de6-96bc-47be-a3ca-d77063f36d2f
    Rapportstatus: 268435456
    Opgedeelde bucket:
    Code:
    Event[2177]:  Log Name: System
      Source: Display
      Date: 2017-12-08T15:10:28.811
      Event ID: 4101
      Task: N/A
      Level: Waarschuwing
      Opcode: Info
      Keyword: Klassiek
      User: N/A
      User Name: N/A
      Computer: Tim
      Description: 
    Beeldschermstuurprogramma igfx reageert niet meer en is hersteld.
    Code:
    Event[4601]:  Log Name: System
      Source: Microsoft-Windows-WER-SystemErrorReporting
      Date: 2017-12-13T23:48:50.677
      Event ID: 1018
      Task: N/A
      Level: Informatie
      Opcode: N/A
      Keyword: Klassiek
      User: N/A
      User Name: N/A
      Computer: Tim
      Description: 
    Het dumpbestand in C:\WINDOWS\MEMORY.DMP is verwijderd omdat het schijfvolume minder dan 25 GB vrije ruimte heeft.
    Code:
    Event[4600]:  Log Name: System
      Source: Microsoft-Windows-WER-SystemErrorReporting
      Date: 2017-12-13T23:48:03.908
      Event ID: 1001
      Task: N/A
      Level: Fout
      Opcode: N/A
      Keyword: Klassiek
      User: N/A
      User Name: N/A
      Computer: Tim
      Description: 
    De computer is opnieuw opgestart na een bugcontrole. De bugcontrole is 0x00000124 (0x0000000000000000, 0xffffcb89402db028, 0x00000000be000000, 0x0000000000800400). Er is een dump opgeslagen in: C:\WINDOWS\MEMORY.DMP. Rapport-id: 3368b830-ede3-4b7c-8ebb-c2603a220f45.
    Code:
    Event[3713]:  Log Name: System
      Source: Microsoft-Windows-WER-SystemErrorReporting
      Date: 2017-12-11T08:46:44.600
      Event ID: 1001
      Task: N/A
      Level: Fout
      Opcode: N/A
      Keyword: Klassiek
      User: N/A
      User Name: N/A
      Computer: Tim
      Description: 
    De computer is opnieuw opgestart na een bugcontrole. De bugcontrole is 0x00000101 (0x0000000000000030, 0x0000000000000000, 0xfffff800ea2ad180, 0x0000000000000000). Er is een dump opgeslagen in: C:\WINDOWS\MEMORY.DMP. Rapport-id: 69c12129-0eea-455a-b732-b767f411ce5d.
    Code:
    Event[3638]:  Log Name: System
      Source: Disk
      Date: 2017-12-10T21:14:14.574
      Event ID: 11
      Task: N/A
      Level: Fout
      Opcode: N/A
      Keyword: Klassiek
      User: N/A
      User Name: N/A
      Computer: Tim
      Description: 
    Het stuurprogramma heeft een controllerfout gevonden in \Device\Harddisk1\DR2.
    Code:
    Event[5004]:  Log Name: System
      Source: Disk
      Date: 2017-12-19T16:53:06.332
      Event ID: 11
      Task: N/A
      Level: Fout
      Opcode: N/A
      Keyword: Klassiek
      User: N/A
      User Name: N/A
      Computer: Tim
      Description: 
    Het stuurprogramma heeft een controllerfout gevonden in \Device\Harddisk1\DR1.
    Code:
    Event[5352]:  Log Name: System
      Source: Disk
      Date: 2017-12-22T22:08:30.146
      Event ID: 11
      Task: N/A
      Level: Fout
      Opcode: N/A
      Keyword: Klassiek
      User: N/A
      User Name: N/A
      Computer: Tim
      Description: 
    Het stuurprogramma heeft een controllerfout gevonden in \Device\Harddisk1\DR2.
    Last edited by zbook; 26 Dec 2017 at 14:57.
      My ComputerSystem Spec


 

Related Threads
Solved Clock_watchdog_timeout in BSOD Crashes and Debugging
I'm getting the CLOCK_WATCHDOG_TIMEOUT on a new build and all I am simply trying to do is run the major Win 10 update through Windows 10 Update assistant as the copy of Win 10 I have is the original from when it was first released. My screen will...
Clock_watchdog_timeout in BSOD Crashes and Debugging
I have installed Windows 10 Pro on my computer, and 3 minutes or so after it boots, the computer freezes and gives me the blue screen with "CLOCK_WATCHDOG_TIMEOUT" message. Is there a fix?
BSOD clock_watchdog_timeout in BSOD Crashes and Debugging
So I got this bsod CLOCK_WATCHDOG_TIMEOUT. PC froze at 30% while it was auto restarting. Added 2 more ram sticks and this happens a day after. Had issue with the ram's software (to control RGB). They are G.skill Trident Z RGB. Installed the...
Hi! So I have got 2 BSOD while playing. First one said whea uncorrectable error and other one said clock_watchdog_timeout. During that last BSOD it did not create a dumpfile because it stayed at 50% and I had to restart. I have attached logs to this...
So I made a new thread a few days ago but I marked it as solved because the problem didn't happen for a few days. It is happening again though. In addition to the things I listed as doing in my original post, I followed a analyst directions to...
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 05:59.
Find Us