dxgi.dll is missing or crashes a game: what the file is and how to fix it
dxgi.dll is DirectX Graphics Infrastructure, the part of Windows that finds your graphics card and monitors and puts every finished frame of a Direct3D 10, 11 or 12 game on the screen. Windows ships it, so there is nothing to install. When a game crashes in it or says it is missing, the cause is usually a graphics mod's copy in the game folder, the graphics driver, or a damaged Windows file.
Prefer to fix it yourself? The manual steps follow.
How to fix dxgi.dll errors
First look in the folder of the game that fails, next to its .exe file. A dxgi.dll there is not Windows' copy: it belongs to a shader or post-processing injector, a graphics mod, an upscaler or frame rate tool, and the game loads it instead of the genuine file in System32. Rename it to dxgi.dll.bak and start the game. If the game now starts, update or remove that mod. If there is no copy in the game folder, install the newest graphics driver from your card's maker, close overlays, and read the crash event in Event Viewer. When several games fail, repair Windows: install the pending updates, then run sfc /scannow and DISM from an administrator Command Prompt.
The DirectX End-User Runtime is not the fix for this file. That package installs old DirectX SDK libraries such as the D3DX9 files and xinput1_3.dll, which Windows does not include. dxgi.dll is already part of Windows 10 and Windows 11 and is repaired and updated only by Windows itself.

