Why some games crash without warning when using DirectX 12

Having a game crash without warning when using DirectX 12 can be frustrating, especially when there are no error messages and everything seems fine at first glance. In many cases, the problem isn't with the game itself, but with a combination of Graphics drivers, system options, startup parameters, and background tasks that collide with DX12.

After reviewing various real-life experiences and technical recommendations, some patterns emerge that help us understand the origin of these shutdowns and, most importantly, how to prevent them. There is no single universal cause, but there are a number of key points: unstable drivers (especially on DX12), the Windows CFG function, simultaneous use of hardware encoding/decoding and, in specific cases, launch configurations or GPU support for DirectX feature levels.

Why DirectX 12 can cause crashes without a message

First of all, it's important to keep in mind that Windows 10 includes the DirectX 12 API, but that doesn't mean your graphics card implements all the feature levels needed for certain games. Diagnosis is done with dxdiag and the so-called “feature levels”: If your GPU doesn't expose 12_0 or 12_1, a game that strictly requires those capabilities may crash.

In addition to compatibility, DirectX 12 places significant demands on drivers. In real-world environments, crashes have been seen when DX12 gaming shares the GPU with video tasks, such as Record with OBS using H.265 hardware encoding or play YouTube (H.264/H.265 hardware decoding). This conflict can cause freezes of several seconds and then the game to close.

Another little-known factor is the Windows protection called Exploit Protection, specifically the option Control Flow Guard (CFG) applied by applicationThere are DX12 titles that, due to how they handle their code and calls, can crash with CFG and crash without a trace. Disabling it only for the game executable (not globally) has stopped crashes in some cases.

Finally, certain launch options such as -dx12 o -d3d12 Forced installations from Steam can cause the opposite error: messages like «Not running directx12» or startup crashes. There are also those who use the parameter -d3d11 as an emergency exit: it usually stabilizes the game, although with a loss of performance compared to DX12.

Signs and real cases that fit these failures

A recurring pattern on AMD cards is this: if you play in DX12 and the system is simultaneously using the GPU for video, the game can freeze and crash. In a reproducible test with a Radeon RX 6900 XT and drivers 23.10.2, recording with OBS in H.265 via hardware caused 5 second pauses and the game would close after a few minutes.

Interestingly, changing the recording to x264 (CPU) made the crashes disappear… until opening a YouTube video on a second monitor. That simple action triggered the H.264/H.265 hardware decoder And the symptoms returned: graphical glitches and erratic behavior, leading to a crash. When I closed the video, everything was back to normal.

Boot messages such as have also been seen "Not running directx12" in The First Descendant which indicate either an incorrect launch parameter setting or the system being unable to satisfy the DX12 path required by the game. In titles like inZOI, the text “DirectX 12 is not supported on your system” often indicates that the GPU is not providing the level of features the game requests in DX12.

Quick checks before diving into advanced solutions

First, confirm your GPU's actual compatibility with DX12. Press Windows + R, type dxdiag and, in the Display tab, look Feature levelsIf you see 12_0 or 12_1, your card supports DX12 at the API level. If the highest setting is 11_1, games requiring native DX12 may not launch or may crash.

Second, check the game's Launch Options in Steam. In Properties, uncheck the Launch box if you had -dx12 o -d3d12 forced. Sometimes, DX12 explicit forcing clashes with autodetect from the game or with the driver.

Third, run it without any overlay software or video-intensive tasks. Close OBS (or switch to x264), and avoid playing YouTube in the background while testing; keep in mind that Windows does not free VRAM may aggravate conflicts. With AMD cards, eliminate the burden of hardware encoding/decoding during DX12 gameplay is a critical test.

Finally, make sure you have Windows updated via Windows Update and check for the latest GPU drivers from the manufacturer. Sometimes the problem disappears after installing a newer and more stable driver for DX12.

Proven solutions that stop shutdowns in DX12

Disable CFG for the game only: On Windows, search for “Exploit Protection”, go to Program Settings, press “Add program to customize” and choose the exact path of the game executable (e.g., Discovery.exe if it is the title file). Within the program options, scroll down to “Control Flow Guard (CFG),” select “Override system configuration,” and set it to Disabled. Apply the changes.

This change has stopped crashes in specific DX12 titles. Don't disable CFG globally; the idea is to apply the exception only to that executable. If the developer or driver later resolves the issue, re-enable CFG for the game to maintain protection.

