• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

How I resolved an Error 43 issue on my graphics card

Joined
Oct 5, 2017
Messages
5 (0.00/day)
So, I had a computer where any graphics card i installed would fail with error 43 on the graphics card.
It did this with every graphics card I put in, didn't matter if it was AMD or Nvidia, New or Old.

I couldn't figure out for the life of me why or how i can resolve this. It only had issues in windows, on boot up it seemed completely fine with both screens turning on but the driver doesn't last more than a second or two on this machine.

So my set up is a bit weird. Since the graphics card can run on Microsoft Basic Video Driver, I just ran 1 monitor through the graphics card, 1 through the intel built in graphics, and 1 through a usb to vga adapter.

But when the Graphics card driver crashed, it crashed the other video drivers. So they needed to be restarted to get my displays back.

After some research I found a developement tool from Microsoft called devcon.exe. So I dropped a copy of it to my system32 folder and created a .bat script to restart my other two graphics drivers for me so the monitors would automatically start up for me. I created the script and then added it to group policy to the Startup Scripts policy.

Miraculously on startup the Graphics driver loads without an issue and doesn't crash anymore.

This is weird cause I had tried disabling other graphics devices and restarting with no avail. as well as unplugging and disabling the intel gpu in bios with again no luck.

But it works so can't complain. Weird fix but atleast it works.

Thought i should post this somewhere so it can help someone.

Install Devcon:
https://superuser.com/questions/100...ce=google_rich_qa&utm_campaign=google_rich_qa
Devcon Guide:
https://ccm.net/faq/1886-enable-disable-a-device-from-the-command-line

Open notepad and type in the commands to disable and enable the devices you want. I found finding the device instance path was easier in device manager. Under details the property Device Instance Path. I used commands like "devcon disable *DEV_1912*" as i found the DEV part of the instance path was unique to the device, but it is ideal to double check this with devcon find * and copy and pasting to notepad and using the find function.

Can't find a guide for Local Group policy set up so i'll just type what to do.

Start>search Edit Group Policy>Computer Configuration>Windows Settings>Scripts>Startup
In that policy point to the .bat you created and that should be everything.

For this to work, you have to have another graphics device and something plugged into it preferably. (haven't tested it without something plugged into it but feel free to let me know how it goes)
This guide is a bit half a*sed but i'm hoping the people who read this are IT literate. If not feel free to reply to this thread and i'll happily reply with assistance. or a proper guide if needed.

My script:
devcon disable *DEV_1912*
devcon disable *VID_0711*
ping 127.0.0.1 -n 5 > nul
devcon enable *DEV_1912*
devcon enable *VID_0711*

device instances may vary. I will be removing the USB to VGA adapter when i get a longer cable aswell.
The ping is to create a delay before the next command is ran.

Sorry for the long post. Hope this will help others.
 
Last edited:
Nice intro. Welcome to TPU. :toast:
 
I have tried the cards nvidia geforce 210, nvidia geforce gt 710, AMD 5450, and an AMD 7750.

The link only refers to AMD cards. Is this an AMD specific issue? if so why did the NVidia cards not work?

Also, the issue is on a my work computer, and i need it to do work. so this can cause unnecessary downtime to test.

It's not broke anymore. so if it ain't broke, don't fix it. but i'm sure someone in the future may be able to test it if the same conditions ever occur again.

(running the AMD 5450 at the moment btw)
 
One also might solve this by placing the gpu in another slot as per the motherboard manual, and making sure chipset drivers are up to date and windows itself is not corrupted, and of course using DDU to cleanly wipe all old traces of video drivers
 
No other slots available. single slot only motherboard (if there were two slots i wouldn't be using integrated intel). Used DDU multiple times with no luck and i tried many different versions of the driver ranging from old to new. I made sure chipset drivers are up to date and BIOS. Windows may have an issue, but again, work PC. any downtime is kinda un-beneficial. I believe i have ran DISM /online though with no luck aswell.
 
Also you haven't mentioned which windows version. I would have tried latest windows 10 image or even insider preview, with in-place upgrade so your apps will be intact. But you got it sorted somehow, so there's that. Does the gpu work fine now in terms of graphics performance?
 
It seems to be ok. Windows build is 1709. but the issue has existed over multiple build versions that have been installed on this machine. Also when the driver crashes it reverts back to Microsoft Basic Display adapter (doesn't tell you that but thats what windows does by default) which prevented me from using multiple monitor connections to the card. but now it's working i have 2 monitors connected to the card and I ran a stress test on it and it performed as it should.
 
Back
Top