F5F Stay Refreshed Software Operating Systems Debug check for DPC_WATCHDOG_VIOLATION at line 133

Debug check for DPC_WATCHDOG_VIOLATION at line 133

Debug check for DPC_WATCHDOG_VIOLATION at line 133

S
Samheardofgod
Junior Member
35
03-30-2022, 06:39 AM
#1
The Win 2016 server is restarting unexpectedly. The minidump analysis reveals a DPC watchdog violation: PC_WATCHDOG_VIOLATION (133). The DPC detected a long duration at an IRQL of DISPATCH_LEVEL or higher. Supporting arguments include: Arg1 – 0000000000000001, indicating the system stayed at DISPATCH_LEVEL for a significant time; Arg2 – 0000000000001e00, marking the watchdog interval; Arg3 – fffff800d85a8540, pointing to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK with extra details. Further below, the entry shows: SYMBOL_NAME: hpqilo3chif+1d6b MODULE_NAME: hpqilo3chif IMAGE_NAME: hpqilo3chif.sys STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 1d6b FAILURE_BUCKET_ID: 0x133_ISR_hpqilo3chif!unknown_function OS_VERSION: 10.0.14393.4350 BUILDLAB_STR: rs1_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {fd87dd5a-420d-b9b7-7814-2d56e13547ee} I’ve attached the minidump for reference. Any assistance would be greatly appreciated. Thanks, Real 050221-25078-01.dmp
S
Samheardofgod
03-30-2022, 06:39 AM #1

The Win 2016 server is restarting unexpectedly. The minidump analysis reveals a DPC watchdog violation: PC_WATCHDOG_VIOLATION (133). The DPC detected a long duration at an IRQL of DISPATCH_LEVEL or higher. Supporting arguments include: Arg1 – 0000000000000001, indicating the system stayed at DISPATCH_LEVEL for a significant time; Arg2 – 0000000000001e00, marking the watchdog interval; Arg3 – fffff800d85a8540, pointing to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK with extra details. Further below, the entry shows: SYMBOL_NAME: hpqilo3chif+1d6b MODULE_NAME: hpqilo3chif IMAGE_NAME: hpqilo3chif.sys STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 1d6b FAILURE_BUCKET_ID: 0x133_ISR_hpqilo3chif!unknown_function OS_VERSION: 10.0.14393.4350 BUILDLAB_STR: rs1_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {fd87dd5a-420d-b9b7-7814-2d56e13547ee} I’ve attached the minidump for reference. Any assistance would be greatly appreciated. Thanks, Real 050221-25078-01.dmp

I
ImperialNerF
Member
68
03-30-2022, 06:39 AM
#2
I didn't realize I was linked to ILO during the previous incident.
I
ImperialNerF
03-30-2022, 06:39 AM #2

I didn't realize I was linked to ILO during the previous incident.

J
jpt01
Junior Member
46
03-30-2022, 06:39 AM
#3
After further checking, I realized the update HP sent me for ILO was outdated. I downloaded and installed the newest version. Let's see what happens.
J
jpt01
03-30-2022, 06:39 AM #3

After further checking, I realized the update HP sent me for ILO was outdated. I downloaded and installed the newest version. Let's see what happens.