Update to a driver that fixes the bug: On AMD cards, it has been reported that the version 24.9.1 fixed the issues of crashes with DX12 observed in previous branches. Note that, for example, 24.6.1 had another issue: audio and video desync when recording gameplay, which made it difficult to recommend upgrading if you needed to capture.

If you have an NVIDIA driver, there are two main lines of drivers: Game Ready (for games) and Studio (for creation). Install them manually from the official website instead of relying on utilities like GeForce Experience. Test the appropriate controller type (Game Ready to play) and different versions can make a difference.

If you suspect hardware issues, install the GPU in another computer with different components or process a warranty claim. If a card with the same software configuration failure on several devices, it is advisable to rule out a physical defect.

If your GPU doesn't support DX12 at the feature level, force DX11: in the game's Properties in Steam, add -dx11 in Startup Options. The title will use DirectX 11 and, in most cases, it will stabilize. The downside is that performance may decrease or some effects may be missing, but at least you'll avoid the silent closing.

Install DirectX runtimes: Download the DirectX End-User Runtime Web Installer from Microsoft and run it. Although Windows 10 comes with DX12, some legacy DirectX components may be missing if you have not installed certain packages, and several games need them to run well.

Concrete steps for repeated cases with AMD and DX12

If you use OBS: Temporarily change the encoding method to x264 (CPU) and see if the freezes disappear. This isolates the role of hardware encoding in the problem. If you want to stick with hardware, try H.264 versus H.265 and see if the behavior changes.

If you usually watch videos while playing: turn off the browser hardware acceleration during your gaming session, or use another device to play content. This way, you can avoid the GPU having to decode H.264/H.265 while running a demanding DX12 title.

Keep in mind driver versions: with the combination i9‑9900K + Radeon RX 6900 XT + 23.10.2 Crashes occurred in DX12 if hardware encoding/decoding was enabled. Upgrade if possible. If not, minimize video tasks.

If the developer and GPU manufacturer release patches, please report them: sharing these findings helps speed up the fix. The more feedback comes to AMD/NVIDIA, they prioritize corrections in their DX12 drivers.

DirectX True Compatibility: What Feature Levels Mean

It's common to see in dxdiag that the computer reports "DirectX 12" and, at the same time, that the card shows "feature level 11_1". This is not a contradiction: Windows provides the DX12 API, but your GPU implements it. up to a certain level of functions. If a game requires strict 12_0/12_1 and your card doesn't support it, the title will fail, even if the system says “DirectX 12”.

That's why the best check isn't the "DirectX 12" label on your system, but what dxdiag shows under Feature Levels. If 12_0 or 12_1 is listed, good; if not, plans to use DX11 when the game allows it or consider a GPU compatible with the capabilities required by that DX12 title.

Good practices with drivers and system

Keep Windows up to date: Microsoft distributes improvements and compatibility patches through Windows Update that impact the graphics stack. Manually check for updates. pending updates affecting video drivers and components.

Update your GPU drivers from the manufacturer: NVIDIA, AMD, or Intel. Avoid older or generic versions. On OEM computers, visit the PC manufacturer's website (MSI, for example) to install them as well. the chipset and the VGA approved for your model, especially if the equipment is a brand name.

For NVIDIA, install the driver manually from the support website and try the appropriate version (Game Ready for games or Studio for creative software) if applicable. Some users improve stability by switching to a different driver branch, as Not all branches prioritize the same thing.

If all else fails, consider testing the graphics card on another PC or seeking warranty assistance. When the crashes persist despite proper drivers, reasonable tweaks, and cross-testing, The hardware failure hypothesis gains strength.

Common messages and how to interpret them

"Not running directx12" on startup: This usually indicates that the game was expecting DX12 and has detected either a conflicting startup parameter, or that the stack isn't responding as it should. The first step is clear startup options in Steam and let the game autodetect. If it persists, check dxdiag and drivers.

"DirectX 12 is not supported on your system" on inZOI: This almost always indicates that your GPU isn't exposing 12_0/12_1. In that case, there are two options: force DX11 with -dx11 If the game allows it, or update your hardware. This can be complemented by checking files on Steam and the latest drivers.

