GPU Shows a Yellow Warning in Device Manager With an Error Code That Isn't 43? Code 10, 12, 31 & 45 Diagnosis Guide

2026-11-05 | GPU維修 | 11 min | HK GPU Fix 編輯部

GPU Shows a Yellow Warning in Device Manager With an Error Code That Isn't 43? Code 10, 12, 31 & 45 Diagnosis Guide

Key Takeaway

A yellow warning in Device Manager means Windows recognises the card but cannot run it normally. The error code in the status — Code 10, 12, 31, or 45 — says which layer is failing: device start, resource allocation, driver loading, or connection. Read the code first, record it after each step, and change only one variable at a time.

The Error Code Is the First Evidence

When a graphics card in Device Manager carries a yellow warning, the warning itself says very little. It means Windows can see the device but the device is not working normally. Which layer is at fault, whether the driver, the device start, the resource allocation, or the connection, is not visible from the warning icon alone.

The evidence is the error code, also called the problem code, shown in the device properties. Open Device Manager, open the graphics card properties, and read the device status text on the general tab. The detailed information tab can also show the problem code. Write down the full status wording, not just the words yellow warning, because the wording is what separates the four codes in this guide.

Each code corresponds to a different layer, and each layer leads in a different diagnostic direction. Reinstalling the driver before reading the code is guessing. For one code the driver is the right first suspect; for another the driver is irrelevant, and the fix sits in the BIOS or in the physical connection.

One more principle applies throughout. After every diagnostic step, read the error code again. If the code changes, for example from Code 45 to Code 10, that change is itself diagnostic information: the previous layer problem is resolved and the next layer problem has surfaced. If the code disappears but the device still does not work normally, record that too. A code that changes is progress, even when the device is not yet working.

A yellow warning is not a death sentence for the card. The error code is a sorting tool, not a verdict. Different codes have different causes, and the steps below work through each one on its own terms.

Code 10 — This Device Cannot Start

Code 10 means Windows tried to start the device but the device failed to initialise. The driver has loaded, or has tried to load, but the device itself did not respond or failed to start. The distinction matters: the failure is at the device start stage, not at the driver loading stage.

The possible layers span the driver, the device initialisation, and the hardware. On the driver side, the driver version may not match the graphics card or the Windows version, the driver files may be damaged, or leftover files from a previous driver may be interfering. On the initialisation side, the card may fail to complete its start sequence because of power delivery, slot contact, or firmware state. On the hardware side, the card itself may fail to initialise. That last possibility is considered last, not first.

The diagnostic steps for Code 10 are: first, record the driver version and date and compare them with when the symptom began, including whether a driver or Windows update happened just before. Second, perform a clean driver reinstall, cleaning out in Safe Mode with DDU and reinstalling, testing with the same driver version first rather than changing versions at the same time. Third, try another driver version as a rollback test, changing only one variable at a time. Fourth, check the Event Viewer around the time of the start failure for related errors. Fifth, shut down, disconnect power, and reseat the card and its power cables, then start again and check whether the code has changed. Sixth, if conditions allow, try a different slot, or fit the card in another computer as a comparison. That last test is the decisive separation between the card itself and the environment of this particular machine.

Do not write Code 10 off as always a driver problem or always a hardware problem. Both are possible, and only the steps above separate them.

Code 12 — This Device Cannot Find Enough Free Resources

Code 12 means Windows cannot allocate enough resources for the device. Most often the resource in question is memory address space, known as BAR, or Base Address Register, allocation. It is not a shortage of power supply wattage, and it is not a shortage of power in general. Treating it as a power problem leads the investigation in entirely the wrong direction.

The common layers are firmware resource allocation and system resource contention. On the firmware side, the motherboard BIOS may not have Above 4G Decoding enabled, so a card with a large BAR cannot be given enough address space. CSM, the compatibility mode, being enabled can restrict address allocation. Resizable BAR settings are also involved in BAR allocation. On the system side, a second card, additional expansion cards, or several large BAR devices can compete for the same address space.

The trigger timing is a strong clue. Code 12 often appears after a card has been changed, a second card has been added, the BIOS has been updated, or the BIOS settings have been reset. If any of those changes happened just before the code appeared, the investigation starts there.

The diagnostic steps for Code 12 are: first, check what changed recently, whether hardware was swapped or added, the BIOS was updated, or the BIOS settings were reset. Second, enter the BIOS and check whether Above 4G Decoding is enabled, whether CSM is enabled, and what the Resizable BAR setting is, following the motherboard manual, since menu layouts differ between boards. Third, remove non-essential expansion cards or a second graphics card and see whether Code 12 disappears; if it does, the cause is resource contention. Fourth, load the BIOS default values and reconfigure the settings, to test whether a previous setting was the cause. Fifth, if this is a new card in an older machine, compare the motherboard BIOS generation, UEFI or CSM mode, PCIe generation, and Resizable BAR conditions, a direction that has its own dedicated discussion and is only diverted to here.

