Skip to content
TroubleGrid

DirectX 12 games fail at shader compilation on NVIDIA 621.14 (CreatePipelineState 0x8007000E)

Last verified November 2026Tested against NVIDIA GeForce Game Ready 621.14 WHQL (4 November 2026) - the version every report names, Driver build 32.0.16.2114, branch r621_02, NVIDIA Release 620 (R620) driver branch, NVIDIA GeForce 617.42 and 617.70 - the versions reporters rolled back to successfully, GeForce RTX 4070 Ti, RTX 4080, RTX 4090 and RTX 5080 named in reports, Both RTX 40 and RTX 50 series affected, Windows 11 26H2 (builds 26300 and 26300.9818) named in reports, Direct3D 12 only - Vulkan unaffected in the one game where it was tested, Path of Exile 2, Borderlands 4, World of Warcraft: Forever, S.T.A.L.K.E.R. 2Good evidence

Four unrelated DirectX 12 games - Path of Exile 2, Borderlands 4, World of Warcraft: Forever and S.T.A.L.K.E.R. 2 - fail at pipeline or shader compilation on GeForce 621.14. Two of the reports capture the same error, D3D12 CreatePipelineState returning E_OUTOFMEMORY (0x8007000E) while the card still has VRAM free; the other two fail at the same stage without an error code logged. NVIDIA's 621.14 release notes list no open issues at all, so there is no vendor fix to wait for. Rolling back to 617.42 or 617.70 resolved it for both reporters who tried it. Check first that your crash began at the driver update.

This page exists because the symptom looks different in every game — a fatal Unreal Engine error in one, a silent freeze in another, a client that goes "Not Responding" minutes into play in a third — while the underlying failure is the same one line in a log. No vendor documents it: NVIDIA's 621.14 notes say "N/A" under open issues, and none of the four games' developers has acknowledged it either. What follows is what the reports actually establish, and what they do not.

Symptoms

  • A DirectX 12 game exits to the Unreal Engine Crash Reporter during startup shader compilation
  • The crash log reads "LowLevelFatalError [File:.\Runtime/RHI/Private/PipelineStateCache.cpp] [Line: 621] Shader compilation failures are Fatal."
  • The game's own log shows "CreatePipelineState Failed (HR:0x8007000E)" or "Pipeline creation failed ... (error: 0x8007000e)"
  • The game reaches the shader compilation stage and freezes before the progress bar starts moving
  • The client goes "Not Responding" within 1 to 10 minutes of DirectX 12 play, with "Deadlock detected with timeout 15000ms" in the log
  • The game reports a GPU memory budget of 0 MB although the card has gigabytes of VRAM free
  • No TDR, nvlddmkm or bugcheck event is logged — only Application event 1002 in the Windows log
  • The same game runs normally if it offers a Vulkan renderer and you select it

Why this happens

The R620 driver reports no memory budget, so pipeline-state creation fails

The reports converge on one stage: the game asks Direct3D 12 to create a graphics pipeline state object, and that call fails. Two of the four capture the return value, E_OUTOFMEMORY (0x8007000E). Microsoft documents that value as meaning there is insufficient memory to create the pipeline state object, so the game is being told by the driver that memory ran out. The World of Warcraft: Forever report is the one that shows this is not true: at the moment of failure the game logs a GPU budget of 0 MB on a 16 GB RTX 5080 with roughly 243 MB tracked. A zero budget reported to the application explains why the card looks full when it is empty. What each game does next is what makes the symptom look unrelated - Unreal Engine treats a shader compilation failure as fatal and crashes to its reporter, Path of Exile 2 keeps retrying until its render graph deadlocks, and World of Warcraft: Forever loses its device context and tries to recover in a loop. The Borderlands 4 report points at the same component from the other direction: its minidump names NVIDIA's shader compiler, nvgpucomp64.dll, at version 621.14.

Confirm it is the driver and not the game's own shader bug · Switch the game to Vulkan, if it offers one · Clean install the 617-series driver you last had working

These games also have their own shader-compilation crashes, which look identical

