ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Proliant 6000 restarts to BSD after Windows 2003 Server fresh Install but will Boot from poweroff.

Daniel Rainville
Occasional Visitor

Proliant 6000 restarts to BSD after Windows 2003 Server fresh Install but will Boot from poweroff.

I just installed Windows 2003 server on Proliant 6000 (quad 450pII,2mb ram, 2x9gb mirrored boot drive, 3x9gb raid 5 part, 4x18gb raid 5 part on 3100es raid controller. Have latest support pack installed 7.10a, latest bios. When I try a restart the machine will come back up and hang on the BSD "failed to initialize video". I also noticed in the integrated managment logs that there is a "caution" error just prior to this "critical" stop error. The error 1792-Drive array reports valid data founf in array accelerator. I also noticed that the server is very slow to shutdown. If I power the server completely down and then startup, no problem, boots normally. Any help would be greatly appreciated. Attached is the integrated management log in csv format
3 REPLIES
Stephen Grimmer
Trusted Contributor

Re: Proliant 6000 restarts to BSD after Windows 2003 Server fresh Install but will Boot from poweroff.

Error Message: STOP: 0x000000B4 The Video Driver Failed to Initialize (319120)


Err Msg: Stop 0x000000B4 The Video Driver Failed to Initialize (240369)


Either of these apply?

Daniel Rainville
Occasional Visitor

Re: Proliant 6000 restarts to BSD after Windows 2003 Server fresh Install but will Boot from poweroff.

Steve

Not sure what exactly you are refering to here: (319120)(240369) Are these KB articles from Microsoft?

The actual stop error is STOP: 0x000000B4 (0x00000000, 0x00000000, 0x00000000, 0x00050000))video driver failed to initialize
Daniel Rainville
Occasional Visitor

Re: Proliant 6000 restarts to BSD after Windows 2003 Server fresh Install but will Boot from poweroff.

Stephen:

My bad. I see that they were KB's. I had gone to MS and saw these. I tried the LPT port setting with no results. The last Known Good Configuration would not have applied as this started as soon as I installed Windows 2003. There was no config to go back to.

But thank you for your research.