• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1983
  • Last Modified:

Server reboot with bugcheck

Hi guys,
Have a Windows2003 Citrix server that did an unexpected shutdown, cant see much in the event logs at the time only the bugcheck msg. Event ID 1001
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009c (0x00000000, 0xf77452b0, 0xbe000300, 0x20030169). A dump was saved in C:\windows\memory.dmp

Have had a look at the dump file but it doesnt say much, see below any ideas?


FAULTING_MODULE: 80800000 nt


BUGCHECK_STR:  0x9C_GenuineIntel


LAST_CONTROL_TRANSFER:  from 80a84154 to 8087c480

WARNING: Stack unwind information not available. Following frames may be wrong.
f773d280 80a84154 0000009c 00000000 f773d2b0 nt!KeBugCheckEx+0x1b
f773d3b4 80a7b86f f7737fe0 00000000 00000000 hal!KeStallExecutionProcessor+0x388
00000000 00000000 00000000 00000000 00000000 hal+0x186f

STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  ntkrnlmp.exe


Followup: MachineOwner
  • 3
1 Solution

The BSOD is consistant with a hardware error. Have you installed anything from Intel lately?
FSIrelandAuthor Commented:
No nothing at all.
OK, the secret is out:

This is the article I use a lot to help folks overcome BSOD:

Where it says:
(Click to consult the online MSDN article  http://msdn.microsoft.com/en-gb/library/ms795775.aspx .)
This is a hardware issue: an unrecoverable hardware error has occurred. The parameters have different meanings depending on what type of CPU you have but, while diagnostic, rarely lead to a clear solution. Most commonly it results from overheating, from failed hardware (RAM, CPU, hardware bus, power supply, etc.), or from pushing hardware beyond its capabilities (e.g., overclocking a CPU).
Error Message: STOP: 0x0000009C... {http://support.microsoft.com/kb/329284} Win XP
Understanding and Troubleshooting the Stop 0x0000009C Screen { http://support.microsoft.com/kb/162363 } Win NT4, Win 2000

http://msdn.microsoft.com/en-gb/library/ms795775.aspx tells you what the parameters are, depending on your OS.

SO:> 0x9c is a hardware issue
Parameter 1,2,3, and 4 can be found on the MSDN article.

Please, before we go swapping out hardware, lets test a couple things:
1) download speed fan and check out the CPU cores for heat. They shouldn't be above about 52 degrees C. Being in a controlled environment may slow down the Heat problems on a CPU, but not resolve it. So, you may be going along and all of a sudden heat up to the point of failure.

2) Then consider doing a thorough memtest.
For x86 operating systems:

I truly beleive this is a memory issue, (especially after seeing the IMAGE_NAME:  ntkrnlmp.exe within the bugcheck)
Something to use as a reference to ntkrnlmp.exe:

That says a plausible issue with the ntkrnlmp.exe is a bad memory stick:

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now