How do we stop our Windows 2008 SBS server from Blue Screening ?

Our Windows Small Business Server 2008 blue screened last night after some Windows Updates were applied.  The server begins to boot up and you can see Windows loading up but then you get a Blue Screen.  I have tried Safe Mode, Safe Mode with Networking and Last Known Good Configuration - all of which made no difference.  I also Disabled Driver verification check from the Advanced options but that didn't work either.

The driver that is causing the Blue Screen is volsnap.sys

Can anyone offer any advice how this can be fixed ?

Many thanks in advance
PurityITAsked:
Who is Participating?
 
Radhakrishnan RSenior Technical LeadCommented:
0
 
spherrodCommented:
Are you able to copy the file from another 2008 machine which hasn't had the same updates applied and restore it to the affected machine in Recovery Console?
0
 
hknoopCommented:
You can start from the dvd and then copy the file back, otherwise run a repair from the dvd.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
PurityITAuthor Commented:
Hi both and thanks for your posts,

I tried to boot from the internal SATA DVD drive and I got the same error.  I then tried to boot from an External USB drive and again got the Blue Screen with the volsnap.sys error
0
 
Cliff GaliherCommented:
Volsnap is the volume snapshot service. While it is the process that is running when the blue screen  happens, thus it "owns" the problem, it is very unlikely that it is the cause, so replacing the file will not help.
The volume snapshot service is, as its name implies, responsible for various tasks involving disk integration with Windows. As with any blue screen in since the XP era, about the only code that has enough low-level access ot cause windows itself to be unstable enough to croak are drivers. Which in this case would be completely consistent. Volsnap is attempting to perform a task on the disk subsystem and thus is calling a driver that is not acting appropriately.
Three possible causes:
1) Failing disk.
2) Failing disk controller.
3) Bad disk controller driver (RAID controller ,etc)
HTH,
-Cliff
 
0
 
PurityITAuthor Commented:
Hi and thanks for your post,

How do I then detect what the hardware failure is if I can't boot into the OS ?
0
 
PurityITAuthor Commented:
We were able to use the UBD to boot into the recovery environment.  Once we were in here we then were able to copy across the volsnap.sys file and this allowed the system to boot up
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.