GPU Code 19 or Code 39 in Device Manager? Registry Damage vs Corrupted Driver — Diagnosis & Reinstall Guide

Key Takeaways
Code 19 means Windows cannot start your graphics card because its registry configuration is incomplete or damaged. Code 39 means Windows cannot load the device driver because the driver file is corrupted or missing. Both start with uninstalling the device and scanning for hardware changes, then split: Code 19 follows a settings-recovery route, Code 39 follows a clean driver-reinstall route.
Code 19 and Code 39 Are Not the Same Problem
Device Manager can show either of these two codes on a graphics card, and they look alike at first glance: a yellow exclamation mark, a card that does not work, and a status message about something being wrong. They are not the same problem. One sits in the configuration layer, the other in the driver-file layer, and the fix that works for one does not necessarily work for the other.
| Code 19 | Code 39 | |
|---|---|---|
| Problem layer | Configuration layer: the device node's configuration information, held in the registry service key, is incomplete or damaged, so Windows cannot get the device started before the driver is even loaded. | Driver-file layer: the configuration is fine, but the driver file itself cannot be loaded because it is corrupted, missing, or cannot be read. |
| What Windows fails to do | It fails to start the device. | It fails to load the device driver. |
| Typical triggers | An incomplete driver uninstall, an interrupted installation, a registry cleaning tool removing a service key by mistake, or settings left inconsistent after a system restore or update. These are possible mechanisms, not a conclusion about any individual machine. | A corrupted driver file, an interrupted installation leaving mixed-version files behind, a disk or file-system problem, or a driver that references an entry point in another binary file that could not be loaded. These are possible mechanisms, not a conclusion about any individual machine. |
| First fix | Uninstall the device, then scan for hardware changes. If the code persists, follow the settings-recovery route. | Uninstall the driver, then scan for hardware changes to reinstall it. If the code persists, follow the clean-reinstall route. |
Both codes share the same first step, which is why they are so often confused. The split comes afterwards: Code 19 is followed down a settings-recovery path, and Code 39 down a driver-file replacement path. Running the wrong second step wastes time and can make the picture harder to read.
What the Messages Actually Say
The first diagnostic step for either code is to copy the full status text from the General tab of the device properties. The two messages are different, and the wording is the reliable way to tell them apart.
Code 19 reads: "Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)" Microsoft lists the causes as follows: "This error can result if more than one service is defined for a device, there is a failure opening the service key, or the driver name cannot be obtained from the service key." Its recommended fix is to uninstall and reinstall the device, and to restore the most recent working registry configuration, using a System Restore point if one has been created.
Code 39 reads: "Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)" Microsoft lists the causes as follows: "Reasons for this error include a driver that is not present; a binary file that is corrupted; a file I/O problem, or a driver that references an entry point in another binary file that could not be loaded." Its recommended fix is to uninstall the driver and then scan for hardware changes to reinstall or upgrade it.
Note the verbs: Code 19 is about starting, Code 39 is about loading. That single-word difference maps directly onto the two layers described above.
Step by Step Diagnosis
Work through the steps in order and re-read the device status after each one. Record the code shown after every step, including when it changes, because a code change is itself diagnostic information.
1. Read the code and the context
Copy the full status text, not just the code number. Note the driver version and date, and the Windows version. A code without its context is much less useful, because the same code can arise from different histories.
2. Ask when it started
When did the code first appear, and what happened just before it? An interrupted driver update, an interrupted uninstall, a Windows Update, a cleaning tool, or a disk error all point towards Code 19 or Code 39. If there is no interruption history at all, other codes should be ruled out first before assuming one of these two.
3. The shared first step: uninstall, then scan
In Device Manager, right-click the graphics card and choose Uninstall device, ticking the option to also remove the driver software for the device so Windows clears the driver files as well as the settings. Then open the Action menu and choose Scan for hardware changes, and let Windows detect the card and assign a driver again. Restart the computer and read the code again.
Uninstalling once is not the same as repairing. The uninstall only clears the old settings and files; if the scan and reinstall that follow are skipped, the problem does not go away. The two halves of this step belong together.
4. If Code 39 persists: clean driver reinstall
If Code 39 is still shown after the shared first step, the driver files need a clean replacement rather than another ordinary reinstall. Run a clean reinstall in Safe Mode using a display driver uninstaller tool, then install the full installation package from the graphics card manufacturer's official website, and read the code again. Chasing the newest driver version is not the point here: Code 39 can be caused by file corruption rather than by an old version, so the priority is a clean install, not the latest number.
5. If Code 19 persists: restore the settings
If Code 19 is still shown after the shared first step, the settings layer needs recovery. Check whether a System Restore point was created before the problem appeared. Only if such a point exists can the system be restored to it, and the restore will also affect programs and drivers installed after that point, so that consequence should be understood before proceeding. If no restore point exists, that must be accepted as a fact: a restore cannot be assumed into existence.
Microsoft's documentation still mentions an older option, Last Known Good Configuration, as part of the Code 19 fix. That option no longer exists as a boot choice on Windows 10 and Windows 11, so it should not be looked for or followed on a modern machine. The modern equivalent is the System Restore point described above.
6. A system-level check both codes share
Run `sfc /scannow` from an elevated Command Prompt to check protected system files. This is a system-level step, not a graphics-card step: it checks the integrity of Windows system files, which can be relevant when a driver file or a configuration file cannot be loaded or read. It does not diagnose the graphics card itself, and a clean result does not prove the card is healthy.
7. Watch for the code changing
Re-read the code after every step. If Code 19 becomes Code 39, or Code 39 becomes Code 19, the previous layer has been cleared and the next layer has surfaced. Record the change and the step that produced it, then follow the route for the new code. A code change is progress in diagnosis, not a failure of the step just taken.
8. Cross-testing, where a second machine is available
If a second computer is available, the same card or the same driver package can be tried there to see whether the problem follows the machine or follows the card and driver package. If no second machine is available, that limitation should be stated plainly rather than guessed around.
9. When to stop trying software fixes
If every step above has been tried and the code remains, or if the code appears together with screen artefacts, no display output, or a burning smell, the problem has moved beyond software into board-level inspection range. Further repeated reinstalls at that point add nothing and should not be attempted.
How Code 19 and Code 39 Differ from Neighbouring Codes
| Code | Meaning in brief | How it differs from Code 19 and Code 39 |
|---|---|---|
| Code 31 | Windows could not load the driver the device needs. The causes are broad: file damage, incompatibility, and signature problems are all possible. | Code 31 is a general load-failure code; Code 39 narrows the fault to a corrupted or missing driver file. The status text is the only reliable way to tell them apart. |
| Code 10 | The driver loaded, but the device failed to start. | Code 10 fails after loading; Code 19 and Code 39 fail before loading or starting has completed. |
| Code 43 | The device reported a problem while running, and Windows stopped it. | Code 43 is an operation-layer fault; Code 19 and Code 39 are load and start-layer faults. |
| Code 52 | Driver signature verification failed, so Windows refused to load the driver. | Code 52 is a signature-layer fault; Code 39 is a file-damage fault. A driver with a valid signature but a damaged file produces Code 39, not Code 52. |
| Code 28 | The device driver is not installed. | Code 28 means not installed; Code 39 means installed but unable to load. A Code 28 device often appears as Microsoft Basic Display Adapter. |
| Code 22 | The device is disabled. | Code 22 is a state layer, a device switched off; Code 19 and Code 39 are damage layers. |
| Code 40 | Service key information is missing or recorded incorrectly. | Code 40 belongs to the same registry service-key family as Code 19, but its status text is different. A machine showing Code 40 is not showing Code 19, and the steps in this guide should not be applied to it as if it were. |
Boundaries You Should Not Cross
The registry is part of the explanation for Code 19, but it must never become a set of operating instructions. Microsoft's fix for Code 19 is uninstall and reinstall, plus a System Restore point. It contains no step that asks a reader to edit the registry by hand, delete any registry key, or follow any registry path. No such instruction appears in this guide, and none should be followed from elsewhere either: hand-editing the registry can damage the system configuration further, and it is not the documented fix for a graphics card.
The same caution applies to registry fixes found online for optical drives. Those fixes were written for CD and DVD drives, not for graphics cards, and they do not transfer to a graphics card showing Code 19 or Code 39. A fix that belongs to one device class should not be applied to another simply because the code number looks familiar.
System Restore deserves a clear statement of its limits. It only works if a restore point was created before the problem appeared, and it affects programs and drivers installed after that point. It should not be presented as a step that is always available.
Disk and file-system trouble is listed by Microsoft as one possible cause of Code 39, because a driver file that cannot be read cannot be loaded. Even so, a disk check is only a system-level direction of suspicion. It is not a diagnosis of the graphics card, and disk tools should not be used as graphics-card diagnostics.
Reinstalling Windows should not be promised as a certain cure either. A reinstall resets driver and system-file layers, but it does not necessarily clear the configuration damage behind a Code 19, and it is a large step to take for a problem whose layer has already been identified.
Code 19 is not a sign of malware, and Code 39 is not a sign of a dead card. Microsoft's listed causes for Code 19 are service definitions, service keys, and driver names, all configuration-layer matters. Code 39's causes are file-level matters. Neither code is a diagnosis of infection or of hardware death.
Common Misconceptions
| Misconception | What is actually true |
|---|---|
| "Code 19 and Code 39 are the same problem." | Wrong. Code 19 is a registry configuration layer fault, where the device cannot start; Code 39 is a driver-file layer fault, where the driver cannot load. Their second steps split in different directions. |
| "Code 39 means the card is dead." | Wrong. Code 39 only says the driver could not be loaded, and the cause is usually a corrupted or missing file. Hardware suspicion comes last, not first. |
| "Any registry fix found online will work." | Wrong. Registry fixes written for optical drives do not apply to graphics cards. Microsoft's fix for a graphics card is uninstall and reinstall, plus System Restore. |
| "Uninstalling once is the same as repairing." | Wrong. Uninstalling only clears the old settings and files. Without the scan for hardware changes and the reinstall that follow, the problem stays. |
| "The newest driver will always fix Code 39." | Wrong. Code 39 can be file corruption rather than a version problem. A clean reinstall comes first; chasing the newest version does not. |
| "Code 19 means the machine has a virus." | Wrong. Microsoft's listed causes are repeated service definitions, a service key that cannot be opened, and a driver name that cannot be obtained, all configuration-layer problems, not a malware diagnosis. |
Before Bringing the Card In: A Short Checklist
If the steps above do not clear the code, gather the following before seeking a hands-on inspection:
- The exact status text from the General tab, and whether it is Code 19 or Code 39.
- The installed driver version and date, and the Windows version.
- When the code first appeared, and what happened just before it, such as an interrupted update, an interrupted uninstall, a Windows Update, a cleaning tool, or a disk error.
- Which steps have already been tried, and what code was shown after each step.
- Whether a System Restore point exists from before the problem appeared.
- Whether the problem is accompanied by screen artefacts, no display output, or a burning smell.
Repairs are charged on the site's published three tiers, from HK$400 to HK$2,800, with the final quote confirmed after inspection. The workshop is at Room 1209, Dali Plaza, Shek Mun. The phone number is 2186 8010, and WhatsApp is 6558 6806. There is no Mong Kok shop and no on-site service.
Frequently Asked Questions
What is the difference between Code 19 and Code 39?
Code 19 is a configuration-layer fault: Windows cannot start the device because its configuration information in the registry is incomplete or damaged. Code 39 is a driver-file layer fault: Windows cannot load the device driver because the driver file is corrupted or missing. The status text is the reliable way to tell them apart.
How do I fix Code 19 on a graphics card?
Uninstall the device in Device Manager, then choose Scan for hardware changes from the Action menu so Windows detects the card again. If Code 19 persists, restore the system to a System Restore point created before the problem appeared. Do not edit the registry by hand: Microsoft's documented fix contains no manual registry step.
How do I fix Code 39 on a graphics card?
Uninstall the device in Device Manager, ticking the option to also remove the driver software, then choose Scan for hardware changes. If Code 39 persists, run a clean reinstall in Safe Mode using a display driver uninstaller tool, then install the full package from the manufacturer's official website.
Can I use a registry fix I found online for Code 19 or Code 39?
Only if it is the documented fix for a graphics card, which is uninstall and reinstall plus System Restore. Registry fixes written for optical drives do not apply to graphics cards, and hand-editing the registry is not part of Microsoft's fix for either code.
Does Code 39 mean my graphics card is broken?
No. Code 39 says the driver could not be loaded, and the usual causes are a corrupted or missing driver file, an interrupted installation, or a file read problem. Hardware is suspected only after the clean-reinstall and system-level steps have been tried and the code remains.
Why does the code change after I uninstall and reinstall?
Because each step clears one layer and reveals the next. If Code 19 becomes Code 39, the configuration layer has been cleared and a driver-file problem has surfaced, and the fix route changes with it. Record the new code and follow the guidance for that code.