How to Keep Boot Log from a Failed Boot-Up?

I would like to know how to get a copy of boot log from a failed boot-
up that hangs.

Since three days ago, my PC cannot boot up. It always hang at a black
screen right after showing the Windows logo blue screen. I am trying
to use the /BOOTLOG option to see at which driver is causing the
problem. But when I get a failed boot up and then I reboot to "Safe
Mode with Network Connectivity", I find that the boot log file (C:
\Windows\ntbtlog.txt) has been overwritten by the boot log from
booting up at Safe Mode. This means I cannot get a boot log from the
failed boot-up.

I know I could have moved the C: drive from that PC and connected it
to another PC and view the boot log file from that PC. But this seems
to be a lot of work, and I believe that there must be an easier way.

Is there a way to keep the boot log from the failed boot up?

Thanks in advance for any help.

Jay Chan

How do you know a driver is causing the problem?

Can you boot to Safe Mode? Or can you eventually boot to the desktop? In
either case, Event Viewer may have the details you need.

Also try this:

"How to perform advanced clean-boot troubleshooting in Windows XP"
http://support.microsoft.com/kb/316434
---
Leonard Grey
Errare humanum est

Jay Chan wrote:
> I would like to know how to get a copy of boot log from a failed boot-
> up that hangs.
>
> Since three days ago, my PC cannot boot up. It always hang at a black
> screen right after showing the Windows logo blue screen. I am trying
> to use the /BOOTLOG option to see at which driver is causing the
> problem. But when I get a failed boot up and then I reboot to "Safe
> Mode with Network Connectivity", I find that the boot log file (C:
> \Windows\ntbtlog.txt) has been overwritten by the boot log from
> booting up at Safe Mode. This means I cannot get a boot log from the
> failed boot-up.
>
> I know I could have moved the C: drive from that PC and connected it
> to another PC and view the boot log file from that PC. But this seems
> to be a lot of work, and I believe that there must be an easier way.
>
> Is there a way to keep the boot log from the failed boot up?
>
> Thanks in advance for any help.
>
> Jay Chan

Jay


In Safe Mode examine the log for the failed normal mode boot and post
copies of any Warnings or Errors? Note log entries are date and time
stamped, which will enable you to determine which is a safe mode and
which is a normal mode. The easiest way forward is do another normal
mode boot and note the time.

Have a look in the System and Application logs in Event Viewer for
Errors and Warnings and post copies here. Don't post any more than 48
hours ago.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer. When researching the meaning
of the error, information regarding Event ID, Source and Description
are important.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.Microsoft.com/kb/308427/en-us

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.

The problem could well be a driver that is only needed in normal mode.
In safe mode boot a report is to be found in Event Viewer of drivers not
loaded. A copy of that Report would also be helpful.

USB drivers can be problematic. Disconnect USB devices and see what
affect that has on a normal mode mode. If you have a wireless mouse and
keyboard replace it with a wired keyboard may make a normal boot
possible.

Problems with a network card tend to manifest themselves in normal mode
and not in safe mode.

--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Jay Chan wrote:
> I would like to know how to get a copy of boot log from a failed boot-
> up that hangs.
>
> Since three days ago, my PC cannot boot up. It always hang at a black
> screen right after showing the Windows logo blue screen. I am trying
> to use the /BOOTLOG option to see at which driver is causing the
> problem. But when I get a failed boot up and then I reboot to "Safe
> Mode with Network Connectivity", I find that the boot log file (C:
> \Windows\ntbtlog.txt) has been overwritten by the boot log from
> booting up at Safe Mode. This means I cannot get a boot log from the
> failed boot-up.
>
> I know I could have moved the C: drive from that PC and connected it
> to another PC and view the boot log file from that PC. But this seems
> to be a lot of work, and I believe that there must be an easier way.
>
> Is there a way to keep the boot log from the failed boot up?
>
> Thanks in advance for any help.
>
> Jay Chan

