I have XP Pro and the "autochk" utility ran at startup because of an
unexpected restart. It checked my C: drive and encountered and fixed
several errors. However, I fell asleep waiting for it to complete the
entire scan. When I woke up, it was at the desktop. Where do I find
the results of the what problems it found and what it fixed?

I already looked at the Event Viewer, but the most recent winlogin
1001 event was generated on 12/21/2008. I see nothing for today. I
also looked for the bootex file under the C: drive but nothing there
either. So what happened?

Using the Even Viewer, I looked under the system logs and I see
several reports of bad sectors with the exact timeframe of when
autochk would have been running. But those doesn't really give any
exact information about the problem and the results.

How do I find the actual "chkdsk" log output?

Thanks for your help,

--Randall

It's located in "event-viewer".

"R Krause" wrote:

> I have XP Pro and the "autochk" utility ran at startup because of an
> unexpected restart. It checked my C: drive and encountered and fixed
> several errors. However, I fell asleep waiting for it to complete the
> entire scan. When I woke up, it was at the desktop. Where do I find
> the results of the what problems it found and what it fixed?
>
> I already looked at the Event Viewer, but the most recent winlogin
> 1001 event was generated on 12/21/2008. I see nothing for today. I
> also looked for the bootex file under the C: drive but nothing there
> either. So what happened?
>
> Using the Even Viewer, I looked under the system logs and I see
> several reports of bad sectors with the exact timeframe of when
> autochk would have been running. But those doesn't really give any
> exact information about the problem and the results.
>
> How do I find the actual "chkdsk" log output?
>
> Thanks for your help,
>
> --Randall
>

Thanks but that doesn't answer my question. It's not in the event
viewer.

On Jan 19, 9:19*pm, Andrew E. <eckric...@msn.com> wrote:
> * It's located in "event-viewer".
>
>
>
> "R Krause" wrote:
> > I have XP Pro and the "autochk" utility ran at startup because of an
> > unexpected restart. It checked my C: drive and encountered and fixed
> > several errors. However, I fell asleep waiting for it to complete the
> > entire scan. When I woke up, it was at the desktop. Where do I find
> > the results of the what problems it found and what it fixed?
>
> > I already looked at the Event Viewer, but the most recent winlogin
> > 1001 event was generated on 12/21/2008. I see nothing for today. I
> > also looked for the bootex file under the C: drive but nothing there
> > either. So what happened?
>
> > Using the Even Viewer, I looked under the system logs and I see
> > several reports of bad sectors with the exact timeframe of when
> > autochk would have been running. But those doesn't really give any
> > exact information about the problem and the results.
>
> > How do I find the actual "chkdsk" log output?
>
> > Thanks for your help,
>
> > --Randall- Hide quoted text -
>
> - Show quoted text -

"Andrew E." <(E-Mail Removed)> wrote in message
news:ED226CA0-327C-4F20-ACF1-(E-Mail Removed)...
> It's located in "event-viewer".

World's most helpful response! Andrew, did you actually read the post beyond
the subject line?

Randall, it *is* in the Event Viewer, the Application log, under a source of
Winlogon (not "winlogin"). It should start with something like this:

"Checking file system on C:
"The type of the file system is NTFS.
"Volume label is WinXP.

"A disk check has been scheduled.
"Windows will now check the disk...."

but doesn't give you any more info than you would have seen if you'd stayed
awake :-)

The contents of the bootex.log file are copied to the event log upon startup
and the file deleted, so you can't see it (unless something interrupts
bootup or you are working in the Recovery Console).

Are your system date and time correct?

Maybe someone more knowledgeable can chip in with how to obtain more
detailed output, but I'm not sure it's available.

I much prefer to use Spinrite for this sort of thing - chkdsk *can* lose you
data whereas Spinrite tries *much, much* harder.

>
> "R Krause" wrote:
>
>> I have XP Pro and the "autochk" utility ran at startup because of an
>> unexpected restart. It checked my C: drive and encountered and fixed
>> several errors. However, I fell asleep waiting for it to complete the
>> entire scan. When I woke up, it was at the desktop. Where do I find
>> the results of the what problems it found and what it fixed?
>>
>> I already looked at the Event Viewer, but the most recent winlogin
>> 1001 event was generated on 12/21/2008. I see nothing for today. I
>> also looked for the bootex file under the C: drive but nothing there
>> either. So what happened?
>>
>> Using the Even Viewer, I looked under the system logs and I see
>> several reports of bad sectors with the exact timeframe of when
>> autochk would have been running. But those doesn't really give any
>> exact information about the problem and the results.
>>
>> How do I find the actual "chkdsk" log output?
>>
>> Thanks for your help,
>>
>> --Randall
>>

