HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Proliant DL580 G1 Stop errors

 
Jvan
Occasional Advisor

Proliant DL580 G1 Stop errors

Good day,

I have a Proliant DL580 G1 server that is behaving problematic. Proliant Support Pack 7.1 and firmware maintenace kit 7.1 has been instrumented to troubleshoot possible inconsistancies. (We have not yet standerised on the latest version) I have a feeling that its either an OS or application related error. The follwowing entries were captured in the HP IML.


1 Blue Screen Trap (BugCheck, STOP: 0x000000C2 (0x00000007, 0x00000B8A, 0x84017000, 0x84017008)) 11/7/2005 11:07PM 11/7/2005 11:07PM
2 Blue Screen Trap (BugCheck, STOP: 0x0000001E (0xC0000005, 0xF5AC30AE, 0x00000000, 0x00000050)) 10/28/2005 11:02AM 10/28/2005 11:02AM
3 Blue Screen Trap (BugCheck, STOP: 0x0000001E (0xC0000005, 0xF5AE30AE, 0x00000000, 0x08000048)) 10/25/2005 3:52PM 10/25/2005 3:52PM
4 Blue Screen Trap (BugCheck, STOP: 0x000000D1 (0x00804919, 0x00000002, 0x00000000, 0xF5B1B088)) 10/23/2005 7:55AM 10/23/2005 7:55AM
5 ASR Detected by System ROM 10/14/2005 1:54PM 10/14/2005 1:54PM
6 Blue Screen Trap (BugCheck, STOP: 0x0000001E (0xC0000005, 0xBFA110AE, 0x00000000, 0x08000048)) 10/14/2005 1:44PM 10/14/2005 1:44PM 1
7 Blue Screen Trap (BugCheck, STOP: 0x000000D1 (0x49207409, 0x00000002, 0x00000000, 0xBFA11088)) 9/18/2005 12:08AM 9/30/2005 8:23AM

There are also no indication of any errors in the event logs, with the expection of the IML errors as mentioned earlier.

Please find a copy of the survey.txt file for additional information.

Kind regards,
Jvan de Lange
1 REPLY
Basil Vizgin
Honored Contributor

Re: Proliant DL580 G1 Stop errors

There can be many reasons, you got 3 type of errors...

One of than can by caused by a memory failure or bad boot driver, another by either a buggy driver or a situation that a driver can't handle or IRQ conflict, and the 0x1E happens when the CPU traps an event but the operating system can't recover from it.
The first value is usually 0xC0000005 which means kernel32.dll caused an access violation but since it's the kernel doing it, it's something very serious.
http://aumha.org/win5/kbestop.php