BSOD STOP: 0x0000007B (0xF789EA94,0xC0000034,0x00000000, 0x00000000) on Proliant DL370 G6

[Kim Siang, Lim]

BSOD STOP: 0x0000007B (0xF789EA94,0xC0000034,0x00000000, 0x00000000) on Proliant DL370 G6

I continue encounter BSOD STOP: 0x0000007B on Proliant DL 370 G6 server is running on Windows 2003 Standard R2 edition.

No application installed on the server, just Mcafee 8.5 AV. After frequent reboot (For testing purpose), the server when bluescreen with the above error.

Ran HW diagnostic on the server, no HW errors detected.

HP CE (HW support team) replaced the motherboard, cache module, backplane, 2 x 72GB HDD. The issue reoccurred.

Same issue happened on another Proliant DL 370 G6 server as well. Out of 10 servers, there are 5 servers having BSOD STOP: 0x0000007B.

When BSOD STOP: 0x0000007B happened, server not able to access to Safe Mode. Last known good also not fixed the error.

I running out of idea, the actual root cause for this issue.

Can anyone able to assist. Thanks

[Diego Castelli]

Start configuring the systems to have the small memory dump instead of the full memory dump inside the system properties (sysdm.cpl) -> advanced -> startup and recovery.

Then download blue-screen viewer or other blue screen analyzer. Analyze the subsystem that cause the issue.
----

Anyway there's a known issues on that servers in PSPs prior to 7.30.
Try to update to the last supported PSP (you can find your server model in HP site- support section and there you'll find the smart-start download of the last supp. version).

have a look here:
http://h30499.www3.hp.com/t5/ITRC-ProLiant-deployment/Windows-2003-Slipstreamed-with-SP1-in-RDP-2-00-Errors/m-p/3521154#M1660

they're discussing about RDp, but the workaround was to install PSP7.30 "manually" in the deployment packets.

HTH
Bye!

[Diego Castelli]

Sry, i meant:

there's a known issue on some SA controllers that caused that BSOD.

not precisely on that model of server.

Anyway i think you should always mention PSP level when starting a thread...

[Kim Siang, Lim]

We used SmartStart CD version 8.50 and SmartStart CD version 8.60 to do Windows installation.

We also ran PSP8.50 and PSP8.60, same BSOD occurred.

The BSOD did not happen immediately, it happen after few days or weeks monitoring.

[Michael A. McKenney]

7B can be a bad drive or controller also. Did you install the latest firmware on the server board, drives, and controller.

[Kim Siang, Lim]

Yes. Issue still reoccured after latest firmware installed

[Diego Castelli]

Hi Kim, did u analyze the minidump with blue scrree viewer?

Which subsystem/driver cause the problem?

[Michael A. McKenney]

Run chkdsk /r on the drives. You might have to boot the Windows disk to a recovery session to a DOS prompt to run it. See if any errors are repaired. Could be a corrupted NTFS partition.

[Kim Siang, Lim]

We ran chkdsk /r /f as well. Error persist

[Michael A. McKenney]

5 servers doing it.

You upgraded firmware on the servers. Same issues. I would replace the controllers if you can't go back on the firmware. I would get the previous drivers and try them. I can't believe you have that many bad drives.

I would call HP and go back to a previous revision on firmware and drivers.