RTX 3060M - Code 43

[KARMAAA]

Hey,

So I got one of those AliExpress RTX 3060M's for Desktop and tried to install both or either the notebook and desktop drivers by adding the HW ID to my Windows 11 machine via NVCleanInstall.

I definitely added the HW ID and everything correctly because it installed and passed the compatibility check and it even assigned the driver to the device. But I get a Code 43 error on the device in Device Manager and only OpenGL is ticked as available in GPU-Z despite the driver installing. CUDA and everything else is unchecked and it detects 0 MB of VRAM. First I thought it was a VBIOS issue, but then I did some research and I'm running the same VBIOS as others who have it working and even the hashed VBIOS' match. I tried enabling and disabling EAC signing in NVCI, still code 43 in Device Manager. I tried recompiling the nv_disp.cat through some trickery to get NVCleanInstall to accept all the modified INF files, it got me a bit further but still... Code 43.

I have a feeling the driver needs an additional signature in order to operate properly? Or maybe there's some step I am missing. I did try turning on test-signing and turning off secure boot, only to get similar results, so I'm not sure what the problem is. Perhaps W1zzard or someone else knows?

Any help would be appreciated because I'd much prefer to build the drivers via NVCleanInstall than use a modified driver from someone else for security/malware reasons. Yes I know a certain GitHub driver exists, but I prefer clean drivers. I would feel more comfortable with the GitHub driver, if the method of compilation was actually open source to compile for myself, but they seem to want to keep it a secret, so they can charge money behind a paywall for the latest driver releases.

 

[eidairaman1]

Send it back

 

[W1zzard]

Yes I know a certain GitHub driver exists

I'm curious .. got a link?

 

[KARMAAA]

I'm curious .. got a link?

DM'd

Send it back

I could care less it's a paper weight, I bought it for tinkering, I got a 3060 Ti right now in my rig serving me well.

 

[W1zzard]

http://imgur.com/9HPGPaq

Hmm .. let me see what they've changed

 

[KARMAAA]

There's one folder removed as stated in the image above, NVPCF as it apparently creates Error 31.

There's two more folders added, one with a root certificate and an .nvi file, which is installed via the NVIDIA Setup Executable. They've made it a hidden option but you can see it by looking at Setup.CFG, that it installs.

The other folder had to do with EAC and nv_disp.cat. It must use that recompiled nv_disp.cat instead of the one in the driver.display folder.

 

[W1zzard]

Yeah, plus the changes in the inf files.. nothing suspicious there

Their EAC patch seems similar to what NVCleanstall does, it adds a new root cert in the system trusted store.

Not seeing anything obvious. You can use NVCleanstall's show folder option, delete the NVPC folder, double check the inf file changes manually. and then run setup.exe

Do you know more about that NVPCF issue? Worth adding an option to remove that?

 

[KARMAAA]

Not seeing anything obvious. You can use NVCleanstall's show folder option, delete the NVPC folder, double check the inf file changes manually. and then run setup.exe

I tried this, still Code 43. I basically tried to recreate their driver using a clean source that I modified myself and then installed via NVCleanInstall but it ended up always in Code 43. The only difference is that SHA256 driver certificate that it installs via NVIDIA Driver Setup, which is a hidden option. That has to be the key to getting it working.

Do you know more about that NVPCF issue? Worth adding an option to remove that?

I have no idea, I never tried it with NVPCF.

 

[W1zzard]

The only difference is that SHA256 driver certificate that it installs via NVIDIA Driver Setup, which is a hidden option

You did use the "rebuild signature" option in NVCleanstall? installing showed an "unsigned driver" warning?

 

[KARMAAA]

You did use the "rebuild signature" option in NVCleanstall? installing showed an "unsigned driver" warning?

Yes I did, still Code 43. Used the auto accept option too.

 

[W1zzard]

And if you add the folder with the cert, it works?

 

[KARMAAA]

And if you add the folder with the cert, it works?

Never tried it because you need to also add parameters in Setup.cfg to get it working, from what I understood it's a hidden checkbox like PhysX or HD Audio is in the Setup.exe, but it's automatically always checked in the Github driver and installs the certificate automatically, look at the "hidden" flag for instance and it's also "critical". If I dragged it to my own folder, I doubt it would work as it seems to need nvdisp.cat to also recognise it I assume to get it working.

I have no idea how certificates and stuff like that works, I thought it would be kind of dangerous to drag their certificate as it might be infected or something, so I never did it. I'm practically a novice at this type of thing. I tried downloading WDK and such for nv_disp.cat to compile it via inf2cat, but I could only get a test signing working, which is no good to get this working for actual use as a driver. But I did work out that I can just get NVCleanInstall to do nv_disp.cat for me after I've made all my changes.

I am happy though to try someone else's beta builds or ideas however. I am also happy to look into NVPCF as an option and testing with it on and off to see if it's worthwhile to include as an option. But I've come here basically for help because, been at this problem for 12 straight hours and I am kind of tired now haha. Soon I'll be going to sleep, but I will be sure to check this thread when I awake.

 

[Dan.G]

Could it be a power-related issue? As in, the 6/8 pin PCIe connector on the PCB not working properly?

 

[KARMAAA]

Could it be a power-related issue? As in, the 6/8 pin PCIe connector on the PCB not working properly?

No I can assure you with the right driver it works because I eventually gave in after 11 hours of problem solving and tried the other driver and it works, ran TimeSpy for an hour no problem. I never touched the power connectors and they are in tight, same with PCI-E slot.

 

[DescomplicandoHW]

I've got this problem too but managed to fix.

If you try to install the NVCleanInstall driver without installing a modded one first it gives you CODE 43 (there's something in the background blocking the execution of the driver)
First of all you need to Install a modded Driver called Frankendriver By Arutar, after installing and reboot you can build your packages as you like with NVCleanInstall and update that everything should work as desired, hope it helps, I'm here at Brasil and made this account just to help you, since the content on these cards is very vague.

 

[W1zzard]

there's something in the background blocking the execution of the driver

How interesting .. and once you installed Frankendriver once you can use NVCleanstall normally?

 

[KARMAAA]

How interesting .. and once you installed Frankendriver once you can use NVCleanstall normally?

I will try tonight adding the certificate from the other driver to NVCleanInstall. And I will also try seperately what @DescomplicandoHW has said and report back my findings.

 

[DescomplicandoHW]

How interesting .. and once you installed Frankendriver once you can use NVCleanstall normally?

Yes, by some reason after FrankenDriver I didn't got code 43 anymore, I tried to edit the bios and the driver manually for days, I've even got able to make a custom bios with new ID and powerlimits but I wasn't able to fix the checksum, flashing throug SPI results in black screen with spinning fans, the insteresting part is that the card is seen on Network miningOS, so maybe the modded bios worked partially, after that I went back to drivers, and after some time trying NVCleanInstall I got it to work after installing FrankenDriver, the same happens with the old chinese driver but it has alot of warning on my antivirus and has to disable integrity checking so, I wasn't that happy with the chinese driver, so Frankendriver and NVClean did to me.

Anyways I don't have this card anymore, as you can see mine come with some defect on gpu and was working only X8 of the lanes,

the performance was not much affected but I was affraid that other GPU Segments would be harmed as MCU so I returned, but it is a great card, even stronger than my current 5600 XT using only 80 Watts.