Windows 10: WINDOWS 10 - BSOD - DELL G5 15 5590 - CLOCK_WATCHDOG_TIMEOUT and WHEA_UNCORRECTABLE_ERROR

Discus and support WINDOWS 10 - BSOD - DELL G5 15 5590 - CLOCK_WATCHDOG_TIMEOUT and WHEA_UNCORRECTABLE_ERROR in Windows 10 BSOD Crashes and Debugging to solve the problem; Dear all, i'm having this problem with my Dell G5 15 5590 i purchased 3 months ago. Last friday i got some updates from Intel® Driver & Support... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Acapovilla, Nov 9, 2020.

  1. WINDOWS 10 - BSOD - DELL G5 15 5590 - CLOCK_WATCHDOG_TIMEOUT and WHEA_UNCORRECTABLE_ERROR


    Dear all,


    i'm having this problem with my Dell G5 15 5590 i purchased 3 months ago. Last friday i got some updates from Intel® Driver & Support Assistant. I was running COD Warzone when i got a BSOD after changing the antisotropic. My laptop wouldn't boot either normal or in safe mode. BSOD errors where:


    1. clock_watchdog_timeou

    2. whea_uncorrectable_error.


    Somehow I managed to get to the BIOS and start changing some settings one by one and trying to get the laptop to boot. Suddenly i found out that when the laptop wasn't plugged in it could run but inmediately after i plugged it, it crashes or freezes. I then decided to fully charge it and try to rollback some drivers while unplugged to see if that was the problem. I have even downgraded the BIOS to 1.12 version, nothing worked. Unfortunatelly the only way i could make the laptop run while plugged is with only one processor available. Every time i set all the processors back and plug it it crashes.


    I debugged a .dump file with Windbg but i have any knowlage to read it. Here are the results:



    ---------------------------------------------------------------------------------------------------------------------------------------



    Microsoft R Windows Debugger Version 10.0.19041.1 AMD64

    Copyright c Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Users\capov\Desktop\110920-10906-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available





    ************* Path validation summary **************

    Response Time ms Location

    Deferred SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

    Executable search path is:

    Windows 10 Kernel Version 19041 MP 8 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Machine Name:

    Kernel base = 0xfffff802`11400000 PsLoadedModuleList = 0xfffff802`1202a3b0

    Debug session time: Mon Nov 9 17:42:21.520 2020 UTC - 3:00

    System Uptime: 0 days 0:08:45.376

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ................................................................

    .........................

    Loading User Symbols

    Loading unloaded module list

    ...............

    For analysis of this file, run !analyze -v

    1: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    WHEA_UNCORRECTABLE_ERROR 124

    A fatal hardware error has occurred. Parameter 1 identifies the type of error

    source that reported the error. Parameter 2 holds the address of the

    WHEA_ERROR_RECORD structure that describes the error conditon.

    Arguments:

    Arg1: 0000000000000000, Machine Check Exception

    Arg2: ffffe50ebae7d028, Address of the WHEA_ERROR_RECORD structure.

    Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.

    Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.



    Debugging Details:

    ------------------



    fffff8021200f340: Unable to get Flags value from nt!KdVersionBlock

    fffff8021200f340: Unable to get Flags value from nt!KdVersionBlock

    *************************************************************************

    *** ***

    *** ***

    *** Either you specified an unqualified symbol, or your debugger ***

    *** doesn't have full symbol information. Unqualified symbol ***

    *** resolution is turned off by default. Please either specify a ***

    *** fully qualified symbol module!symbolname, or enable resolution ***

    *** of unqualified symbols by typing ".symopt- 100". Note that ***

    *** enabling unqualified symbol resolution with network symbol ***

    *** server shares in the symbol path may cause the debugger to ***

    *** appear to hang for long periods of time when an incorrect ***

    *** symbol name is typed or the network symbol server is down. ***

    *** ***

    *** For some commands to work properly, your symbol path ***

    *** must point to .pdb files that have full type information. ***

    *** ***

    *** Certain .pdb files such as the public OS symbols do not ***

    *** contain the required information. Contact the group that ***

    *** provided you with these symbols if you need this command to ***

    *** work. ***

    *** ***

    *** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***

    *** ***

    *************************************************************************

    fffff8021200f340: Unable to get Flags value from nt!KdVersionBlock

    *************************************************************************

    *** ***

    *** ***

    *** Either you specified an unqualified symbol, or your debugger ***

    *** doesn't have full symbol information. Unqualified symbol ***

    *** resolution is turned off by default. Please either specify a ***

    *** fully qualified symbol module!symbolname, or enable resolution ***

    *** of unqualified symbols by typing ".symopt- 100". Note that ***

    *** enabling unqualified symbol resolution with network symbol ***

    *** server shares in the symbol path may cause the debugger to ***

    *** appear to hang for long periods of time when an incorrect ***

    *** symbol name is typed or the network symbol server is down. ***

    *** ***

    *** For some commands to work properly, your symbol path ***

    *** must point to .pdb files that have full type information. ***

    *** ***

    *** Certain .pdb files such as the public OS symbols do not ***

    *** contain the required information. Contact the group that ***

    *** provided you with these symbols if you need this command to ***

    *** work. ***

    *** ***

    *** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***

    *** ***

    *************************************************************************

    *** WARNING: Unable to verify timestamp for win32k.sys



    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 3



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-5S3AUDE



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 3



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 75



    Key : Analysis.System

    Value: CreateObject





    BUGCHECK_CODE: 124



    BUGCHECK_P1: 0



    BUGCHECK_P2: ffffe50ebae7d028



    BUGCHECK_P3: be000000



    BUGCHECK_P4: 800400



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    PROCESS_NAME: System



    STACK_TEXT:

    ffff9701`665068e8 fffff802`118b31ca : 00000000`00000124 00000000`00000000 ffffe50e`bae7d028 00000000`be000000 : nt!KeBugCheckEx

    ffff9701`665068f0 fffff802`0e0b15b0 : 00000000`00000000 ffffe50e`bae7d028 ffffe50e`ba243790 ffffe50e`bae7d028 : nt!HalBugCheckSystem+0xca

    ffff9701`66506930 fffff802`119b4d3e : 00000000`00000000 ffff9701`665069d9 ffffe50e`bae7d028 ffffe50e`ba243790 : PSHED!PshedBugCheckSystem+0x10

    ffff9701`66506960 fffff802`118b4af1 : ffffe50e`d2098070 ffffe50e`d2098070 ffffe50e`ba2437e0 ffffe50e`ba243790 : nt!WheaReportHwError+0x46e

    ffff9701`66506a40 fffff802`118b4e63 : 00000000`00000001 ffffe50e`ba2437e0 ffffe50e`ba243790 00000000`00000001 : nt!HalpMcaReportError+0xb1

    ffff9701`66506bb0 fffff802`118b4d40 : ffffe50e`b9efac68 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0xef

    ffff9701`66506c00 fffff802`118b4f91 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0

    ffff9701`66506c40 fffff802`118b41fb : 00000000`00000000 00000000`00000000 ffff9701`66506ed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9

    ffff9701`66506c70 fffff802`118b6a45 : ffffe50e`b9efac68 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x5f

    ffff9701`66506ca0 fffff802`1190c179 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35

    ffff9701`66506cd0 fffff802`118042fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9

    ffff9701`66506d00 fffff802`11803fb7 : 00000000`00000000 fffff802`11803eec 00000000`00000002 00000000`00000000 : nt!KxMcheckAbort+0x7a

    ffff9701`66506e40 fffff802`275d138f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277

    ffff8980`ad42f598 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x1f





    MODULE_NAME: GenuineIntel



    IMAGE_NAME: GenuineIntel.sys



    STACK_COMMAND: .thread ; .cxr ; kb



    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR__UNKNOWN



    OS_VERSION: 10.0.19041.1



    BUILDLAB_STR: vb_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {86f02343-3a24-6d22-b341-ad6c04114faf}



    Followup: MachineOwner

    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------


    Laptop specs:


    IntelR CoreTM i5-9300H CPU @ 2.40GHz Turbo Boost 4.1 GHz

    x2 16gb RAM DDR4 2666mhz 32 total

    512gb SSD NVMe WDS500G3X0C-00SJ

    nVidia GTX 1650 4gb vram

    :)
     
    Acapovilla, Nov 9, 2020
    #1
  2. Tintai Win User

    BSOD whea_uncorrectable_error and clock_watchdog_timeout

    Hello,

    After Cmos reset and clean Windows 10 install I'm started getting some BSODs.
    First time I've got whea_uncorrectable_error and some time later clock_watchdog_timeout.

    Now I'm getting clock_watchdog_timeout all the time when I try to start AIDA64 stability test and in the middle game of CS:GO.

    Here is dump from bluescreenview:
    http://tintaiexcess.com/dmp.htm

    And here is the dump files from "C:\Windows\Minidump":
    http://www.mediafire.com/download/q2oy1mc5ku7girx/080315-7468-01.dmp
    http://www.mediafire.com/download/ap25qa4ilr4gtc0/080315-7359-01.dmp

    My CPU is running at 4.6G at 1.328V. RAM at 1866Mhz at 1.5V.
    Stock looks stable.

    Thanks
    Tintai
     
    Tintai, Nov 9, 2020
    #2
  3. BSOD whea_uncorrectable_error and clock_watchdog_timeout

    drop your overclock to stock and run it, W10 has some teething to get through
     
    eidairaman1, Nov 9, 2020
    #3
  4. Steevo Win User

    WINDOWS 10 - BSOD - DELL G5 15 5590 - CLOCK_WATCHDOG_TIMEOUT and WHEA_UNCORRECTABLE_ERROR

    BSOD whea_uncorrectable_error and clock_watchdog_timeout

    I disagree, it is hardware, windows 10 is using more of the advanced instruction abilities to speed up the OS than Windows 8, just like when we took X86 stable overclocks into X64 and they failed, more data is being moved and used and the chances for failure are significantly higher, and the rounding that every processor does didn't add up in X64.

    So as previously suggested, add more volts, or back down the overclock.


    Windows 8, and 7 drivers work in Windows 10 as the kernel is very similar, and MS is updating hardware with whatever "stable" WHQL they have for the piece of hardware based off its Hardware ID.

    I am fairly certain without even looking that the memory address referenced in your dump files will be very low, and may even be in the processor cache with a pointer to the RAM address.


    Yep, your second BSOD referenced "3594f" which is in HEX, and correlates to "219,471" which is the number in Kb from 0 that was in use, so a "101" and "124"BSOD with a very low memory address to me smells exactly like more core voltage needed, or a lower overclock.
     
    Steevo, Nov 9, 2020
    #4
