I wonder if anyone had any insight as to why my Windows 7 install blue screens whenever I start VirtualBox VMs while HyperSLI is enabled. I know that HyperSLI is the issue, because if I restart the computer and disable it, or remember to disable it beforehand, the computer doesn't blue screen. This started happening as recently as VirtualBox 4.1.8. Prior to that version, I would get thrown an error saying that a certain BIOS parameter (AMD-V or VT-x) is not enabled. Before 4.1.8, the virtual machine would run just fine and I couldn't seem to notice any issues at all. What did VirtualBox change? The error code was much friendlier than the blue screen halting all of my work.
Well, something is quite obviously starting Driver Verifier, a tool for us kernel/driver developers to check the sanity of our drivers. And since you can pinpoint it already to a component (HyperSLI), the best would be to disable that component or "unconfigure" Driver Verifier from verifying that driver (may have to be done in a scheduled task in case that component is enabling it again and again).
First, use (in an elevated prompt):
to find which driver is being verified. This should yield a result other than
and reboot the machine to turn off Driver Verifier entirely. Remember that the HyperSLI might be re-enabling it, so short of removing it, you'll have to run this on every startup after HyperSLI does (in case it does).