chkdsk c: /f gives "An unspecified error occurred" error message
in [Storage]
|
From: John. on 10 Feb 2007 09:13 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?
From: Rod Speed on 10 Feb 2007 13:34 Michael Cecil <macecil(a)gmail.com> wrote: > On Sat, 10 Feb 2007 06:13:01 -0800, John. <noemail(a)cox.net> wrote: > >> 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. 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. >> I can run chkdsk c: /p from the recovery console to >> do full scan for bad sectors, and both disks are fine. Odder and odder. >> 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. Except that the repair console is quite different to the installed XP. >> 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? 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. >> There's nothing in the event viewer logs, probably because it happens >> so early. Yep. >> Any ideas on how to debug or get more info, or resolve? > Perhaps you have something loading at boottime that is interfering > with the chkdsk process. What things are listed in the bootexecute > string in the registry at the following key? > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager Its unlikely to be that because that comes after the chkdsk run at startup. > You can enable boot logging from the Safe Mode menu screen. > Perhaps that can show what's happening. Ditto.
From: John. on 10 Feb 2007 14:56 On Sat, 10 Feb 2007 08:56:07 -0600, Michael Cecil <macecil(a)gmail.com> wrote: > >Perhaps you have something loading at boottime that is interfering with >the chkdsk process. What things are listed in the bootexecute string in >the registry at the following key? >HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager > >You can enable boot logging from the Safe Mode menu screen. Perhaps that >can show what's happening. 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?
From: John. on 10 Feb 2007 14:58 On Sun, 11 Feb 2007 05:34:09 +1100, "Rod Speed" <rod.speed.aaa(a)gmail.com> wrote: > >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. 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.
From: Rod Speed on 10 Feb 2007 15:47
John. <noemail(a)cox.net> wrote > Rod Speed <rod.speed.aaa(a)gmail.com> wrote >> 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. > I swapped my two 512mb memory cards and tried again. Same results. Thats not good enough, try an overnight run of memtest86+ > Of course I can still run chkdsk from the Recovery Console, but kind of inconvenient. And thats running on PE, not XP. |