Main Forum > General Computer Support

Windows Repair (All In One)

(1/7) > >>

Boggin:
I'm new to this forum and not sure how to see if anyone else has had this or other problems after running the program in the thread title, but I've run this program with default settings on two Win 7 SP1 x64 bit laptops and on one it froze the system after the reboot and had great difficulty in establishing a Wireless connection.

I was eventually able to get into the Reliability history where it had a Critical Error of Windows Media Center Host Module Stopped and no answer as to why when checking for solutions.

The laptop has managed to repair itself and is now running okay as far as I can tell.

I'm not sure why in the forum rules it says that posts are not actively monitored when the program says to come to this forum for Feedback, but I'd appreciate it if someone did have an explanation for the Critical Error.

Shane:
Never had any of those problems on any Windows 7 system i have ran my Windows Repair on.

The only time I have found really odd side effects after running the repairs was normally when the hard drive had bad sectors and the user didnt know it. So when the repairs ran some of the system files or settings got on a bad sector and everything went bonkers from there.

Have you do a bad sector check yet on the drive? It is a long scan that can take a hour or more depending on the size of the drive.

Open a cmd.exe as administrator. Then put in
chkdsk c: /f /r

Hit enter, it will come up and say the drive is in use would you like to schedule it, hit Y and hit enter.

Now reboot, before windows boots it should start the scan, if it doesnt, try again.

Then go have some coffee because it will take a while. Once it is done it will put a entry in the event viewer of the reaults and we can see if it found any bad sectors. (We want to see 0 KB in bad sectors) in the log. :wink:

Shane

Boggin:
Thanks for the reply Shane but that's not it.

To save time I just run chkdsk in read-only mode and that comes up clean both on the volume and bad sectors although I haven't run a Seagate test on it.

When running chkdsk from within Windows there's no need to add c: and /r has the attributes of /f so you only need to enter chkdsk /r for the combined hard disk and file check, but it's best to run the read-only first as data can be lost if it finds bad sectors and moves what data it can to the good areas of the disk.

Shane:
The read only test doesnt test for bad sectors on the drive though, the scan would take a long longer if it did, please do the test that I asked, the read only check in windows chdsk is different then the program that windows uses at boot up to scan the drive.

Even if it only checked the sectors the data was on the scan would still take a while as it would be testing 30+ GB of data depending what you have on the system. :wink:

Shane

Boggin:
I've seen a read-only report 4KB in Bad Sectors before now but I've run the chkdsk /r and other than cleaning up some unused index and security descriptors, it came back clean for the volume and bad sectors.

Navigation

[0] Message Index

[#] Next page