Compaq ProLiant DL380 and Bugcheck

[MattWray]

We have several compaq servers that are rebooting themselves randomly. We receive this information in the event log:

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 5/8/2003
Time: 8:39:33 AM
User: N/A
Computer: HOUCTX03
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xc0000005, 0xa001d22b, 0x00000000, 0x00000023). Microsoft Windows 2000 [v15.2195]. A dump was saved in: M:\WINNT\MEMORY.DMP.


Anyone recognize this?

Thanks,

Matt Wray

http://www.total-tec.com

http://www.sss-steel.com

 

[Walter349]

The server has recovered from BSOD, the 0x1E Kmode_exception_not_handled error would be in the phase 3 or 4 of the loading sequence. It can be hardware or software related but is more normally a hardware problem.

You need to use a utility like DUMPCHECK to examine the Memory.dmp file.

If you actually got observe the BSOD in action, it would have pointed to a file name in which the server failed, this might help with a quick check, but the data would be in the Memeory Dump file anyway.

It would be difficult to be more accurate without seeing the memory dump file data.

 

[MattWray]

The output from the Dump File is:

Windows 2000 Crash Dump Analysis

Filename............memory.dmp
Signature...........PAGE
ValidDump...........DUMP
MajorVersion........free system
MinorVersion........2195
DirectoryTableBase..0x6ec21000
PfnDataBase.........8x890c3000
PsLoadedModuleList..8x80483fa0
PsActiveProcessHead.8x804856e8
MachineImageType....i386
NumberProcessors....2
BugCheckCode........0x0000001e
BugCheckParameter1..0xc0000005
BugCheckParameter2..0xa001d22b
BugCheckParameter3..0x00000000
BugCheckParameter4..0x00000023

ExceptionCode.......0x80000003
ExceptionFlags......0x00000001
ExceptionAddress....0x8042f034


->Validating the integrity of the PsLoadedModuleList

->No errors in the module list.

->This dump file is good!

That mean anything to anybody?

Thanks,

Matt Wray

http://www.total-tec.com

http://www.sss-steel.com

 

[Walter349]

OK,

First, try running the comapq diagnostics, and check that everything comes up ok, I would go interactive and check the memory modules first, to rule out a module failure.

Second, Compaq diagnostics, Interactive, Check the drives.

Third, check the Compaq IML logs and see what comes up there.

This is trying to narrow things down a little.

Meanwhile I am having a look at the dump data you gave.

 

[MattWray]

I'm sorry, I don't know how to run the Compaq Diagnostics...

Thanks,

Matt Wray

http://www.total-tec.com

http://www.sss-steel.com

 

[epohl]

What Service Pack are you currently running?

 

[MattWray]

SP-3...

Thanks,

Matt Wray

http://www.sss-steel.com

http://www.total-tec.com

 

[Walter349]

To Run the diagnostics,

Boot the server and at the Compaq 'Splash' screen press F10. this will put you into the Configuration menu.

The server should have a compaq system partition on the primary HDD which would have been created if you used the compaq smart start CDs to set up the sever HDD. But if you didn't, then the compaq smartstart CDs will allow you to create the configuration and diagnostics utilities on 3.5 FDDs and then you can run them from there.

Hope this helps

 

[MattWray]

Thank you, I will look into this on Tuesday...

Thanks,

Matt Wray
MCSE, MCSA, MCP, CCNA

http://www.sss-steel.com

http://www.total-tec.com