Bootlog?

So I'm trying to troubleshoot something going on in Windows XP, and I'd like to use the bootlog option. I'm selecting the option from the boot options when booting into windows, and then reboot into Windows Safe Mode with Command Prompt. Will this work, or do I need to boot with an emergency startup disc to recover the log? Also, where does Windows store the log file?

You set the option under msconfig?

If so it should create C:/bootlog.txt or perhaps NTBTLOG.txt

I did not set the option. I inherited a computer from my dad that has a problem with rebooting seconds after I get to the destkop. I was hoping a logged boot could provide some answers as to why this may be happening. Not sure what options have been set, but I definitely do not see either file in the C:\ directory after booting into safe mode w/command prompt.

I suspect this may be a driver conflict issue, since I can boot into safe mode steadily and without it automatically rebooting. My hope was that the bootlog would be able to provide me with a clue or two as to where I may start.

If it all comes down to it, I've got the recovery discs from HP. I've been yearning to do a -u format on this baby for quite some time...

...you CAN still do that in XP, right?

In order to get a boot log you need to go to start Run... msconfig | BOOT.INI

Check the box /BOOTLOG

This will then create a boot log when ever you boot.

The Recovery Options depend on HP. What is the exact HP model? In most cases you cannot totally format as HP stores recovery data on the hard drive. We can look up your specific model to verify:

http://welcome.hp.com/country/us/en/support.html

Thanks for the tip. I'm booting into safe mode to make sure that's enabled.

I've found my machine, but I'm not sure where to go from here:

http://h10025.www1.hp.com/ewfrf/wc/p...&lang=en&cc=us

I have a hp pavilion 520n.

http://h10025.www1.hp.com/ewfrf/wc/d...cname=bph07145

So my machine has this hidden partition. Would I be able to identify and remove that partition with a utility such as the QTPARTed that comes with KNOPPIX?

I've enabled the bootlog and did the enable logging option when booting into windows, and the problem is now gone. I mean, it's been running for at least ten minutes now and isn't rebooting. Possibly because all the drivers and such are still not loading?

As I read that HP page that partition is used to create the disks if you choose to create them. Otherwise it is used from within XP to reinstall.

In other words the main partition C: drive will be formatted but this HP partition will not.

If you were to totally wipe the hard drive (both partitions) you would need a retail Microsoft XP CD to reinstall.


Logging should not affect what drivers load as Safe Mode does.


Look in your Event viewer: rt. click My Computer then click Manage then Event Viewer.
Or: Administrative Tools/Event Viewer or Start/Run/ eventvwr
Open the system as well as the application tabs & look for red X errors. Click error line for details.
Post back the source & event id & Description especially of errors that seem to coincide with this issue.
Also check the Information lines that might coincide with this issue.

How to view and manage event logs in Event Viewer in Windows XP

There are quite a few errors here. These are what really caught my eye:

System Tab:
EventID 7: The device, \Device\HardDisk0\D, has a bad block
EventID 7026: The following boot-start or system-start driver(s) failed to load:
eeCtrl
Fips
IPSec
MRxSmb
NetBIOS
NetBT
RasAcd
Rdbss
SAVRTPEL
SYMTDI
Tcpip

Application Tab:
EventID 4609: The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\nt_qxp\com\com1x\src\events\tier1\eventsystemob j.cpp. Please contact Microsoft Product Support Services to report this error.
EventID 8193: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206

I don't figure that can be anything good.

Those unloaded drivers could have been during Safe Mode boot?

Also is your XP loaded on C:

If so I assume that D: is the HP partition? Or is this a partition that you use?

If D:=HP the Bad Block as well as the Bad Return might simply be HP's way of protecting that partition. Of course if D: is a partition that you use then the previous idea is not relevant.

A bad block is a sector of a hard drive that has been removed from use usually because of mechanical damage. It otherwise should not affect the remainder of the drive.

If you want to go back to the beginning: What are the exact problems that you were/are having?