Thema:

WINDOWS 10 - BSOD - DELL G5 15 5590 - CLOCK_WATCHDOG_TIMEOUT and WHEA_UNCORRECTABLE_ERROR

Loading...
  1. WINDOWS 10 - BSOD - DELL G5 15 5590 - CLOCK_WATCHDOG_TIMEOUT and WHEA_UNCORRECTABLE_ERROR - Similar Threads - BSOD DELL 5590

  2. Dell Latitude 5590 - BSOD - CRITICAL_PROCESS_DIED

    in Windows 10 BSOD Crashes and Debugging
    Dell Latitude 5590 - BSOD - CRITICAL_PROCESS_DIED: Hi, I followed the instructions posted by ZigZag3143 MS -MVP, "BSOD Finding and fixing them", and below is the link for the mini dump files and my system's .NFO file. I've had two BSODs this month and would appreciate any assistance you can offer. Thanks!...
  3. Multiple of Random BSOD on Dell G5

    in Windows 10 BSOD Crashes and Debugging
    Multiple of Random BSOD on Dell G5: Hello, Please i have big problem lately I have many randomly BSOD with caused by Ntoskrnl.exe ! I will join the last 2 Minimum files! https://1drv.ms/u/s!AvGr5YVKmHnsgelKEfCAytEEwoR62Q https://1drv.ms/u/s!AvGr5YVKmHnsgelJDC3PEUEHOtyfAg?e=BEb2PQ Can you help...
  4. Bsod: Clock_watchdog_timeout

    in Windows 10 BSOD Crashes and Debugging
    Bsod: Clock_watchdog_timeout: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online. - log v2 Windows 10 1909 18363.1016 I've upgraded my CPU to a Ryzen 3600, with new mobo and DDR4 ram to boot. Everything was fine for the first month or so, but now I got multiple BSOD of the...
  5. WHEA_UNCORRECTABLE_ERROR Common & Clock_WatchDog_Timeout Rare

    in Windows 10 BSOD Crashes and Debugging
    WHEA_UNCORRECTABLE_ERROR Common & Clock_WatchDog_Timeout Rare: Hello, I purchased my computer recently, instead of building it myself and it seems to have come back to bite me. I have been having BSOD's atleast once or twice a day, usually WHEA_UNCORRECTABLE_ERROR and rarely Clock_WatchDog_Timeout. I have analyzed the dumpfiles and...
  6. CLOCK_WATCHDOG_TIMEOUT and WHEA_UNCORRECTABLE_ERROR 4 times within an hour.

    in Windows 10 BSOD Crashes and Debugging
    CLOCK_WATCHDOG_TIMEOUT and WHEA_UNCORRECTABLE_ERROR 4 times within an hour.: I've had this issue for a couple days now, but today is a really bad day for it. It started after enabling my xmp profile which I have done in the past, but still with blue screens, so I would disable it. It is currently disabled and has been for a couple days, but I'm still...
  7. Dell g5 15 how to set downloads to D Drive?

    in Windows 10 Drivers and Hardware
    Dell g5 15 how to set downloads to D Drive?: I recently purchased the Dell g5 15 gaming laptop from currys. I downloaded Adobe Premier and World if warcraft. Now my C drive is full. I wanted to download after edfects and it says my driver is full. So i went to settings to change ir so all things i download go directly...
  8. BSOD Whea_Uncorrectable_Error into multiple Clock_Watchdog_Timeout

    in Windows 10 BSOD Crashes and Debugging
    BSOD Whea_Uncorrectable_Error into multiple Clock_Watchdog_Timeout: Hello there! Yesterday evening, as I was playing Counter-Strike: Global Offensive, I received a BSOD "Whea_Uncorrectable_Error". After my computer did the usual reboot, after having logged into Windows 10, in less than a minute the PC crashed again with a...
  9. CLOCK_WATCHDOG_TIMEOUT BSOD

    in Windows 10 BSOD Crashes and Debugging
    CLOCK_WATCHDOG_TIMEOUT BSOD: Hello All, My computer has been experiencing BSOD's starting last week. The BSOD will only occur while I am playing a videogame and even then the time in which the BSOD occurs will vary each time. I could have just booted the game or have been playing for an hour. The error...
  10. clock_watchdog_timeout and whea_uncorrectable_error

    in Windows 10 BSOD Crashes and Debugging
    clock_watchdog_timeout and whea_uncorrectable_error: Hi thanks in advance I woke up and my PC was in the bios screen saying there was a CPU fan error I am using a custom water loop system so this should have been set to ignore already. I went into bios to set it back to ignore and saved into windows then started to get BSOD so...