On May 27, 5:14*pm, "Gerry" <ge...@nospam.com> wrote:
> Jay
>
> In Safe Mode examine the log for the failed normal mode boot and post
> copies of any Warnings or Errors? Note log entries are date and time
> stamped, which will enable you to determine which is a safe mode and
> which is a normal mode. The easiest way forward is do another normal
> mode boot and note the time.
>
> Have a look in the System and Application logs in Event Viewer for
> Errors and Warnings and post copies here. Don't post any more than 48
> hours ago.
>
> You can access Event Viewer by selecting Start, Control Panel,
> Administrative Tools, and Event Viewer. When researching the meaning
> of the error, information regarding Event ID, Source and Description
> are important.
>
> HOW TO: View and Manage Event Logs in Event Viewer in Windows XPhttp://support.Microsoft.com/kb/308427/en-us
>
> A tip for posting copies of Error Reports! Run Event Viewer and double
> click on the error you want to copy. In the window, which appears is a
> button resembling two pages. Click the button and close Event
> Viewer.Now start your message (email) and do a paste into the body of
> the message. Make sure this is the first paste after exiting from
> Event Viewer.
>
> The problem could well be a driver that is only needed in normal mode.
> In safe mode boot a report is to be found in Event Viewer of drivers not
> loaded. A copy of that Report would also be helpful.
>
> USB drivers can be problematic. Disconnect USB devices and see what
> affect that has on a normal mode mode. If you have a wireless mouse and
> keyboard replace it with a wired keyboard may make a normal boot
> possible.
>
> Problems with a network card tend to manifest themselves *in normal mode
> and not in safe mode.
>
> --
>
> Hope *this helps.
>
> Gerry
> *~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
>
>
> Jay Chan wrote:
> > I would like to know how to get a copy of boot log from a failed boot-
> > up that hangs.
>
> > Since three days ago, my PC cannot boot up. *It always hang at a black
> > screen right after showing the Windows logo blue screen. *I am trying
> > to use the /BOOTLOG option to see at which driver is causing the
> > problem. *But when I get a failed boot up and then I reboot to "Safe
> > Mode with Network Connectivity", I find that the boot log file (C:
> > \Windows\ntbtlog.txt) has been overwritten by the boot log from
> > booting up at Safe Mode. *This means I cannot get a boot log from the
> > failed boot-up.
>
> > I know I could have moved the C: drive from that PC and connected it
> > to another PC and view the boot log file from that PC. *But this seems
> > to be a lot of work, and I believe that there must be an easier way.
>
> > Is there a way to keep the boot log from the failed boot up?
>
> > Thanks in advance for any help.
>
> > Jay Chan- Hide quoted text -
>
> - Show quoted text -

Thanks for everyone who has responded.

I checked the ntbklog.txt file, and I could see that it keeps all the
successful boot-up's (such as all the Safe Mode boot up's). But it
didn't recorded any failed boot up -- none, not one line. This means
the idea of trying to save the boot log from the failed boot up is not
applicable in this case -- there was no info from the failed boot up
was saved in the boot log anyway.

I also checked the Event Viewer. There was no event recorded for any
of the failed startup either.

I gave up. And I used the Windows installation CD from the computer
manufacturer to repair Windows in my PC (fix it in place instead of a
fresh install). There were some problems here and there. Finally
almost everything is back to normal (except for one third party
software that I still cannot get it to run properly).

Just try to let everyone know how thing ends.

Jay Chan

