mpack wrote:Perhaps because the driver certificates in the VBox drivers are not among your trusted providers.
This makes sense. Unfortunately, I have Win 7 HP, which does not have 'Local Group Policy', so I'm not certain how to check otherwise.
Perryg wrote:If I might suggest that the issue may be because of the VMware filters being installed? I have tested VMware and VirtualBox together and found many issues that caused conflicts including Video drivers, & Network drivers. With VMw installed and looking at the VBox settings it appeared that the VBox drivers were actually tied to the VMw drivers instead of the host.
This isn't the issue. I only installed VMware after the VB incident, so no VMware drivers were installed at the time.
Perryg wrote:Admittedly I have not tested this (VBox with VMw installed) in regards to USB, but I know for a fact that USB can be a really big issue in Windows. There are a lot of apps and drivers that can cause a conflict. Mine turned out to be a HP printer. The extra software installed was the issue in my case and not the specific print driver.
This makes sense. Is there a way to test what driver may be conflicting with the VB USB filter drivers, w/o uninstalling software/devices?
Perryg wrote:The fact that you have a lock-up indicates the drivers are being loaded but accessing reserved memory, Etc (IMHO).
On the same principle...how may I determine which IRQ VB USB filter drivers need, and then maybe I can visually see via Device Manager what other device is occupying that IRQ?