sk1080
sk1080
Ive seen code 43 in cases where the virtualization platform simply isn't capable of setting up a passed through graphics card. A quick search shows that at least as of...
Original debugging was done with windbg, with breakpoints on known instances of the cpuid instruction within the nvidia driver. I wouldn't be surprised if other virtualization platforms trigger things a...
Probably isn't vendor ID that is tripping it with my patch in place, especially as I verified mine is currently set as "Microsoft Hv", which they blacklist. If I get...
Haven't given windows 7 a test, but I did have a go with Windows 10, xen 4.7 (not xenserver...), and driver 373.06, which seems to work for me (driver doesn't...
I just added Windows 7 x64 Support to the repo. Also, code 43 seems to happen for reasons unrelated to the hypervisor detection, and can be dependent on the bios...
I don't know if he did, but I "did". However, got horrible graphics corruption and issues, although the card did "work". libvirt/qemu is probably a better idea.
Id advise you try pasting the bytes into a tool like https://defuse.ca/online-x86-assembler.htm#disassembly2 and looking at the corresponding code in the driver with a proper disassembler such as IDA, radare2, or...
Looks like gencert still has issues, ill take a look EDIT: gencert error isn't fatal
However, in this case, not really sure whats going on...
Could you remove the "| Out-Null" parts out of the script where it calls commands, and paste the full output log?