dumpchk question

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have dumpchk.exe in c:\windows\system32, and i have a dumpfile in
windows\minidump.

from cmd prompt i use cd to change to system path (as above) but I'm not
able to read this file and get error messages.

So what is the correct syntax?
 
Hi,

How to read minidump files:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/minidump_files.asp

Basically, the casual user will not be able to do this, nor understand what
they are looking at even with the symbols installed. Dumpcheck.exe is used
to create the minidump file on system failure, and it can be used to help
analyze what has gone wrong by someone with the right skill set. Are you
actually having a problem or are you just curious?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org
 
Both. I'm having a problem and want to learn. I have the dump file as a txt
file now. The dump_header32 section is where I should be looking for the
driver issue. But what I need to know is how to do this. BugCheckCode is
100000d1. I don't see anything like this: 0x0000
 
bugcheckparameter4 is f76b3ala. So would this be the exception address? Or is
bugcheckcode the exception address?
 
Hi,

100000d1 is probably a driver error, but without the full dump it's
impossible to tell. The .dmp file may contain stack and module information
that indicates where the problem is.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org
 
It is the same details as this error.

Driver Development Tools: Windows DDK

Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 Memory referenced
2 IRQL at time of reference
3 0: Read
1: Write

4 Address that referenced memory


Cause
A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high.

This bug check is usually caused by drivers that have used improper addresses.

Resolving the Problem
To begin debugging, use a kernel debugger to get a stack trace.

Send feedback on this topic. / Built on Thursday, February 13, 2003
 
That's what I'm figuring, but need to look at the dump to see which driver
is causing the error.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

"David Candy" <.> wrote in message
It is the same details as this error.

Driver Development Tools: Windows DDK

Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This
indicates that a kernel-mode driver attempted to access pageable memory at a
process IRQL that was too high.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 Memory referenced
2 IRQL at time of reference
3 0: Read
1: Write

4 Address that referenced memory


Cause
A driver tried to access an address that is pageable (or that is completely
invalid) while the IRQL was too high.

This bug check is usually caused by drivers that have used improper
addresses.

Resolving the Problem
To begin debugging, use a kernel debugger to get a stack trace.

Send feedback on this topic. / Built on Thursday, February 13, 2003
 
I tracked this down to NDIS.sys by utilising pstat to id the driver closest
to the bugcheckcode i.e. 0xd1. There is a stated problem and an experimental
patch for this network device at Microsoft. I guess the unloaded modules
would have done the job of pstat.
 
Back
Top