BSOD on Windows 10 since 6.1.14, including 6.1.16

[jc3ferrari]

I'm getting a BSOD on Windows 10 Pro (all updates installed, except 20H2). This has occurred since 6.1.14, with prior versions working OK. VAs are Ubuntu 16.04 and Ubuntu 32-bit. As soon as I try to start the VA, BSOD occurs SYSTEM_SERVCIE_EXCEPTION, CProCtrl.4.0.0.17.sys. HyperV is OFF. Logs attached. Any help would be most appreciated. If any additional logs are needed, please let me know.

[Elwexo]

Hi, do you have a Vbox log file where you experience the BSOD? From the looks of the attached log (which is from August, and you're running 6.1.12) everything is ok, so there's nothing to diagnose

[jc3ferrari]

That is the most recent vbox.log on the entire system, which is why I posted it along with the other logs. I don't know the internals of VBox enough to know when logs are created during startup of a VA. Perhaps vbox.log gets created after the VM is created, but before the VA is started within it, meaning it is the VM creation that is failing? The most recent vbox.log is from 6.1.12, but the other two logs were created on 6.1.16. That must mean something of significance.

[fth0]

You have a Symantec software running that invades the VirtualBoxVM process memory, and the crash happens inside a CryptoPro software driver. For a test, uninstall both softwares and see if the problem persists.