PC Review


Reply
Thread Tools Rate Thread

How can I open and read the minidump file?

 
 
=?Utf-8?B?VG9ueSBW?=
Guest
Posts: n/a
 
      31st Dec 2006
I have a Gateway DX300 that has MCE XP Home and I had a crash yesterday that
created a minidump file on my machine. I have SP2 and the machine is patched
and current. I run AVG anti-virus and firewall and also Spysweeper.

How do I open it and attempt to read/understand what the cause of the crash
was? Are there any debug tools I can download and use as a home user?

Please advise. Thanks
Tony V
 
Reply With Quote
 
 
 
 
Gerry Cornell
Guest
Posts: n/a
 
      31st Dec 2006
Tony

They are very difficult to interpret.

Can you provide a copy of the Stop Error Report?

I suggest you Disable automatic restart on system failure. This
should help by allowing time to write down the STOP code properly.
Right click on the My Computer icon on the Desktop and select
Properties, Advanced, StartUp and Recovery, System Failure and uncheck
box before Automatically Restart.

Do not re-enable automatic restart on system failure until you have
resolved the problem. Check for variants of the Stop Error message.

There will also be Error Reports in Event Viewer. Please post copies.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer. When researching the meaning
of the error, information regarding Event ID, Source and Description
are important.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/kb/308427/en-us

Part of the Description of the error will include a link, which you
should double click for further information. You can copy using copy
and paste. Often the link will, however, say there is no further
information.
http://go.microsoft.com/fw.link/events.asp
(Please note the hyperlink above is for illustration purposes only)

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event Viewer.
Now start your message (email) and do a paste into the body of the
message. This will paste the info from the Event Viewer Error Report.
Make sure this is the first paste after exiting from Event Viewer.



--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~




--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Tony V wrote:
> I have a Gateway DX300 that has MCE XP Home and I had a crash
> yesterday that created a minidump file on my machine. I have SP2 and
> the machine is patched and current. I run AVG anti-virus and
> firewall
> and also Spysweeper.
>
> How do I open it and attempt to read/understand what the cause of
> the
> crash was? Are there any debug tools I can download and use as a
> home
> user?
>
> Please advise. Thanks
> Tony V


 
Reply With Quote
 
=?Utf-8?B?VG9ueSBW?=
Guest
Posts: n/a
 
      1st Jan 2007
Gerry -- Thanks for your help. I'm posting the error info from Event Viewer
below:

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 12/30/2006
Time: 6:06:31 PM
User: N/A
Computer: GATEWAYPC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a
(0x909cb6f0, 0x00000002, 0x00000000, 0x8051a599). A dump was saved in:
C:\WINDOWS\Minidump\Mini123006-01.dmp.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


In addition, my log also shows the following later that same evening:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/30/2006
Time: 8:05:23 PM
User: N/A
Computer: GATEWAYPC
Description:
Error code 1000000a, parameter1 909cb6f0, parameter2 00000002, parameter3
00000000, parameter4 8051a599.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 30 1000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 39 30 eters 90
0030: 39 63 62 36 66 30 2c 20 9cb6f0,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 35 31 00, 8051
0050: 61 35 39 39 a599

Any help you can offer would be appreciated. We made no hardware or software
changes recently as far as I know--I have 3 teenagers but they're usually
pretty good about being careful with any installs or trouble shooting.

Thanks again, and Happy new Year from NYC.

Gerry Cornell" wrote:

> Tony
>
> They are very difficult to interpret.
>
> Can you provide a copy of the Stop Error Report?
>
> I suggest you Disable automatic restart on system failure. This
> should help by allowing time to write down the STOP code properly.
> Right click on the My Computer icon on the Desktop and select
> Properties, Advanced, StartUp and Recovery, System Failure and uncheck
> box before Automatically Restart.
>
> Do not re-enable automatic restart on system failure until you have
> resolved the problem. Check for variants of the Stop Error message.
>
> There will also be Error Reports in Event Viewer. Please post copies.
>
> You can access Event Viewer by selecting Start, Control Panel,
> Administrative Tools, and Event Viewer. When researching the meaning
> of the error, information regarding Event ID, Source and Description
> are important.
>
> HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
> http://support.microsoft.com/kb/308427/en-us
>
> Part of the Description of the error will include a link, which you
> should double click for further information. You can copy using copy
> and paste. Often the link will, however, say there is no further
> information.
> http://go.microsoft.com/fw.link/events.asp
> (Please note the hyperlink above is for illustration purposes only)
>
> A tip for posting copies of Error Reports! Run Event Viewer and double
> click on the error you want to copy. In the window, which appears is a
> button resembling two pages. Click the button and close Event Viewer.
> Now start your message (email) and do a paste into the body of the
> message. This will paste the info from the Event Viewer Error Report.
> Make sure this is the first paste after exiting from Event Viewer.
>
>
>
> --
>
> Hope this helps.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
>
>
>
> --
>
> Hope this helps.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
>
> Tony V wrote:
> > I have a Gateway DX300 that has MCE XP Home and I had a crash
> > yesterday that created a minidump file on my machine. I have SP2 and
> > the machine is patched and current. I run AVG anti-virus and
> > firewall
> > and also Spysweeper.
> >
> > How do I open it and attempt to read/understand what the cause of
> > the
> > crash was? Are there any debug tools I can download and use as a
> > home
> > user?
> >
> > Please advise. Thanks
> > Tony V

