i got a blue screen issue accidentally after boot up for a day. btw, i got
the *.dmp file, but dun know how to analysis and find the problems. how can i
open this? thankss

"muitommy" <muitommy@discussions.microsoft.com> wrote in message
news:A2E0E760-2981-4F41-93EC-3D098411CD49@microsoft.com...[color=blue]
>i got a blue screen issue accidentally after boot up for a day. btw, i got
> the *.dmp file, but dun know how to analysis and find the problems. how
> can i
> open this? thankss[/color]

Dump file are really for sending to Microsoft for debugging. There is very
little in there that will be of use to you.
You can upload your dump to OCA [url]http://oca.microsoft.com/en/Welcome.aspx[/url] or
send it to an engineer if you open a case about it.
As an end user if you just want to do bit of work yourself the blue screen
information contained all the relevant information you require to work on
this problem.
--

Mike Brannigan

Hi,

If you really want to analyze these files yourself, then download WinDBG
(part of the Debugging Tools for Windows) from the Microsoft website.

Open WinDBG and type the following commands:

..symfix
..reload
!analyze -v

That performs some automated analysis of the dump file, and may give you
some pointers. That said, reading dumps generally requires some knowledge of
Window internals, and how Windows works. If this is something you'd like to
learn about, then Windows Internals 4th Ed (by Mark Russinovich and David
Solomon) is worth buying.

Cheers
Ken


"muitommy" <muitommy@discussions.microsoft.com> wrote in message
news:A2E0E760-2981-4F41-93EC-3D098411CD49@microsoft.com...[color=blue]
>i got a blue screen issue accidentally after boot up for a day. btw, i got
> the *.dmp file, but dun know how to analysis and find the problems. how
> can i
> open this? thankss[/color]

Ken, the 4th Ed does not cover Vista, so while a useful primer it may lead
to a few "bum steers"

--

Mike Brannigan
"Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
news:eyMDH1LjHHA.4520@TK2MSFTNGP02.phx.gbl...[color=blue]
> Hi,
>
> If you really want to analyze these files yourself, then download WinDBG
> (part of the Debugging Tools for Windows) from the Microsoft website.
>
> Open WinDBG and type the following commands:
>
> .symfix
> .reload
> !analyze -v
>
> That performs some automated analysis of the dump file, and may give you
> some pointers. That said, reading dumps generally requires some knowledge
> of Window internals, and how Windows works. If this is something you'd
> like to learn about, then Windows Internals 4th Ed (by Mark Russinovich
> and David Solomon) is worth buying.
>
> Cheers
> Ken
>
>
> "muitommy" <muitommy@discussions.microsoft.com> wrote in message
> news:A2E0E760-2981-4F41-93EC-3D098411CD49@microsoft.com...[color=green]
>>i got a blue screen issue accidentally after boot up for a day. btw, i got
>> the *.dmp file, but dun know how to analysis and find the problems. how
>> can i
>> open this? thankss[/color]
>[/color]

It can, but it usually can at least pin it to a specific driver. At least
in my case it was able to.

Joe

"Mike Brannigan" <Mike.Brannigan@localhost> wrote in message
news:DC3FB9C8-0EBC-44FC-BF8E-3DC7242CB87F@microsoft.com...[color=blue]
> Ken, the 4th Ed does not cover Vista, so while a useful primer it may lead
> to a few "bum steers"
>
> --
>
> Mike Brannigan
> "Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
> news:eyMDH1LjHHA.4520@TK2MSFTNGP02.phx.gbl...[color=green]
>> Hi,
>>
>> If you really want to analyze these files yourself, then download WinDBG
>> (part of the Debugging Tools for Windows) from the Microsoft website.
>>
>> Open WinDBG and type the following commands:
>>
>> .symfix
>> .reload
>> !analyze -v
>>
>> That performs some automated analysis of the dump file, and may give you
>> some pointers. That said, reading dumps generally requires some knowledge
>> of Window internals, and how Windows works. If this is something you'd
>> like to learn about, then Windows Internals 4th Ed (by Mark Russinovich
>> and David Solomon) is worth buying.
>>
>> Cheers
>> Ken
>>
>>
>> "muitommy" <muitommy@discussions.microsoft.com> wrote in message
>> news:A2E0E760-2981-4F41-93EC-3D098411CD49@microsoft.com...[color=darkred]
>>>i got a blue screen issue accidentally after boot up for a day. btw, i
>>>got
>>> the *.dmp file, but dun know how to analysis and find the problems. how
>>> can i
>>> open this? thankss[/color]
>>[/color]
>[/color]

You can also download and install windbg from Microsoft. Run it as
administrator and open the dump file.

Use the commands:

..symfix
..reload
!analyze -v

It should at least pin down the driver that caused the BSOD.

Joe

"muitommy" <muitommy@discussions.microsoft.com> wrote in message
news:A2E0E760-2981-4F41-93EC-3D098411CD49@microsoft.com...[color=blue]
>i got a blue screen issue accidentally after boot up for a day. btw, i got
> the *.dmp file, but dun know how to analysis and find the problems. how
> can i
> open this? thankss[/color]