find address of loaded drivers

  • Thread starter Thread starter Rob Alexander
  • Start date Start date
R

Rob Alexander

Hi all,

I'm getting a lot blue screens with errors of the form:

IRQL_NOT_LESS_OR_EQUAL
STOP 0x0000000A (0x00000004, 0x00000002, 0x00000001, 0x804FA2E1)

The last parameter (address of the instruction that caused the error)
seems fairly consistent, so I suspect that it might provide a clue as
to what process or driver is causing the error. So, is there any way
that I can get a list of the base addresses for loaded drivers and
processes?

It seems like earlier versions of Windows provided this information on
the blue screen, but XP doesn't?


yours,
rob
 
Hi all,

I'm getting a lot blue screens with errors of the form:

IRQL_NOT_LESS_OR_EQUAL
STOP 0x0000000A (0x00000004, 0x00000002, 0x00000001, 0x804FA2E1)

The last parameter (address of the instruction that caused the error)
seems fairly consistent, so I suspect that it might provide a clue as
to what process or driver is causing the error. So, is there any way
that I can get a list of the base addresses for loaded drivers and
processes?

Solved my own problem - the tool needed is PSTAT, which is installed
as part of the Windows XP support tools. They're on the Windows XP cd.

Doesn't help much in my case - the address I get in the error is right
in the middle of ntoskrnl.exe, so doesn't implicate any particular
driver or process.


rob
 
Back
Top