Borderlands 4 and S.T.A.L.K.E.R. 2 both have long-standing shader-compilation crash reports that have nothing to do with this driver — they appear on AMD and Intel hardware, with different error signatures such as EXCEPTION_ACCESS_VIOLATION or shader-model mismatches. That matters because the fix is different: a driver rollback will not help a game-side problem. The reports here are distinguished by three things together — the failure started at the 621.14 update, the log carries 0x8007000E specifically, and going back to a 617-series driver stops it.

Confirm it is the driver and not the game's own shader bug

Fixes

Confirm it is the driver and not the game's own shader bug

about 10 min

A driver rollback is wasted effort if the crash predates the driver. Three checks separate the two, and all of them are read-only.

Applies to: GeForce RTX 40 and RTX 50 series on driver 621.14, DirectX 12 games

  1. Check which driver you are on. Open the NVIDIA App, or run this in PowerShell and look for version 32.0.16.2114, which is 621.14.
    Get-CimInstance Win32_VideoController | Select-Object Name, DriverVersion
  2. Establish when it started. This problem begins at the driver update: the game worked on the driver you had before, and the first failure came after installing 621.14 and letting the game rebuild shaders. If the game was already crashing on 617.x or earlier, this article is not your problem.
  3. Find the error code in the game's own log, not in Windows. Look for 0x8007000E or E_OUTOFMEMORY next to a pipeline-creation line. Path of Exile 2 records this in its Client.txt log; Unreal Engine titles such as Borderlands 4 show the fatal error in the Crash Reporter window and keep logs in the game's own Saved\Logs folder. Not every affected game logs a code - two of the four reports here had none, so treat a missing code as inconclusive rather than as a clean bill of health.
  4. Check the Windows System log for TDR or nvlddmkm entries. In these reports there are none — only Application event 1002, "stopped interacting with Windows". If you do have nvlddmkm or bugcheck 116 events, you are looking at a different fault.

Reported to work by 4 users; not confirmed by the vendor.

Source: NVIDIA GeForce Forums, NVIDIA GeForce Forums, Grinding Gear Games — Path of Exile forums, Microsoft

Switch the game to Vulkan, if it offers one

about 15 min

The failure is in the Direct3D 12 path. Where a game has a Vulkan renderer, selecting it sidesteps the driver code that fails, and it is a setting you can put straight back.

Applies to: Games that ship both a DirectX 12 and a Vulkan renderer, such as Path of Exile 2

  1. Look for a graphics API setting in the game's video options, usually "Renderer", "Graphics API" or "DirectX 12 / Vulkan". Some games only offer the choice in a launcher dialog before the game starts, or as a Steam launch option.
  2. Select Vulkan, apply, and restart the game. Expect a one-off shader rebuild on the new renderer, which can take several minutes before you can judge whether it worked.
  3. If the game has no Vulkan option, skip to the rollback below. Of the four titles reported here, only Path of Exile 2 was confirmed to offer the choice and to run cleanly on it. Do not force a renderer through a third-party wrapper to get around this.

Reported to work by one user; not confirmed by the vendor.

Source: NVIDIA GeForce Forums, Grinding Gear Games — Path of Exile forums

Clean install the 617-series driver you last had working

Check before applyingabout 40 min

This is the only step reported to resolve the failure outright, by both people who tried it — 617.42 for Borderlands 4 and 617.70 for Path of Exile 2. Note that a plain reinstall of 621.14 is not a substitute: it cleared the pipeline errors for one reporter and the hangs came back.

Applies to: GeForce RTX 40 and RTX 50 series on driver 621.14

Before you do this

Rolling a graphics driver back gives up every fix shipped since, and the 617 branch is not problem-free either - the same forum carries a separate report of intermittent black screens at boot on 617.x. Keep the 621.14 installer so you can go forward again, and do not roll back further than 617.x hoping for more: the display and wake regressions in this branch are reported to start at 621.01, not before.

First:

  • Download the 617-series installer before uninstalling the current driver, so you are not left without one
  • Know your exact GPU model and Windows version to pick the right package
  1. Download the driver before you remove anything, from NVIDIA's own driver page. Pick 617.42 or 617.70 for your card and Windows version, and save the installer locally.
  2. Note what you give up. 621.14 carries NVIDIA's fix for incorrect colours in Call of Duty: Modern Warfare 4 and for video playback freezing on RTX 50 Series cards, and 617.x has neither. If those affect you, this is a trade rather than a clean win.
  3. Uninstall the current driver cleanly. Either run the saved installer, choose Custom (Advanced) and tick "Perform a clean installation", or use Display Driver Uninstaller in Safe Mode if the plain route leaves the problem behind.
  4. Reboot, install the 617-series driver, and reboot again.
  5. Stop Windows Update from putting 621.14 back. In Settings > Windows Update > Advanced options > Optional updates, leave driver updates unselected; otherwise the next update can undo this.
  6. Launch the game and let it rebuild shaders once. Judge the result on the second launch, not the first.

