The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
Our IddCx-based display adapter driver installs and works fine for most users (we target Windows 10 exclusively). Once or twice per week, however, a user requests support, and I eventually find in Device Manager that their device instance (a virtual display adapter with no hardware backing) is displaying the yellow caution icon. Checking the device's status, I see
Unfortunately, I've never been able to reproduce this situation in a local test environment, so I'm left to guessing as to what the cause might be...
Of the PnpPowerCallbacks, I only created D0Entry and D0Exit handlers. The thinking was that I didn't need to handle any more than the minimum power callbacks, since ours is a software device.
When I started seeing reports of this error, I thought perhaps these specific users had laptops configured with non-default power plan settings. "Perhaps Windows 10 expects that a driver explicitly confirm its capability to enter some low-power mode, and because mine is missing some behavior, Windows refuses to start it?"
Unfortunately, I've tried reproducing this locally on a laptop by setting various power management plan settings, but everything works fine.
Can anyone help shed light on this?
Windows Developer since 1989
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!|
|Developing Minifilters||24 May 2021||Live, Online|
|Writing WDF Drivers||14 June 2021||Live, Online|
|Internals & Software Drivers||27 September 2021||Live, Online|
|Kernel Debugging||15 November 2021||Live, Online|