I am developing a win2k driver for PCI based NIC.
The driver works fine with interrupts disabled…
but with intrs enabled, sometimes crashes when my device generates
interrupts.==> this is not a consistent behaviour…
The context parameter to my ISR is a pointer to DeviceExtension object
whis i suppose is locked in memory…
******Moreover the strange part is i am sure there’s nothing wrong in the
ISR or DPC since i’ve put an ASSERT(0) just at the beginning of ISR for me
to know for sure that ISR is called … & system (when int crashes)crashes
before comming to ASSERT macro… i.e. before entering the ISR.
=======>But the debugger shows IRQL 9 i.e. DIRQL of my device how’s
that???
hence,I just wanted to know if there something more to interrupt
handling… like locking entire driver code etc??? however default
behaviour is to lock the entire code… is it???
anyways… this is the dump on my debugger… please can anyone trace the
problem…???
MM:***PAGE FAULT AT IRQL > 1 Va ED064726, IRQL 9
*** Fatal System Error: 0x000000d1
(0xED064726,0x00000009,0x00000000,0xED064726)
Hard coded breakpoint hit
kv
ffffffffba5602f4 ffffffff80438bab NT!RtlpBreakWithStatusInstruction
(FPO: [1,0,0])
ffffffffba560324 ffffffff8043919e NT!KiBugCheckDebugBreak+0x31 (EBP)
ffffffffba5606b0 ffffffff804c2160 NT!KeBugCheckEx+0x390 (EBP)
ffffffffba5606b0 ffffffffed064726 NT!KiTrap0E+0x2a4 (FPO: [0,0]
TrapFrame @ ba5606cc)
ffffffffba5602f4 ffffffff80438bab 0xFFFFFFFFED064726 (No FPO)
0000000000000246 0000000000000000 NT!KiBugCheckDebugBreak+0x31 (EBP)
Thanx,
SP.