Driver developers use the checked build of Microsoft Windows to identify and diagnose operating-system-level problems. In the checked build: | • | Many compiler optimizations are disabled to make it easier to understand disassembled machine instructions and trace problems. | | • | Many debugging checks are enabled to help identify internal inconsistencies and problems, including: | • | Parameter validation checks | | • | Internal checks for operating system correctness and consistency | | • | Informational checks and tracing output, often documented in Microsoft Knowledge Base articles |
|
Most checks in the checked build determine whether values in parameters or data structures are within anticipated typical ranges. Successfully debugging drivers with the checked build requires the developer to understand the reason for each failure that the checked build finds. Checked builds are provided on MSDN Subscriber CDs or from the Subscription area on MSDN. How to Use Checked Builds How to Obtain Checked Builds Online  | Subscriber Downloads on MSDN
For example, in the Download Directory in the left pane on MSDN Subscriptions, select Platforms > Windows Server 2003 > English > Windows Server 2003 Enterprise Edition - Checked/Debug (English). Install just the Checked Operating System and HAL. |
| 