>
>

 
Reply With Quote
 
Rock
Guest
Posts: n/a
 
      1st Jan 2007
"Tony V" wrote

> Gerry -- Thanks for your help. I'm posting the error info from Event
> Viewer
> below:
>
> Event Type: Information
> Event Source: Save Dump
> Event Category: None
> Event ID: 1001
> Date: 12/30/2006
> Time: 6:06:31 PM
> User: N/A
> Computer: GATEWAYPC
> Description:
> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a
> (0x909cb6f0, 0x00000002, 0x00000000, 0x8051a599). A dump was saved in:
> C:\WINDOWS\Minidump\Mini123006-01.dmp.


<snip>

There are many possible causes for this error including faulty or
incompatible hardware, hardware drivers or software.
http://aumha.org/win5/kbestop.htm
0x0000000A: IRQL_NOT_LESS_OR_EQUAL


--
Rock [MVP - User/Shell]

 
Reply With Quote
 
Gerry Cornell
Guest
Posts: n/a
 
      1st Jan 2007

Tony

General troubleshooting advice:
http://aumha.org/win5/kbestop.htm

http://msdn.microsoft.com/library/de...933845.xml.asp
if link broken try
http://snipurl.com/l6o7

The problem seems to be memory related.

You need to remove the side panels on the box and check that the fans
are working. Look in the Manual for a diagram showing their location.
If not working the computer can overheat causing memory problems. Dust
can also be a problem. The best way to remove dust is to use an Air
Duster (Compressed Air in a can) available from large computer
stores). If these measures fail to identify or eliminate the problem
you should test the memory. See Test the RAM in the next link.
http://www.elephantboycomputers.com/...ardware_Tshoot

I have some more thoughts if the above do not resolve the problem.


--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Tony V wrote:
> Gerry -- Thanks for your help. I'm posting the error info from Event
> Viewer below:
>
> Event Type: Information
> Event Source: Save Dump
> Event Category: None
> Event ID: 1001
> Date: 12/30/2006
> Time: 6:06:31 PM
> User: N/A
> Computer: GATEWAYPC
> Description:
> The computer has rebooted from a bugcheck. The bugcheck was:
> 0x1000000a (0x909cb6f0, 0x00000002, 0x00000000, 0x8051a599). A dump
> was saved in: C:\WINDOWS\Minidump\Mini123006-01.dmp.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> In addition, my log also shows the following later that same
> evening:
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 12/30/2006
> Time: 8:05:23 PM
> User: N/A
> Computer: GATEWAYPC
> Description:
> Error code 1000000a, parameter1 909cb6f0, parameter2 00000002,
> parameter3 00000000, parameter4 8051a599.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 53 79 73 74 65 6d 20 45 System E
> 0008: 72 72 6f 72 20 20 45 72 rror Er
> 0010: 72 6f 72 20 63 6f 64 65 ror code
> 0018: 20 31 30 30 30 30 30 30 1000000
> 0020: 61 20 20 50 61 72 61 6d a Param
> 0028: 65 74 65 72 73 20 39 30 eters 90
> 0030: 39 63 62 36 66 30 2c 20 9cb6f0,
> 0038: 30 30 30 30 30 30 30 32 00000002
> 0040: 2c 20 30 30 30 30 30 30 , 000000
> 0048: 30 30 2c 20 38 30 35 31 00, 8051
> 0050: 61 35 39 39 a599
>
> Any help you can offer would be appreciated. We made no hardware or
> software changes recently as far as I know--I have 3 teenagers but
> they're usually pretty good about being careful with any installs or
> trouble shooting.
>
> Thanks again, and Happy new Year from NYC.
>
> Gerry Cornell" wrote:
>
>> Tony
>>
>> They are very difficult to interpret.
>>
>> Can you provide a copy of the Stop Error Report?
>>
>> I suggest you Disable automatic restart on system failure. This
>> should help by allowing time to write down the STOP code properly.
>> Right click on the My Computer icon on the Desktop and select
>> Properties, Advanced, StartUp and Recovery, System Failure and
>> uncheck box before Automatically Restart.
>>
>> Do not re-enable automatic restart on system failure until you have
>> resolved the problem. Check for variants of the Stop Error message.
>>
>> There will also be Error Reports in Event Viewer. Please post
>> copies.
>>
>> You can access Event Viewer by selecting Start, Control Panel,
>> Administrative Tools, and Event Viewer. When researching the
>> meaning
>> of the error, information regarding Event ID, Source and
>> Description
>> are important.
>>
>> HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
>> http://support.microsoft.com/kb/308427/en-us
>>
>> Part of the Description of the error will include a link, which you
>> should double click for further information. You can copy using
>> copy
>> and paste. Often the link will, however, say there is no further
>> information.
>> http://go.microsoft.com/fw.link/events.asp
>> (Please note the hyperlink above is for illustration purposes only)
>>
>> A tip for posting copies of Error Reports! Run Event Viewer and
>> double click on the error you want to copy. In the window, which
>> appears is a button resembling two pages. Click the button and
>> close
>> Event Viewer. Now start your message (email) and do a paste into
>> the
>> body of the message. This will paste the info from the Event Viewer
>> Error Report. Make sure this is the first paste after exiting from
>> Event Viewer.
>>
>>
>>
>> --
>>
>> Hope this helps.
>>
>> Gerry
>> ~~~~
>> FCA
>> Stourport, England
>> Enquire, plan and execute
>> ~~~~~~~~~~~~~~~~~~~
>>


 
Reply With Quote
 