Do not present Code 12 as a failed card, and do not present a larger power supply as the remedy. The resource is address space, not wattage.

Code 31 — Windows Cannot Load the Drivers Required for This Device

Code 31 means the driver itself failed to load. The device is recognised and a driver has been assigned, but Windows cannot load the driver files. The starting point is different from Code 10: with Code 31 the driver loading stage itself has failed, while with Code 10 the driver loaded and the device then failed to start.

The possible layers are the driver files, the driver signing and compatibility layer, and the system files. Driver files may be damaged, incomplete, blocked by third-party software or security software, or left in a broken state by an interrupted installation. On the compatibility side, the driver may not match the Windows version, there may be a driver signing problem, or a Windows update may have replaced the driver with an incompatible version. On the system side, damaged system files can affect driver loading.

The diagnostic steps for Code 31 are: first, uninstall the device, including the option to delete the driver software, then scan for hardware changes and let Windows assign the driver again. Second, perform a clean driver reinstall in Safe Mode with DDU, using the complete installation package from the card maker, not a third-party driver tool. Third, check the compatibility between the Windows version and the driver version, and compare the timing against any Windows update. Fourth, a system file check with sfc is a system layer step, not a graphics card step, and should be described as such. Fifth, try another driver branch for testing purposes only, noting that switching between branches such as Game Ready and Studio is a test, not a casual change.

Code 31 and Code 10 are not the same problem. Code 31 is driver loading failure; Code 10 is device start failure. The steps differ because the starting points differ.

Code 45 — Currently, This Hardware Device Is Not Connected to the Computer

Code 45 means Windows believes the device is currently not connected. The device entry is still present, usually as a leftover entry, but the system cannot enumerate the device. This is a connection and enumeration problem, not a driver problem.

The common layers are the physical connection and leftover entries. The card may not be seated firmly, the slot contact may be poor, the power cables may not be fully inserted, or the motherboard BIOS may have disabled the slot. Separately, a device that has been removed or replaced can leave a leftover entry that was never cleared, and a device that enumerates intermittently can flip between working and Code 45.

The diagnostic steps for Code 45 are: first, check whether the device is genuinely in the machine: shut down, disconnect power, and check that the card is seated firmly, the power cables are fully inserted, and the slot is not loose. Second, enter the BIOS and check whether the BIOS recognises the graphics card. If the BIOS does not recognise it either, the problem sits in the hardware, slot, or power layer. If the BIOS recognises it but Windows reports Code 45, the problem sits in the enumeration or driver layer. Third, in Device Manager, show hidden devices and look for greyed-out leftover graphics card entries. Delete the leftover entries and then scan for hardware changes. Fourth, try a different slot, and if conditions allow, compare with another computer. Fifth, record whether the symptom is constant or intermittent. Intermittent Code 45, where the card is sometimes recognised and sometimes reports Code 45, points more towards contact, slot, or power layers than towards the driver layer.

Do not present uninstalling the device once as a repair for Code 45. Uninstalling only clears the leftover entry. If the root cause is slot contact, power, or a BIOS-disabled slot, uninstalling will not fix it.

Four Codes Compared

CodeStatus wordingFailing layerFirst step
Code 10This device cannot startDevice start, after driver loadRecord driver version, then clean reinstall
Code 12Cannot find enough free resourcesResource allocation, usually BAR address spaceCheck recent hardware or BIOS changes, then BIOS settings
Code 31Cannot load the drivers requiredDriver loading itselfUninstall with driver deletion, then clean reinstall
Code 45Hardware device is not connectedConnection and enumerationCheck seating and cables, then BIOS recognition

Use this table to confirm the code before acting. The first step differs for each code, which is why reading the code first matters more than any single repair step.

A Shared Diagnostic Flow for All Four Codes

Whatever the code, the same seven-step flow applies.

  1. Read the code first. Record the full error code and the complete device status wording. Do not report only that there is a yellow warning.
  2. Compare the timing. When did the symptom start, and what changed just before it: a driver update, a Windows update, a BIOS update, added hardware, moving the machine, or cleaning inside it. A symptom with no preceding change and a symptom after a change point in different directions.
  3. Check the Event Viewer around the time the device failed for driver or device errors and warnings.
  4. Look at the other devices. Is only the graphics card showing a yellow warning, or do other devices show one too? Several devices failing at once points at the system, motherboard, or BIOS layer. Only the graphics card failing points at the card, its driver, or its slot.
  5. Change only one variable at a time. After each step, read the error code again and record whether it changed. Do not reinstall the driver, change the slot, and alter the BIOS all at once.
  6. Check for hidden devices. In Device Manager, show hidden devices and look for greyed-out leftover graphics card entries, which can interfere with diagnosis.
  7. Before seeking inspection, gather the records: the error code, the driver version, the Windows version, the BIOS version, the steps already tried, and how the code changed after each step. An inspection decision needs these records.

