Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a driver that for one reason or an other it hanged for more than 1 second and crashed my app.

What possible causes do you know that can make a driver hang for more than one second inside an OS? Think here of special conditions, automatic updates, antivirus, etc.

My OS is Windows 2000.

share|improve this question
How do you know it's a driver that's hanging? – John Gardeniers Nov 12 '09 at 11:35

Almost anything, it could even be the driver itself. Drivers are basically an low level application for communicating with something, they can have bugs, exploits and issues themselves just like any program. I often find a lot of OS level issues stem from a bad driver. There is one driver for HP management we have to downgrade to an older version because the one that came with the equipment causes a ton of errors and eventually triggers a random reboot.

share|improve this answer
Can it be that it's not the driver, but the OS who does something else and does not assigns enough priority to it? – cmserv Nov 12 '09 at 14:59
I call a function from its API which returns a timeout error, signaling that it spends a lot of time extra on something which I can't actually inspect due to its closed source character. – cmserv Nov 12 '09 at 15:05
Did you inspect the documentation on why it returned the timeout? Given its actually telling you it would seem likely the driver was waiting on something else to occur. – Shial Nov 14 '09 at 19:15

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.