| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 67312 | 2006-03-24 03:42:00 | Too many chkdsk errors on XP Home SP2? | braindead (1685) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 440300 | 2006-03-24 03:42:00 | Recently I noticed that chkdsk was working after almost every reboot, scanning some or all of the partitions on my system (8 alltogether, spread over 2 HDs), and finding quite a bit of stuff such as: - First allocation unit is not valid. Entry will be truncated. - Converting lost chains to files. For example: 10992 kb in 68 recovered files found. Windows has made corrections to the file system. - Lost clusters found and corrected. ...that sort of thing. Sometimes after a reboot, there are only a few small sized corrections, sometimes involving much larger chunks of data. The results of the chkdsk scan appear in my C: as folders called 'found.000' etc, each containing file fragments. I was worried about all this huffing and puffing by chkdsk and suspected my HD might be going south. I bought a new HD to be on the safe side and Ghosted an earlier OS image to the new drive. But it too is exhibiting the same chkdsk behaviour. I've done a lot of reading and some say this is 'normal' and nothing to worry about. I'd much appreciate some advice on this, and also what to do with the found.000 folders. Delete? Does this mean there are now 'gaps' in my HD's data where these found files came from? Thanks! |
braindead (1685) | ||
| 440301 | 2006-03-25 02:00:00 | Bump. Anyone? | braindead (1685) | ||
| 440302 | 2006-03-25 02:11:00 | This is definitely not normal behaviour . ;) One sure way to provoke it is to turn the power off at the wall, rather than doing a proper shutdown . This is not recommended . I suspect Windows does this only when it knows it hasn't been shutdown properly (by looking at one of its own files, or it might be still using the byte in the BIOS CMOS memory) . Unless you are a real bit-bashing expert, all you can do with the found . xxx files is delete them . They tend to be parts of files, rather than complete identifiable files . (If they were recognisable, CHKDSK would fix them . :D) . I get this happening when I am running computers from a generator . When the generator stops, I get unplanned stoppages . ;) W2K seems to survive it, though one computer won't run some DOS programmes now . I suspect the the Windows startup (after CHKDSK has finished) checks the system files and quietly replaces any missing ones . If you aren't doing nasty things with the power, watch carefully what happens when you tell Windows to shut down . It should not be immediate . There will usually be some disk activity before it stops finally, unless the computer has been sitting idle for some time . If that looks OK, I'd go for the other Prime Suspect For Unexplained Things: memory . Try a memory tester . Memtest86 is good, and free . |
Graham L (2) | ||
| 440303 | 2006-03-25 03:06:00 | I know malware can make chkdisk scan on reboot. I fixed a pc a few mths ago, for my nephews mate. Chkdsk would appear everytime I rebooted. The guy had over 250 files relating to spyware/trojans etc. Once I got rid of the files, chkdisk stopped coming up on reboot. |
Speedy Gonzales (78) | ||
| 440304 | 2006-03-25 06:59:00 | Thank you very much for your replies guys! It's too early to tell without full testing but I may have located the source(s) of the problems I've been having. I have a Soltek 75KAV mobo, a bit old now but it's been extremely reliable for several years. Thanks to some posts elsewhere on Press F1 and BadCap.com, I was alerted to "The Curse Of The Bad Cap" - a batch of crap capacitors that Soltek and many other mobo manufacturers got sucked into using. Sure enough, on closer inspection my mobo had all the hallmarks of bad caps. A trip to JayCar in Newmarket procured 20x 2200uF 10v low ESR caps for around $10. A couple of hours of work, some honing of technique and the new caps were in place. With some trepidation, after a thorough check using a strong magnifying headband, I switched on and lo and behold all previous problems disappeared!!! I couldn't believe it at first. I rebooted and opened and closed various progs a number of times to be sure. All problems gone. Unbelievably, not only were 10x mobo caps faulty but some of the caps inside the power supply had gone down the toilet as well. I haven't replaced those yet but will do soon. Boy, you never can tell when you're being sold crap components. The suppliers take no responsibility for it and frequently a fault like this only reveals itself long after the warranty has expired. Soltek didn't want to know and in any case, they're no longer making mobos. Anyway - thanks for your help guys. I won't jump off a tall building just yet :) |
braindead (1685) | ||
| 440305 | 2006-03-25 07:57:00 | hm........well done......me I"m lazy .....with that many dead caps i'd have biffed the board and replaced it, much easier. | drcspy (146) | ||
| 440306 | 2006-03-25 08:07:00 | Cool! Whatever floats your boat. | braindead (1685) | ||
| 440307 | 2006-03-25 09:05:00 | Heh nothing like having ones finger crossed when turning on the computer :D | bob_doe_nz (92) | ||
| 440308 | 2006-03-25 09:14:00 | That's for sure! | braindead (1685) | ||
| 440309 | 2006-03-25 09:20:00 | I've had bad caps also cause the power supply to fail (in some cases odd stuff such as taking out specific lines such as the power to hard drives). Happening with Dell stuff too (the GX270s are well known to have used the faulty caps). Dell won't do anything until you get "signs" it is failing and they are only costing themselves as it seems to destroy the power supplies too.. Many more corpses are yet to be unearthed at my work :angry |
gibler (49) | ||
| 1 2 | |||||