Proliant ML 530 G2 Bugcheck 0x0000001E, Exception code 0x80000004, W2K SP # 4

[SEBEMISMNUSA]

A HP Proliant ML 530 G2 is intermittently crashing and rebooting. I am trying to determine why.

There are no errors being listed from the Insight agents nor from the monitoring Compaq Insight Manager 5.5 software nor the HP Insight Manager 7 sp2.3 software. The web page for the computer, https://computer:2381, also lists no errors - nothing failed nor degraded.

I am also aware of the Microsoft Technet article - KB148978.

Bugcheck 0x0000001E with Exception Code of 0x80000004
When a bugcheck 0000001e error occurs with an exception code of 80000004, it may indicate that there is faulty hardware on the computer.

This computer has been running fine since November 22, 2002 until March 29, 2004 - no crashes.
I have included the survey file for this computer as an attachment. Listed at the top of this attachment are the crash dump analysies. It has many more details on this computer (hardware installed - all HP, software installed W2k server sp # 4 plus the numerous Microsoft security updates. On April 21, 2004, I installed the Microsoft security updates MS04-011 to MS04-014. I also installed the Proliant Support Pack version 7.00A.

**** The system event view messages ******


May 5, 2004
Date: 05/05/204 Source: EventLog
Time: 10:43 . . Category: None
Type: Error Event ID: 6008
User: n/a
Description: The previous system shutdown at 10:27 P.M. on 5/5/2004 was unexpected.
and the alert from Insight Manager

---Original Message-----
From:
Sent: Wednesday, May 05, 2004 10:44 PM
To:
Subject: ASR Recovery Complete (Ver. 3): SERVER Minor Event HTTP://xxxxx:280

Event Name: ASR Recovery Complete (Ver. 3)
Event originator: xxxx
Event Severity: Minor
Event received: 05-May-2004, 22:43:56

Event description:The server is operational again. The server has previously been shutdown by the Compaq Automatic Server Recovery (ASR) feature and has just become operational again.
Assigned To:
Comment:

May 4, 2004

Date: 5/4/2004 Source: SaveDump
Time: 3:07:17 P.M. Category: None
Type: Information Event ID: 1001
User: N/A
Computer: DS098039
Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0x80000004,0x88ddf2a9,0x88ddf18a, 0xbe3ff59c). Microsoft Windows 2000 [15.2195]. A dump was saved in c:\winnt\memory.dmp.

5/4/2004 1:41 P.M.
Date: 5/4/2004 Source: SaveDump
Time: 2:00:31 PM Category: None
Type: Information Event ID: 1001
User: N/A Computer: DS098039
Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0x80000004, 0x88df22a9, 0x000000e1, 0x00000001) Microsoft Windows 2000 [(v15.2.2195]. A dump was saved in C:\WINNT\memory.dmp

March 29, 2004

Date: 3/29/2004 Source: SaveDump
Time: 7:47:12 A.M. Category: None
Type: Information Event Id: 1001
User: N/A
Computer: xxxxx
The computer has rebooted from a bugcheck. The bugcheck was:
0x000000d1 (0x1e68be67, 0x000000ff, 0x00000000, 0x1e68be67). Microsoft Windows 2000 [v15.2195. A dump was saved in C:\WINNT\MEMORY.DMP.
Other event viewer messages:
Date: 3/29/2004 Source: EventLog
Time: 7:41 A.M. Category: None

Type: Error Event Id: 6008
Computer: xxxxx
The previous system shutdown at 7:24:02 A.M. on 3/29/2004 was unexpected.

End

[Sean Marshall_1]

I have seen this issue before on an identical server. The problem was a faulty DIMM. Have you tried running with the minimum amount of memory? Just a suggestion

Hope it helps

[JohnWRuffo]

I am inclined to agree with Sean (CCISS and many other driver/process errors all over the place), but your inspect also shows that your bios is a bit out of date.

Try loading the new bios (Intel processor fixes included):
http://h18000.www1.hp.com/support/files/server/us/download/21276.html

Let us know if it does not clear up?
-john

[SEBEMISMNUSA]

8/13/2004

In May 2004, using the Version control manager and the version control agent, along with all the updates from HP's web site, I updated all the firmware to current versions. The computer has not crashed since (August 2004)

Scott Bemis

[SEBEMISMNUSA]

Or as posted in a different thread

Jun 3, 2004 13:20:18 GMT N/A: Question Author

--------------------------------------------------------------------------------
June 3, 2004

In summary, using HP Version Control Manager 2.0x and the Version control agent 2.0x., I quickly identified what firmware and drivers were not current. I updated everything (as I was planning to contact HP in case the crashes/blue screens continued). The firmware/drivers were relatively current. There were a few yellow icons in version control agent. This computer has been updated about once per year for firmware & drivers.
So far, this has stopped this blue screen/crashes.

End.