Boundary Cases: When This Is Not One of the Four Codes

Code 43 has its own dedicated discussion, and this guide diverts to it with a single line rather than repeating it. If Device Manager shows no graphics card entry at all, with no error code, that is a different problem, a card that is not detected at all. Virtual machine passthrough producing Code 43 is its own topic. A new card in an older machine that is not recognised involves motherboard BIOS generation, UEFI or CSM mode, PCIe generation, power connectors, and Resizable BAR conditions, which have their own discussion. A card that is not recognised or performs worse after a BIOS update involves BIOS default resets, UEFI or CSM, Resizable BAR, Above 4G Decoding, and PCIe generation settings. A driver forcibly changed by Windows Update is its own topic. Driver installation failure, rollback, and clean installation have their own guide, and this article uses the DDU clean reinstall only as a test step. A machine that became worse after a driver or game update belongs to the update comparison and rollback topic. A driver crash and recovery event is a TDR topic. Modular power supply cable mixing and single-cable split power delivery are their own topics; the power checks for Code 10 and Code 45 here cover only whether the power cables are firmly inserted.

Common Misconceptions

A yellow warning does not mean the graphics card has failed. It only means the device is not working normally, and the cause can sit in the driver, resources, connection, or settings. The error code says which layer.

Not every yellow warning is a driver problem to be fixed by reinstalling the driver. Code 12 is a resource allocation problem that reinstalling the driver will not touch. Code 45 is a connection and enumeration problem that reinstalling the driver will not touch either.

Code 10 and Code 31 are not the same thing. Code 31 is driver loading failure; Code 10 is device start failure. Different starting points, different steps.

Code 12 does not mean the power supply is too weak. The resource in Code 12 is memory address space, BAR allocation, not power wattage.

Uninstalling the device once does not repair Code 45. Uninstalling only clears leftover entries. If the cause is slot contact, power, or a BIOS-disabled slot, uninstalling solves nothing.

Updating all drivers at once with a third-party driver tool is not a diagnostic step. Such tools can install the wrong version or an incompatible driver, making Code 31 and Code 10 harder to separate. Testing should use the complete installation package from the card maker, changing one variable at a time.

The error code is not unimportant, and reinstalling Windows is not a shortcut around it. Before any reinstall, the error code has already said which layer is at fault, and reinstalling Windows does not fix slot contact, BIOS resource allocation, or hardware initialisation problems.

A newer driver does not necessarily fix Code 31. Code 31 can be a mismatch between the driver and the Windows version, so the newest version is not automatically the right one. Compatibility must be compared, not assumed.

When to Stop and Seek Inspection

Stop and seek in-shop inspection when the error code does not change after the steps for that code, when the code changes but the device still does not work and the records do not explain why, or when the next step would involve swapping hardware that is not available. Bring the error code and its full status wording, the driver version, the Windows version, the BIOS version, and the list of steps tried with how the code changed after each one.

Inspection is available at the Shatin shop: Room 1209, Dali Plaza, Shek Mun. Telephone 2186 8010. WhatsApp 6558 6806. Published inspection and repair pricing on the site runs across three tiers from HK$400 to HK$2,800. There is no on-site service, so the machine is brought to the shop for inspection.

Frequently Asked Questions

The card has a yellow warning. Does that mean it has failed?

No. A yellow warning only means the device is not working normally. The cause can be the driver, resource allocation, connection, or settings. Read the error code in the device status first, because the code says which layer is failing, and different codes lead in different directions.

Is Code 10 the same as Code 31?

No. Code 31 means Windows cannot load the driver files at all. Code 10 means the driver loaded, or tried to load, and the device then failed to start. The starting points are different, so the diagnostic steps are different too.

Will a bigger power supply fix Code 12?

No. Code 12 is about resource allocation, most often memory address space for BAR allocation, not about power wattage. The relevant checks are Above 4G Decoding, CSM, Resizable BAR settings in the BIOS, following the motherboard manual, and whether other cards are competing for address space.

I uninstalled the device once and Code 45 came back. Why?

Because uninstalling only clears the leftover device entry. If the root cause is the card not being seated firmly, a loose slot contact, a power cable not fully inserted, or a BIOS-disabled slot, uninstalling does not touch the cause. Check the physical connection first, then check whether the BIOS recognises the card.

Should I use a third-party tool to update all my drivers at once?

No. Third-party tools can install a wrong or incompatible driver version, which makes Code 31 and Code 10 harder to separate. Use the complete installation package from the card maker, and change only one variable at a time, reading the error code again after each step.

What should I bring when I come in for inspection?

Bring the error code and its full status wording, the driver version, the Windows version, the BIOS version, and a list of the steps already tried with how the code changed after each one. The shop is at Room 1209, Dali Plaza, Shek Mun. Telephone 2186 8010. WhatsApp 6558 6806.

Related articles

Related services

If you need Chip-level GPU repair, see these service pages: