Incorrect driver is selected for debugging

NTDEV
1

I have two kernel mode drivers running on destination computer: PrcbKmdf.sys and DeebKmdf.sys. Starting remode debugging with WinDbg, I ask to break when PrcbKmdf loads. Actually, I see that another driver breaks:

Kernel Debugger connection established
…
8052b600 cc int 3
kd> sxe ld:prcbkmdf
kd> g
…
Breakpoint 0 hit
DeebKmdf!DriverEntry+0x48:
b8175d58 68201217b8 push offset DeebKmdf!WPP_MAIN_CB (b8171220)

As result of this, I cannot debug the driver: WinDbg tries to debug PrcbKmdf, while DeebKmdf is actually debugged. What can be a reason of this?

2

> As result of this, I cannot debug the driver: WinDbg tries to debug PrcbKmdf, while DeebKmdf is actually

debugged

Both are actually debugged, and the DriverEntry event will fire for both drivers.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

3

Thanks, it really breaks later when PrcbKmdf starts.

4

How do you set the breakpoint?