I have a problematic driver. No updates are available.
If the driver crushes, the application that uses it will crush too.
NET STOP driver
and
SC STOP driver
say that the driver cannot be controlled at it's current state.
End Process and End Process Tree from task manager cannot kill the process,
no error is reported.
#taskkill -f -im process.exe
SUCCESS: The process "process.exe" with PID 3216 has been terminated.
But the process is still running - it is locked, waiting for the crushed
driver to return some information, but the driver is halted.
If I restart (disable and re-enable) the driver from the Device Manager, the
application will close and everything works again. But the Device Manager
won't let me disable the driver, without restart.
1. Can I kill the driver (force it to close)? I'll take responsibility for
the results.
2. I don't think that this is a normal behavior. Any code that stops
responding should be killed and memory freed. May be a fix is required for
Windows?
3. The driver is from Microsoft.
4. The driver only crushes when I use a specific program (it's from
Microsoft too).
5. All this applies to both Windows 2003 Server and Windows XP with all
updates installed.
Thank You for any support!
George Valkov
|
Similar Threads