Reported to work by 2 users; not confirmed by the vendor.

Source: NVIDIA GeForce Forums, Grinding Gear Games — Path of Exile forums

Known issues

  • NVIDIA has not acknowledged this. Section 3.2 of the 621.14 release notes, "Open Issues in Version 621.14 WHQL", lists only "N/A" — the driver ships with no documented open issues, so there is no bug number to track and no stated fix date.

    Affects NVIDIA GeForce Game Ready 621.14 WHQL (4 November 2026) · Status: open

  • What 621.14 does fix is unrelated to this: incorrect visual colours in Call of Duty: Modern Warfare 4 (bug 6972531), and video playback freezing or black-screening on RTX 50 Series and RTX Spark after 621.01 (bug 6979343). Neither touches pipeline-state creation.

    Affects NVIDIA GeForce Game Ready 621.14 WHQL (4 November 2026) · Status: fixed

  • None of the four games' developers has acknowledged it either. The Path of Exile 2 report had no reply from Grinding Gear Games as of 9 November 2026.

    Affects Path of Exile 2, Borderlands 4, World of Warcraft: Forever, S.T.A.L.K.E.R. 2 · Status: open

If none of this worked

Three things would mean this article is not your problem. First, if the game was crashing during shader compilation before you installed 621.14 — Borderlands 4 and S.T.A.L.K.E.R. 2 both have their own shader-compilation crashes, reported on AMD and Intel GPUs too, and a driver rollback will not touch those. Second, if your Windows System log carries nvlddmkm, VIDEO_TDR_FAILURE or bugcheck 116 events: that is a driver timeout or hardware fault, not this, and the same 621.14 forum thread has a separate cluster of those with high PCIe error counters. Third, if going back to a 617-series driver changes nothing, stop treating it as a driver problem and look at the game. Be aware too of how thin the evidence still is: four people, four games, one of them without an error code captured, and no vendor confirmation. If your log does not contain 0x8007000E next to a pipeline-creation line, you probably have something else.

Common questions

Isn't this the black-screen bug NVIDIA already fixed in 621.14?
No. NVIDIA's 621.14 notes list bug 6979343 — video playback freezing or black-screening on RTX 50 Series and RTX Spark after 621.01 — as fixed, and that is a video-playback problem in browsers and media apps. This is a Direct3D 12 pipeline-creation failure inside games, it is reported on 621.14 itself, and it appears nowhere in NVIDIA's notes.
Will clearing my shader cache fix it?
It did not in the one case where someone tried thoroughly. The Path of Exile 2 reporter deleted the NVIDIA DXCache — which had grown to 56 GB — plus the Windows D3DSCache and the game's own Pipelines and Shaders caches, and the failures continued. Cache clearing is the standard advice for shader crashes and it is harmless to try, but do not read it as the fix here.
I found advice to change MachineGuid in the registry to fix error 0x8007000E. Should I?
No. That suggestion circulates on game forums attached to this error code from older, unrelated cases, and nothing in these reports supports it. MachineGuid identifies your Windows installation to software that relies on it, editing it can break activation and licensing, and it does nothing about a driver returning a zero memory budget.
Does this affect AMD or Intel graphics cards?
No report here does. All four name NVIDIA cards on the R620 branch, and the fix is an NVIDIA driver rollback. The 0x8007000E code itself is generic — it appears in older AMD and Unreal Engine reports with entirely different causes — so the error string alone does not identify this problem. The driver version and the timing do.
Should I install the 621.12 hotfix instead of rolling back?
Nothing supports it. The 621.12 hotfix predates 621.14, sits in the same R620 branch, and targeted the RTX 50 video-playback bug. No report tested it against this failure, so rolling forward to it is a guess; the 617-series rollback is the step with evidence behind it.
How confident should I be in this?
Moderately, and the page is marked medium confidence for that reason. Four independent people, four unrelated games and two GPU generations failing at the same stage on the same driver is a real pattern rather than a one-off. But NVIDIA has confirmed nothing, only two of the four reports capture an error code, only two reporters tested the rollback, and the S.T.A.L.K.E.R. 2 report is a freeze with no code captured at all, so that one may yet turn out to be a different problem.