On May 31, 10:55*pm, Jay Chan <jaykc...@hotmail.com> wrote:
> On May 27, 5:14*pm, "Gerry" <ge...@nospam.com> wrote:
>
>
>
>
>
> > Jay
>
> > In Safe Mode examine the log for the failed normal mode boot and post
> > copies of any Warnings or Errors? Note log entries are date and time
> > stamped, which will enable you to determine which is a safe mode and
> > which is a normal mode. The easiest way forward is do another normal
> > mode boot and note the time.
>
> > Have a look in the System and Application logs in Event Viewer for
> > Errors and Warnings and post copies here. Don't post any more than 48
> > hours ago.
>
> > You can access Event Viewer by selecting Start, Control Panel,
> > Administrative Tools, and Event Viewer. When researching the meaning
> > of the error, information regarding Event ID, Source and Description
> > are important.
>
> > HOW TO: View and Manage Event Logs in Event Viewer in Windows XPhttp://support.Microsoft.com/kb/308427/en-us
>
> > A tip for posting copies of Error Reports! Run Event Viewer and double
> > click on the error you want to copy. In the window, which appears is a
> > button resembling two pages. Click the button and close Event
> > Viewer.Now start your message (email) and do a paste into the body of
> > the message. Make sure this is the first paste after exiting from
> > Event Viewer.
>
> > The problem could well be a driver that is only needed in normal mode.
> > In safe mode boot a report is to be found in Event Viewer of drivers not
> > loaded. A copy of that Report would also be helpful.
>
> > USB drivers can be problematic. Disconnect USB devices and see what
> > affect that has on a normal mode mode. If you have a wireless mouse and
> > keyboard replace it with a wired keyboard may make a normal boot
> > possible.
>
> > Problems with a network card tend to manifest themselves *in normal mode
> > and not in safe mode.
>
> > --
>
> > Hope *this helps.
>
> > Gerry
> > *~~~~
> > FCA
> > Stourport, England
> > Enquire, plan and execute
> > ~~~~~~~~~~~~~~~~~~~
>
> > Jay Chan wrote:
> > > I would like to know how to get a copy of boot log from a failed boot-
> > > up that hangs.
>
> > > Since three days ago, my PC cannot boot up. *It always hang at a black
> > > screen right after showing the Windows logo blue screen. *I am trying
> > > to use the /BOOTLOG option to see at which driver is causing the
> > > problem. *But when I get a failed boot up and then I reboot to "Safe
> > > Mode with Network Connectivity", I find that the boot log file (C:
> > > \Windows\ntbtlog.txt) has been overwritten by the boot log from
> > > booting up at Safe Mode. *This means I cannot get a boot log from the
> > > failed boot-up.
>
> > > I know I could have moved the C: drive from that PC and connected it
> > > to another PC and view the boot log file from that PC. *But this seems
> > > to be a lot of work, and I believe that there must be an easier way.
>
> > > Is there a way to keep the boot log from the failed boot up?
>
> > > Thanks in advance for any help.
>
> > > Jay Chan- Hide quoted text -
>
> > - Show quoted text -
>
> Thanks for everyone who has responded.
>
> I checked the ntbklog.txt file, and I could see that it keeps all the
> successful boot-up's (such as all the Safe Mode boot up's). *But it
> didn't recorded any failed boot up -- none, not one line. *This means
> the idea of trying to save the boot log from the failed boot up is not
> applicable in this case -- *there was no info from the failed boot up
> was saved in the boot log anyway.
>
> I also checked the Event Viewer. *There was no event recorded for any
> of the failed startup either.
>
> I gave up. *And I used the Windows installation CD from the computer
> manufacturer to repair Windows in my PC (fix it in place instead of a
> fresh install). *There were some problems here and there. *Finally
> almost everything is back to normal (except for one third party
> software that I still cannot get it to run properly).
>
> Just try to let everyone know how thing ends.
>
> Jay Chan- Hide quoted text -
>
> - Show quoted text -

Actually repair Windows didn't work. I ended up getting some problems
that I could not fix. Now, I have re-installed Windows-XP (fresh new
install), and so far so good. I still need to re-install everything
though, oh well...

Jay Chan

Jay

Thanks for reporting how you resolved your problem. I have been busy
working the last few days or I would have answered your penultimate post
earlier.

