Server rebooting itself

Hi one of our live servers, running Windows Server 2008 SE, has crashed and is rebooting itself whenever we attempt to start it up. The server gets past the POST screens, just as the Window Server boot up progress bar appears it reboots itself.

Steps taken so far:

Reseating RAM modules – No change.
Booting into safe mode – Doesn’t work and server still reboots itself.
Disabling ‘Driver Signature Enforcement’ in the Advanced Boot Options – No change.
Booted from Windows Server 2008 DVD and attempting chkdsk c: /f /x and sfc /SCANNOW /OFFBOOTDIR=c:\ /OFFWINDIR=c:\windows – chkdsk completes without errors, but sfc does not run with the message “Windows Resource Protection could not perform the requested operation”
Booted from Windows Server 2008 DVD and attempted a “bootrec.exe /fixmbr” – No change.
Disabled 'automatic reboot on failure' in the Advanced Boot Options and the server blue screens with the error code “0x0000007B (0xFFFFFA60005AF9C0, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)”

We're on the verge of a system re-install, but would really like to avoid that.

Who is Participating?
Subhashish LahaConnect With a Mentor Commented:
Stop error code “0x0000007B" signifies issue with Storage controller driver or Display adapter driver.

Is there any changes made on Hardware level?
First: go to sysdm.cpl snap-in (right-click -> properties on my computer->advanced system options) than go to advanced -> startup and recovery.
Select to save a SMALL memory dump (64K) on failure. - OK.

Get Blue Screen View here:

and analyze the last file located in C:\WINDOWS\MINIDUMP.

based on that analysis, you can take remediation actions.

Let us know if u need further assistance.

mbavisiAuthor Commented:
Hi subhashishlaha, I'd upgraded the RAM three weeks ago, but it was working fine up until this weekend.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Subhashish LahaCommented:
Can you boot server with DVD and check the file system on disk? It could be that driver file is corrupt. Also, check BIOS and look for any changes in HDD or RAID configuration.
mbavisiAuthor Commented:
Yeah, we've tried booting from the Windows DVD and running checkdisk and sfc /SCANNOW. Also checked the bios.

We even copied the 'drivers' from another identical server, but still it's rebooting itself.
Subhashish LahaCommented:
Did you checked BIOS for any changes or RAID controller configuration? Also, check the Display adapter and its driver.
I agree with the "subhashishlaha" that this smells clearly like a hardware problem.  I would be suspicious of the RAM suffering "infancy mortality."  Hardware failures are common immediately after starting new hardware in production, or near the end of the mean time between failures (MTBF - much later), although not impossibly between those two high failure rate  points in time.  Can you put the old RAM back in place for a time to differentially diagnose?
mbavisiConnect With a Mentor Author Commented:
We've managed to get the server booting by disabling ‘Driver Signature Enforcement’ in the Advanced Boot Options screen at start up. Looks like a driver issue which. We'll have to use a process of elimination to identify which driver exactly.
mbavisiAuthor Commented:
Thanks for all your input. As we've managed to get the server to boot, I'm accepting subhashishlaha suggestion that it's possibly a driver issue, however I still don't know what driver exactly.
All Courses

From novice to tech pro — start learning today.