How to catch faulty driver in the stack

I am not able to catch the faulty driver on crash dump analysis. Following is the output of crash dump analysis.If someone could help me on this it would be great help. How does one get NT-type BSOD(where the complete stack is dumped on screen, and 2K only gives me the bugcode)



An attempt was made to access a pagable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.


Arg1: 00000000, memory referenced

Arg2: 00000002, IRQL

Arg3: 00000000, value 0 = read operation, 1 = write operation

Arg4: 8041736c, address which referenced memory


Read address 00000000, Unknown

Current IRQL 2

Faulting IP 8041736c ( ntoskrnl!ExpCheckForResource+38 )

TrapFrame ee04ba24

eax=804733b0 ebx=000004d0 ecx=f78d4000 edx=00000000 esi=00000000 edi=f78d3b30

eip=8041736c esp=ee04ba98 ebp=ee04baa4 iopl=0 nv up ei pl nz na pe cy

vip=0 vif=0

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010203

ErrCode = 00000000

8041736c 8b36 mov esi,[esi]

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)