We help IT Professionals succeed at work.

ProLiant DL360 G6 Win 2008 R2 SP 1 Rebooting regularly

Medium Priority
717 Views
Last Modified: 2012-08-05
My HP ProLiant DL360 G6 running Windows 2008 R2 SP1 is rebooting regullarly with BSODs. The fault has been present for over a year, even after upgrading firmware and  Windows SP/Updates.

Analysing the DMP file seems to provide little help - copy attached.

The HP IML report also doesn't seem to pin point the error  and reports the following:

"Operating System failure (BugCheck, STOP: 0x00000001 (0xFFFFF800022CE770, 0x0000000000000000, 0x000000000000FFFF, 0x0000000000000001))",Operating System,1,Critical,1,02/11/2011 06:15,02/11/2011 06:15

I have run the HP diagnostics and it shows up no hardware faults.

Does anyone have any suggestions?

Thanks

 dump.txt
Comment
Watch Question

It looks like you Windows installation in corrupt.  I would try to run a repair on the Windows installation or restore back to a previous point before this started to happen.  The other option would be to reinstall the OS.

Author

Commented:
Does anyone else have anything to add?
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
Flakey power? Is it on a UPS and if so is it a pure-sinewave UPS because those servers won't run on cheapo "simulated sinewave" ones.

Author

Commented:
It's connected to an APC 2200 VA UPS.
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
Is that a back-ups or smart-ups?

Author

Commented:
Smart UPS, but we have experienced the same problem with the server at two different addresses.

Since the problem has been on-going, a system restore is not feasible.

Anyone have any further suggestions?

Commented:
I am going to agree that a rebuild of this server is probably the only solution. Having already run the Hardware diagnostics I too am led to believe it's a corrupt OS issue.

Author

Commented:
Thanks for your comments, is there any futther information I could supply to help find a solution?
Obviously, due to downtime, we would like to avoid a complete reinstall of Win Server.

Alex

Commented:
We still need to know what's running on this and what it's used for. It sounds that it's not terribly mission critical, but that information would be good to have. You could try to perform a repair as mentioned above, and you may luck out. My experience with that has been mixed at best. You may end up spending additional time and it not working but then again, it could repair it successfully. Do you know for certain what the worst case scenario is if you rebuild it? My experience dictates that a full reload would be the better bet at ensuring this machine gets fixed the first time.

I will say that at this point, waiting any longer is just going to prolong the inevitable. Short of having to backup any data the actual OS install shouldn't take more than a few hours.

If you have any other questions, let us know and we will be glad to help.

Commented:
Check this out:

http://hpserversupport.com/Forum/tabid/54/forumid/15/postid/37/scope/posts/Default.aspx

We had to replace our system board in order to fix the problem.

Author

Commented:
Now working with Microsoft support on this issue.
Commented:
In the end, we found after the 4D Database engine used by their accounts software was upgraded the rebooting stopped. Thanks everyone for your suggestions.

Author

Commented:
Surprisingly this was the solution

Explore More ContentExplore courses, solutions, and other research materials related to this topic.