On Jan 20, 3:20*am, "Olórin" <inca...@erkljrjre890aeraekj4na.com>
wrote:
> Randall, it *is* in the Event Viewer, the Application log, under a sourceof
> Winlogon (not "winlogin"). It should start with something like this:
>
> "Checking file system on C:
> "The type of the file system is NTFS.
> "Volume label is WinXP.
>
> "A disk check has been scheduled.
> "Windows will now check the disk...."

Thanks for the helpful response. However, I looked under the Event
Viewer in the Application Log. This is all I could find for the past
seven days:

Error - 1/20/2009 - 2:58:28 AM - nview_info - None - 1
Error - 1/19/2009 - 1:49:47 PM - Application Error - 1000
Error - 1/19//2009 - 12:42:49 PM - Application Hang - 1002
Error - 1/19/2009 - 12:37:10 PM - Application Hang - 1002
Information - 1/19/2009 - 3:48:11 AM - LoadPerf - 1000
Information - 1/19/2009 - 3:48:10 AM - LoadPerf - 1001
Information - 1/19/2009 - 3:44:38 AM - Security Center - 1800
Error - 1/18/2009 - 5:58:55 PM - Application Hang - 1002
Error - 1/17-2009 - 11:58:55 PM - Application Hang - 1002
Error - 1/15/2009 - 1:06:32 AM - Application Error -1000

Examining each event in detail, I can find nothing even remotely
resembling the output of a disk scan which should have completed
around 3:40 AM on 1/19/2009. Do you have any other advice? I'm getting
concerned because everywhere I look online I'm told that Winlogon
should always be there. So what am I missing?

Thanks,
--Randall

R Krause <(E-Mail Removed)> wrote:

>Examining each event in detail, I can find nothing even remotely
>resembling the output of a disk scan which should have completed
>around 3:40 AM on 1/19/2009. Do you have any other advice? I'm getting
>concerned because everywhere I look online I'm told that Winlogon
>should always be there. So what am I missing?

That it's highly probably that CHKDSK didn't run.

On Jan 21, 3:13*pm, Danny Krychek <krych...@crstordan.invalid> wrote:
> R Krause <rkra...@searstower.org> wrote:
> >Examining each event in detail, I can find nothing even remotely
> >resembling the output of a disk scan which should have completed
> >around 3:40 AM on 1/19/2009. Do you have any other advice? I'm getting
> >concerned because everywhere I look online I'm told that Winlogon
> >should always be there. So what am I missing?
>
> That it's highly probably that CHKDSK didn't run.

If it didn't run then why on January 19 at 3:10 am did it come up with
a blue screen stating that Windows needed to check my disk for
consistency and asked me whether I wanted to continue to which I
selected yes?

--Randall

If you are using NTFS, use the /V switch which will display any cleanup
messages. I don't know if the window stays until you press the any key, or
if it just reboots as usual when it's done. I tried it earlier, but had no
cleanup messages, so. . .
SC Tom

"Olórin" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "Andrew E." <(E-Mail Removed)> wrote in message
> news:ED226CA0-327C-4F20-ACF1-(E-Mail Removed)...
>> It's located in "event-viewer".
>
> World's most helpful response! Andrew, did you actually read the post
> beyond the subject line?
>
> Randall, it *is* in the Event Viewer, the Application log, under a source
> of Winlogon (not "winlogin"). It should start with something like this:
>
> "Checking file system on C:
> "The type of the file system is NTFS.
> "Volume label is WinXP.
>
> "A disk check has been scheduled.
> "Windows will now check the disk...."
>
> but doesn't give you any more info than you would have seen if you'd
> stayed awake :-)
>
> The contents of the bootex.log file are copied to the event log upon
> startup and the file deleted, so you can't see it (unless something
> interrupts bootup or you are working in the Recovery Console).
>
> Are your system date and time correct?
>
> Maybe someone more knowledgeable can chip in with how to obtain more
> detailed output, but I'm not sure it's available.
>
> I much prefer to use Spinrite for this sort of thing - chkdsk *can* lose
> you data whereas Spinrite tries *much, much* harder.
>
>>
>> "R Krause" wrote:
>>
>>> I have XP Pro and the "autochk" utility ran at startup because of an
>>> unexpected restart. It checked my C: drive and encountered and fixed
>>> several errors. However, I fell asleep waiting for it to complete the
>>> entire scan. When I woke up, it was at the desktop. Where do I find
>>> the results of the what problems it found and what it fixed?
>>>
>>> I already looked at the Event Viewer, but the most recent winlogin
>>> 1001 event was generated on 12/21/2008. I see nothing for today. I
>>> also looked for the bootex file under the C: drive but nothing there
>>> either. So what happened?
>>>
>>> Using the Even Viewer, I looked under the system logs and I see
>>> several reports of bad sectors with the exact timeframe of when
>>> autochk would have been running. But those doesn't really give any
>>> exact information about the problem and the results.
>>>
>>> How do I find the actual "chkdsk" log output?
>>>
>>> Thanks for your help,
>>>
>>> --Randall
>>>
>
>
>