alanrimer
asked on
Server 2008 R2 blue screen and reboots
A problem has been detected & windows has been shut down to prevent damage to your computer-
We have run StartRep.exe - Gives corrupt volume error message
We run chkdsk /r /f it found an error then tried startrep.exe again and same problem
sfc /SCANNOW /OFFBOOTDIR=d:\ /OFFWINDIR=d:\windows - didn't find any problems
Plse help!!!!
We have run StartRep.exe - Gives corrupt volume error message
We run chkdsk /r /f it found an error then tried startrep.exe again and same problem
sfc /SCANNOW /OFFBOOTDIR=d:\ /OFFWINDIR=d:\windows - didn't find any problems
Plse help!!!!
Hi there, the easy way is to start in safe mode Tap F8 @ startup
Then look over the event logs for errors prior to the reboot,
Turn off automatic reboots by right clicking on my computer, and choosing properties, then advanced system settings, and change the option (drop down menu) to minidump file.
Next time it reboots you will be able to view the error message
If you cant work it out from thatm If its still a problem you may want to post the mini dump file for me or someone else to take a look at for you. C:\windows\minidump
All the best
Jamie
Then look over the event logs for errors prior to the reboot,
Turn off automatic reboots by right clicking on my computer, and choosing properties, then advanced system settings, and change the option (drop down menu) to minidump file.
Next time it reboots you will be able to view the error message
If you cant work it out from thatm If its still a problem you may want to post the mini dump file for me or someone else to take a look at for you. C:\windows\minidump
All the best
Jamie
ASKER
No same thing in safe mode. We can access the drive through the recovery console there is no mindump folder but there is a folder called memory dump, which is 691mb
The stop error is the same as the attached image (which I copied off the internet but the "Stop error is 7B" not F4
Bluescreen.jpg
The stop error is the same as the attached image (which I copied off the internet but the "Stop error is 7B" not F4
Bluescreen.jpg
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Try this:
Remove the CMOS battery from your Servers motherboard,
Power up.
Power Down
Reinstall,
even better replace it.
That should solve the 0x000000F4 error.
Remove the CMOS battery from your Servers motherboard,
Power up.
Power Down
Reinstall,
even better replace it.
That should solve the 0x000000F4 error.
ASKER
Ok so original server is an Intel S5000 with 2 x 500Gb Sata Drives Mirrored (C Drive) and 2 x 500Gb Sata Drives Mirrored (D drive). We tried all of the above and got Blue Screens - Cant check if it was also 7B sto error now, as we are busy running a restore to that server from a backup that's 4 days old.
We bought a new ML350G6 Server (Great deal as they just launched G8's), installed VM Ware 5 and ran a restore to it! I realise this could be the problem as its using a LSI Logic SAS Controller and it may need a Parallel Controller? but if so can i fix this?
We bought a new ML350G6 Server (Great deal as they just launched G8's), installed VM Ware 5 and ran a restore to it! I realise this could be the problem as its using a LSI Logic SAS Controller and it may need a Parallel Controller? but if so can i fix this?
Sorry not understanding what you did to restore? Installed VMWare 5?? So you are restoring to a VM? How are you doing this exactly?
ASKER
We doing a Baremetal restore backup software R1soft - boot off CD give server ip address then restore drive partition, then full C drive. It all restores fine but on the Blue screen stop error 7B.
Our restore from last week Monday just finished to the original server (no Vmware) and we getting the same error as the new VMware server
Our restore from last week Monday just finished to the original server (no Vmware) and we getting the same error as the new VMware server
Alternate the boot sequence with paired dimms. (Could be memory related)
Remove connections to Tape Drive, and any daughter cards,
Disable NICS in bios and if you have any additional cards for any purpose remove them all temporarily of course.
physically remove the mirrored d: disks (I assume Data store) from the array
Boot up the machine.
Whats the result...?
Remove connections to Tape Drive, and any daughter cards,
Disable NICS in bios and if you have any additional cards for any purpose remove them all temporarily of course.
physically remove the mirrored d: disks (I assume Data store) from the array
Boot up the machine.
Whats the result...?
I assume this R1soft has the option to do bare metal recovery?
Have you no support from them?
I've never heard of that software but if after a restore you are getting a 7B bluescreen it means the storage controller isn't loading correctly, this may not work properly into VMWare at all either
I'd contact their tech support for help to be honest
Have you no support from them?
I've never heard of that software but if after a restore you are getting a 7B bluescreen it means the storage controller isn't loading correctly, this may not work properly into VMWare at all either
I'd contact their tech support for help to be honest
ASKER
We got it!!!! without swearing ..... yay!!! So the original server was doing the same thing. You said 7B storage controller and that's what kept my mind thinking.
The original rubbish Motherboard Bios must have reset itself. Raid wasn't enabled and it was booting off IDE therefore different "Storage Controller". Thanks so much for responding! If you hadn't made me think ......
The original rubbish Motherboard Bios must have reset itself. Raid wasn't enabled and it was booting off IDE therefore different "Storage Controller". Thanks so much for responding! If you hadn't made me think ......
ASKER
Most problems refer back to basics!
Good news, thanks for the update, glad u are booting!
If so can you access C:\Windows\Minidump folder for the crash file and post here?
Or what is the bluescreen code you are seeing?
If its just rebooting without showing the error, press F8 to access the Safe mode menu, then select Disable Automatic Restart - this will then allow you to see the bluescreen code at least