logo elektroda
logo elektroda
X
logo elektroda
Dostępna jest polska wersja

Czy wolisz polską wersję strony elektroda?

Nie, dziękuję Przekieruj mnie tam

NVidia GeForce GT 630 - code 43 - The system reports a graphics card error (CODE

EA7Lorus 16107 15
Best answers

Why does a GeForce GT 630 show Code 43 in Windows 7/8.1 64-bit on one PC but work on another, and is the power supply likely the cause?

It is unlikely to be the weak PSU; the thread points more toward a motherboard/chipset or driver compatibility issue, because the GT 630 works in another PC and also runs correctly under Mint 64-bit [#16867025][#16871711][#16873564] Suggested checks were to clean out NVIDIA drivers with DDU, reinstall chipset drivers, and update the motherboard BIOS [#16873004][#16875658] One reply also suggested testing the card in Linux and using GPU-Z to see whether the card is detected properly and whether the driver state changes at all [#16867025][#16873004] A specific driver package, NVIDIA 320.18 WHQL, was linked as a possible fix for similar Code 43 cases, but it did not solve the issue here [#16866878][#16867917] Since the card failed on both Windows 7 64-bit and Windows 8.1 64-bit while working on 32-bit Windows and Linux, the thread never found a definitive Windows-x64 fix [#16867917][#16871711][#16878451]
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 16866866
    EA7Lorus
    Level 8  
    Posts: 15
    Rate: 6
    Hello,
    I have assembled my new computer set but unfortunately I have a problem running the Gigabyte GeForce 630 2GB DDR3 graphics card on it.
    After installing the drivers, it is seen by the system, while it reports the visible name error with a yellow exclamation mark "Windows has stopped this device due to reported problems. (Code 43)".
    I tried old drivers and the latest ones, as well as reinstalling the system, while the problem does not go away. Can it be a too weak power supply as for my set which I present below?
    The card is definitely functional, checked on the second set which is nice.
    If my assumptions are confirmed, what power supply do you recommend? Just OCZ Fatality 550W?
    Alternatively, thank you in advance for any other advice and ideas on how to deal with this problem.

    Specification of my equipment (PROBLEM WITH THE CARD)

    -Main Board: Ascrock M3A-UCC
    Processor: Amd Athlon II x4 640 (4x3.0Ghz)
    - RAM memory: 2x2GB DDR3 1333Mhz
    Graphics Card: Gigabyte GeForce GT630 2GB DDR3 (Problem is reported)
    -Power supply: Qltec SilentLine 425W
    -System: Windows 7 64Bit

    The second set on which the card works without a problem

    - Motherboard: NTT P5GC-MX
    Processor: Intel Pentium Dual Core E2180 (2x1.8Ghz)
    RAM memory: 2x1GB DDR2 1066Mhz
    - Graphics Card: Gigabyte GeForce GT630 2GB DDR3 (Works without problem)
    - Power supply: Logic 400W
    -System: Windows XP 32Bit

    Regards
  • ADVERTISEMENT
  • ADVERTISEMENT
  • #3 16867025
    safbot1st
    Level 43  
    Posts: 21951
    Help: 2719
    Rate: 1583
    It's no secret that blacklisted pseudo-PSUs like to damage motherboards.
    Check that the tips of the electrolytic capacitors (black ones) on the Ascrock M3A-UCC are not swollen / cracked.
    https://www.elektroda.pl/rtvforum/topic1199271.html
    Possible other problems due to the fault of the pseudo-PSU.
    Of course, it also happens that the drivers "do not match" the card and throw BSODs and errors.
    Check under bootable linux whether GPU acceleration works on this set # 1.
  • #4 16867917
    EA7Lorus
    Level 8  
    Posts: 15
    Rate: 6
    witoldwitoldowicz wrote:


    Unfortunately, but in my case these drivers did not solve the problem, of course, I previously uninstalled the current and removed all traces of them. As well as I tried the format and installation on a clean system.

    safbot1st wrote:
    It's no secret that blacklisted pseudo-PSUs like to damage motherboards.
    Check that the tips of the electrolytic capacitors (black ones) on the Ascrock M3A-UCC are not swollen / cracked.
    https://www.elektroda.pl/rtvforum/topic1199271.html
    Possible other problems due to the fault of the pseudo-PSU.
    Of course, it also happens that the drivers "do not match" the card and throw BSODs and errors.
    Check under bootable linux whether GPU acceleration works on this set # 1.


    My guess is that this is not a high class power supply, but it has existed with me for 3 years without any complaints, at least on the previous set. Capacitors checked and all in perfect condition without any damage or changes. Unfortunately, the test under Bootable linux dropped out due to a problem with its launch, I tried on several versions but unfortunately always loading hangs on a black screen.

    What else can be the reason for this?
    I plugged into it an old graphics card model Nvidia 7300GT and started without any problem, all drivers installed without a problem and the system does not report errors. Also it must be strictly about this GT630.

    EDIT
    I broke the bed and tested all the drivers for this card, of course, including the oldest ones, the card did not move on any, and there is still information about the problem with the device driver (CODE 43).
    However, I was tempted to temporarily change the system from 64-bit Windows 7 Ultimate to the 32-bit version and, interestingly, there is no problem with this version, I installed the first better drivers and the card works, is correctly installed and the system does not report any errors.
    In that case, is this a problem with the 64 Bit System? Anyone have ideas why it works on that and not on it and how to solve this problem?, I am already missing ideas.
    I'm still trying to get Windows 8.1 64-bit to see if the same problem will occur there as well.

    I merged. RADU23
  • #5 16870805
    safbot1st
    Level 43  
    Posts: 21951
    Help: 2719
    Rate: 1583
    safbot1st wrote:
    Check under bootable linux whether GPU acceleration works on this set # 1.

    There you have the normal Geforce support. E.g. Mint 18 64bit. Free.
  • ADVERTISEMENT
  • #6 16870985
    310artur
    Level 43  
    Posts: 9002
    Help: 980
    Rate: 670
    Maybe a problem with the chipset drivers and not the card itself? That's my guess.
  • #7 16871711
    EA7Lorus
    Level 8  
    Posts: 15
    Rate: 6
    safbot1st wrote:
    There you have the normal Geforce support. E.g. Mint 18 64bit. Free.


    I downloaded and started the linux edition you mentioned. The card works normally, it was detected without problems, and the latest drivers were installed. So far the only problem is on Win 7 64Bit.

    310artur wrote:
    Maybe a problem with the chipset drivers and not the card itself? That's my guess.


    Unfortunately, but on the manufacturer's website "Asrock" There are no drivers for the chipset for this board, while all drivers that are there have been installed.

    EDIT.

    I also tested on Windows 8.1 Pro 64Bit and unfortunately as in the case of Windows 7 the system reports problems with the CODE 43 card driver.
  • #8 16872962
    310artur
    Level 43  
    Posts: 9002
    Help: 980
    Rate: 670
    Do you have the option to swap the CPU? Not likely but it's possible that there is a problem somewhere.
  • #9 16873004
    safbot1st
    Level 43  
    Posts: 21951
    Help: 2719
    Rate: 1583
    EA7Lorus wrote:
    I broke the bed and tested all the drivers for this card, of course, including the oldest ones, the card did not move on any, and there is still information about the problem with the device driver (CODE 43).
    EA7Lorus wrote:
    Unfortunately, but on the manufacturer's website "Asrock" There are no drivers for the chipset for this board

    Let's start with the AMD 480X CrossFire (TM) Chipset, and you put ... NVidia.
    Maybe it's a problem
    But did you check if they change at all? Eg in GPU-Z?

    Added after 38 [seconds]:

    Did you clean the remains of the previous driver with DDU?
  • #10 16873522
    EA7Lorus
    Level 8  
    Posts: 15
    Rate: 6
    310artur wrote:
    Do you have the option to swap the CPU? Not likely but it's possible that there is a problem somewhere.


    Unfortunately, but I have no such possibility, it has no other processor under this socket.

    safbot1st wrote:
    Let's start with the AMD 480X CrossFire (TM) Chipset, and you put ... NVidia.
    Maybe it's a problem
    But did you check if they change at all? Eg in GPU-Z?

    Did you clean the remains of the previous driver with DDU?


    But in my opinion if there was a problem with the chipset because it is "AMD" and I push "Nvidie" then the insight card would not move, and the problem is only on 64-bit systems. (Unless I don't know each other and it is somehow connected).
    I checked and the drivers change normally but the card behaves like dead, its name, memory etc. are not shown.
    Of course, I was cleaning leftovers from older DDU drivers.
    Unfortunately, there is no solution.
  • Helpful post
    #11 16873564
    safbot1st
    Level 43  
    Posts: 21951
    Help: 2719
    Rate: 1583
    EA7Lorus wrote:
    the problem is only on 64 bit systems. (Unless I don't know each other and it is somehow connected).

    After all, it works on Mint 64bit. I don't see the connection any more. . . as you wrote - "dot without a solution" ... :(
  • ADVERTISEMENT
  • #12 16874952
    EA7Lorus
    Level 8  
    Posts: 15
    Rate: 6
    safbot1st wrote:
    After all, it works on Mint 64bit. I don't see the connection any more. . . as you wrote - "dot without a solution" ... :(


    Yes, but Mint is the only 64 Bit system on which it worked flawlessly.
    Anyway, it's possible that the disc has some conflict with this card because of the chipset, I decided to sell it and switch to some Radeon, I think that will solve any problems. Thank you all for your commitment and great willingness to help.
  • #13 16875658
    safbot1st
    Level 43  
    Posts: 21951
    Help: 2719
    Rate: 1583
    Update the BIOS
    http://www.asrock.com/mb/AMD/M3A%20UCC/index.asp?cat=Download#BIOS
    and look under the processor - physically,
    310artur wrote:
    Do you have the option to swap the CPU?

    , legs are not bent etc. following this way of thinking.
    The BIOS of the card can also be flash, and we still do not know whether the fault is hardware or software (bug in the driver).
  • #14 16878451
    EA7Lorus
    Level 8  
    Posts: 15
    Rate: 6
    safbot1st wrote:


    Bios, I did it right after the card didn't work, but it didn't work.

    safbot1st wrote:
    and look under the processor - physically, legs are not bent etc. following this way of thinking.
    The BIOS of the card can also be flash, and we still do not know whether the fault is hardware or software (bug in the driver).


    The processor just in perfect condition, there are no crooked legs, I looked into it when assembling the computer again, i.e. a few days ago, when replacing the thermo paste with a new one. Also still at the starting point.

    EDIT.

    Unfortunately, despite the passage of time, and a multitude of ideas, combinations, I could not run this card on 64-bit Windows.
    Also the decision fell on the purchase of Gigabyte Radeon R7 250OC 2GB or probably a twin card for my current GT630, I hope that the chipset of the same family will solve the problem.
  • #15 16890898
    Xind97
    Level 7  
    Posts: 7
    EA7Lorus wrote:
    Also the decision fell on the purchase of Gigabyte Radeon R7 250OC 2GB or probably a twin card for my current GT630, I hope that the chipset of the same family will solve the problem.


    If you have not bought this Radeon yet, it is better to be interested in Radeon 7770 1GB DDR5, a card much more efficient than this 250OC. You should find her for a few zlotys more. Especially if you plan to play any games.
  • #16 16893032
    EA7Lorus
    Level 8  
    Posts: 15
    Rate: 6
    Xind97 wrote:
    If you have not bought this Radeon yet, it is better to be interested in Radeon 7770 1GB DDR5, a card much more efficient than this 250OC. You should find her for a few zlotys more. Especially if you plan to play any games.


    I analyzed various forums and decided to buy Gigabyte Radeon 7770 1GB GDDR5, I am just waiting for its arrival.

    The topic can be considered closed, thank you all for your input and statements.

Topic summary

✨ The discussion revolves around a user experiencing a "Code 43" error with a Gigabyte GeForce GT 630 graphics card after assembling a new computer. Despite the card functioning correctly on another system, it fails to operate on the user's setup, which includes an Asrock M3A-UCC motherboard and an AMD Athlon II x4 640 processor. The user has attempted various driver installations, including older versions and a clean OS install, but the issue persists. Suggestions from other users include checking the power supply, chipset drivers, and BIOS updates. The user successfully tested the card on a Linux system, indicating a potential compatibility issue with Windows. Ultimately, the user decided to switch to a Radeon graphics card, specifically the Gigabyte Radeon 7770, to resolve the problem.

FAQ

TL;DR: 2 out of 2 tested 64‑bit Windows installs returned Code 43, while “The card works normally” on Mint 64‑bit; start with BIOS and driver hygiene. [Elektroda, EA7Lorus, post #16871711] Why it matters: This FAQ helps Windows users fix or decisively triage GT 630 Code 43 on older AMD/Asrock platforms.

Quick Facts

What does Windows “Code 43” mean for an Nvidia GeForce GT 630?

Windows disabled the device after detecting a problem. In Device Manager, GT 630 shows a yellow mark and Code 43 after driver install. This indicates the OS stopped the GPU due to reported issues, not necessarily a dead card. [Elektroda, EA7Lorus, post #16866866]

Does this issue affect only 64‑bit Windows in the reported case?

Yes. The same hardware produced Code 43 on Windows 7 64‑bit and Windows 8.1 64‑bit. The card worked under Mint 64‑bit, confirming the GPU functions. That pattern points to a Windows driver or platform interaction, not a failed card. [Elektroda, EA7Lorus, post #16871711]

Will the GT 630 work on Windows 7 32‑bit with the same parts?

Yes. The user reinstalled Windows 7 32‑bit. Drivers installed and the system reported no errors. This establishes a control showing the GPU can operate on Windows, just not on the 64‑bit builds used. [Elektroda, EA7Lorus, post #16867917]

How can I clean-install Nvidia drivers properly (DDU method)?

  1. Uninstall Nvidia software, then reboot to Safe Mode.
  2. Run Display Driver Uninstaller (DDU) to remove remnants, then reboot.
  3. Install the desired Nvidia driver and check Device Manager. “Did you clean the remains… with DDU?” was a key prompt. [Elektroda, safbot1st, post #16873004]

Could chipset drivers be the reason for Code 43?

It’s plausible. One responder pointed to chipset drivers as a root cause, not the GPU. On older boards, missing or generic chipset packages can break PCIe device initialization and power states, triggering Code 43. [Elektroda, 310artur, post #16870985]

Should I update the motherboard BIOS to fix GT 630 Code 43?

Yes. A BIOS update was advised, along with checking CPU seating and considering a GPU VBIOS flash. Firmware fixes can resolve PCIe compatibility quirks that manifest as Code 43. “Update the BIOS” was the explicit guidance. [Elektroda, safbot1st, post #16875658]

How do I verify the card is detected at hardware level?

Use GPU‑Z and observe whether the device ID, clocks, and memory fields populate. If they remain blank or erratic after driver changes, that supports a platform or driver problem rather than only software. This check was suggested in-thread. [Elektroda, safbot1st, post #16873004]

Can a poor‑quality PSU really cause GPU errors like this?

Yes. A contributor warned that blacklisted pseudo‑PSUs can damage motherboards. Inspect electrolytic capacitors for bulging or cracking. Unstable rails can provoke device errors under driver load and cause intermittent detection. [Elektroda, safbot1st, post #16867025]

My Linux live USB hangs on a black screen. Is the GPU dead?

Not necessarily. The same user first saw a black‑screen hang from several Linux images, then later booted Mint 64‑bit and confirmed the GT 630 worked. Live media can fail for reasons unrelated to GPU health. [Elektroda, EA7Lorus, post #16867917]

What quick triage steps should I try before replacing the card?

Do a DDU clean and reinstall, check with GPU‑Z, and update the motherboard BIOS. If possible, test on a Linux Mint live session to validate hardware. These steps were all recommended across replies. [Elektroda, safbot1st, post #16873004]

Is switching to an AMD Radeon a practical workaround on this platform?

The OP opted to move to Radeon and closed the thread. This is a pragmatic exit if repeated 64‑bit Windows attempts still trigger Code 43 with GT 630 on the M3A‑UCC. [Elektroda, EA7Lorus, post #16893032]

Which Radeon alternatives were suggested as upgrades?

A helper recommended the Radeon HD 7770 1GB GDDR5 over the R7 250 OC due to better performance for a small price delta. The OP later chose the 7770. [Elektroda, Xind97, post #16890898]

Is flashing the GPU’s VBIOS worth considering?

It was mentioned as an option after updating the motherboard BIOS and checking the CPU seating. Flashing carries risk, but can resolve rare compatibility issues. Proceed only after safer steps. [Elektroda, safbot1st, post #16875658]

Does a stable PSU history rule it out as a cause?

No. The PSU reportedly ran three years without complaint, yet the board still showed issues. Aging or marginal PSUs can pass light loads but fail under driver‑initialized states. Inspect and, if needed, swap for a known‑good unit. [Elektroda, EA7Lorus, post #16867917]

Bottom line: what was the final outcome here?

After extensive attempts, the user moved to a Radeon HD 7770 and considered the topic closed. This indicates a platform‑specific incompatibility with GT 630 on 64‑bit Windows for that build. [Elektroda, EA7Lorus, post #16893032]
ADVERTISEMENT