Gerry Cornell
Guest
Posts: n/a
 
      1st Jan 2007
Rock

You misread the Stop Error message!

It was 0x1A: MEMORY_MANAGEMENT

Happy New Year. I forgot this earlier. Memory's not what it was
<sigh>.

--

Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Rock wrote:
> "Tony V" wrote
>
>> Gerry -- Thanks for your help. I'm posting the error info from
>> Event
>> Viewer
>> below:
>>
>> Event Type: Information
>> Event Source: Save Dump
>> Event Category: None
>> Event ID: 1001
>> Date: 12/30/2006
>> Time: 6:06:31 PM
>> User: N/A
>> Computer: GATEWAYPC
>> Description:
>> The computer has rebooted from a bugcheck. The bugcheck was:
>> 0x1000000a (0x909cb6f0, 0x00000002, 0x00000000, 0x8051a599). A dump
>> was saved in: C:\WINDOWS\Minidump\Mini123006-01.dmp.

>
> <snip>
>
> There are many possible causes for this error including faulty or
> incompatible hardware, hardware drivers or software.
> http://aumha.org/win5/kbestop.htm
> 0x0000000A: IRQL_NOT_LESS_OR_EQUAL


 
Reply With Quote
 
Rock
Guest
Posts: n/a
 
      1st Jan 2007
"Gerry Cornell" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Rock
>
> You misread the Stop Error message!
>
> It was 0x1A: MEMORY_MANAGEMENT
>
> Happy New Year. I forgot this earlier. Memory's not what it was <sigh>.
>
> --
>
> Regards.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
> Rock wrote:
>> "Tony V" wrote
>>
>>> Gerry -- Thanks for your help. I'm posting the error info from Event
>>> Viewer
>>> below:
>>>
>>> Event Type: Information
>>> Event Source: Save Dump
>>> Event Category: None
>>> Event ID: 1001
>>> Date: 12/30/2006
>>> Time: 6:06:31 PM
>>> User: N/A
>>> Computer: GATEWAYPC
>>> Description:
>>> The computer has rebooted from a bugcheck. The bugcheck was:
>>> 0x1000000a (0x909cb6f0, 0x00000002, 0x00000000, 0x8051a599). A dump
>>> was saved in: C:\WINDOWS\Minidump\Mini123006-01.dmp.

>>
>> <snip>
>>
>> There are many possible causes for this error including faulty or
>> incompatible hardware, hardware drivers or software.
>> http://aumha.org/win5/kbestop.htm
>> 0x0000000A: IRQL_NOT_LESS_OR_EQUAL



Oops, ok but I think the possible causes overlap.

--
Rock [MVP - User/Shell]

 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Blue screen - Can someone read a minidump *.dmp file? E Computer Hardware 27 18th Mar 2008 02:42 PM
Blue screen - Can someone read a minidump *.dmp file? E Windows XP Help 10 18th Mar 2008 09:58 AM
How do you open a minidump file Chelle Windows Vista Performance 4 9th Mar 2008 03:46 AM
Re: err 102 event 1003 and using pstat.exe to read minidump file Gerry Cornell Windows XP Performance 0 25th Jan 2007 10:06 PM
RE: err 102 event 1003 and using pstat.exe to read minidump file =?Utf-8?B?QWFyb24=?= Windows XP Performance 0 25th Jan 2007 08:23 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 06:04 PM.