Which driver is causing the STOP error?

[Paul Ferguson]

I am running XP Pro on a P4 and ASUS P4P800 Deluxe motherboard.

I have been having intermittent Stop 0xA blue screens. I might run the
whole day with none, but I might get several in a day.

I am attempting to find the cause of the error. I have read many of
the recommendations. I did get new drivers and firmware that I could
find. I also pulled out all expansion cards except the MSI GeForce FX
5600 video card and still had the problem. I know the error could be
caused by bad hardware such as memory or motherboard, but I want to
purse the bad driver area first.

Most of the errors are exactly the same:

Stop 0x0000000A

Parm 1= 0X680C7727 (the address referenced improperly)
Parm 2 = 0x00000FF (the IRQL)
Parm 3 = 0X00000000 (read)
Parm 4 = 0X80534A84 (address of instruction that made the improper
reference)


Microsoft says this is often caused by a bad driver . Parameter 4
gives the address of the instruction resulting in the error. I would
think that if I knew what driver issued the improper reference, I
would have a better idea of the cause.

Is there a way to find out which driver is issuing this reference?
Maybe there is a program that would map what driver is loaded where?
More specifically -- I want to know the program name with the
instruction at the address given in Parameter 4.

PaulF

 

[The Unknown P]

Sure there is. It's called the event viewer and is part of
your administrative tools in the control panel. Once there
you will see three logs. Open each one and when you do you
will see the log in the right screen. Now all you have to
do is look for the red Xs and double click on them to open
the screen that gives you the details. This will often
tell you the program as well as the exact module that
caused your problem. You should look for any red Xs that
correspond to the time of your problem. Have fun.

 

[Paul Ferguson]

Sure there is. It's called the event viewer and is part of
your administrative tools in the control panel. Once there
you will see three logs. Open each one and when you do you
will see the log in the right screen. Now all you have to
do is look for the red Xs and double click on them to open
the screen that gives you the details. This will often
tell you the program as well as the exact module that
caused your problem. You should look for any red Xs that
correspond to the time of your problem. Have fun.

I have been there but it is of little help - I see a System error
Catagory (102) Event 1003.
The description is:
Error code 0000000a, parameter1 680c7727, parameter2 000000ff,
parameter3 00000000, parameter4 80534a84.

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

Going to the above link says there is no addirional info known.

This is why I am looking for a clue as to which program module or
driver is loaded at the parameter4 address.

PaulF