Corrupted File?
Posted: Tue Apr 01, 2008 10:34 pm
I was doing my usual weekly system maintenance(XP) and I came across a file that sucks up my cpu cycles when I try to access it in Explorer or try to check the file for viruses. It does this even when I attempt to click on the file to view it's properties. The system is literally stuck trying to access this file until I shutdown windows and even doing that takes forever (since my CPU usage is always at 100%).
The disk needed to be defragged so I thought the resource hogging file could of been fragmented. I went ahead and ran scandisk and then defragged the hard drive, came back to the file afterwards and it still does the same thing. I tried to specify the file in the command console and I was able to see it's directory properties. I was also able to view the properties in Explorer via Safe Mode... so it sounds like there's something going on in Normal Windows, but what?
I've been thinking about just deleting the file. The file is not necessary for Windows to run or is a file to make other programs run and the file can easily be replaced. It's just that I don't know why one single file would do this to my system's CPU cycles.
What do you guys think?
Specs:
--------
- Asus A8N32-SLI Deluxe
- AMD FX-57 Single Core (Clocked @ 3.0Ghz)
- 2GB DDR400
- 2x 7900GTX Super OC in SLI
- 2x 150GB 10K Raptor X's RAID 0
- Windows XP SP2
The disk needed to be defragged so I thought the resource hogging file could of been fragmented. I went ahead and ran scandisk and then defragged the hard drive, came back to the file afterwards and it still does the same thing. I tried to specify the file in the command console and I was able to see it's directory properties. I was also able to view the properties in Explorer via Safe Mode... so it sounds like there's something going on in Normal Windows, but what?
I've been thinking about just deleting the file. The file is not necessary for Windows to run or is a file to make other programs run and the file can easily be replaced. It's just that I don't know why one single file would do this to my system's CPU cycles.
What do you guys think?
Specs:
--------
- Asus A8N32-SLI Deluxe
- AMD FX-57 Single Core (Clocked @ 3.0Ghz)
- 2GB DDR400
- 2x 7900GTX Super OC in SLI
- 2x 150GB 10K Raptor X's RAID 0
- Windows XP SP2