Unexplained Stop Error 0x0000009c

[CHR1S]

Server 2003 R2 - 0x0000009c (0x00000005, 0xf77552b0, 0xb2000010, 0x80200e0f)

It happens randomly, during the night, under no load with no tasks or backups running.
There are no errors in the event log or anything relevant.
The server is performing fine.

The limited info I can find says its a hardware/stress/overheating issue, but I cant see how.

Anyone able to help with this?

Thanks

Chris

[themightymrp]

Anything in the system event logs? The error 0x0000009c is usually some kind of hardware fault. On occasions when I have seen this it wsa an iffy RAM stick. Could you run a memory tester program through it?

[CHR1S]

As I said, not a thing in the event log, if it wasn't for the pop-up telling me the server restarted I would never know it happened.

Ill try to get the server brought down for a RAM test but its not something I can just squeeze in

[SYNACK]

Upgrade the BIOS/firmware of the components. Clean out the fans/heatsinks/circut boards with compressed air. Check the hardware even log - if the system has one for cpu overheats. Clean off and replace the thermal paste between the CPU and heatsyncs. Run a chkdsk on the hard drives and run a chek on the RAID if the controller allows for it. Update the drivers and install any vendor monitering/logging software that the server vendor may have avalible.

All just suggestions but may help shake out the fault.

[CHR1S]

Just had the OFSTED call, going to lower this down my list for a few days

[themightymrp]

Ooo unlucky

[CHR1S]

Right, Ive had some time to investigate this further.

Had 56 days of uptime and today it randomly BSODed, here is the minidump info for the faulting items -

Crash List


Created by using BlueScreenView

Filename	Address In Stack	From Address	To Address	Size	Time Stamp	Time String	Product Name	File Description	File Version	Company	Full Path
hal.dll	hal.dll+a154	0x80a5a000	0x80a86000	0x0002c000	0x45d6972a	17/02/2007 05:48:26	 	 	 	 	 
ntkrnlpa.exe	ntkrnlpa.exe+9db40	0x80800000	0x80a5a000	0x0025a000	0x4b7a90ad	16/02/2010 12:33:49	Microsoft® Windows® Operating System	NT Kernel & System	6.1.7601.17640 (win7sp1_gdr.110622-1506)	Microsoft Corporation	C:\Windows\system32\ntkrnlpa.exe

Any ideas?

[TheMan100]

Right, Ive had some time to investigate this further.

Had 56 days of uptime and today it randomly BSODed, here is the minidump info for the faulting items -

Crash List

Possibly a dodgy RAM module; try and run Memtest on it to see if any errors come up. Also, have you made sure all of the drivers are up to date?


Created by using BlueScreenView

Filename	Address In Stack	From Address	To Address	Size	Time Stamp	Time String	Product Name	File Description	File Version	Company	Full Path
hal.dll	hal.dll+a154	0x80a5a000	0x80a86000	0x0002c000	0x45d6972a	17/02/2007 05:48:26	 	 	 	 	 
ntkrnlpa.exe	ntkrnlpa.exe+9db40	0x80800000	0x80a5a000	0x0025a000	0x4b7a90ad	16/02/2010 12:33:49	Microsoft® Windows® Operating System	NT Kernel & System	6.1.7601.17640 (win7sp1_gdr.110622-1506)	Microsoft Corporation	C:\Windows\system32\ntkrnlpa.exe

Any ideas?

Possibly a dodgy RAM module; try and run Memtest on it to see if any errors come up. Also, have you made sure all of the drivers are up to date?

[CHR1S]

Going to bring the server down during the strike Wednesday and run it then.

[SYNACK]

Depending on the server Memtest probably won't pick it as ECC may hide most if the errors most of the time, use the server vendors testing tools or run memtest then check the ECC logs/system logs in bios.