Hi!
I have been dealing some some issues for the last couple mo months now. A VM with Windows Server 2019 Standard is facing BSOD every weekend!!!! As for weekdays, working like a charm!! BSOD error is HAL_INITIALIZATION_FAILED.
VM is installed on VMware ESXi 6.7.0 Update 3 (Build 17700523), running on a Cisco UCS C240 M5L.
Memory.dmp file analysis show as below:
Bugcheck Analysis *
HAL_INITIALIZATION_FAILED (5c)
Arguments:
Arg1: 0000000000000115
Arg2: fffff7a0c00164b0
Arg3: 0000000000026254
Arg4: ffffffffc0000001
Debugging Details:
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 2
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on CY-CTBACKUP001
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 9
Key : Analysis.Memory.CommitPeak.Mb
Value: 64
Key : Analysis.System
Value: CreateObject
VIRTUAL_MACHINE: VMware
BUGCHECK_CODE: 5c
BUGCHECK_P1: 115
BUGCHECK_P2: fffff7a0c00164b0
BUGCHECK_P3: 26254
BUGCHECK_P4: ffffffffc0000001
ADDITIONAL_DEBUG_TEXT: Halfailures structure in bugcheck.cpp needs updated. Please information OCA (alias:werka).
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
PROCESS_NAME: System
STACK_TEXT:
ffffcc00`b637feb8 fffff800`4a04bbf2 : 00000000`0000005c 00000000`00000115 fffff7a0`c00164b0 00000000`00026254 : nt!KeBugCheckEx
ffffcc00`b637fec0 fffff800`4a04b572 : 00000040`d6a54b55 00000000`00026253 fffff7a0`c0017410 ffffee05`bb44f490 : hal!HalpVpptUpdatePhysicalTimer+0x13e
ffffcc00`b637ff00 fffff800`4a001276 : 00000040`d6a54b55 ffff9782`498a0a00 ffffee05`bb44f510 00000000`00000000 : hal!HalpVpptAcknowledgeInterrupt+0x102
ffffcc00`b637ff30 fffff800`4a183505 : 00000040`d6a1e2a8 ffff9782`498a0a00 ffff9782`498a0ab0 ffffcf16`ad48a9dd : hal!HalpTimerClockInterrupt+0x36
ffffcc00`b637ff60 fffff800`4a256eaa : ffffee05`bb44f510 ffff9782`498a0a00 00000000`0000034e ffff9782`498a0a00 : nt!KiCallInterruptServiceRoutine+0xa5
ffffcc00`b637ffb0 fffff800`4a2573f7 : 00000000`00000001 00000000`00000000 ffffee05`bb44f5c0 00000000`00000001 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffee05`bb44f490 fffff800`4a258ea2 : ffffffff`00000000 ffffcc00`b62e6180 ffffcc00`b62f6480 ffff9782`504d7080 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffee05`bb44f620 00000000`00000000 : ffffee05`bb450000 ffffee05`bb449000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x32
SYMBOL_NAME: nt!KiCallInterruptServiceRoutine+a5
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: a5
FAILURE_BUCKET_ID: 0x5C_nt!KiCallInterruptServiceRoutine
OS_VERSION: 10.0.17763.1
BUILDLAB_STR: rs5_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8e155cd0-c545-25d5-7ee1-936e57893c8c}
Followup: MachineOwner
3: kd> !blackboxbsd
Stream size mismatch (expected = 176, read = 168)
3: kd> !blackboxpnp
PnpActivityId : {00000000-0000-0000-0000-000000000000}
PnpActivityTime : 132644882536502555
PnpEventInformation: 3
PnpEventInProgress : 0
PnpProblemCode : 24
PnpVetoType : 0
DeviceId : SWD\MMDEVAPI\{3.0.0.00000002}.{6C26BA7D-F0B2-4225-B422-8168C5261E45}
VetoString :
3: kd> lmvm nt
Browse full module list
start end module name
fffff800`4a09e000 fffff800`4ab09000 nt (pdb symbols) C:\ProgramData\dbg\sym\ntkrnlmp.pdb\7C131E18E159B11A8B15A0E63C2BEA261\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 444E5B3E (This is a reproducible build file hash, not a timestamp)
CheckSum: 0093F534
ImageSize: 00A6B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
Opened a case with VMware, suggested updating some drivers didn't help.
Any more suggestions??
Thanks!