Windows Update Hosed my 5793

After a reboot following a MS update, I got a BSOD with a message saying to the effect the computer was shut down to prevent further damage along with an error number of 0x0000C1F5.

I did some research on the error and about the only thing I could come up with is that it is a very rare message and the solution is to reseat the memory and hard drive. I have an e-mail to Sager tech support to see what they have to say as any attempt to do a system restore or even a clean install dies with the same BSOD before the main Vista startup screen even loads.

As far as the Sager itself, I am very impressed with the build quality and when it comes to replacing the wife's aging Dell Inspiron 6000, it sure will not be with another Dell but with a Sager instead.

Mike

 

So did you reseat the RAM and HDD?

 

good point there



you might have a failed HDD.

my dell HDD failed like that, but i was extremely weird. Ubuntu linux would run fine, but even trying to reinstall windows would bring a blue screen, Xp and Vista. So dell sent me a new one.

 

It's brand new, less than a week old and I don't want to touch it before I hear from tech support. Since I've been working with computers since 1974, I have no problem with reseating either the memory or the drive but seeing as I paid for the 3 year warranty along with the dead pixel guarantee I don't want to give them an excuse for saying customer abuse.

Mike

 

I had the same thing on my new NP5972 ( http://forum.notebookreview.com/showthread.php?t=218724)

Are you running Vista-64? Think it was a driver problem for me. Reinstalled and it's been working just fine...so far.

 

If it is a driver issue--though drivers are not typically included in auto updates--reboot into SAFE MODE, and run system restore to the previous day.


It is more likely a file that interacts with a driver, but either way....

 

I am running Vista 64 but I do not even get as far as you did in the boot process with your problem. I did some further research and it seems the update somehow causes the system not to see the disk drive.

Another fix I found is to disconnect the a-c power and the battery and let the notebook just sit for awhile then put power back and that should restore things to normal.

You just have to love updates sometimes, they make life so interesting.

 

That basically resets the BIOS.

 

I would like to hear more about what sager tech says about this.

 

I have had this problem before. I was able to fix it by booting into safe mode and removing the offending file that caused the BSoD.

 

Here is an update to the thread. Nothing we tried worked so tech support sent me a program called disktool which erases the hard drive among other tests it can do. Even with a fresh hard drive and a clean install of Vista and the drivers, I then could not get either the wireless or ethernet connections working. We tried everything to get at least one of the connections working but it was always no joy.

I ran a new cable to the switch where the router is and nothing just the Windows default local IP address. The wireless connection did the same exact thing.

We finally came to the conclusion that the best course of action was to send the 5793 back and let them re-image it back to factory configuration, test it to make sure it is all working and then ship it back to me.

I have seen a few posts in other forums where Microsoft has pulled the update on Vista SP1 as some of the files being pushed over WU can cause a computer to have all sorts of problems from different BSOD messages to continual reboots.

I am just glad Sager is going to fix my 5793 and I'll give an update when I get it back.

Mike

 

were the devices even present in device manager?

I find this to be an extraordinary turn of events. It should be noted that Vista sp1 is not supposed to be available without a registry hack for exactly this reason--there were/are driver issues that needed to be addressed before sp1

 

The devices were present in device manager and reported out as working properly. As far as the registry hack, I know about it but did not implement it since I felt that MS was still working on the release and why risk problems.

Here is a link to one article that talks about MS pulling from WU problem file(s) that cause users different problems.

http://www.informationweek.com/news/showArticle.jhtml?articleID=206800819

My 5793 goes back to Sager tomorrow by overnight insured FedEx and I hope to have it back by sometime late the following week.

Mike

 

Godspeed, and good luck!

 

Thanks, looking forward to getting a working notebook again!

 

You're most welcome. I'd like a working notebook, too. When I bought this consarned (sp??) vaio, I didn't realize that, when they said it had a cpu frequency of 1.3GHz, what they really meant was that it ran as fast as 1.3 GerbilHz.

 

I got this messege yesturday on my HP DV9720 after a reformat....I assume something overheated.