-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SbieDrv.sys causes BSOD when Driver Verifier is launched #57
Comments
hmm... i have tested that and the crash seams to originate in GetThreadTokenOwnerPid, |
This happened for me as well, back when I was using sophos's version... they did not bother having the the driver approved by microsoft... I asked them about this personally and the developer told me personally they had no plans on doing this because it would negate the functionality of the driver... that it modifies certain functionality in windows that would never be approved, or some such thing. That was in the old forums. If i can find a link to those forums I can dig it all up. |
Here is some of the info I dug up, some of my post from sysnative "I was told by sandboxie developers that "driver verifier does not work with sandboxie"... so if you can determine which dump was related to the sandboxie driver, and let me know what the results were, aka memory corruption and the like, that would be appreciated." |
Read "Due to the nature of Sandboxie, MS Driver Verifier will not work with SbieDrv.sys." He goes into extensive detail why, as I grilled him on it quite heavily, you can find the rest if you dig around |
Various Driver Verifier issues will be fixed in the next build, including the BSOD on boot. Seriously why Invincia never fixed them it wasn't so hard... |
😁 |
Steps to reproduce:
The text was updated successfully, but these errors were encountered: