11-02-2008 11:00 PM
Server: PROLIANT DL580 G5
OS: windows server2003 R2 Ent x64 edition
IML error: Blue Screen Trap (BugCheck, STOP: 0x000000F4 (0x0000000000000003, 0xFFFFFADFFF8E3A40, 0xFFFFFADFFF8E3CA8, 0xFFFFF800013C0FE0))
Appreciate and thanks a ton if you guys could able to help me to resolve this incident.
11-02-2008 11:28 PM
you should start trying the latest System ROM
and get the service pack or latest updates for your system
what about Drivers (proliant support version)?
11-02-2008 11:30 PM
11-03-2008 12:34 AM
this is a totally different server :O . It has the ROM updated to the latest version and also has SP2 applied.
Any other suggestions?
11-03-2008 12:48 AM
well what about firmware update for he other components? and as I asked you before what about proliant support pack? 8.11?
to tell you the truth there is no much information about that blue screen
let see tomorrow to check more resources
11-03-2008 04:57 PM
even though try updating Proliant Support pack and let me know
11-27-2008 03:11 AM
We first had a problem when the server rebooted itself with the ASR Function, after an unrecoverable system error code. HP asked me to upgrade all firmwares, system bios and PSP to version 8.11a. they assured me that upgrading Bios to 09/23/2008 would fix the problem.
After I had done this we had two Blue Screen traps.
They have escalated the problem. My confidence in them is rapidly diminishing. As they don't seem to know what they are doing. I would like to speak to a 3rd level support person who know's his onions so to speak rather than some body sitting in India speaking from a standard script.
12-08-2008 07:29 AM
Do you get a memory.dmp created?
12-11-2008 07:46 PM
It occurred five times between November 6 and today.
What is the model number of your servers?
My server : HP DL380 G5 433527-291.
Smart array E200 controller and 128MB BBWC enabler are installed.
OS: windows server 2003 R2 SP2 STD x64 edition
The problem has not occurred in 32bit of the same composition.
Moreover, the problem has not occurred even to Smart array P400 controller of DL380G5 433525-291 of 64bit.
I feel the problem in the combination of WinServer2003 64bit and Smart array E200 controlle.
12-12-2008 04:36 AM
This seems to be a communication issue between HDD-BackPlane-Controller-CHIPSET.
Re-fixing the first 3 components should solve the issue.
If not then Kindly update the latest firmwares (not from the Firmware maintenance disk but from the site) and update it.
02-19-2009 07:55 AM
DL180 G5 with Windows Server 2008 x32, with an E200 controller. Firmware, etc. all latest versions. Tried reseating all sorts.
02-19-2009 08:13 AM
I have been working with HP on this problem for over four months. It is a problem with the PCI-E 8x riser card. They are aware of then issue and it is in the hands of the L3 driver dev team. They are actively working on a BIOS/firmware upgrade to fix the problem. Hopefully it will be fixed soon!
02-19-2009 08:21 AM
02-19-2009 08:23 AM
02-19-2009 08:47 AM
We discovered an HP article re blue screen of death when upgrading from version 184.108.40.206 to version 220.127.116.11 of the HP network drivers (reported fixed in V18.104.22.168 as applied yesterday) - the server has not crashed since dec 08
02-19-2009 08:53 AM
02-20-2009 01:23 AM
02-21-2009 04:44 AM
I'm experience the same error too on a ML350 G5 server. The server shuts down and reboots unexpectedly approximately once a day. No MEMORY.DMP dump file is created although Windows is configured to create on.
The serverâ s hardware configuration is as follows:
Intel XeonE5540,2.83 GHz
4 GB RAM
E200i RAID Controller
2x 146 GB SAS, SFF, 10k, (RAID1)
NC373i Gigabit NIC
Windows Small Business Server 2008, x64
Firmware version: Firmware maintenance CD 8.40. In particular:
System board ROM: D21-11/02/2008
NC 373i: 22.214.171.124
SAS harddisks: HPD9
Driver version: PSP 8.15 (B). In particular:
Raid controller driver: 126.96.36.199
NIC driver: 188.8.131.52
The server showed several times the mentioned BugCheck, STOP: 0x000000F4 (0x0000000000000003, 0xFFFFFA8005217AB0, 0xFFFFFA8005217CE8, 0xFFFFF80001B49DA0) error. The most recent reboots donâ t generate a Bluescreen so I think the enabled ASR option comes into action.
I will open a ticket at HP on Monday. Letâ s see what they say.
03-03-2009 06:52 AM
03-03-2009 08:30 AM