New
#70
Good idea.
Is there a way I can convert my VMDK virtual disk to hyper-V format?
I found this below that may work to convert VMWare VMDK to Hyper-V VHD.
How to Convert a VMWare VMDK to Hyper-V VHD s blog
My AMD A8-3850 PC (Asus F1A75-M) simply reboots to a blue screen with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, and then auto-reboots and disables 'Memory Integrity' again. No BSOD dumps are stored to disk.
Must be one of these drivers:
dump_diskdump.sys- built-insdump_storahci.sys- built-insdump_dumpfve.sys- built-ins- usbfilter.sys - AMD's USB 2.0/3.0 0.96 driver ver: 2.1.11.304 (most recent)
- nvvad64v.sys - recent Nvidia Virtual Audio driver
- nvhda64v.sys - recent Nvidia HDMI Audio driver
- nvvhci.sys - recent Nvidia Virtual USB Host driver
- nvlddmkm.sys - recent Nvidia graphics driver
- L1C63x64.sys - ethernet driver (ver: 2.1.0.16) that ships with Windows 10. Also tried more recent ver: 2.1.0.27
All of these pass the driver verifier test by 'Device Guard and Credential Guard hardware readiness tool'. For the other things the tool is moping that I don't have secure boot and some other things that seem to more or less require UEFI (HSTI, TPM, Secure MOR, NX Protector, SMM Mitigation). Yes my system has the NX bit.
So.. How do you figure out what driver is tripping the memory protections? Maybe force disable ASLR, and then compare the 2nd number that's dumped on the screen with DriverView addresses?
It's not so easy to figure it out.
For me, it was Zemana, even though I did not have active protection enabled.
Comodo firewall is not fully supported, and Kapersky Internet Security is not fully supported, but I don't think they will cause a BSOD.
I am just saying the ones I know.
I've disabled the network driver and used DDU to uninstall the nvidia drivers. What remained of third party drivers was usbfilter.sys.
Still a blue screen. So it's either the USB driver, or none of the listed drivers. I only use Windows Defender. After reinstalling nvidia from Windows Update, I seem to have lost nvvhci.sys
btw, uninstalling the usb filter is not adviced; made me search my PS/2 keyboard
It could be a problem with your systems handling of your hypervisor platform, or what ever AMD's version of Virtualization technology(in BIOS).
Well, this is a Windows 10 Home install, so I can't really test Hyper-V any more than this. I don't remember having any trouble running VMs (under Linux at least) in the past. Everything ought to work.
Still wondering if there is a way to fall back to Microsoft generic USB drivers. Do they exist?