Step by step
- Look in the game folder. Right-click the game's shortcut and choose Open file location, or in a game launcher use the option to browse local files. If you see dxgi.dll next to the .exe, often together with an .ini file, a folder of shaders or presets, or other DLLs such as d3d11.dll, a graphics mod or tool put it there. Games do not ship their own copy of this Windows file.
- Rename that copy and test. Rename it to dxgi.dll.bak rather than deleting it, so you can put it back. Start the game. If it runs, the mod's copy was the cause. A game update very often breaks these tools until their authors release a new version, and two tools that both want to be dxgi.dll cannot work together. Update the mod, install only one such tool, or leave it disabled.
- Verifying the game files will not remove it. The verify or repair option of a game launcher checks the files the game shipped and puts back what is damaged. It usually leaves extra files alone, so a mod's dxgi.dll stays in place after a verify. Remove or rename it yourself.
- Install the newest graphics driver. Download the driver for your card from the website of its maker, or from the maker of your laptop, and install it. If the crashes started right after a driver update, install the previous version instead. dxgi.dll hands every frame to the graphics driver, so a driver fault is the most common reason the file appears in a crash report. On a laptop with two graphics chips, also check in Settings, System, Display, Graphics that the game uses the one you expect.
- Close overlays and undo overclocking. In-game overlays, FPS counters, recording and streaming tools, and RGB or fan utilities hook into the same presentation step that dxgi.dll handles. Turn them off one at a time and test. If you overclocked the graphics card with a tuning tool, return it to the default clocks: an unstable card often shows up as crashes in dxgi.dll or as a device removed error.
- Read the crash event. Press Windows+R, type eventvwr.msc and press Enter. Open Windows Logs, Application, and look for an Error from the source Application Error at the time of the crash. Faulting application name tells you which program crashed; Faulting module path tells you which dxgi.dll was involved. A game folder path means a mod's copy; C:\Windows\System32 or SysWOW64 means Windows' copy, which points to the driver, overlays or the card.
- Install Windows updates and restart. Open Settings, Windows Update, install everything that is offered and restart, even if Windows does not ask. Updates replace system files, dxgi.dll included, with the current build for your Windows release, and they also bring graphics fixes that newer games expect.
- Run System File Checker. Type cmd in the Start menu, right-click Command Prompt and choose Run as administrator. Run sfc /scannow and wait until it reaches 100%. It compares protected Windows files with the stored originals and repairs a damaged or replaced dxgi.dll in System32 or SysWOW64. Restart afterwards.
- If System File Checker cannot repair everything, run DISM. In the same administrator window run DISM /Online /Cleanup-Image /RestoreHealth. It repairs the store that System File Checker copies its originals from, using Windows Update. When it finishes, run sfc /scannow once more, then restart.
- Still failing: repair Windows in place. On Windows 11, Settings, System, Recovery offers Fix problems using Windows Update, which reinstalls the current version of Windows and keeps your files, apps and settings. On Windows 10 the same result comes from running Microsoft's installation media and choosing to keep personal files and apps.
Download the genuine dxgi.dll for your Windows version
Each file below is Microsoft's own dxgi.dll for one Windows release, fetched from Microsoft's own server and checked against Winbindex, the index of the files in Windows images and updates. Pick your Windows version (Settings, System, About shows it) and the build: 64-bit for System32, 32-bit for SysWOW64. The repair steps above are still the better fix, because Windows protects these folders and keeps its copy updated. Use a file here to compare it with a copy you have, or when System File Checker and DISM cannot repair the file.
Older Windows releases
A free uGetFix account is needed to download. Sign in, or create one in a minute, and you come straight back here.
What not to do
Do not install the DirectX End-User Runtime for this file.
Many guides suggest it, and it does not help here. It adds legacy DirectX libraries that Windows lacks, and it does not contain or replace dxgi.dll. The error stays exactly as it was.
Do not download dxgi.dll from a DLL collection site.
You cannot tell which Windows release, build or architecture the file comes from, or whether it was changed. dxgi.dll is closely tied to the rest of the graphics stack of your Windows build, so a copy from another release can break every game and even the desktop. Use the genuine files above, and the checker below for a file you already have.
Do not copy a file into System32 or SysWOW64 by hand.
These copies are protected Windows files owned by the system, and the Desktop Window Manager that draws your desktop uses the 64-bit one all the time. A hand-placed file of the wrong build can leave you with a black screen after sign-in, and the next update or System File Checker run may replace it anyway. Repair with sfc /scannow instead.
Do not put a downloaded Windows copy into the game folder.
A game folder copy of dxgi.dll only makes sense for a graphics mod. A Windows copy there adds nothing, because Windows already loads the one in System32, and it stays behind when Windows updates its own.
Do not keep a flagged copy by turning off protection.
If Microsoft Defender quarantines a dxgi.dll from a game folder, find out where that mod came from before you restore it. Graphics injectors are sometimes flagged because of how they work, but the same name can be used by cheats and by malicious mod packages. The security page linked below explains how to tell them apart.
Check the copy on your PC
Choose the dxgi.dll you are unsure about, for example the one in a game folder. Its checksum is calculated in your browser and compared with 321 Microsoft builds of the file from Windows releases and updates.
The file stays on your computer. Nothing is uploaded: the checksum is computed locally.
11 genuine programs have been documented loading a planted copy of dxgi.dll. Found a dxgi.dll you did not expect, in a game folder you did not mod, in Downloads, Temp or AppData? The name is used by graphics mods, and it can be used by cheats and malware. That is a security question, not a missing-file one. Is the dxgi.dll you found genuine? On 2-Spyware
The error messages and what each one means
The wording tells you which problem you have. These are the texts Windows and games show, as written, with the file name filled in.

