P
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.
In the past few days I have had 1 or 2 Stop errors on boot up. In
looking at the 4 parameters that go with the Stop 0xA error, they seem
to be the same:
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)
I would think that if I knew what driver issued the improper reference
(Parrm 4) I would have a better clue.
Is there a way to find out what driver is issuing this reference?
Maybe there is a program that would map what driver is loaded where?
PaulF
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.
In the past few days I have had 1 or 2 Stop errors on boot up. In
looking at the 4 parameters that go with the Stop 0xA error, they seem
to be the same:
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)
I would think that if I knew what driver issued the improper reference
(Parrm 4) I would have a better clue.
Is there a way to find out what driver is issuing this reference?
Maybe there is a program that would map what driver is loaded where?
PaulF