- chkdsk c: /f gives "An unspecified error occurred" error message
- Posted by John. on February 10th, 2007
This is probably an XP issue, but can anyone help me getting "An
unspecified error occurred"?
After running 'chkdsk c: /f' from the command prompt, I get the prompt
to run at startup which I say yes to.
After startup, I get the 10 second countdown, and then immediately the
message: "An unspecified error occurred." and then chkdsk terminates
and xp pr sp2 loads.
Is there any way to find out WHAT the error is?
It happens on both c: and d: (paging file) drive. I can run chkdsk c:
/p from the recovery console to do full scan for bad sectors, and both
disks are fine.
I don't think it is an actual drive problem because it happens
immediately after starting chkdsk, almost as if there is some XP
return code problem.
I've thoroughly scanned the pc with multiple anti-malware products,
and everything seems ok otherwise.
Any ideas on what it is, or how I can get more info to debug this?
There's nothing in the event viewer logs, probably because it happens
so early.
Any ideas on how to debug or get more info, or resolve?
- Posted by Rod Speed on February 10th, 2007
Michael Cecil <macecil@gmail.com> wrote:
Thats likely significant because while chkdsk can just give
up like that on some subtle NTFS problems, you're unlikely
to have developed those on two different partitions.
Odder and odder.
Except that the repair console is quite different to the installed XP.
I'd try and overnight memtest86 run, it could be that you have a
minor memory problem thats only visible in the startup chkdsk run.
Might be early bad caps on the motherboard too.
Might even be a bad power supply, excessive
ripple can produce the weirdest symptoms.
Yep.
Its unlikely to be that because that comes after the chkdsk run at startup.
Ditto.
- Posted by John. on February 10th, 2007
On Sat, 10 Feb 2007 08:56:07 -0600, Michael Cecil <macecil@gmail.com>
wrote:
The BootExecute key shows the normal: autocheck autochk *
I enabled boot log, but I think that is after the pre-windows chkdsk
runs.
Other that this annoyance, everything is working fine. I just have to
use the Recovery Console to run chkdsk which is annoying.
Any other ideas?
- Posted by John. on February 10th, 2007
On Sun, 11 Feb 2007 05:34:09 +1100, "Rod Speed"
<rod.speed.aaa@gmail.com> wrote:
I swapped my two 512mb memory cards and tried again. Same results.
Of course I can still run chkdsk from the Recovery Console, but kind
of inconvenient.
- Posted by Rod Speed on February 10th, 2007
John. <noemail@cox.net> wrote
Thats not good enough, try an overnight run of memtest86+
And thats running on PE, not XP.
- Posted by John. on February 11th, 2007
On Sat, 10 Feb 2007 16:33:56 -0600, Michael Cecil <macecil@gmail.com>
wrote:
Yes, it's there. Your suggestion though has led me to review the
security and permissions for the c: drive and folders. Some look a
little strange, but so far no luck. It is almost like the autochk
program is getting denied access to the drive or some other registry
abnormality affecting this only. (I'm not planning to reformat just
for this. Think I'll wait awhile for Vista if I'm going to redo
everything.)
Thanks for your ideas.
- Posted by Cl.Massé on February 12th, 2007
"John." <noemail@cox.net> a écrit dans le message de news:
sgkrs29n4veusv6t9ppep285s8ei37u50l@4ax.com
Apparently, the chkdsk exe on your hard drive is corrupt. With the recovery
console, you use the one on the installation CD. The solution is to copy it
again from the CD.
Something like: expand E:\I386\chkdsk.ex_ C:\Windows\system32\chkdsk.exe
--
~~~~ clmasse on free F-country
Free technical support at : http://www.protonic.com/