The code execution cannot proceed because dxgi.dll was not found. Reinstalling the program may fix this problem.
The wording of Windows 10 and Windows 11. Windows did not find a usable copy for that program. Because Windows ships the file, this points to a damaged or missing system file: install updates, then run sfc /scannow and DISM.
dxgi.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support.
A dxgi.dll was found but could not be loaded. Almost always this is a copy in the game folder: a graphics mod of the wrong build, a damaged download, or a file blocked by security software. Rename the game folder copy and test again.
The application was unable to start correctly (0xc000007b). Click OK to close the application.
This one does not name a file, but after installing a graphics mod it often means a 32-bit dxgi.dll in a 64-bit game folder, or the other way round. Use the build of the mod that matches the game.
The procedure entry point CreateDXGIFactory2 could not be located in the dynamic link library dxgi.dll.
The game asked for a DXGI function that your Windows does not have. Microsoft added CreateDXGIFactory2 in Windows 8.1, so on Windows 7 or 8 a game that needs it cannot run. On Windows 10 or 11 the same message points to an outdated mod copy in the game folder: rename it.
Faulting module name: dxgi.dll
A line from the Application log in Event Viewer after a crash. Look at the Faulting module path line of the same event. A game folder path means the crash happened inside a mod's copy: update or remove that mod. A System32 or SysWOW64 path means the driver, an overlay or the card: update the graphics driver, close overlays and return to default clocks.
DXGI_ERROR_DEVICE_REMOVED (0x887A0005) or DXGI_ERROR_DEVICE_HUNG (0x887A0006)
These are DXGI error codes, not a broken file. The graphics card stopped responding or the driver was reset while the game used it. The fix is the driver, a stable clock speed, enough power and cooling for the card, and the game's own updates. Replacing dxgi.dll does nothing for them.
File facts
dxgi.dll is DirectX Graphics Infrastructure. It sits between Direct3D and the graphics driver: it lists the graphics adapters and the monitors connected to them, creates the swap chain that holds the frames a game draws, presents each finished frame to the screen, and switches between windowed and full screen modes. Direct3D 10, 11 and 12 all go through it, and so does the Desktop Window Manager that draws the Windows desktop. When the card or the driver fails, dxgi.dll is where the game finds out, which is why it shows up in so many crash reports. What Windows reports for the genuine file:
- Description in the file
- DirectX Graphics Infrastructure
- Where the genuine dxgi.dll belongs
C:\Windows\System32C:\Windows\SysWOW64- Signed by
- Microsoft Windows, with a Windows catalog signature: the file's Properties show no Digital Signatures tab, which is normal. Check it in PowerShell: Get-AuthenticodeSignature <path to the file> (Status: Valid).
On 64-bit Windows, System32 holds the 64-bit file and SysWOW64 the 32-bit one; the folder names are historical. When a game starts, Windows looks for dxgi.dll in the game's own folder first, which is exactly what graphics injectors rely on: a file with this name next to the game's .exe is loaded instead of the Windows copy. The genuine file describes itself as DirectX Graphics Infrastructure (Properties, Details, File description) and is about 1 MB: in the Windows 11 24H2 and 25H2 builds the 64-bit file is 1,316,248 bytes and the 32-bit one 1,090,024 bytes, in Windows 10 22H2 the 64-bit file is 1,013,816 bytes. A mod's copy usually shows another description, another size, and no Microsoft signature.

