BugCheck, STOP: 0x000000F4 (0x0000000000000003

[Tharmarajah Kesavan]

I have the following issue on my server and need an expertise advice as how to resolve this incident on our server.

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.

cheers
Rajah

[KarloChacon]

hi


you should start trying the latest System ROM

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15...


and get the service pack or latest updates for your system

http://support.microsoft.com/kb/904779

what about Drivers (proliant support version)?

bye

[KarloChacon]

what a minute is this the same server?


http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1280267

bye

[Tharmarajah Kesavan]

Hello Buddy,

this is a totally different server :O . It has the ROM updated to the latest version and also has SP2 applied.

Any other suggestions?

cheers
Rajah

[KarloChacon]

that's a relief I thought it was the same server

well what about firmware update for he other components? and as I asked you before what about proliant support pack? 8.11?


http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15...


to tell you the truth there is no much information about that blue screen

let see tomorrow to check more resources

bye

[KarloChacon]

I did not find any more info about that BSOD

even though try updating Proliant Support pack and let me know

[Peter Stringer]

We have had exactly the same problem, we are running 64 bit Enterprise on 2003 R2. We also have the best support contract with HP, I have been disappointed in the HP Level of expertise, as we have a project to Virtualize our entire Datacenter environment I doubt if we will be buying HP. This is supposed to be a high end flagship bit of kit.

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.

[Matt Kramer]

We are still having this exact same BSOD with a 0xF4 stop code on a DL180. No memory.dmp is every created even though the system is configured to write out the file to the root of the os drive. This is Server 2008 x64 on a DL180 G5 with two NC360T NICs and a P400 controller.

Do you get a memory.dmp created?

[Ryuichi Shudo]

The same phenomenon has occurred with three servers that I have.
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.

[Prabhu Raj]

Hi,
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.

[Matt Kramer]

I am at the latest firmware 5.22 for the P400 controller and DL180 Bios 019 and still am having the problem.

[R Bloomfield]

Chiming in with the same problem.
DL180 G5 with Windows Server 2008 x32, with an E200 controller. Firmware, etc. all latest versions. Tried reseating all sorts.

[Matt Kramer]

Hello,

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!

-matt

[R Bloomfield]

I don't suppose there's even a vague ETA is there? This particular server is our backup storage server and is about to have a SAN attached to it so I'm concerned that I won't be able to get it running.

[Matt Kramer]

Not that I'm aware of, I get a status update every Friday and as of last Friday they didn't have an ETA. I'm guessing another few weeks! :( If I here anything different I'll post back to this thread.

[Peter Stringer]

We fixed it on our own:

We discovered an HP article re blue screen of death when upgrading from version 4.4.24.0 to version 4.6.16.0 of the HP network drivers (reported fixed in V4.6.17.0 as applied yesterday) - the server has not crashed since dec 08

[Matt Kramer]

In our case we have narrowed down the problem by just having a P400 in the 8x slot and no cards in the two 4x slots. In this config the machine will BSOD or hard lock under load.

[R Bloomfield]

I've taken the server out of the rack and have run it with the lid off and the E200 straight into PCI slots 5 and 6, with no luck, so it doesn't seem to be the riser at fault in our case.

[Peter Stringer]

Take a look at the network card drivers and the advisories.

[R Bloomfield]

The network card drivers you point to are for the x64 edition, we're using x32, and we're up to date as of yesterday.

[DominikR]

Hi,

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:

ML350 G5
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
E200i: 1.80
NC 373i: 2.1.3.1
iLO2: 1.70
SAS harddisks: HPD9

Driver version: PSP 8.15 (B). In particular:

Raid controller driver: 6.14.0.64
NIC driver: 4.4.24.0

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.

Regards,
Dominik

[R Bloomfield]

Well, we've managed to fix it. Definently a driver issue in our case. I went back through every item in Device Manager and made sure that we had the latest for each. At least two items didn't have the latest available driver, one of which was the network card, despite reporting as having the latest in the Performance Monitor. Since then we've been running Microsoft DPM and have transferred several TB's without hassle.

[Peter Stringer]

Yes it was a problem with our network card driver, as soon as I updated it, our stop error ceased. We have been running server now without problem for months.