Crashes after a few minutes of gameplay (DX12): If you are recording with OBS in H.265 hardware or watching videos, suspect the hardware encoding/decoding concurrency on the same GPU. Switch to x264, close your browser, or update drivers to versions that mitigate the conflict (e.g., AMD 24.9.1).

A brief step-by-step guide to stabilizing DX12

1. Confirm compatibility: Open dxdiag and look at Feature Levels. If 12_0/12_1 appears, your GPU supports DX12 at the API level; if not, consider playing in DX11 whenever possible.
2. Check Steam startup options: delete -dx12 y -d3d12 if they were set. Leave the box empty and try. Sometimes the forced automatic detection worsens.
3. Update drivers: from NVIDIA/AMD/Intel, and on OEM computers also chipset/VGA from the manufacturer's website. With AMD, check for versions that fix crashes in DX12 (e.g. 24.9.1).
4. Avoid hardware video tasks: Temporarily use x264 in OBS and disable browser hardware acceleration. This reduces conflicts. GPU video + DX12 gaming.
5. Per-game CFG exception: Under Exploit Protection, add the game's EXE (e.g., Discovery.exe) and disable CFG only there. If it resolves the crash, keep the exception until the driver/game fixes it.
6. Install DirectX runtimes: Run the Microsoft web installer to cover legacy component dependencies that some titles require and avoid silent failures.
7. If it persists: Verify file integrity on Steam, run as administrator, and test the title on DX11 with -dx11 as a last resort for stability while waiting for patches. On many teams this eliminates the closure.

Specific notes for different scenarios

AMD and Recording/Streaming: If your stream relies on hardware HEVC, consider upgrading to hardware AVC or x264 depending on your CPU. avoid playing videos in parallel with DX12 if you notice artifacts, and monitor upcoming driver releases.

NVIDIA: Install drivers from the official website, not just through GeForce Experience. Try Game Ready if you primarily play games, and if you experience instability, compare with Studio. On specific models, Changing branches stabilizes certain titles.

OEMs and Laptops: In addition to the GPU driver, install the chipset and video drivers validated for your model from the computer manufacturer's website. The OEM often packages the driver. power settings, firmware and profiles that prevent closures under load.

The case of inZOI and conflicting configurations

To inZOIA good start is to remove any settings that force DX12 in Steam and let the game decide. Then, run dxdiag and verify that your GPU shows 12_0 or 12_1 in Feature Levels. If it doesn't appear, use -dx11 if the game supports it.

Accompany these tests with recent drivers from your manufacturer (NVIDIA/AMD/Intel), install the DirectX runtime from Microsoft and, if it continues to fail, check file integrity in Steam, run as administrator and close background software. This usually resolve the incompatibility message in teams that do comply.

What to do if the game shows “Not running directx12”

Leave Steam's startup options blank, delete -dx12/-d3d12, and try a clean boot. If the message persists, update drivers and confirm with dxdiag that your GPU exposes 12_0/12_1. Ultimately, if the title allows it, spear with -dx11 to play stable while a patch arrives.

When to use the -d3d11 parameter

If nothing else works in DX12, -d3d11 o -dx11 It's the emergency exit. It offers almost immediate stability at the expense of a few FPS or certain features. In games where DX12 is not working properly due to the driver, upgrade to DX11. prevents sudden shutdown and freezing until an official arrangement is made.

Maintenance checklist that helps prevent

• Keep Windows up to date and drivers up to date, especially for the GPU. Avoid versions with known issues if you rely on hardware recording, and when a fix is ​​available (such as AMD 24.9.1), updates.
• Don't mix demanding DX12 games with hardware-intensive video tasks on the same GPU. If you do, uses CPU to encode temporarily or disable browser acceleration.
• Avoid overlays, aggressive overclocking, and resident software that injects DLLs. These add-ons are sometimes interfere with the DX12 stack and shoot silent closures.
• Consider hardware cross-testing if instability persists. Test a GPU on another computer. clarifies whether the origin is physical or software.

With all this map, you now have a practical plan: confirm the feature level with dxdiag, clear startup parameters, update drivers from the manufacturer, eliminate hardware video loads while playing in DX12, consider CFG exceptions per application if a specific title crashes, and use DX11 as a lifeline if needed. Following these steps, Crashes without messages when using DirectX 12 usually disappear Or at least, they are limited to a specific problem while awaiting official correction. Now you know Why some games close without a message when using DirectX 12.