BSOD CLOCK_WATCHDOG_TIMEOUT

Question

Hello All,

Hoping someone can help me out with a Laptop we just recently deployed. HP Pavillion 15-eg100. User is getting random BSOD with the Clock_Watchdog_Timeout.

He used to think it crashed whenever he was watching videos in chrome, but now its starting to do it randomly everywhere. I have done the normal standard steps that I can think of. Reinstalled the video drivers, ran SFC and DISM, ran numerous mem tests and processor stress tests, made sure he was on the latest BIOS version, Windows is up to date with all optional updates installed.. I have pulled the most recent dmp file. I have tried to uninstall/disable HyperVisor and VirtualMachinePlatform since we dont use it, but to no avail. Most of the time it just BSODs and will sit there and spin at 0% and wont give me a .dmp file. In the 10 or so times it has BSOD for the same stop code, i have only gotten two dmp files. Any help is greatly appreciated.

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

* *

* Bugcheck Analysis *

* *

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

HYPERVISOR_ERROR (20001)

The hypervisor has encountered a fatal error.

Arguments:

Arg1: 0000000000000011

Arg2: 0000000000237150

Arg3: 0000000000001007

Arg4: ffffe80000c91f00

Debugging Details:

---

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 4389 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 4724 

Key  : Analysis.IO.Other.Mb 

Value: 0 

Key  : Analysis.IO.Read.Mb 

Value: 0 

Key  : Analysis.IO.Write.Mb 

Value: 0 

Key  : Analysis.Init.CPU.mSec 

Value: 686 

Key  : Analysis.Init.Elapsed.mSec 

Value: 14678 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 96 

Key  : Bugcheck.Code.DumpHeader 

Value: 0x20001 

Key  : Bugcheck.Code.Register 

Value: 0x20001 

Key  : Dump.Attributes.AsUlong 

Value: 180c 

Key  : Dump.Attributes.DiagDataWrittenToHeader 

Value: 1 

Key  : Dump.Attributes.ErrorCode 

Value: 0 

Key  : Dump.Attributes.InsufficientDumpfileSize 

Value: 1 

Key  : Dump.Attributes.KernelGeneratedTriageDump 

Value: 1 

Key  : Dump.Attributes.LastLine 

Value: Dump completed successfully. 

Key  : Dump.Attributes.ProgressPercentage 

Value: 0 

Key  : Dump.Attributes.RequiredDumpfileSize 

Value: 0x9e23a4e5 

FILE_IN_CAB: 111522-10500-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x180c

Insufficient Dumpfile Size

Kernel Generated Triage Dump

BUGCHECK_CODE: 20001

BUGCHECK_P1: 11

BUGCHECK_P2: 237150

BUGCHECK_P3: 1007

BUGCHECK_P4: ffffe80000c91f00

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

ffffd1018bcb3ca8 fffff80449937821 : 0000000000020001 0000000000000011 0000000000237150 0000000000001007 : nt!KeBugCheckEx

ffffd1018bcb3cb0 fffff80449873cd6 : 0000000000000100 fffff8044960770c ffffd1018bcc1a10 ffffd1018bcb3d30 : nt!HvlSkCrashdumpCallbackRoutine+0x81

ffffd1018bcb3cf0 fffff80449836042 : 0000000000000100 ffffd1018bcb3ef0 0000000000000000 0000000000000000 : nt!KiProcessNMI+0x26d256

ffffd1018bcb3d30 fffff80449835dae : 0000000000000100 ffffd1018bcb3ef0 0000000000000000 be1739d30748cae7 : nt!KxNmiInterrupt+0x82

ffffd1018bcb3e70 fffff80447820003 : fffff8044979635a 0000000000000000 0000000000000000 0000000000000000 : nt!KiNmiInterrupt+0x26e

fffffb8e08e46d18 fffff8044979635a : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0xfffff804`47820003

fffffb8e08e46d20 fffff80449936a75 : 0000000000000000 fffff8044962af92 fffff78000000340 0000000597dbcf17 : nt!HvcallInitiateHypercall+0x6a

fffffb8e08e46dc0 fffff80478443dbe : 00000000000100de 0000000000000000 0000000597d8c154 0000000000000000 : nt!HvlRequestProcessorHalt+0x35

fffffb8e08e46df0 fffff8047844594e : 0000000000000002 fffff8044979dbec 0000000000000000 ffffd1018bc33510 : intelppm!HvRequestIdle+0x2e

fffffb8e08e46e40 fffff80449627407 : ffffa98c00000000 0000000000000000 0000000000000000 ffffd1018bc2b180 : intelppm!PepIdleExecute+0x2e

fffffb8e08e46e90 fffff8044962626b : 0000000000000000 0000000000000000 ffffffffffffffff 0000000000000000 : nt!PpmIdleExecuteTransition+0x1137

fffffb8e08e47350 fffff8044982d174 : 0000000000000000 ffffa98c0cec7040 ffffa98c3b4d3080 ffffa98c3bb3d300 : nt!PoIdle+0x67b

fffffb8e08e47540 0000000000000000 : fffffb8e08e48000 fffffb8e08e41000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x54

SYMBOL_NAME: intelppm!HvRequestIdle+2e

MODULE_NAME: intelppm

IMAGE_NAME: intelppm.sys

IMAGE_VERSION: 10.0.22621.891

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 2e

FAILURE_BUCKET_ID: 0x20001_11_237150_intelppm!HvRequestIdle

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {397b3da7-0e09-5fc1-0253-3037e84dfa80}

Followup: MachineOwner

Answer 1

Hi Chris, glad to help!

Answer 2

Dave, again thank you for the response. I have ran the built in windows memory diagnostic tool and the one built into the HP Support Assistant and both found no errors. I will also try the one you suggested just to be safe. I will also re-install the chipset drivers and get back with you.

Thanks,

Answer 3

Hi Chris,

Your minidump files indicates memory (RAM) corruption and the Intel Chipset driver.

1

Go to the support page for your PC or Motherboard on the manufacturers website, then from there, download and install the version of Chipset drivers they recommend and while there, check for any BIOS update that may need to be installed

2

Wait to see if your system stabilizes, if not, the best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors

Answer 4

Thank You for your response Dave,

I have uploaded the two dmp files that I could get. Hopefully this works:

DMP Files

Thanks,

Answer 5

Hi Chris,

I am Dave, I will help you with this.

Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so we can take a look for you.