dmp, hdmp & mdmp debug

Hi all,

is there anyone that can point me out on how to debug these crash dump file 
(dmp, hdmp, mdmp)? How can I integrated it with the visual studio IDE on my 
local pc in order to debug it?

Those crash dump file is correspond to the stop message on my remote Windows 
2003 server and it crashed whenever there's huge traffic that go into the 
IIS. I got different kinds of bug check code each time it crashes (ie: 0xa, 
0x19, 0x50, 0x8e, 0xc2) but most of the time it was 0xa and 0x50. 

The extension does not tell much about their origin, but,
I would start from `[cdb|ntsd|windbg] -z <path_to_dumpfile>`.
I'm told that DevEnv, starting VS2005 can open full crashdumps
for user-mode processes, but, in your case, you probably have
kernel minidumps or kernel  fulldumps, so, only the standard debuggers can 
help you.

-- 

-- 
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


"gnoh" <gnoh@discussions.microsoft.com> wrote in message 
news:088712FB-9991-43F2-AB1E-901F5DF5955A@microsoft.com...
> Hi all,
>
> is there anyone that can point me out on how to debug these crash dump 
> file
> (dmp, hdmp, mdmp)? How can I integrated it with the visual studio IDE on 
> my
> local pc in order to debug it?
>
> Those crash dump file is correspond to the stop message on my remote 
> Windows
> 2003 server and it crashed whenever there's huge traffic that go into the
> IIS. I got different kinds of bug check code each time it crashes (ie: 
> 0xa,
> 0x19, 0x50, 0x8e, 0xc2) but most of the time it was 0xa and 0x50.
>
> please advice. 

Hi Ivan, thanks for the reply.
Yes, those are the minidump files I got from the minidump folder as well as 
from the temporary folder when the prompted to send a error report to 
Microsoft after the crash which stored in .cab file. I managed to open the 
.dmp file with windbg and able to get some information like bug check code 
and also the process/image name that causes the reboot.

When I further check the .cab file containing the .hdmp and .mdmp files, it 
just shows me few lines and I do not understand it, somemore the filesize is 
more than 10Mbytes which I don't think it contain just a few lines of 
information. I try to open it directly from the VS2005, it did shows that it 
was from my own project name, and able to run it in debug mode, and further 
show the bug check code once the run button clicked. Is it possible to link 
this dump file to my source code so that I can check where's the bugs at, 
though I found that from the web stated that some of the bug check code might 
not able to catch by the try catch exception block.

What should I do next to find out the root cause of the crash? 



"Ivan Brugiolo [MSFT]" wrote:

> The extension does not tell much about their origin, but,
> I would start from `[cdb|ntsd|windbg] -z <path_to_dumpfile>`.
> I'm told that DevEnv, starting VS2005 can open full crashdumps
> for user-mode processes, but, in your case, you probably have
> kernel minidumps or kernel  fulldumps, so, only the standard debuggers can

> help you.
> 
> -- 
> 
> -- 
> This posting is provided "AS IS" with no warranties, and confers
no rights.
> Use of any included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> 
> 
> "gnoh" <gnoh@discussions.microsoft.com> wrote in message 
> news:088712FB-9991-43F2-AB1E-901F5DF5955A@microsoft.com...
> > Hi all,
> >
> > is there anyone that can point me out on how to debug these crash dump

> > file
> > (dmp, hdmp, mdmp)? How can I integrated it with the visual studio IDE
on 
> > my
> > local pc in order to debug it?
> >
> > Those crash dump file is correspond to the stop message on my remote 
> > Windows
> > 2003 server and it crashed whenever there's huge traffic that go into
the
> > IIS. I got different kinds of bug check code each time it crashes (ie:

> > 0xa,
> > 0x19, 0x50, 0x8e, 0xc2) but most of the time it was 0xa and 0x50.
> >
> > please advice. 
> 
> 

You have given quite confusing information
with regard of what you are trying to do and waht you are working with.

In the original post, you seem to imply that the maching bugcheck with
stop codes such as 0xA - IRQL_IS_NO_LESS_OR_EQUAL,
while, in the description below it seems you have user-mode
watson/WER dumps.
Watson dumps are made in certain operative system
by minidumps and heap dumps (.mdmp and .hdmp).
In order to be meraningfully debugged, the require a preliminary step
that merges them in a partial dump file. This step is normally done
on the receiving side of the *.CAB files prepared for submission.

Since you seem inclined to have your own dumps and debug them,
I would recomend to set up Wer to get full dumps, that can be easily
debugged with any debugger, without incurring the problems of partial dumps,
where only certain regions of the address space are actually stored.
Alternatively, you may want to consider using ADPlus.vbs that
allows a greater configurability of crash-dump options.

-- 

-- 
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


"gnoh" <gnoh@discussions.microsoft.com> wrote in message 
news:FD4D721F-9191-438C-83E1-9D0C806AD789@microsoft.com...
> Hi Ivan, thanks for the reply.
> Yes, those are the minidump files I got from the minidump folder as well 
> as
> from the temporary folder when the prompted to send a error report to
> Microsoft after the crash which stored in .cab file. I managed to open the
> .dmp file with windbg and able to get some information like bug check code
> and also the process/image name that causes the reboot.
>
> When I further check the .cab file containing the .hdmp and .mdmp files, 
> it
> just shows me few lines and I do not understand it, somemore the filesize 
> is
> more than 10Mbytes which I don't think it contain just a few lines of
> information. I try to open it directly from the VS2005, it did shows that 
> it
> was from my own project name, and able to run it in debug mode, and 
> further
> show the bug check code once the run button clicked. Is it possible to 
> link
> this dump file to my source code so that I can check where's the bugs at,
> though I found that from the web stated that some of the bug check code 
> might
> not able to catch by the try catch exception block.
>
> What should I do next to find out the root cause of the crash?
>
>
>
> "Ivan Brugiolo [MSFT]" wrote:
>
>> The extension does not tell much about their origin, but,
>> I would start from `[cdb|ntsd|windbg] -z <path_to_dumpfile>`.
>> I'm told that DevEnv, starting VS2005 can open full crashdumps
>> for user-mode processes, but, in your case, you probably have
>> kernel minidumps or kernel  fulldumps, so, only the standard debuggers

>> can
>> help you.
>>
>> -- 
>>
>> -- 
>> This posting is provided "AS IS" with no warranties, and
confers no 
>> rights.
>> Use of any included script samples are subject to the terms specified
at
>> http://www.microsoft.com/info/cpyright.htm
>>
>>
>> "gnoh" <gnoh@discussions.microsoft.com> wrote in
message
>> news:088712FB-9991-43F2-AB1E-901F5DF5955A@microsoft.com...
>> > Hi all,
>> >
>> > is there anyone that can point me out on how to debug these crash
dump
>> > file
>> > (dmp, hdmp, mdmp)? How can I integrated it with the visual studio
IDE 
>> > on
>> > my
>> > local pc in order to debug it?
>> >
>> > Those crash dump file is correspond to the stop message on my
remote
>> > Windows
>> > 2003 server and it crashed whenever there's huge traffic that go
into 
>> > the
>> > IIS. I got different kinds of bug check code each time it crashes
(ie:
>> > 0xa,
>> > 0x19, 0x50, 0x8e, 0xc2) but most of the time it was 0xa and 0x50.
>> >
>> > please advice.
>>
>>
>>