"You don't seen to have liked my original response, but I will make it again. Driver verifier has never worked with Sandboxie. You can search this forum and see the posts that go back over 10 years.
search.php?keywords=driver+verifier
For example, the text of the error in the DMP posted in your other thread is "
Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)"
The use of NX memory requirement was added in Win 8 (Sandboxie still supports Win 7). The additional error text "
A device driver attempting to corrupt the system has been caught." is a gross exaggeration by Microsoft. The driver verifier is actually reporting that SbieDrv.sys has allocated R/W memory which has does not meet this new NX memory safety requirement. No system "corruption" has occurred.
SbieDrv.sys is a driver that has close interaction with the OS. To make SbieDrv.sys fully compliant with Win 7 - Win 10 driver verifiers will require a lot of changes that will show no benefit to the user -- if it is even possible. As I said before, SbieDrv.sys is not a normal, self-contained driver. It intercepts a lot of Windows system calls and interacts tightly with Windows. Driver verifier does not like these types of interactions. This has never been a major problem for anyone in the past.
We have not had a genuine BSOD reported for Sandboxie in a long time. When they are reported, they are immediately fixed. Since no one else is reporting any problems, and none have shown up in testing, the problem on your machine most likely lies elsewhere."