Easy-GPU-PV icon indicating copy to clipboard operation
Easy-GPU-PV copied to clipboard

Published 20 hours ago • verified publisher icon jamesstringerparsec

GPU Driver Fail (Code 43) on IvyBridge with GTX1060 - Win10

Open jabza opened this issue 3 years ago • 5 comments

Hi,

I've been trying to get setup on an IvyBridge i5 3570k with a GTX 1060. Windows 10 PRO (10.0.19043 Build 19043).

The first error I ran into was the MMIO capacity one (due to old CPU) (https://github.com/jamesstringerparsec/Easy-GPU-PV/issues/40)

This was fixed by setting the max down from 32GB to 512MB. Although I'm unsure what side-effects this will cause.

After that the VM boots, but clearly in device manager the GTX 1060 is showing with the warning symbol, code 43. I've noticed on Host that there is no change to Display Adapters, not sure if there's more ways to check how things are going wrong?

I've tried the following:

  • Rolling back to older an Nvidia driver.
  • Updating BIOS
  • Forcing Gen3 PCI-E
  • Switching card to a 4X PCI-E lane
  • Manually copying Nvidia driver DLLs

Wondering if this might be a lost cause due to older hardware.

Any thoughts on this would be much appreciated.

jabza avatar Feb 14 '22 02:02 jabza

Unfortunately you need a new MB+CPU. I had an old Ivy Bridge PC (Z68, i7-3770, GTX 1060) and spent days trying to solve the Code 43 error with no luck. When I bought a new PC (B550, R9 5900X and the same GTX 1060), GPU-P works like a charm. Also found another guy on Reddit who had the same problem with Ivy Bridge, later they upgraded to Zen 2 or 3 (don't remember) and had no problems since.

mirobartovic avatar Apr 01 '22 16:04 mirobartovic

I have the same issue. Is there really no way software could fix this @mirobartovic? I'm getting new parts soon anyways but I'd really like to test the waters sooner than later..

Flamity avatar Apr 21 '22 20:04 Flamity

@Flamity I'm not a developer of Easy-GPU-PV. If you want to test GPU-P, try running Windows Sandbox. It's automatically configured there and it's the only officially supported use of GPU-P. But the Sandbox VM is wiped at shutdown. Maybe GPU-P works there even on old HW. That would mean it's really a SW problem, but I don't think anyone will look into it.

mirobartovic avatar Apr 22 '22 06:04 mirobartovic

@mirobartovic I have Z77, i7-3770,1070. I tried Windows Sandbox with vGPU enabled and GPU-P works without problem. Benchmark ran almost as fast as host. I tried tinkering on Powershell about Hyper-V settings with no good results. It just won't work on Hyper-V VMs.

slayermaster avatar Aug 31 '22 09:08 slayermaster

@slayermaster that was also my experience on Z68+i73770+GTX1060. GPU-P worked in Sandbox, but not in Hyper-V.

mirobartovic avatar Sep 01 '22 10:09 mirobartovic