No Crash Logo
Simple install, no plumbing Solar Hot Water! Save $$$   Click Here

 weird problems and changes to xp after chkdsk util Post a Reply  
From: Wes on 06/19/2006
Never had any issues with machine running XP Home SP2, 40GB 256MB RAM, 2.0 P4, until last night. I always run virus scans and utilities compliments of System Mechanic 6's suite of trusty tools. I stress, I have never had a problem with this machine!

I used Norton Partition Magic to resize an active ntsc partition on the primary (only) harddrive. It is a 40 GB hd and had about 20 GB free. So I decided to resize the partion (C) to 30 GB and then create a new 10 GB partition in the newly added space to use for backup or whatever. I clicked apply and the program did its thing and then prompted me to restart to reflect the changes.

As it booted back up, it went into a norton partion magic screen which showed a couple progress bars indicating where it was at as far as performing the tasks I had asked it to do. When it was all said and done, it restarted again to reflect changes. This is where I think it started going down hill. As I watched it sucessfully restart, the chkdsk utility started and told me that one or more drives needed to be checked or verified (or something like that). I let it do its thing, while I left the room for about 30 seconds. When I returned, it had started something new automatically - it was listing off hundreds of the following:
Deleting an index entry with Id 256 from index $SII of file 9.
Deleting an index entry with Id 257 from index $SII of file 9.
Deleting an index entry with Id 258 from index $SII of file 9.
Deleting an index entry with Id 259 from index $SII of file 9.
Deleting an index entry with Id 260 from index $SII of file 9.
Deleting an index entry with Id 261 from index $SII of file 9.
Deleting an index entry with Id 262 from index $SII of file 9.
Deleting an index entry with Id 263 from index $SII of file 9.
Deleting an index entry with Id 264 from index $SII of file 9.
Deleting an index entry with Id 256 from index $SDH of file 9.
Deleting an index entry with Id 261 from index $SDH of file 9.
Deleting an index entry with Id 264 from index $SDH of file 9.
Deleting an index entry with Id 260 from index $SDH of file 9.
Deleting an index entry with Id 258 from index $SDH of file 9.
Deleting an index entry with Id 263 from index $SDH of file 9.
Deleting an index entry with Id 259 from index $SDH of file 9.
Deleting an index entry with Id 257 from index $SDH of file 9.
Deleting an index entry with Id 262 from index $SDH of file 9.

Then as soon as it ended with that it started listing off THOUSANDS of:
Replacing invalid security id with default security id for file 11.
Replacing invalid security id with default security id for file 29.
Replacing invalid security id with default security id for file ............

AND THIS WENT ON FOR A GOOD 15 MINUTES. Unsure of why and what it was doing and fearful of stopping it in the middle of what it was doing somehow, I allowed it to continue. The number at the end always grew and grew, and must have gone through at least 100,000.

Votes:

Rating: 0
Delete: 0
FAQ | Search     Post a Reply  

Home | About | Privacy & Security | Helpful Programs

Solar Energy News and more at the TechLuck Green Energy Forum

Copyright © 1999 thru 2024 Kronos Technologies Inc. All Rights Reserved.
See Terms and Conditions for more information.