I am somewhat at a loss as to how to debug a D1 bugcheck that I get when debugging my driver… The information presented is quite meaningless, and I am clueless as to how to proceed. Might be that the stack itself is getting corrupted by the time I get to have a look at it…
I get a trap frame, but .trap gave me the following:
0006fef8 01003fae 000001f4 00814d5c 00000005 0x77e8affe
0006ff38 010046c8 77fb9045 77f83e80 7ffdf000 0x1003fae
0006ff70 0100b55f 00000001 00813648 00812928 0x10046c8
0006ffc0 77e992a6 77fb9045 77f83e80 7ffdf000 0x100b55f
0006fff0 00000000 0100b460 00000000 000000c8 0x77e992a6
PARAM 4 - supposedly the address causing the problem is pointing to non-code area of memory
None of these addresses are pointing to any code. How can I proceed to debug my driver ??
Thanks
-Johnny
====
BugCheck D1, {77e8b000, 2, 0, 77e8affe}
Probably caused by : ntkrnlmp
Followup: MachineOwner
nt!RtlpBreakWithStatusInstruction:
80453e90 cc int 3
1: kd> kb
ChildEBP RetAddr Args to Child
f7bc598c 8042a357 00000003 f7bc59d4 77e8b000
nt!RtlpBreakWithStatusInstruction
f7bc59bc 8042a94a 00000003 77e8b000 77e8affe nt!KiBugCheckDebugBreak+0x31
f7bc5d48 80466f7c 00000000 77e8b000 00000002 nt!KeBugCheckEx+0x390
f7bc5d48 77e8affe 00000000 77e8b000 00000002 nt!KiTrap0E+0x284
0006fef8 01003fae 000001f4 00814d5c 00000005 0x77e8affe
0006ff38 010046c8 77fb9045 77f83e80 7ffdf000 0x1003fae
0006ff70 0100b55f 00000001 00813648 00812928 0x10046c8
0006ffc0 77e992a6 77fb9045 77f83e80 7ffdf000 0x100b55f
0006fff0 00000000 0100b460 00000000 000000c8 0x77e992a6
Get your FREE download of MSN Explorer at http://explorer.msn.com.