dxgi.dll versions by Windows release
Every Windows release has its own build of dxgi.dll, updated together with Windows. Winbindex lists 300 distinct Microsoft builds; the table shows the newest one indexed for each release and the update that delivered it.
| Windows release | File version | Delivered by | Size, 64-bit |
|---|---|---|---|
| Windows 11 26H1 | 10.0.28000.2952 | KB5129194, September 14, 2026 | 1,307,256 bytes |
| Windows 11 25H2 | 10.0.26100.9711 | KB5127648, October 13, 2026 | 1,316,248 bytes |
| Windows 11 24H2 | 10.0.26100.9711 | KB5127648, October 13, 2026 | 1,316,248 bytes |
| Windows 11 23H2 | 10.0.22621.5415 | KB5099414, July 14, 2026 | 1,017,976 bytes |
| Windows 11 22H2 | 10.0.22621.5415 | KB5099414, July 14, 2026 | 1,017,976 bytes |
| Windows 11 21H2 | 10.0.22000.2600 | KB5044280, October 8, 2024 | 1,001,472 bytes |
| Windows 10 22H2 | 10.0.19041.7802 | KB5126657, October 13, 2026 | 1,013,816 bytes |
| Windows 10 21H2 | 10.0.19041.7802 | KB5126657, October 13, 2026 | 1,013,816 bytes |
| Windows 10 21H1 | 10.0.19041.7802 | KB5126657, October 13, 2026 | 1,013,816 bytes |
| Windows 10 20H2 | 10.0.19041.7802 | KB5126657, October 13, 2026 | 1,013,816 bytes |
| Windows 10 2004 | 10.0.19041.7802 | KB5126657, October 13, 2026 | 1,013,816 bytes |
| Windows 10 1909 | 10.0.18362.1500 | KB5013945, May 10, 2022 | 944,664 bytes |
Older copies of dxgi.dll found on PCs
Public DLL catalogues have collected 21 copies of dxgi.dll uploaded from PCs, from version 6.0.6000.16386 to 10.0.19041.1. Many come from older Windows releases. The table lists each with its checksums, so you can tell which one you have.
None of these replaces the file your Windows ships: the newest build indexed for Windows is 10.0.28000.2952, and each release keeps its own. If the check on this page finds your file in this list, it is most likely an older Microsoft build that was copied somewhere by hand. Confirm the Microsoft signature, remove the copy from the game folder, and let Windows use its own.
| Version | Build | Size | MD5 | SHA-1 |
|---|---|---|---|---|
10.0.19041.1 | 32-bit | 768 KB | 67149243068fa6efb9d58ced1506191b | 88ec05afe37c23507957606c51944cee381890a2 |
10.0.18362.815 | 64-bit | 922 KB | 3edd65ee32ec6f94955bf18417da1707 | 917fa75bdf531e29b584048cb2604d26a05aa4ad |
10.0.18362.815 | 32-bit | 758 KB | 86490b5a47341321c509a3a67aafe943 | c8300e1b3f1f3d1aed63c64ebf1c52150338eda1 |
10.0.18362.693 | 64-bit | 922 KB | ae299b218772ce03dfa7449169b47149 | dea2b43d6b20ac68385c80e64ea5032f473977d3 |
10.0.18362.387 | 64-bit | 922 KB | b1492bdad8d4ce701d9198e66650ed14 | 3d00694cbe4c869a945fa973856360491a1dfa11 |
10.0.18362.387 | 32-bit | 758 KB | 9eae88c4b54150bd14bfd14d68c2ede2 | 106a8d41535ab854f433c409a881a2cbe6156c3c |
10.0.18362.145 | 64-bit | 922 KB | 5a628b2c17c07b491dade464b2ce7cd6 | 63f78a1af9a3ba5e20e7a8edc7e3033662323209 |
10.0.18362.145 | 32-bit | 758 KB | 24f281c2b812a4c8b6c3f84a1ee178ba | 924c3a310bb6b2c80f01a66177a3fc77b12d60db |
10.0.16299.98 | 64-bit | 686 KB | 46d2f0e302bd88193d3fedf1fe9ef250 | 5a07a3df066c2595509f430c3872e9cf4592619b |
10.0.14393.0 | 64-bit | 625 KB | ee4503cc4c5f08ea029734d05e368950 | 4d964dab63e1b06c90befb8c135b42d4edabe5cb |
10.0.14393.0 | 32-bit | 512 KB | 7560db98b66fccd79b13e284b2f9ea3c | 0596f828654e7f09e6cecdcfec0d331bb8c39839 |
10.0.10586.494 | 64-bit | 635 KB | bd7e2f50a8c984500358e1ae1d1b89fc | f9440afd592a740bc0320f2e456bbc04047653b2 |
10.0.10586.494 | 32-bit | 512 KB | 7cda291cf22b91ddbb88b5089ebe25ce | 3f81c6bd5d06a1ab5439f2cc26c80954516fc245 |
6.3.9600.17041 | 32-bit | 399 KB | 15fbe33156a5f17280c549dba993442c | 306e47789e5f04d07ee871e0af08e2c5ed85dc3e |
6.2.9200.16492 | 32-bit | 287 KB | d4f264fe23f8953d840904418220c15e | b8a977a885cd6877420accb16047a8e8e3324ba8 |
6.2.9200.16420 | 64-bit | 451 KB | 02df949c584b02fab05868502c578d42 | cb57b7f2395621834bf883fd2944c265c3604064 |
6.2.9200.16420 | 32-bit | 358 KB | 4d77a4ecfafcce6cee0f8fee88e637a8 | 5c2c6c200398dcc3caeb5bcaec112ab164b9f4cd |
6.1.7600.16385 | 32-bit | 492 KB | dd76301614636306414efa94a9ac5a03 | e3534963909dd833572e80566c83b930bdc71a19 |
6.0.6001.18000 | 64-bit | 236 KB | 25b748a17d0b748cc709e716762d647f | 69230e6fa04ec06dac93c0f211331d55710b31f5 |
6.0.6001.18000 | 32-bit | 164 KB | ba29e0f81a45a6dc0f0fdd1f11a7cb9c | 73552cfe257f6ca6697f84f3116be86670131943 |
6.0.6000.16386 | 32-bit | 164 KB | 8a4d582902926dc8fed5435f560d8c4f | 8a4c0121710eb30c206bce108b831f842f5f125c |
Copies uploaded by users to a public DLL catalogue, read on 17 October 2026. We list their checksums so you can identify a file; we do not offer them for download and we did not verify each one against Microsoft's signature.
Questions people ask
Is dxgi.dll a virus?
The copies in System32 and SysWOW64 are genuine Windows files and are harmless. A dxgi.dll in a game folder is not Windows' copy: most often it is a graphics mod, but other tools can use the same name because games load it automatically. Check the file with the tool on this page and read the security page linked above.
Do I need to install DirectX to get dxgi.dll?
No. dxgi.dll is part of Windows 10 and Windows 11 and cannot be installed separately. The DirectX End-User Runtime adds other, older libraries and does not touch this file. If Windows' own copy is damaged, System File Checker, DISM and Windows Update repair it.
Why does a game crash at start after an update when it ran fine before?
If you use a graphics mod, the usual reason is its dxgi.dll in the game folder. A game update changes the code the mod hooks into, and it crashes until its author releases an update. Rename dxgi.dll in the game folder to test. Without mods, a new graphics driver or a new overlay is the next thing to check.
Can I delete dxgi.dll?
Not the copies in System32 or SysWOW64: every Direct3D 10, 11 and 12 game and the Windows desktop itself need them, and Windows treats them as protected system files. A dxgi.dll in a game folder can be removed or renamed safely as far as Windows is concerned; only the mod that relies on it stops working.
Will System File Checker remove a mod's dxgi.dll?
No. System File Checker repairs protected Windows files in the Windows folders. It does not look inside game folders, so a mod's dxgi.dll there stays until you remove it.
Can I run a game that needs CreateDXGIFactory2 on Windows 7?
No. That function exists from Windows 8.1 on, and copying a newer dxgi.dll into Windows 7 does not add it: the file depends on the rest of the newer graphics stack and breaks the system instead. Such a game needs Windows 10 or 11.
Is DXGI_ERROR_DEVICE_REMOVED a problem with dxgi.dll?
No. It is an error that DXGI reports when the graphics card was reset or stopped responding while the game used it. Look at the driver, the card's clock speeds, its power and temperature, and the game's own updates. The file only passes the news on.
Related guides
dxgi.dll is missing or crashes a game: what the file is and how to fix it
FixHow to fix ELEX II crashing on startup in Windows 11 and 10
FixHow to fix "could not allocate sufficient memory" DirectX error in Windows?
FixHow to fix "UE4 Game has crashed and will close" error in Windows?
Sources
- Winbindex, the Windows binaries index (m417z)
- Microsoft Learn: Use the System File Checker tool to repair missing or corrupted system files
- HijackLibs: dxgi.dll
File data read on October 17, 2026.
The editors who write and check uGetFix guides and reference pages. File facts are read from Microsoft's own installers and documentation, and every page shows the date its data was read.
Questions and experiences
Ask about this page: members and our editors answer. Reading is open; writing needs a free account.
…