Solved: CHKDSK always runs on startup after backing up hard drive

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Akril

Thread Starter
Joined
Mar 1, 2007
Messages
204
Hello,

I'm running Windows XP SP3 on a Gateway DX200X, and lately it's been behaving in a way that makes me a bit concerned.

I have an internal hard drive which I copy the contents of my primary hard drive to using Macrium Reflect. However, over the past few months, doing this has prompted my computer to run CHKDSK whenever I restart it. Not only that, but when I back up my hard drive's contents to an HP portable hard drive and try to look at its contents, I get an error message saying, "the file or directory is corrupted and unreadable." (though the drive's contents do become viewable after unplugging it, then plugging it back in). If I attach the hard drive to my HP laptop (running Windows 7), I get a message saying that I need to format the drive before I can use it. Whether I back up to my internal secondary hard drive or my portable hard drive, when I finish backing up my hard drive, I've gotten a "[name of the drive I just backed up to] is not accessible. The parameter is incorrect" error message.

I suspect that something might be seriously wrong, but I can't seem to figure out what it is. Could someone please lend me some advice?

Thank you.
 

Macboatmaster

Trusted Advisor
Spam Fighter
Joined
Jan 14, 2010
Messages
24,071
Forgetting for the moment the possibility that both the internal hard drive used for backup and the HP USB drive have both started to fail with bad sectors, I suspect your main hard drive, or a more serious problem when backup is taking place, such as a motherboard, power or processor fault

Were it to be the latter examples I feel sure you would have noticed problems, other than at times of backup.

I would start with a chkdsk /r on the main drive.

That is cmd prompt at C if that is the letter of the main drive and then type
chkdsk /r

key enter and go from there it will run on restart and then get the results from event viewer.

Control Panel Admin tools, event viewer, application log on left pane, winlogon entries, click column heading to sort, it should be the most recent

I am signing off now as I am in the UK but I would follow that if chkdsk is OK with a check on voltages and temps
Use this
CPUID
free edition HW Monitor
Download is right hand side below HW Monitor Pro
http://www.cpuid.com/softwares/hwmonitor.html

If you need to post that as a screenshot with all options expanded using the same image as shown on the download page


That Gateway - here
http://support.gateway.com/s/PC/DX200/1008552/1008552nv.shtml

Do not know your level of knowledge so please do not be upset by me asking but when did you last open the case to check cleanliness of fans and cooling fins of CPU



Goodnight
Back about 1600 will check to see if you need further assistance
Of course someone else may well assist in the meantime
 

Akril

Thread Starter
Joined
Mar 1, 2007
Messages
204
All right -- I ran CHKDSK and took a look at the Event Viewer. This is what I found under the latest Winlogon entry:

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 2/5/2013
Time: 12:26:53 AM
User: N/A
Computer: JESS
Description:
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 144 unused index entries from index $SII of file 0x9.
Cleaning up 144 unused index entries from index $SDH of file 0x9.
Cleaning up 144 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x463ee9f000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x463ee9f000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x463ef1f000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x463ef2a000 for 0x1000 bytes.
Windows replaced bad clusters in file 454161
of name \SYSTEM~1\_RESTO~1\RP808\A0282469.dll.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Adding 4 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

488384000 KB total disk space.
334266180 KB in 491169 files.
180052 KB in 32295 indexes.
168 KB in bad sectors.
739624 KB in use by the system.
65536 KB occupied by the log file.
153197976 KB available on disk.

4096 bytes in each allocation unit.
122096000 total allocation units on disk.
38299494 allocation units available on disk.

Internal Info:
e0 69 08 00 d3 fc 07 00 de f9 0b 00 00 00 00 00 .i..............
0c 5f 00 00 02 00 00 00 05 05 00 00 00 00 00 00 ._..............
60 17 0d 0e 00 00 00 00 80 d2 b6 ee 00 00 00 00 `...............
40 13 f4 19 00 00 00 00 d0 77 23 ca 11 00 00 00 @........w#.....
10 06 2c 14 05 00 00 00 f0 6e c1 ff 17 00 00 00 ..,......n......
99 9e 36 00 00 00 00 00 b8 39 07 00 a1 7e 07 00 ..6......9...~..
00 00 00 00 00 10 fd b1 4f 00 00 00 27 7e 00 00 ........O...'~..

Windows has finished checking your disk.
Please wait while your computer restarts.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I also downloaded and installed CPUID, and attached a screenshot of the Hardware Monitor.

As for the cleanliness of the computer's interior, I opened the case a couple of weeks ago to clean out the interior. It was a little dusty, but it didn't seem like it was filthy enough to be affecting the system performance (but then again, I'm not a hardware expert).
 

Attachments

Macboatmaster

Trusted Advisor
Spam Fighter
Joined
Jan 14, 2010
Messages
24,071
168 KB in bad sectors.
Not a lot more to be said really, especially as

Adding 4 bad clusters to the Bad Clusters File.
and
Read failure with status 0xc000009c at offset 0x463ee9f000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x463ee9f000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x463ef1f000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x463ef2a000 for 0x1000 bytes.
Windows replaced bad clusters in file 454161
of name \SYSTEM~1\_RESTO~1\RP808\A0282469.dll.
my advice is secure all that is important to you ASAP
 

Akril

Thread Starter
Joined
Mar 1, 2007
Messages
204
I see -- can't say I'm all that surprised by this diagnosis. I'm just glad that I was able to figure out that things were going bad before my hard drive finally gave up the ghost. I'll get it replaced as soon as possible.

Thank you very much for your help, Macboatmaster.
 
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Top