Every physical device object (PDO) must have a name . Furthermore, if you read the entire MSDN page, you see that any device attached to the PDO must not have a name. Why does such a rule exist? To answer this question, let's explore what happens if more...

For those of you who are trying to find the WDK download link on WHDC, it is not longer there. It has moved to the Microsoft Connect site. Peter Wieland previously described how to get the WDK Beta 2 ISO from this site and nearly the same instructions...

Michael Howard has a great posting on improvements made in the compiler with respect to the /GS flag (stack checking using a "canary" on function exit). Before these changes, #pragmas to explicitly turn the functionality on or off, the compiler itself...

This problem falls into the category being hidden by a macro that does not indicate in its name what it touches. If you call IoMarkIrpPending on an IRP that you allocated in your driver, chances are that you are corrupting memory. First, let's look at...

It sounds obvious, but sometimes it needs to be stated. For instance, let's say that you are allocating your own IRP, your context contains I/O related data (like a URB ) and you encounter the issue where the DeviceObject passed to your I/O completion...