Chkdsk errors

[timftse]

Hi,

I have a problem with repeated chkdsk errors on my PC. The corruption is minor - often the Startup menu items (I looked in the found001 folder where the orphaned links /files are put, and rebuilt the menu, which has since got corrupted again). Chkdsk often runs on start-up, and either finds nothing to fix, or fixes a few files, then the machine boots okay. I may then get a yellow warning triangle saying some file is corrupt during use, or a grey-box msg at shut-down/hibernate, and chkdsk runs again next boot-up.

I am running XP SP2, on a Gigabyte K8NF-9 board, Athlon 3000+, 1gb RAM. Firewall is Outpost, AV is Norman.
This problem first happened a few months back, and got so the machine would not boot into Windows at all, it just kept re-starting. I was advised to re-install Windows then, and did so. This fixed the problem, but now 4 months later it is back. I have changed from Norton Internet Security 2005 to the above in the meantime as I thought Norton might have caused the problem (and anyway Norton screwed itself up, asking to uninstall & re-install, but would not uninstall itself properly). However, as Outpost files are now starting to be affected, I assume whatever firewall is running is simply first in line for corruption problems. I also upgraded the m/b bios not long before this first outbreak, and, incase it was the cause, fell it back again, but this did not seem to help. I am running 2 IDE hard disks (80gb/40gb)in master/slave config, and corruption has been found on both ! This makes me think the disks are not the problem. Both disks are over 75% empty.

Any ideas welcome,

Thanks in advance.

 

[NDeters]

The only guess that I have is that your IDE cable may be bad. I just ran into a similar situation where I thought my DVD drive was bad (because it was burning with errors, having read errors) but decided to replace the IDE cable anyways...and everything went back to working perfectly. There was no visible damage to the cable, and it didn't have any extreme bends that would cause a kink in the cable, but it was definately what was causing the problem.

The other piece of this is that you may want to check and see if you have the newer type of IDE cable, which has more (and skinnier) cables...maybe by installing a new cable that is the new version you can solve your problem.

Noah

 

[wolluf]

I'd check your RAM - something like memtest. Bad hardware can cause filestore corruptions - and RAM would be my first guess.

 

[s0121]

open C:\ properties tools and uncheck all boxes..
then reboot.. if you have any chkfiles (I looked in the found001 folder) recommend you simply DELETE them..if you use them to recover that is your problem... I would recommend you delete them - use system restore...instead

Frank Smith irc.dhcnetwork.com

SomeWhere in Kansas Near Dodge City

 

[linney]

To check your RAM.

http://www.memtest86.com/

http://oca.microsoft.com/en/windiag.asp

To check your Hard Drive.

The drive manufacturer will have free diagnostic software to thoroughly check your drive for problems.

You can also load the Recovery Console and run ChkDsk /r to check for problems.

HOW TO: Install and Use the Recovery Console for Windows XP (Q307654)

http://support.microsoft.com/support/kb/articles/q307/6/54.asp

 

[timftse]

Thanks for the suggestions. I will try them and let you know.
I have already tried system restore, but Windows will not complete the restore - I have had chkdsk errors in one of the restore files itself, so that may be why.

Timftse.

 

[timftse]

It looks like the RAM is the problem. I have 1gb - 2 x 512mb, one newer than the other, and it is only since I added the 2nd that the errors started. I ran the windiag test with both DIMMS in and 1st pass gave an error, although the 2nd and 3rd didnt... I then tried with the 2 DIMMS individually and both seemed fine. Both are rated as PC3200 400mhz SDRAM DIMMS, so I don't know why there should be a problem. Both are bog-standard parts from DABS. Anyway, I have taken the newer one out and touch wood all has been fine the past few days.

Cheers.

 

[ASG0856]

Sounds like an impending hard drive failure. Try obtaining some hard drive diagnostics for your drive and see what that generates

 

[allteltec]

I had the same problems with a Asus MB. Athlon 3000+ I build for my son a couple years ago. It would BSD if both 512k sticks where in but was ok with one stick at a time. Asus had a list of Ram that was aproved for the MB. that I used when I order the Ram, but the place where I ordered from changed the Ram and said it would work ok, I only started have problems after a 3 to 4 weeks. The Athlon's are fussey about there Ram check the Gigabyte K8NF-9 info to see if thay have a list of aproved Ram.