sfc and corrupt Acer recovery partition

Hi, everyone -- I'm hendis, new to the forums, and looking for a way to solve a problem that I've never experienced before. Fervent thanks to anybody and everybody who helps, can help, wants to help, or is even slightly interested...

I own an Acer Aspire 4330 notebook (purchased 12/2009). Recently, I began to experience multiple problems with the computer, including random BSODs, random "hard" shutdowns, slow (or unavailable) HDD reads (preventing startup), slow startup and shutdown (that is, if there's a startup or shutdown), as well as very slow internet speeds, slow file operations (copy, move, etc...), webpages not loading (I use Cable/WiFi) and not responding errors on all apps. (There are even more errors, all unpredictable and random, but I think that you get the idea.) All of these problems led me to decide to reformat.

I reformatted, recovered from Acer's hidden partition, and without changing any settings or installing any software, immediately ran System File Checker. SFC found several corrupt files, none of which I was able to find, identify or fix. As a result, the problems mentioned previously remain and are rapidly getting worse.

The corrupted system files that SFC detected came directly untouched from the restore partition, which came directly untouched from Acer. Question 1: Is the recovery partition corrupted/damaged?

I contacted Acer support, and got the "out of warranty, we're sorry, but we can't help you" song and dance.

I wouldn't be surprised if there were multiple errors on my machine, but first things first: How do I fix (or find and replace) the corrupted system files detected by sfc?

Hello, see this http://www.vistax64.com/tutorials/66978-system-files-sfc-command.html
Notice in the big yellow box, you need a Vista install cd to actually repair the missing/corrupt ones.

All I got from Acer was a restore partition, not a Vista CD.

Does this mean I'm out of luck, and can't replace the damaged files?

hendis

The primary problem seems to be the BSODs, please post
http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html

Dear richc46,

Solly for the delayed reply -- I'm on call for work 24/7/365, and work called, so I was out of pocket for a while.

- Saved your exe.
- disconnected all external peripheral devices and USB hubs
- reformatted again (my personal docs, photos, etc are on a different partition)
- ran your exe (without reconnecting anything)
- screenshot of report attached as "BSOD Report 1.txt"

Doesn't make much sense to me, but I'm hoping that you'll have better luck...

Also, just wanted to include a bit of strange info...

I've got two USB hubs daisy-chained, and normally plugged in to my 4330. The closest hub has a WD external ("My Passport") 1TB HDD attached. The second USB hub has a Panasonic KX-MB271 laser printer attached. The unused USB ports on each USB hub contain dedicated USB cords (supplied by each manufacturer) for assorted equipment (GPS, handheld receipt scanner, etc.) not usually connected to the USB wire.

I have no problems (BSOD's, freezes, randon shoutdowns, etc.) as long as the USB hubs (with only the WD 1TB and the Panasonic printer) are NOT attached. Once the external storage HDD and the printer are reconnected, the problems recur. (Please keep in mind that ONLY the WD external storage and the Panasonic printer are usually connected -- not the GPS or handheld scanner.) Nothing was connected when I ran your exe file.

I cannot help, today or tomorrow, since I am not home and need special software to read your reports. If no one helps by late Sunday, post something to remind me and you will get expedited help. Happy Holidays.

Take your time -- enjoy your Christmas holiday -- sometimes I can't get back when I want to, either...

hendis

richc46,

It's been about a week...

Are we going to work on this problem?

hendis

BSOD squad has been swamped , sorry for delay, they answer at numerous forums. Please be patient while they get to your logs. again. thanks for using VistaForums.

Hi,

sorry for any delays here but could you please revisit the instructions in the 4th post: -

http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html

You need to post the full report to allow us to diagnose your needs. OK?

Lottiemansion,

The first time that I ran the BSOD program, the results that I got were exactly what I posted.

Now, when I checked the forums and read your post, I disconnected everything from my computer and ran the BSOD program again. This time, I received the results shown in the attachment.

Go figure -- I don't quite understand the reason for the difference. But anyway, here you go...

---------------------------------------------------------------------------------------

NOTE: Error Message --

---------------------------------------------------------------------------------------------

Now what? (Nothing was attached or uploaded, AFAIK)

hendis

Lottiemansion,

The first time that I ran the BSOD program, I posted all of the results that I received.

When I checked the forums a few minutes ago and read your latest post, I disconnected everything from my computer and ran the BSOD program again. This time, I received results that had numerous files in a "Windows_NT6_BSOD_jcgriff2" folder within my Documents folder. I've zipped the files and attached it to this post. (Hope that it makes more sense to you than it did to me...)

Thanks again for all of the help from the Vista forums.

hendis

I guess that everything worked better the second time around...

(It's also a very good idea to read ALL of the instructions...)

Hi,

Please look in your C:/Windows/Minidump folder & post the zipped files from within.

These are the files that enables use to review what has happened during the crash. It is part of the crash file collection process but they seem to have been missed?

I will look at the files you have provided & get back to you this afternoon.

Thank you.

Lottiemansion,

Sorry about taking so long to get back to you -- this is the first time that I've been able to get to the forums in about a week or more...

Also, I got an email notification the last time that someone posted to the thread, but I didn't get a notice when you made your last post (# 14)

Anyhow, on with the minidump file...

OK, I'm kind of confused...

From an administrator account on Vista, when I try to zip the one minidump file, instead of zipping the file (using the right-click "Send To" option), I receive a security warning --

When I right-click the file, there's no option to "run as administrator", so elevated priveleges are out. I don't know of any way to zip the file. If I back up to the "Minidump" folder, the same thing takes place.

Obviously, the forums needs the file to continue debugging the problem. How do I get you the info?

hendis

Lottiemansion,

One question -

the minidump folder contains only one file. Is there supposed to be one file for each BSOD? If so, then there's a problem, because the BSOD has happened on several occasions, not just one...

Also, there's a related, but different problem also going on here, too. It's a phenomenon that I call a "cold shutdown" (might be the wrong term).

Essentially, it's as if someone pressed the power button on my laptop -- screen goes black, power indicator goes out, no fan, no nothing. The computer is totally inert, as if it was shut down and put in storage.

To restart, the user needs to use the power button, and when the screen reappears, it is a DOS screen with a number of choices, and the text "Start Windows Normally" is highlighted.

Occasionally, I will try to restart my computer (using the power button) but, instead of restarting, I will be taken to "Windows Startup Repair".

hendis

OK,

You need to follow the BSOD instructions.

This "failure to collect all the information" is due to running the file without a escalation to administrator.

When the Download file is downloaded to your desktop right click it & "Run as an administrator". This will enable the sftware to collect all the files & then you can post a full set. OK?

As for the power thing: -

Please check all the power connections on your computer as this kind of shutdown can only be from some sort of a power failure.