If there are no reports in Event Viewer about a failed boot then it can
be that the problem occurs before logging starts. You then have to use
other ways to find out what the problem is.

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Jay Chan wrote:
> On May 31, 10:55 pm, Jay Chan <jaykc...@hotmail.com> wrote:
>> On May 27, 5:14 pm, "Gerry" <ge...@nospam.com> wrote:
>>
>>
>>
>>
>>
>>> Jay
>>
>>> In Safe Mode examine the log for the failed normal mode boot and
>>> post
>>> copies of any Warnings or Errors? Note log entries are date and time
>>> stamped, which will enable you to determine which is a safe mode and
>>> which is a normal mode. The easiest way forward is do another normal
>>> mode boot and note the time.
>>
>>> Have a look in the System and Application logs in Event Viewer for
>>> Errors and Warnings and post copies here. Don't post any more than
>>> 48
>>> hours ago.
>>
>>> You can access Event Viewer by selecting Start, Control Panel,
>>> Administrative Tools, and Event Viewer. When researching the meaning
>>> of the error, information regarding Event ID, Source and Description
>>> are important.
>>
>>> HOW TO: View and Manage Event Logs in Event Viewer in Windows
>>> XPhttp://support.Microsoft.com/kb/308427/en-us
>>
>>> A tip for posting copies of Error Reports! Run Event Viewer and
>>> double
>>> click on the error you want to copy. In the window, which appears
>>> is a
>>> button resembling two pages. Click the button and close Event
>>> Viewer.Now start your message (email) and do a paste into the body
>>> of
>>> the message. Make sure this is the first paste after exiting from
>>> Event Viewer.
>>
>>> The problem could well be a driver that is only needed in normal
>>> mode.
>>> In safe mode boot a report is to be found in Event Viewer of
>>> drivers not
>>> loaded. A copy of that Report would also be helpful.
>>
>>> USB drivers can be problematic. Disconnect USB devices and see what
>>> affect that has on a normal mode mode. If you have a wireless mouse
>>> and
>>> keyboard replace it with a wired keyboard may make a normal boot
>>> possible.
>>
>>> Problems with a network card tend to manifest themselves in normal
>>> mode
>>> and not in safe mode.
>>
>>> --
>>
>>> Hope this helps.
>>
>>> Gerry
>>> ~~~~
>>> FCA
>>> Stourport, England
>>> Enquire, plan and execute
>>> ~~~~~~~~~~~~~~~~~~~
>>
>>> Jay Chan wrote:
>>>> I would like to know how to get a copy of boot log from a failed
>>>> boot- up that hangs.
>>
>>>> Since three days ago, my PC cannot boot up. It always hang at a
>>>> black screen right after showing the Windows logo blue screen. I
>>>> am trying to use the /BOOTLOG option to see at which driver is
>>>> causing the problem. But when I get a failed boot up and then I
>>>> reboot to "Safe Mode with Network Connectivity", I find that the
>>>> boot log file (C: \Windows\ntbtlog.txt) has been overwritten by
>>>> the boot log from booting up at Safe Mode. This means I cannot get
>>>> a boot log from the failed boot-up.
>>
>>>> I know I could have moved the C: drive from that PC and connected
>>>> it to another PC and view the boot log file from that PC. But this
>>>> seems to be a lot of work, and I believe that there must be an
>>>> easier way.
>>
>>>> Is there a way to keep the boot log from the failed boot up?
>>
>>>> Thanks in advance for any help.
>>
>>>> Jay Chan- Hide quoted text -
>>
>>> - Show quoted text -
>>
>> Thanks for everyone who has responded.
>>
>> I checked the ntbklog.txt file, and I could see that it keeps all the
>> successful boot-up's (such as all the Safe Mode boot up's). But it
>> didn't recorded any failed boot up -- none, not one line. This means
>> the idea of trying to save the boot log from the failed boot up is
>> not applicable in this case -- there was no info from the failed
>> boot up was saved in the boot log anyway.
>>
>> I also checked the Event Viewer. There was no event recorded for any
>> of the failed startup either.
>>
>> I gave up. And I used the Windows installation CD from the computer
>> manufacturer to repair Windows in my PC (fix it in place instead of a
>> fresh install). There were some problems here and there. Finally
>> almost everything is back to normal (except for one third party
>> software that I still cannot get it to run properly).
>>
>> Just try to let everyone know how thing ends.
>>
>> Jay Chan- Hide quoted text -
>>
>> - Show quoted text -
>
> Actually repair Windows didn't work. I ended up getting some problems
> that I could not fix. Now, I have re-installed Windows-XP (fresh new
> install), and so far so good. I still need to re-install everything
> though, oh well...
>
> Jay Chan