New memory.dmp file, new challenge... :-)
After loading file to WinDBG and running a standard set of commands I am left with following relevant information.
BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err These errors match the format 0000 1PPT RRRR IILL
Concatenated Error Code: -------------------------- _VAL_UC_EN_ADDRV_PCC_BUSCONNERR_0
This error code can be reported back to the manufacturer. They may be able to provide additional information based upon this error. All questions regarding STOP 0x9C should be directed to the hardware manufacturer.
BUGCHECK_STR: 0x9C_IA32_GenuineIntel <---- Error 0x0000009C
DEFAULT_BUCKET_ID: DRIVER_FAULT
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 80a84154 to 8087c480
STACK_TEXT:
808a0770 80a84154 0000009c 00000000 808a07a0 nt!KeBugCheckEx+0x1b
808a08a4 80a7b86f 80042000 00000000 00000000 hal!HalpMcaExceptionHandler+0x11e
808a08a4 f6932f36 80042000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77
808a3600 80839b02 00000000 0000000e 00000000p3!AcpiC1Idle+0x12
808a3604 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xa
STACK_COMMAND: kb
FOLLOWUP_IP:
p3!AcpiC1Idle+12
f6932f36 6a00 push 0x0
FAULTING_SOURCE_CODE:
SYMBOL_STACK_INDEX: 3
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: p3!AcpiC1Idle+12
MODULE_NAME: p3
IMAGE_NAME: p3.sys <---- Here it looks like p3.sys driver caused the crash
DEBUG_FLR_IMAGE_TIMESTAMP: 45d6972c
FAILURE_BUCKET_ID: 0x9C_IA32_GenuineIntel_p3!AcpiC1Idle+12
BUCKET_ID: 0x9C_IA32_GenuineIntel_p3!AcpiC1Idle+12
Followup: MachineOwner---------
From stack it looks like p3.sys driver (Processor Device Driver) caused the crash of the server. One the other hand error 0x9C (0x0000009C) indicates hardware error.
Best article on the subject of 0x000000C (Understanding and troubleshooting the "Stop 0x0000009C" screen) states:
"The Pentium and Pentium Pro processors provide a mechanism to detect and to report hardware-related problems such as memory parity errors and cache errors. To signal a hardware error, the processor signals the detection of a machine check error by generating a machine check exception (Interrupt 18). Windows NT simply reports the fact that the error occurred and displays parameters that you can use to decode the exception. Contact your hardware vendor or processor manufacturer for information regarding the Machine Check Architecture or consult the Intel Pentium Pro Family Developer's Manual - Volume 3: Operating System Writer's Manual."
Above information is also displayed in dump file.
Full analysis of the dump file can be found here.
Possible resolutions:
Best recommendation suggested by above KB article is "contact your hardware vendor"
Problem caused by computer hardware
What you can do on your own?
- Test your hardware (memory, processor, ...)
- Check hardware connections
- Think about recent hardware changes (incompatible components)
- Think about recent configuration changes (e.g. enable or disable ACPI)
- Update BIOS and other hardware (firmware)
- Stress test your hardware (best done before going into production with the server)