Last updated: July 8, 2026
A DirectX error does not always mean that DirectX itself is missing. Messages such as DirectX Runtime Error, d3dx9_43.dll was not found, XINPUT1_3.dll is missing, A D3D11-compatible GPU is required, and DXGI_ERROR_DEVICE_REMOVED point to different problems.
The correct fix depends on the exact error. Older DLL errors usually require Microsoft’s legacy DirectX runtime components. A D3D11 GPU message is normally related to graphics feature-level support or the wrong GPU being used. DXGI errors are more often caused by an unstable graphics driver, overclock, temperature, or power issue. Errors such as 0xc000007b may be related to Visual C++ or damaged game files instead.
- d3dx9_43.dll, d3dcompiler_43.dll, or XINPUT1_3.dll: install Microsoft’s legacy DirectX runtime.
- A D3D11-compatible GPU is required: check Direct3D feature levels, graphics drivers, and which GPU runs the game.
- DXGI_ERROR_DEVICE_REMOVED or DXGI_ERROR_DEVICE_HUNG: return the GPU to stock settings and check the driver, temperature, and power stability.
- 0xc000007b, VCRUNTIME, or MSVCP errors: repair the official Visual C++ x86 and x64 packages, then verify the game files.
A downloaded DLL may be unsafe, outdated, or built for the wrong architecture. Use Microsoft’s official runtime installers or the installer included with the game.
- Identify the error first
- Check DirectX and feature levels with DxDiag
- Install Windows updates
- Fix missing legacy DirectX DLL files
- Fix the D3D11-compatible GPU error
- Fix DXGI device removed or hung errors
- Verify game files and repair Visual C++
- Run DISM and SFC
- Disable overlays and reset launch options
- Final checklist
- Frequently asked questions
Identify the DirectX Error Before Changing Anything
Write down the full error message before installing or removing software. The DLL name or DXGI code usually tells you which part of the system needs attention.
| Error message | Likely cause | First action |
|---|---|---|
| DirectX Runtime Error | Game files, driver, runtime, or graphics API conflict | Find the detailed message or code |
| d3dx9_43.dll was not found | Legacy D3DX component is missing | Install the official legacy DirectX runtime |
| d3dcompiler_43.dll is missing | Older shader compiler component is missing | Install the legacy runtime and verify game files |
| XINPUT1_3.dll is missing | Legacy XInput 1.3 component is missing | Install the official legacy DirectX runtime |
| A D3D11-compatible GPU is required | Unsupported feature level, wrong GPU, or missing driver | Check DxDiag and Windows graphics settings |
| DXGI_ERROR_DEVICE_REMOVED or HUNG | Driver reset, unstable GPU, heat, or power issue | Restore stock settings and test the driver |
| 0xc000007b | Runtime or 32-bit/64-bit file mismatch | Repair Visual C++ x86 and x64 packages |
| VCRUNTIME or MSVCP DLL missing | Visual C++ Redistributable is missing or damaged | Install or repair the official package |
If only one game fails, start with that game’s files, launch options, mods, and required runtimes. If the same error appears in several games, prioritize Windows, graphics drivers, and system-file checks.
1. Check DirectX Version and Feature Levels with DxDiag
- Press Windows key + R.
- Type
dxdiagand press Enter. - On the System tab, check the DirectX version.
- Open the Display or Render tab.
- Check the graphics-card name, driver date, and Feature Levels list.
- On a laptop, confirm that the dedicated NVIDIA or AMD GPU appears on a separate tab.
The DirectX version installed with Windows and the Direct3D feature levels supported by the graphics hardware are different. Compare the Feature Levels list with the game’s minimum GPU requirements.
2. Install Windows Updates and Restart the PC
On Windows 11, the core DirectX components are maintained through Windows Update. Do not use an unofficial “DirectX 12 download” website.
- Open Settings.
- Select Windows Update.
- Click Check for updates.
- Install available cumulative updates.
- Restart the computer, even if Windows does not immediately ask you to.
Microsoft ended free support for Windows 10 on October 14, 2025. A Windows 10 PC may continue to work, but moving to a supported Windows 11 system is the safer long-term option when the hardware is eligible.
For NVIDIA, AMD, or Intel graphics, compare the driver offered by the GPU manufacturer with the driver recommended by the laptop or PC manufacturer. If the error started immediately after a driver update, testing the previous stable version may be more useful than repeatedly reinstalling the newest one.
3. Fix d3dx9_43.dll, d3dcompiler_43.dll, and XINPUT1_3.dll Errors
Older games may require optional components from the legacy DirectX SDK, including D3DX9, D3DX10, D3DX11, XAudio 2.7, or XInput 1.3. These files are separate from the modern DirectX version built into Windows.
Use the official Microsoft legacy runtime
- Open Microsoft’s official DirectX End-User Runtime Web Installer.
- Download and run the installer.
- Allow it to add the optional legacy components.
- Restart the computer.
- Verify the game files before launching the game again.
It installs optional side-by-side components used by older games while leaving the core DirectX version in Windows unchanged.
4. Fix “A D3D11-Compatible GPU Is Required”
This message is usually not fixed by reinstalling DirectX. It means that the game cannot access the required Direct3D feature level through the current graphics hardware or driver.
Check the graphics driver
Open Device Manager or DxDiag. If Windows shows Microsoft Basic Display Adapter, install the correct driver from NVIDIA, AMD, Intel, or the PC manufacturer.
Force the game to use the high-performance GPU
- Open Settings > System > Display > Graphics.
- Add the game’s main executable file if it is not listed.
- Select the game and open Options.
- Choose High performance.
- Save the setting and restart the game.
Compare the required feature level
If the game requires a feature level that does not appear in DxDiag, changing launch options or copying DLL files will not add hardware support. You may need a supported GPU.
5. Fix DXGI_ERROR_DEVICE_REMOVED or DXGI_ERROR_DEVICE_HUNG
These errors can appear when Windows detects that the graphics driver or GPU has stopped responding correctly. Reinstalling the legacy DirectX runtime is usually not the first step.
- Return GPU overclocking and undervolting settings to their default values.
- Close MSI Afterburner, RivaTuner Statistics Server, ReShade, and graphics filters.
- Install a stable official graphics driver.
- If the error started after an update, test the previous stable driver.
- Verify the game files.
- Check GPU temperature while the game is running.
- Check GPU power connectors and the power-supply condition on a desktop PC.
- Test another graphics API only when the game developer officially supports that option.
Increasing the timeout can delay the error without fixing the driver, temperature, power, or hardware instability that caused it. Test the GPU at default settings first.
6. Verify the Game Files
Damaged executable files, shaders, or bundled runtime installers can cause DirectX-related startup errors. Steam can compare the installed files with the official game files and replace damaged or missing data.
After verification finishes, restart Steam and launch the game without mods or custom launch options.
7. Repair 0xc000007b, VCRUNTIME, and MSVCP Errors
The 0xc000007b error is not a single-purpose DirectX code. It can be caused by damaged runtime files or a mismatch between 32-bit and 64-bit components. Errors that name VCRUNTIME140.dll or MSVCP140.dll point more directly to Microsoft Visual C++.
- Write down the exact DLL name shown in the message.
- Open Microsoft’s official Visual C++ Redistributable download page.
- Install or repair both the current x64 and x86 v14 packages when appropriate.
- If an older game requires a previous runtime, follow the game developer’s documentation.
- Restart Windows and test the game again.
Many older games and launchers are 32-bit applications. They use the x86 Visual C++ runtime even when Windows itself is 64-bit.
8. Run DISM and SFC When Several Games Are Affected
Use Windows system repair when the error affects multiple games or other Windows components. Microsoft recommends running DISM before System File Checker so that SFC can use a repaired Windows image.
- Search for Command Prompt or Terminal.
- Choose Run as administrator.
- Run the DISM command below and wait for it to finish.
- Run the SFC command only after DISM completes.
- Restart the computer.
Do not paste both commands into one line. Allow DISM to finish before starting SFC, and do not force the computer to shut down while either scan is running.
9. Disable Overlays and Reset Launch Options
If the game files and Windows components are healthy, remove software that hooks into the game’s graphics output.
- Steam Overlay
- Discord Overlay
- NVIDIA App or AMD Software recording and filters
- Xbox Game Bar background recording
- MSI Afterburner and RivaTuner Statistics Server
- ReShade, graphics injectors, and unofficial mods
Clear Steam launch options
- Right-click the game and select Properties.
- Copy the current launch options to a text file as a backup.
- Remove options such as
-dx11,-dx12, or-d3d11. - Launch the game with its default settings.
- Restore only the options officially supported by the game developer, one at a time.
If the game produces sound but the window is black, test windowed mode, the selected monitor, resolution, refresh rate, and HDR. If the monitor loses signal or the entire PC restarts, prioritize GPU temperature, power, cables, and hardware stability.
Final DirectX Error Checklist
- Record the full error message and DLL name.
- Use DxDiag to check the DirectX version, GPU, driver, and feature levels.
- Install Windows updates and restart the PC.
- Use Microsoft’s legacy DirectX runtime only for older DLL errors.
- For a D3D11 GPU error, check feature-level support and the selected GPU.
- For DXGI errors, restore stock GPU settings and test driver stability.
- Verify the game files.
- Repair the official Visual C++ x86 and x64 packages when required.
- Run DISM, then SFC, if several games or Windows components are affected.
- Disable overlays, mods, injectors, and custom graphics launch options.
Do not treat every DirectX message as the same error. Missing legacy DLL files, unsupported D3D11 feature levels, DXGI driver crashes, and Visual C++ runtime failures require different fixes. Identifying the exact message first prevents unnecessary reinstalls and unsafe DLL downloads.
Frequently Asked Questions
Can I reinstall DirectX 12 on Windows 11?
DirectX is a Windows component and is maintained through Windows Update. The DirectX End-User Runtime adds optional legacy files for older games; it does not replace the core DirectX version.
Why does DxDiag show DirectX 12 when a game says that DX12 is unsupported?
The Windows DirectX version and the feature levels supported by the GPU are different. Check the Display tab in DxDiag and compare the Feature Levels list with the game’s requirements.
Should I download d3dx9_43.dll by itself?
No. Use Microsoft’s official DirectX End-User Runtime so that the required components are installed together from a trusted source.
Can reinstalling DirectX fix the D3D11-compatible GPU error?
Not when the GPU lacks the required feature level. Check the graphics driver, the active GPU, and the game’s minimum hardware requirements.
Is 0xc000007b always a DirectX error?
No. It may involve Visual C++, damaged game files, or a 32-bit and 64-bit component mismatch. Repair official runtimes and verify the game before replacing any DLL file.
What should I do if DXGI_ERROR_DEVICE_REMOVED keeps returning?
Restore the GPU to default settings, close overlays and monitoring tools, compare stable driver versions, and check temperature and power stability.
