Highlighted
3 Zinc

Re: 15 R3, Unable to update to newest NVIDIA drivers

A Code 43 usually means one of three things. 
1. Bad driver

2. Corrupted vBIOS

3. Dead/Dying GPU

First thing to try is roll back to an earlier driver.

If you still get the Code 43 then you can try flashing the vBIOS

If that doesn’t work then your GPU is having serious issues. 

Current Machines
Alienware M18x R2 - i7-3920XM - GTX 1070 -16GB 1866MHz
17 R1 - i7 4910MQ - No GFX
17 R1 - i7 4710MQ - N0 GFX - Test Machine
M17x R3 - i7 2670QM - GTX 580M - 16gb
M15x - i7 720QM - GTX 660M - 8gb
M15x - i7 840QM - GTX 460M - 8gb
M14x R2 - i7 3630QM - GT 650M - 6gb - Dead Board
X51 R1 - i7 3770 - GTX 1060 - 16gb
Highlighted
2 Bronze

Re: 15 R3, Unable to update to newest NVIDIA drivers

@mattyb3 Thanks for following up. I have rolled back to the Dell A11 (23.21.13.8799) driver and the machine works well with that driver installed. None of the newer drivers work. The frustrating part is that I cannot play games that require updated drivers.

Do you have instructions on how to flash the vbios? 

0 Kudos
Highlighted
3 Zinc

Re: 15 R3, Unable to update to newest NVIDIA drivers

I don’t like to tell people to flash a BIOS’ because there is always a chance of something going wrong. Firstly I’d make sure that your system BIOS is up to date. It’s possible that the vBIOS is also available on the Dell site but if not then TechPowerUp is the home of all the GPU vBIOS’. You need to install NVFlash and watch some YouTube videos or read guides on how to flash. A bad flash can brick your card though. 

Current Machines
Alienware M18x R2 - i7-3920XM - GTX 1070 -16GB 1866MHz
17 R1 - i7 4910MQ - No GFX
17 R1 - i7 4710MQ - N0 GFX - Test Machine
M17x R3 - i7 2670QM - GTX 580M - 16gb
M15x - i7 720QM - GTX 660M - 8gb
M15x - i7 840QM - GTX 460M - 8gb
M14x R2 - i7 3630QM - GT 650M - 6gb - Dead Board
X51 R1 - i7 3770 - GTX 1060 - 16gb
Highlighted
2 Bronze

Re: 15 R3, Unable to update to newest NVIDIA drivers

@mattyb3 

Yeah, I am a bit hesitant to go that far. As I said, everything works fine with the older driver so I might just have to accept it and start planning for my next purchase...

 

0 Kudos
Highlighted
3 Zinc

Re: 15 R3, Unable to update to newest NVIDIA drivers

I’m running a 1070 in my old M18x and I can install the latest drivers straight from Nvidia (but I have to mod it first). There’s something not quite right with yours. It should install the Nvidia driver without an issue but it’s really hard to diagnose over a forum. 

Current Machines
Alienware M18x R2 - i7-3920XM - GTX 1070 -16GB 1866MHz
17 R1 - i7 4910MQ - No GFX
17 R1 - i7 4710MQ - N0 GFX - Test Machine
M17x R3 - i7 2670QM - GTX 580M - 16gb
M15x - i7 720QM - GTX 660M - 8gb
M15x - i7 840QM - GTX 460M - 8gb
M14x R2 - i7 3630QM - GT 650M - 6gb - Dead Board
X51 R1 - i7 3770 - GTX 1060 - 16gb
Highlighted
2 Bronze

Re: 15 R3, Unable to update to newest NVIDIA drivers

The only similar problem I have found on the web is this one:

https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/304967/1070-black-screens-driver-u...

but his "tempanent" fix doesn't work for me unfortunately. Especially with the Code 43 popping up. 

I have been trying to fix this on and off for two years and still haven't gotten anywhere with it. I wonder if it had to do something with the security update to Intel chips (due to the spectre problem?) in 2018. I cannot update to any nvidia drivers that were produced after that and I have come across a number of posts related to graphic cards failing due to that issue.

0 Kudos
Highlighted

Re: 15 R3, Unable to update to newest NVIDIA drivers

Here’s a vBIOS flashing software but I’d suggest you hold back on it.

https://www.techpowerup.com/download/nvidia-nvflash/

Alienware 18 R1 4940MX 4.6GHz, RTX 2080, 32GB DDR3
Alienware 17 R5 i9-8950HK 4.5GHz, GTX 1080 OC, 32GB DDR4 2666MHz
Alienware 15 R1 4710HQ 4.1GHz, GTX 980M, 16GB DDR3
M18x R2 3930MX 4.1GHz, SLI GTX 980M, 16GB DDR3 1600MHz
M17x R5 Core i7-4700MQ 3.7GHz, GTX 980M, 32GB DDR3 1600MHz
My YouTube channel = Area 51 A L X


If my reply solved the issue, please click the, "Accept as Solution" button!