cotton9
asked on
Code 43 for both Radeon and NVIDEA since Win 8.1 upgrade?
Any idea why upgrading from Windows 8 to Windows 8.1 would cause a Code 43 for both NVIDEA and Radeon video cards?
I have a Gateway fx6850 desktop that came with Windows 7. I upgraded to Windows 8 when it became available with no problems at all. Eventually, I upgraded to Windows 8.1 and immediately ran into problems with my video card.
I had an NVIDEA GeForce 440 (PCI Express x16) installed, and it triggered a "Windows has stopped this device because it has reported problems. (Code 43)". If I manually disabled/enabled the card the display would change from a very low resolution to a normal resolution, but it would be black - showing a flickering cursor only.
I tried multiple drivers and eventually found one from November 2013 that would work, but with issues - freezing when going to sleep, occasional BSOD, etc.
I tried another NVIDEA card, with multiple drivers. Same problem. So I've been running with the old driver and original card for months, hoping NVIDEA would release a driver that would work. All new drivers have failed.
The BSODs have become more frequent, so I finally tried a Radeon R5 230 card/driver today - still triggering a Code 43.
Given that the PC was released w/ Windows 7, Gateway doesn't offer any drivers specific to Windows 8.1. But everything was working fine with Windows 8. Any ideas?
I have a Gateway fx6850 desktop that came with Windows 7. I upgraded to Windows 8 when it became available with no problems at all. Eventually, I upgraded to Windows 8.1 and immediately ran into problems with my video card.
I had an NVIDEA GeForce 440 (PCI Express x16) installed, and it triggered a "Windows has stopped this device because it has reported problems. (Code 43)". If I manually disabled/enabled the card the display would change from a very low resolution to a normal resolution, but it would be black - showing a flickering cursor only.
I tried multiple drivers and eventually found one from November 2013 that would work, but with issues - freezing when going to sleep, occasional BSOD, etc.
I tried another NVIDEA card, with multiple drivers. Same problem. So I've been running with the old driver and original card for months, hoping NVIDEA would release a driver that would work. All new drivers have failed.
The BSODs have become more frequent, so I finally tried a Radeon R5 230 card/driver today - still triggering a Code 43.
Given that the PC was released w/ Windows 7, Gateway doesn't offer any drivers specific to Windows 8.1. But everything was working fine with Windows 8. Any ideas?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I had high hopes when I realized that Windows Update hadn't run in months, but no luck. (I had disabled it to prevent it from overwriting the older nvidea driver that was kinda working.
Manually updating chipsets is foreign to me. I checked in the device manager, and everything that had "chipset" in the name was up to date. I ran the Intel driver update utility to check for the chipset, and everything except the LAN card came back as unrecognized (b/c they're Gateway?). I then downloaded the INF update utility and couldn't really figure out how to use it. I'm thinking that's probably not what I wanted anyway. Am I right?
Manually updating chipsets is foreign to me. I checked in the device manager, and everything that had "chipset" in the name was up to date. I ran the Intel driver update utility to check for the chipset, and everything except the LAN card came back as unrecognized (b/c they're Gateway?). I then downloaded the INF update utility and couldn't really figure out how to use it. I'm thinking that's probably not what I wanted anyway. Am I right?
ASKER
I'm working on the Windows to Go troubleshooting right now.
ASKER
Windows to Go didn't work the way I had hoped. After installation on an external hard drive, I was unable to get it to boot up to troubleshoot. I changed the bios boot order, and you could hear the drive running on boot, but it would eventually boot my regular Windows 8.1 from the internal hard drive.
After investing way too much time into this problem, and not coming up with a solution, I hopped in my car and purchased a new $600 Dell from a local retailer. I'm going to try a clean install on my current machine, and if that doesn't work, I'm busting open the new machine and moving on.
Unless anyone has any more ideas . . .
After investing way too much time into this problem, and not coming up with a solution, I hopped in my car and purchased a new $600 Dell from a local retailer. I'm going to try a clean install on my current machine, and if that doesn't work, I'm busting open the new machine and moving on.
Unless anyone has any more ideas . . .
What didn't work with windows 2 go, your feedback is not detailed.
ASKER
I'm not sure where the breakdown occurred. I installed it as prescribed, seemingly without issue. But when I would try to boot the computer, and have windows 8 load from USB, it would always load 8.1 from the C drive.
I tried some things with the bios boot order and eventually decided not to spend any more time troubleshooting that. There's just something extra frustrating about troubleshooting the troubleshooter.
The clean install just started, so we'll see it that helps.
I tried some things with the bios boot order and eventually decided not to spend any more time troubleshooting that. There's just something extra frustrating about troubleshooting the troubleshooter.
The clean install just started, so we'll see it that helps.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the guidance! Ultimately, a clean install of Windows 8.1 was required.
ASKER
I've tried the last half dozen or so drivers that Nvidia has released. I'll look into the chipset when I get back to the PC this evening.