May be difficult to debug because no minidump file is created in the guest OS.
Existing guest OS: Windows 2000 Server from a P2V where source PC had USB. When converted, I set the VM up with NO USB controllers. After P2V I had 'set devmgr_show_nonpresent_devices=1; start devmgmt.msc' and removed the now unused original USB devices with Device Manager.
Created a new VM in beta1, with 'Enable USB Controller' selected and attaching the above VDI and booting, and guest OS recognises the new USB hardware and installs existing drivers (from C:\I386 likely).
USB Devices and drivers:
Standard Enhanced PCI to USB Host Controller
C:\WINNT\system32\drivers\usbehci.sys 5.00.2195.6709
C:\WINNT\system32\drivers\usbhub20.sys 5.00.2195.6655
C:\WINNT\system32\drivers\usbport.sys 5.00.2195.6681
C:\WINNT\system32\usbui.dll 5.00.2134.1
Standard OpenHCD PCI to USB Host Controller
C:\WINNT\system32\drivers\openhci.sys 5.00.2195.6675
C:\WINNT\system32\drivers\usbd.sys 5.00.2195.6658
C:\WINNT\system32\drivers\usbhub.sys 5.00.2195.6689
C:\WINNT\system32\usbui.dll 5.00.2134.1
USB 2.0 Root Hub
C:\WINNT\system32\drivers\usbhub20.sys 5.00.2195.6655
USB Root Hub
C:\WINNT\system32\drivers\usbhub.sys 5.00.2195.6689
*** Stop: 0x0000001E (0xC0000005,0xEB298E17,0x00000000,0x000000CC)
KMODE_EXCEPTION_NOT_HANDLED
(screen dump attached)
Stop: 0x0000001E ... ntoskrnl.exe
Unfortunately, no minidump was indicated in the message or produced (tho' the OS has been setup to create minidumps and has in the past done so).
Guest can be booted by turning 'Enable USB Controller' off, but as soon as it is turned back on, the BSOD occurs.
If I turn it off and 'set devmgr_show_nonpresent_devices=1; start devmgmt.msc' and removed the now unused original USB devices I cna get one boot with 'Enable USB Controller', as the device drivers are installed, but next time BSOD. The '0xEB298E17' number was different the last time I reproduced it, but is consistent
The same sequence of steps in the same VDI image do not give a BSOD in 3.0.12