Zoom Icon

Device Driver Development For Beginners

From UIC Archive

Device Driver Development for Beginners - Reloaded


Device Driver Development For Beginners
Author: Evilcry
Email: [email protected]
Website: gopher://evilcry.xyz
Date: 08/03/2011 (dd/mm/yyyy)
Level: Working brain required
Language: English Flag English.gif


Just a little starter for people interested in starting Kernel-Mode Development. This tutorial is a flexible one, time by time I'll Reload and Expand it.

By following a good thread on UIC forum, opened by a beginner that wanted to know how to start with Device Driver Development, I remembered that long time ago published a similar blog post on that subject.

Development Tools

  1. WDK/DDK - this is the proper Driver Development SDK given by Microsoft, latest edition can be dowloaded http://www.microsoft.com/whdc/DevTools/WDK/WDKpkg.mspx
  2. Visual Studio 2008/2010 - you can also develop without VS, but I always prefer all the Comforts given by a such advanced IDE, especially in presence of complex device drivers.
  3. DDKWizard - DDKWizard is a so-called project creation wizard (for VisualStudio) that allows you to create projects that use the DDKBUILD scripts from OSR (also available in the download section from this site). The wizard will give you several options to configure your project prior to the creation. You can download it http://ddkwizard.assarbad.net/
  4. VisualAssist - (Optional Tool) Visual Assist X provides productivity enhancements that help you read, write, navigate and refactor code with blazing speed in all Microsoft IDEs. You can Try/Buy it http://wholetomato.com/
  5. VisualDDK - Develop and Debug drivers directly from VS, enjoy debugging your driver directly from Visual Studio, speeding up debugging ~18x for VMWare and ~48x for VirtualBox. Download and Step by Step Quick Start Guide http://visualddk.sysprogs.org/quickstart/
  6. Virtual Machine - You need a Virtual Machine to perform efficient Driver Debugging, best options are VMWare or VirtualBox.

Building a Driver Development Environment

As you can see, a good comfortable Driver Development station is composed by a good amount of components, so we need an installation order.

  • Install your IDE - VisualStudio2008 or VisualStudio2010
  • Install WDK package
  • Install DDKWizard
  • Download and place ( usually into C:\WinDDK ) ddkbuild.cmd
  • By following DDKWizard pdf you will be driven to add an new Envirnment Variable directly releated to the OS version in which you are developing and successively add a reference of ddkbuild.cmd into VS IDE. DDWizard Manual is very well written.
  • After finishing DDKWizard integration you can test if your environment is correctly installed, by compilig your first driver. Steps are easy open VS and select DDKWizard templare (not EmptyDriver), you will see the skeleton of a Driver, all what you have to do is to Build Solution and Verify if No Compiling Errors occur, your station is correctly installed.
  • Install VirtualMachine
  • Integrate Debugging help of VisualDDK by following step by step quick start guide
  • Install Visual Assist (this can be done in every moment after VS Installation)

Additional Tools

  • DeviceTree - This utility has two views: (a) one view that will show you the entire PnP enumeration tree of device objects, including relationships among objects and all the device's reported PnP characteristics, and (b) a second view that shows you the device objects created, sorted by driver name. There is nothing like this utility available anywhere else. http://www.osronline.com/article.cfm?article=97
  • IrpTracker - IrpTracker allows you to monitor all I/O request packets (IRPs) on a system without the use of any filter drivers and with no references to any device objects, leaving the PnP system entirely undisturbed. In addition to being able to see the path the IRP takes down the driver stack and its ultimate completion status, a detailed view is available that allows you to see the entire contents of static portion of the IRP and an interpreted view of the current and previous stack locations.


  • DebugMon - Displays DbgPrint messages generated by any driver in the system (or the OS itself) in the application window. Can be used either in local mode or can send the DbgPrint messages to another system via TCP/IP. http://www.osronline.com/article.cfm?article=99
  • DriverLoader - This GUI-based tool will make all the appropriate registry entries for your driver, and even allow you to start your driver without rebooting. It's even got a help file, for goodness sakes! If you write drivers, this is another one of those utilities that's a must have for your tool chest. http://www.osronline.com/article.cfm?article=157

Now you have a full working Develop and Debug Station.

As you should imagine, dealing with driver development implies working with at Kernel Mode, a task pretty challenging, delicate and complex. A badly written driver lead to OS Crash and/or dangerous bugs, just think about a driver used in mission-critical applications like Surgery, a bug or a crash could lead to extremely big dangers. The driver need to be:

  • Bug Free
  • Fault Tolerant
  • Ready to Endure all Stress Situations

This could be done, only by the driver coder, with a large knowledge of following fields:

  • Hardware Architecture
  • Operating System Architecture
  • Kernel and User Mode Architecture
  • Rock Solid C language Knowledge
  • Debugging Ability

Here i'm going to enumerate necessary Documentation/Book/Etc. necessary to acheive a good and solid background and advanced knowledge about driver coding.

Microsoft WDK Page: http://www.microsoft.com/whdc/devtools/WDK/default.mspx

