Debugger log file

[Esteban]

Hi,

I have some somescreen on a computer and i heard about debuglog.txt
file or any name you gave it, that can log all the errors generated by
drivers and i think you need to active the special pool...i used
verifier.exe and enabled it but i don't know how to generated a file
with all the info on drivers errors, blue screen message, etc...

I downloaded the 2 windows debuggers, kd.exe and windbg but i'm not
used to it. Any help to get this log file is apreciate!


Esteban

 

[Wesley Vogel]

Do you mean BOOTLOG?

Start | Run | Type: msconfig | OK |
Boot.ini tab | Select: /BOOTLOG | Apply | OK

/bootlog = Enables boot logging to a file called %systemroot%\Ntbtlog.txt.

C:\WINDOWS\Ntbtlog.txt

/BOOTLOG - This option tells Windows XP to log everything it does during the
boot process to the c:\windows\ntbtlog.txt file. This can be useful for
diagnosing startup problems by seeing exactly where the boot process is
hanging.

Note
[[In safe mode, new boot log entries are appended to the existing
Ntbtlog.txt file.]]

Boot Logging
http://www.microsoft.com/resources/...windows/xp/all/reskit/en-us/prmb_tol_rpsc.asp

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[David Candy]

Type verifier in Start Run, follow the wizard but choose All Drivers. This will slow down your computer and cause more blue screen crashes but will pinpoint what is causing the crash (if the original error message didn't). Once you fix it you rerun verifier and turn it off.

If you can't start after enabling verifier
choose Last Known Good Configuration at the Failed Boot menu (which will
start without verifier).


You will be creating a crash dump file in c:\windows\minidump every blue screen. Make sure you are set to record minidumps (Small Memory Dumps) - type it in Help to see how.

Then

If you have the XP SP2 Security Update CD (else see
http://www.microsoft.com/whdc/­devtools/debugging/symbolpkg.m­spx
)


Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS

Download
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

Load the crash dump file into windbg
and read what it says. You may need to tell it where the symbols are. Read it.
Type
!Analyze -v
into Windbg's command line.
(this will hopefully tell you the faulty component)

If the above is too technical then email the crash dump files to davidc @ mvps.org. Don't send me lots of them. Just the one from your last crash after you turn verifier on. And only one per mail.

You can look up specific details here
http://msdn.microsoft.com/library/d..._ea8b9fd0-2d81-4a04-a7ed-c1c6a80bd501.xml.asp

If it indicates faulty memory might be the cause you can get a memory tester
here
http://oca.microsoft.com/en/wi­ndiag.asp


If it mentions a core windows system file, meaning it a MS fix is required,
upload a minidump to

http://oca.microsoft.com

Also try typing the main error code in Help while online (ie,
Stop 0x50
and also try in the 8 digit form
stop 0x00000050)
and if there are too many hits use a filename if available. Generally memory
addresses are different for each computer (as each computer has a different
mix of drivers) so parameters that are memory addresses aren't that useful for searching, but NTStatus codes are (plus you can look them up here http://cvs.sourceforge.net/viewcvs.py/mingw/w32api/include/ddk/ntstatus.h?rev=1.2).

 

[Ramesh, MS-MVP]

Been in Hibernation last 2 days ?

--
Ramesh, Windows XP MVP
http://windowsxp.mvps.org


"David Candy" <.> wrote in message
Type verifier in Start Run, follow the wizard but choose All Drivers. This
will slow down your computer and cause more blue screen crashes but will
pinpoint what is causing the crash (if the original error message didn't).
Once you fix it you rerun verifier and turn it off.

If you can't start after enabling verifier
choose Last Known Good Configuration at the Failed Boot menu (which will
start without verifier).


You will be creating a crash dump file in c:\windows\minidump every blue
screen. Make sure you are set to record minidumps (Small Memory Dumps) -
type it in Help to see how.

Then

If you have the XP SP2 Security Update CD (else see
http://www.microsoft.com/whdc/­devtools/debugging/symbolpkg.m­spx
)


Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS

Download
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

Load the crash dump file into windbg
and read what it says. You may need to tell it where the symbols are. Read
it.
Type
!Analyze -v
into Windbg's command line.
(this will hopefully tell you the faulty component)

If the above is too technical then email the crash dump files to davidc @
mvps.org. Don't send me lots of them. Just the one from your last crash
after you turn verifier on. And only one per mail.

You can look up specific details here
http://msdn.microsoft.com/library/d..._ea8b9fd0-2d81-4a04-a7ed-c1c6a80bd501.xml.asp

If it indicates faulty memory might be the cause you can get a memory tester
here
http://oca.microsoft.com/en/wi­ndiag.asp


If it mentions a core windows system file, meaning it a MS fix is required,
upload a minidump to

http://oca.microsoft.com

Also try typing the main error code in Help while online (ie,
Stop 0x50
and also try in the 8 digit form
stop 0x00000050)
and if there are too many hits use a filename if available. Generally memory
addresses are different for each computer (as each computer has a different
mix of drivers) so parameters that are memory addresses aren't that useful
for searching, but NTStatus codes are (plus you can look them up here
http://cvs.sourceforge.net/viewcvs.py/mingw/w32api/include/ddk/ntstatus.h?rev=1.2).

 

[Esteban]

Thanks! I used windows debugger to read the dump files but most of the
time it is differents driver that cause the problem so i formated the
system without more then SP1 and i'm now waiting the BSOD...if i don't
get any well i guess it wasn't hardware problem. Most of the problem i
have here with computers blue screen is the the blue screen can happen
in a week, in a month or 2 times a days...this make me nuts cuz it's
hard to diagnostic. Even if i test the memory with memtest, it passed
the test very well...but until the computer doesn't crash it's normal
that the memory test looks fine.

Thanks to all! Have a nice day!