Did this fix work?

If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.

Report a problem with this page

Related problems

Sources

  • NVIDIA · Release notes · checked Nov 9, 2026

    • GeForce Game Ready 621.14 WHQL was published on 4 November 2026 as part of the Release 620 driver branch
    • Section 3.2 "Open Issues in Version 621.14 WHQL" lists only "N/A", so NVIDIA documents no known issue for DirectX 12 pipeline-state creation in this driver
    • 621.14 fixes "Call of Duty: Modern Warfare 4: Game may display incorrect visual colors [6972531]"
    • 621.14 fixes "an issue where video playback may freeze or black screen on some GeForce RTX 50 Series GPUs/RTX Spark after updating to GRD 621.01. [6979343]"
  • Microsoft · Documentation · checked Nov 9, 2026

    • "This method returns E_OUTOFMEMORY if there is insufficient memory to create the pipeline state object."
    • E_OUTOFMEMORY (0x8007000E) from CreateGraphicsPipelineState is the documented result of the driver reporting insufficient memory for the pipeline state object, not a game-side error code
  • NVIDIA GeForce Forums · Forum · checked Nov 9, 2026

    • Three separate users in this thread report DirectX 12 pipeline or shader compilation failures on 621.14, in Path of Exile 2, Borderlands 4 and S.T.A.L.K.E.R. 2
    • Borderlands 4 exits to the Unreal Engine Crash Reporter during startup shader compilation on 621.14 with "LowLevelFatalError [File:.\Runtime/RHI/Private/PipelineStateCache.cpp] [Line: 621] Shader compilation failures are Fatal.", and rolling back to 617.42 resolves it
    • A Borderlands 4 minidump taken on 2026-11-07 names nvgpucomp64.dll (NVIDIA GPU Compiler Driver 621.14) and nvwgf2umx.dll, both file version 32.0.16.2114
    • Path of Exile 2 logs dozens of D3D12 pipeline-creation failures with error 0x8007000e at the login screen on 621.14, runs without hangs under Vulkan on the same driver, and is fixed by a DDU clean install of 617.70
    • Deleting the NVIDIA DXCache (grown to 56 GB), the Windows D3DSCache and the game's own Pipelines and Shaders caches did not resolve the Path of Exile 2 failures on 621.14
    • S.T.A.L.K.E.R. 2 on 621.14 reaches the shader compilation stage and freezes without the compilation progress bar starting, after a clean install of the game
    • Several users in the thread report unrelated 621.14 regressions resolved by returning to 617.42, including multi-monitor DisplayPort wake failures and idle black screens
  • NVIDIA GeForce Forums · Forum · checked Nov 9, 2026

    • World of Warcraft: Forever fails graphics pipeline creation with "OutOfMemory: CreatePipelineState Failed (HR:0x8007000E)" on an RTX 5080 running 621.14 WHQL build 32.0.16.2114, branch r621_02
    • The game reports "GPU Budget: 0 MB" at the moment of failure while the card has 16 GB of VRAM and only about 243 MB tracked, so the failure is not ordinary physical VRAM exhaustion
    • D3D12 device creation and SM6 selection both succeed before pipeline creation fails, and the game reports no outdated GPU driver
    • The failure is followed by a ClusteredShading pipeline creation failure, device-context loss and repeated recovery attempts
  • Grinding Gear Games — Path of Exile forums · Forum · checked Nov 9, 2026

    • The Path of Exile 2 client freezes and shows "Not Responding" within 1 to 10 minutes of DirectX 12 play on 621.14 and logs "Deadlock detected with timeout 15000ms"
    • Windows records Application event 1002 for each hang, with no TDR, nvlddmkm or bugcheck events in the System log
    • Grinding Gear Games had not replied to the report as of 9 November 2026
    • The same reporter posted this problem to both the Path of Exile forums and the NVIDIA GeForce forums, so the two threads are one person's report