Will give you informations about:

  1. WDM ( Windows Driver Model)
  2. WDF (Windows Driver Foundation)
  3. IFS Kit (Installable FileSystem Kit)
  4. Driver Debugging
  5. Driver Stress Testing ( DriverVerifier tool )

PC Fundamentals: http://www.microsoft.com/whdc/system/default.mspx

Device Fundamentals: http://www.microsoft.com/whdc/device/default.mspx

This will give you an large view of 'what mean developing a driver' which components are touched and which aspects you need to know.

It's also obviously necessary to have a Reference about kernel mode involved Functions and Mechanisms, the first best resource is always MSDN, here the starter link to follow MSDN->DDK


How to start Learning

  • Driver Development Part 1: Introduction to Drivers


  • Driver Development Part 2: Introduction to Implementing IOCTLs


  • Driver Development Part 3: Introduction to driver contexts


  • Driver Development Part 4: Introduction to device stacks


  • Driver Development Part 5: Introduction to the Transport Device Interface


  • Driver Development Part 6: Introduction to Display Drivers


It's really important to put in evicence MemoryManagement at KernelMode, the best starting point for these aspects are tutorials written by four-f;


Handling IRPs: What Every Driver Writer Needs to Know http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/IRPs.doc

Book Resources

Tutorial are a great starting point, but a solid understanding is given by a set of 'abstracts', emerges the necessity of a good Book Collection:

  • Windows NT Device Driver Development (OSR Classic Reprints)


  • Windows®-Internals-Including-Windows-PRO-Developer


  • The Windows 2000 device driver book: a guide for programmers


  • Undocumented Windows 2000 Secrets


  • Developing Drivers with WDF


  • Windows NT File System Internals, A Developer's Guide


Web Resources

The first and most important resource about Windows Driver Development is OSROnline:


I strongly suggest you to subscribe:

  1. The NT Insider
  2. NTDEV MailingList
  • NDIS Developer's Reference


  • Information, Articles, and Free Downloads


  • The Undocumented Functions


  • Blog MSDN


  • Windows Vista Kernel Structures


  • Peter Wieland's thoughts on Windows driver development


  • USB Driver Development


  • Hardware and Driver Developer Blogs


Developer Newsgroups

  • microsoft.public.development.device.drivers
  • microsoft.public.win32.programmer.kernel
  • microsoft.public.windbg


  • j00ru//vx tech blog Coding, reverse engineering, OS internals Blog


  • Nynaeve


  • DumpAnalysis Blog


  • Analyze -v Blog


  • Instant Online Crash Dump Analysis


  • Winsock Kernel (WSK)


  • Transport Driver Interface (TDI)


  • Network Driver Interface Specification (NDIS)


  • System Internals


Driver development needs too many time patience and experience to be fully understood, in my opinion the best approach remains LbD ( Learning by Doing ) so, read, study and develop as many experience you build less BSODs and "strange behavior" you will obtain :)




I documenti qui pubblicati sono da considerarsi pubblici e liberamente distribuibili, a patto che se ne citi la fonte di provenienza. Tutti i documenti presenti su queste pagine sono stati scritti esclusivamente a scopo di ricerca, nessuna di queste analisi è stata fatta per fini commerciali, o dietro alcun tipo di compenso. I documenti pubblicati presentano delle analisi puramente teoriche della struttura di un programma, in nessun caso il software è stato realmente disassemblato o modificato; ogni corrispondenza presente tra i documenti pubblicati e le istruzioni del software oggetto dell'analisi, è da ritenersi puramente casuale. Tutti i documenti vengono inviati in forma anonima ed automaticamente pubblicati, i diritti di tali opere appartengono esclusivamente al firmatario del documento (se presente), in nessun caso il gestore di questo sito, o del server su cui risiede, può essere ritenuto responsabile dei contenuti qui presenti, oltretutto il gestore del sito non è in grado di risalire all'identità del mittente dei documenti. Tutti i documenti ed i file di questo sito non presentano alcun tipo di garanzia, pertanto ne è sconsigliata a tutti la lettura o l'esecuzione, lo staff non si assume alcuna responsabilità per quanto riguarda l'uso improprio di tali documenti e/o file, è doveroso aggiungere che ogni riferimento a fatti cose o persone è da considerarsi PURAMENTE casuale. Tutti coloro che potrebbero ritenersi moralmente offesi dai contenuti di queste pagine, sono tenuti ad uscire immediatamente da questo sito.

Vogliamo inoltre ricordare che il Reverse Engineering è uno strumento tecnologico di grande potenza ed importanza, senza di esso non sarebbe possibile creare antivirus, scoprire funzioni malevole e non dichiarate all'interno di un programma di pubblico utilizzo. Non sarebbe possibile scoprire, in assenza di un sistema sicuro per il controllo dell'integrità, se il "tal" programma è realmente quello che l'utente ha scelto di installare ed eseguire, né sarebbe possibile continuare lo sviluppo di quei programmi (o l'utilizzo di quelle periferiche) ritenuti obsoleti e non più supportati dalle fonti ufficiali.