When you learn about WdfSend, you typically learn that there are three different ways that you can send a Request to an I/O Target.  It makes a nice story to describe these three options as equally viable for a driver writer.  Unfortunately, in the majority of cases the only practical option is to send a Request asynchronously and specify a Completion Routine Event Processing Callback.  This quick article describes why this is the case.

Breakpoints are great, but at some point you have to resume from them. What if you want to freeze a thread in place while allowing other threads to continue executing?

A former student provided a crash dump for some analysis, here's what I found...

Confused about WDFMEMORY Objects?  Wonder why they exist at all?  Here, we try to help.

Ever wanted to search a live system or crash dump for strings? In this post we'll show you how!

The Debugger Markup Language makes navigating the command window a breeze. Did you know that you can add links to the debugging output not only from your debugger extensions but also from your drivers? In this Developer Blog entry we'll show you how...

The Win8 WDK makes test signing easy.  No, really.  It does.  Read and see...

Sometimes it's necessary as a developer to break the rules.  Even good developers do it.  Sometimes, to do something cool, you just have to do it.  But where do you draw the line?  Let's explore that question a bit.

SDV has a new rule and there's bugcheck 9F to deal with.  It's about time we thought more about EvtIoStop