Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results


More Info on Driver Writing and Debugging

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:

Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

Static Driver Verifier Ignoring Set Timeout Value

Alex_MAlex_M Member Posts: 1
edited June 1 in NTDEV

Hello, I am attempting to perform static analysis on an NDIS driver but a few of the rulesets timeout. Microsoft's guidance in this situation is to increase the timeout value. I have increased this time, but it did not resolve the issue for every check. Specifically, nullcheck continues to timeout after 50 minutes regardless of the set timeout value. When I run SDV using only the nullcheck rule the status never changes from "linking". Would anyone have an idea of how to resolve this timeout?

Thanks! :smile:


  • Wilhelm_NökerWilhelm_Nöker Member Posts: 44

    A while ago, I had a similiar problem, but found no real solution. However, I can offer some observations:

    • I suspect that the configurable timeout is only checked between rulesets. Whether or not an individual ruleset stops prematurely is determined only by some of its own internal parameters.
    • Running the tests on a different (i.e. slower or faster) hardware can make a difference, but in a slightly random way. What I mean is: If you offer more computing power (more processor cores in particular), PerfMon et. al. will show you that it gets utilized. But a single ruleset that runs successfully will show only minor differences in the time it takes to complete (20 % or so). It looks as though SDV observes the available computing power first and then adjusts the thoroughness of the test schedule within each ruleset accordingly.
    • Enterprise WDK can be helpful if you decide to run your tests on many different computers (because it can be run without installation). Note however that EWDK needs the redistributables for VC 2013 and VC 2015 and fails with an unspecific message ("Unrecoverable error in InterceptedBuild stage") if they are not installed.
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

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