Finding Cause of WinXP Stop Message

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

Guest

Receiving regular 0x0000000a stop messages the 4th parameter is always the same, 0x80512c9d. Only happens when Palm software is running but need it to run so want to see if can do a workaround. Q130802 says 4th stop message parameter is the "address of instruction which attempted to reference the memory at" the address shown in 1st parameter. The stop message doesn't give the name of the driver. Is there any way I can find out the cause of this crash i.e what piece of software? As the 4th parameter is always the same how can this be used to find the culprit? If driver isn't named in crash does this mean it isn't caused by a driver

BTW I have only created minidumps and have used the tool to look into this but it didn't give any extra clue to the cause.
 
-----Original Message-----
Receiving regular 0x0000000a stop messages the 4th
parameter is always the same, 0x80512c9d. Only happens
when Palm software is running but need it to run so want
to see if can do a workaround. Q130802 says 4th stop
message parameter is the "address of instruction which
attempted to reference the memory at" the address shown in
1st parameter. The stop message doesn't give the name of
the driver. Is there any way I can find out the cause of
this crash i.e what piece of software? As the 4th
parameter is always the same how can this be used to find
the culprit? If driver isn't named in crash does this
mean it isn't caused by a driver?


Try
http://www.aumha.org/win5/kbestop.htm
Bill
BTW I have only created minidumps and have used the tool
to look into this but it didn't give any extra clue to the
cause.
 
Back
Top