// The bugcheck code does make it easy - 1st param is 0, so the second and third should be
// <some number greater than 282> and 282 - in this case, the second param is indeed a
// number greater than 282:
0: kd> .bugcheck
Bugcheck code 00000133
Arguments 00000000`00000000 00000000`00000283 00000000`00000282 00000000`00000000
// While this is a minidump, we can see from the thread stack (read bottom up) that
// jraid.sys is calling KeStallExecutionProcessor, and the DPC that is being caused here
// is being caused by the driver on the stack - again, jraid.sys:
0: kd> kn
# Child-SP RetAddr Call Site
00 fffff800`0ad7ed88 fffff800`0afeb143 nt!KeBugCheckEx
01 fffff800`0ad7ed90 fffff800`0aebd011 nt! ?? ::FNODOBFM::`string'+0x13c4c
02 fffff800`0ad7ee10 fffff800`0aebde97 nt!KeUpdateRunTime+0x51
03 fffff800`0ad7ee40 fffff800`0b582eca nt!KeUpdateTime+0x3f9
04 fffff800`0ad7f030 fffff800`0ae8b7ee hal!HalpTimerClockInterrupt+0x86
05 fffff800`0ad7f060 fffff800`0b58bbe0 nt!KiInterruptDispatchLBControl+0x1ce
06 fffff800`0ad7f1f8 fffff800`0b57e0e0 hal!HalpTscQueryCounter
07 fffff800`0ad7f200 fffff880`012036d1 hal!HalpTimerStallExecutionProcessor+0x131
08 fffff800`0ad7f290 00000000`00000000 jraid+0x36d1
0: kd> lmvm jraid
start end module name
fffff880`01200000 fffff880`0121e000 jraid T (no symbols)
Loaded symbol image file: jraid.sys
Image path: \SystemRoot\System32\drivers\jraid.sys
Image name: jraid.sys
Timestamp: Thu Aug 13 04:10:27 2009 (4A83CA73)
CheckSum: 00026B2F
ImageSize: 0001E000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4