Proliantt ML350 Re-booting

[Gerarde Delaney]

We have had three occassions in the last 2 weeks when the Proliant Server has re-booted itself. The Windows 2000 event log of course just says the last shutdown was unexpected. Logged into the system management console and checked for failed or degraded items. All were healthy and tested OK. The Integrated log showed the following error for the days that the server re-booted

Blue Screen Trap (BugCheck, STOP: 0x000000D1 (0xDEADFB06, 0x00000002, 0x00000000, 0xF1EC351E))

Is there something else that I can be checking to see what may be causing the error.

Regards

Gerarde

[Doug Howe]

Gerade

I have also had the same over last 2 weeks with ML350. We have had the Memory replaced but is still happening. I am also bemused.
We are frequently seeing it at the same memory address
Blue Screen Trap (BugCheck, STOP: 0x0000007F (0x00000008, 0x80042000, 0x00000000, 0x00000000)) 7/14/2004 11:02PM 7/14/2004 11:02PM 1
2 Blue Screen Trap (BugCheck, STOP: 0x0000007F (0x00000008, 0xF7747EF0, 0x00000000, 0x00000000)) 7/14/2004 7:34PM 7/14/2004 7:34PM

If anyone has any further info please let me know.

Regards

Doug

[Michael Hove]

Hello!

I have just the same problem:
BugCheckCode . . . . .0x000000d1
BugCheckParameter1 . .0xdeadfb06
BugCheckParameter2 . .0x00000002
BugCheckParameter3 . .0x00000000
BugCheckParameter4 . .0xf23f351e

And I also have a ML350.
The server bluescreens one every 5'th day or
so..

Do any one know witch driver that is
the problem ??

Some one please help!!!

/Michael

[Gary Connolly_1]

Hi,

I'm having the same problem with an ML370 G3 , last week-end it bluescreened 4 or 5 times. win 2k sp4, all the latest patches.

thanks
Gary

[jennifer garland]

we have compaq ENs doing same thing - about 15...remove profile, start fresh, goes away for awhile..then back in about 2 weeks..

[Dick Konijn]

We have several ProLiant DL380's, one of them experienced daily reboots early in the morning.

Error: Blue Screen Trap (BugCheck, STOP: 0x0000007F (0x00000008, 0x80042000, 0x00000000, 0x00000000))

Solution: Check the "mini crash dump", which is located at %systemroot%\Minidump.

You will need to download a tool to analyse this small dump, you can get it at http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

After opening the minidump, you (hopefully) will see more about the actual cause of the crash. For the less technically challenged persons among us ;-) scroll to the bottom, and it will give the most probable cause. In this specific case: "Probably caused by : q57xp32.sys ( q57xp32+186e2 )"

Disabled the secondary NIC (NC77xx), cured the rebooting problem for now (we have no spare left). Possibly a driver update could do the trick, although we have about 10 DL380's with the same configuration without any problems.

[Gary Connolly_1]

Hi,

I have upgraded the agents. I used RDU to install smartstart 7.10A onto the problem server. I requested to overwrite all drivers as I used windows update to install a NIC driver after the initial build. It has worked for me.

Regards,
Gary

[Michael Paul_3]

I have a Proliant ML350 running Windows 2000 with Small Business Server. I have applied all the windows updates I can find. In desperation decided to look at the forum site and found the EXACT error mentioned at the top of the thread.

I downloaded the bug check tools and actually had a full memory.dmp file to play with. After reviewing the file, I found at the end a reference to openhci.sys file. Looking on the system I found the following:
Open Host Controller Interface USB Driver.

I had not been having any reboot problems prior to 8/13/2004. On 7/31/2004 I installed a new APC UPS and instead of using the Serial cable for the Smart Monitoring I chose instead to use the USB cable which the newer APC model of UPS's have. I haven't had a chance to swap out the cable yet but this is the first step I'm going to take. This is the only real hardware change I've made in the past year. The previous UPS was plugged into the serial cable.

If this solves my problem ultimately I'll let everybody know.

[joe blow_13]

Sorry for my english, I'm a french Canadien.

We have the same trouble in the last weeks.
I isolate to the problem was the APC Smart-UPS software. After I will update the APC software : No blue screen again.

Bye

[Doug Howe]

Gerarde

after having HO replace just a vbout everything it was a faulty Hard disk that caused the problem.
Regards

Doug

[Neil Bodsworth]

I have also had this problem with win200 SBS and an APC UPS connected via USB.

We have been advised to use the serial link for the USB as well and I shall post again with any news.

Anyone who has also done this - do you still have problems with any other USB devices or is it only with a UPS?