You might guess that my driver is vjoy, but there is no such function as FxStubDriverUnload in my code. Is it a callback? How do I locate the error in my code?
I get a bugcheck when uninstalling the driver. This is a statistical phenomenon that happens once in several hundreds un-installs.
…
8a01fa1c 82ac1e25 84104308 6083d392 96dd6bb8 vjoy!FxStubDriverUnload+0x1a [d:\vistartm\drivers\wdf\kmdf\src\dynamic\stub\stub.cpp @ 153]
8a01fb74 829cce30 00000001 84234b98 9223f1c8 nt!IopUnloadDriver+0x338
8a01fb98 828e0a27 94dacc18 84234b98 00000001 nt!PnpUnloadAttachedDriver+0x73
…
You might guess that my driver is vjoy, but there is no such function as FxStubDriverUnload in my code. Is it a callback? How do I locate the error in my code?
It’s part of WDF. The “Fx” stands for “framework”. The implication
here is that the framework was trying to close a registry key, but the
key handle was not valid. Do you use registry keys in your driver?
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Looks like someone closed a handle behind kmdf’s back. I would look at your code to see where you close handles and perhaps close an already closed (and thus now invalid ) handle.
d
dent from a phine with no keynoard
-----Original Message-----
From: xxxxx@gmail.com
Sent: Monday, February 14, 2011 11:31 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Bugcheck when uninstalling
You might guess that my driver is vjoy, but there is no such function as FxStubDriverUnload in my code. Is it a callback? How do I locate the error in my code?
Thank you Tim & Doron.
It seems to me now that I made errors in deleting a control device but I’ll have to look into it. What I did was to put many calls to DbgPrint() and see what were the last ones when the machine crashes. The problem with this method as I used it is the the messages are displayed on traceview on the test machine. Not very wise of me. Is there a way to run testview on a remote machine? I could not find how.