Jump to content
Posted 15 October 2005 - 10:00 PM
Posted 16 October 2005 - 11:02 AM
Posted 16 October 2005 - 11:56 AM
Edited by legoman786, 16 October 2005 - 11:56 AM.
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
- Rick Cook
Posted 17 October 2005 - 05:27 PM
Posted 17 October 2005 - 06:58 PM
Edited by Rimmer, 17 October 2005 - 06:59 PM.
Posted 18 October 2005 - 04:49 AM
Edited by B34R, 18 October 2005 - 05:32 AM.
Posted 18 October 2005 - 06:09 AM
Edited by stidyup, 18 October 2005 - 06:12 AM.
Posted 18 October 2005 - 06:55 AM
Running chkdsk may fix the problem.
NTFS4Dos is a freeware floppy disk that has a chkdsk utility that you can run.
Alternatively build the UBCD4Win which will give allow you to run chkdsk and other useful diagnostic utilities.
How to do a repair install
However on another forum I use one member who's a IT admin fears this \windows\system32\config\system as it's a indication that the hdd is failing. So you may want to run your hdd manufacturers diagnostic utility. I've seen this message before and done repair installs etc.... and the hdd has never failed afterwards but it's something else to consider.
Edited by B34R, 18 October 2005 - 08:29 AM.
0 members, 0 guests, 0 anonymous users