Debug server crash

  • Thread starter Thread starter Scott
  • Start date Start date
S

Scott

Guest
I'm getting notification that the server recovered from a serious error.
Sending information to Microsoft indicates a device driver problem. It's a
production Terminal Server so following their process for troubleshooting is
pretty much out of the question, as the crash can not reliably be reproduced.

I downloaded and installed DebugDiag as well as symbol files. When i try and
do a crash analysis of memory.dmp I get an error message that DebugDiag
failed to locate the PEB (Process Environment Block) in memory.dmp, and as a
result, debug analysis for this dump may be incomplete or inaccurate.

Does anyone know what I need to do so that DebugDiag can successfully
analyze the memory.dmp? Or any other ideas on ways to capture and analyze the
source of the random blue screens?
 
Re: Debug server crash


"Scott" <Scott@discussions.microsoft.com> wrote in message
news:0EC66117-F0AF-438A-A9F6-AC60D5A14A14@microsoft.com...
> I'm getting notification that the server recovered from a serious error.
> Sending information to Microsoft indicates a device driver problem. It's a
> production Terminal Server so following their process for troubleshooting
> is
> pretty much out of the question, as the crash can not reliably be
> reproduced.
>
> I downloaded and installed DebugDiag as well as symbol files. When i try
> and
> do a crash analysis of memory.dmp I get an error message that DebugDiag
> failed to locate the PEB (Process Environment Block) in memory.dmp, and as
> a
> result, debug analysis for this dump may be incomplete or inaccurate.
>
> Does anyone know what I need to do so that DebugDiag can successfully
> analyze the memory.dmp? Or any other ideas on ways to capture and analyze
> the
> source of the random blue screens?

You might need to post on a System Programming newsgroup.

I am (at times) a system programmer and have done crash
dump analysis but generally have to fight my way through it
unless I have done it recently.

Post which tool (there are several) you are using to read the dump
file; what edition and version of the OS (exactly) you are using
exactly, and which symbols and what command line youa re
using explicitly -- as well as any subsequent steps if you are using
one of the graphical debuggers.

(Do this on a system level newgroup as I, or most of us here,
probably cannot tell you of the top of our head which step is
incorrect or give you the correct method.)

Find one of the online procedure guides for analyzing the dump
file and try to follow it explicitly -- this gives you a good way
to both ensure you are attempting it correctly and to communicate
exactly what steps, and why, you performed.

Last time I did this is was some couple of hours before I got a
clean analysis.

BTW, this may not be the best way.

Merely performing a chkdsk /r (repair) and then a REPAIR
install might be a more effective use of your time and effort.

Other than that the obvious of removing/updating any recent
driver changes.
 
Debug server crash - Scot

Debug server crash - Scot

The symbol server package that is being utilized would be wrong. Please follow the below steps
1. Start the Windows Debugger (WinDbg.exe).
2. On the File menu, click Symbol File Path.
3. In the Symbol path box, type the following command:
SRV*your local folder for symbols*http://msdl.microsoft.com/download/symbols
where your local folder for symbols is the folder in which you copy your local symbol cache. The debug symbols are downloaded to this location.
 
Re: Debug server crash - Scot

Re: Debug server crash - Scot

Hello Prashanth,

Is this an error mesaage, event viewer entry or something else? Please describe
your problem in detail, also the OS service pack and version you are using.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> The symbol server package that is being utilized would be wrong.
> Please follow the below steps
>
> 1. Start the Windows Debugger (WinDbg.exe).
>
> 2. On the File menu, click Symbol File Path.
>
> 3. In the Symbol path box, type the following command:
>
> SRV*your local folder for
> symbols*http://msdl.microsoft.com/download/symbols
>
> where your local folder for symbols is the folder in which you copy
> your local symbol cache. The debug symbols are downloaded to this
> location.
>
 
Debug server crash - Scot - Prashanth Naganna

Debug server crash - Scot - Prashanth Naganna

In addition you can also try the debugwiz tool. This does not require any symbol files and you can directly do a dump analysis by running the tools and poiting to the Memory.dmp file.
 
Back
Top