cwindowsdebuggingkernelwdm

Debugging a driver with WinDbg - How set a breakpoint at DriverEntry?

I have a driver which is, for some unknown reasons causing a bugcheck 0x0000003b.

So I decided to set up a Hyper-V VM and use kernel debugging to see what exactly is going on. I already enable testing signing with bcdedit, and checked that the driver is indeed loaded and running with sc query. The problem is that I want WinDbg to step in ONLY when the offending driver is being called and not when the windows debugee is booting, how can I do that? How do I instruct windbg to pause at the DriverEntry function of my driver?

Solution

  • You can add a breakpoint at DriverEntry using command 'bm DriverName!DriverEntry'.