Windows 11 December 2025 Patch KB5072033 Improves AMD GPU Stability

Microsoft’s December cumulative has quietly absorbed an earlier preview patch that many gamers credit with stopping mid‑session AMD GPU crashes, but the fix is more nuanced than social posts suggest and still requires cautious rollout and testing before you declare victory.

Background / Overview​

Microsoft shipped the December 9, 2025 cumulative update — KB5072033 — as the monthly Patch Tuesday rollup for Windows 11, and it folds in code that first appeared in the December 1 preview update KB5070311. Microsoft’s support notes show KB5072033 advances 25H2 systems to Build 26200.7462 and 24H2 systems to Build 26100.7462, while the earlier preview package was published as OS builds 26200.7309 and 26100.7309. Those build numbers matter because they distinguish the optional preview that some enthusiasts installed immediately (KB5070311) from the mandatory cumulative that has now been widely distributed (KB5072033). The preview introduced multiple UI and stability tweaks — notably broader File Explorer dark‑mode coverage and a handful of graphics‑stack changes — while the December rollup consolidated those preview fixes and the latest servicing stack into the formal monthly LCU+SSU package.

---

What users reported: the crash symptoms and scope​

Starting in late October and continuing through November, a wave of high‑profile reports appeared across forums and social channels describing GPU timeouts, black screens, and driver removal messages while playing modern AAA titles. The most common error patterns included:

• “GPU hung,” “driver removed,” or DXGI_ERROR_DEVICE_REMOVED / DXGI_ERROR_DEVICE_HUNG messages during gameplay.
• Sudden black screens or frozen displays that required a hard reboot.
• Device Manager showing the GPU as disabled after recovery attempts.
• Problems occurring with Adrenalin Edition driver builds around 25.10.x / 25.11.1, with users calling out high‑end RDNA‑4 cards such as the Radeon RX 9070 XT and other recent RX 9000/9060 series cards.

Community reports highlighted titles where crashes were common — Battlefield 6, Call of Duty: Black Ops 7, ARC Raiders and other modern engines that heavily exercise GPU scheduling and driver features — and many users believed the root cause was a bad AMD driver release. But subsequent testing and the rollout of Microsoft’s preview patch suggested the underlying issue had a significant OS‑side compatibility/detection element.

---

What Microsoft actually changed (and why that matters)​

Microsoft’s public KB notes for the December updates are deliberately conservative: the company explicitly documents a fix for an issue where a supported GPU could be incorrectly flagged as “unsupported”, plus a range of display/enumeration and explorer UI fixes. That phrasing points to changes in the graphics detection/compatibility stack rather than a direct rewrite of third‑party driver internals. Why that’s important:

• If a driver or the OS misidentifies a GPU or its capabilities, games and drivers may take alternative codepaths, enable/disable features, or trigger compatibility layers that change timing and resource usage.
• Many of the reported crashes (DXGI timeouts, device removal) are driven by complex interactions between the Windows Display Driver Model (WDDM), graphics drivers (AMD’s amdkmdag/amdkmdap family), and game engines’ rendering loops. A subtle change in how the OS enumerates or reports GPU features to userland can eliminate a race condition or remove a conflicting compatibility switch — and that can reduce crashes without AMD having to ship a new driver.

In short: the OS fix appears to remove the false “unsupported” gating or to adjust the detection logic, which in some configurations prevented problematic combinations of driver behavior and game engine code from occurring. That’s a narrower, but still meaningful, remediation compared with a blanket “driver crash fixed” statement.

---

Cross‑evidence from vendors and the community​

Two threads of evidence matter when you evaluate the practical effect of the December rollup:

• Vendor documentation: AMD’s official Adrenalin Edition 25.11.1 release notes (the driver build many users were running when crashes spiked) list game support and several fixed/known issues, but they do not mention that Microsoft’s KB5070311/KB5072033 resolves driver crashes. That absence is notable because vendors typically document OS‑level interactions only when the fix requires changes on the driver side or when the vendor cooperates on a joint advisory.
• Community testing: multiple forum threads and user reports indicate that installing KB5070311 (or the full December cumulative) eliminated crashes for many affected users, especially on certain RX 9000 series cards. However, results were mixed — some users reported complete stability, others still experienced timeouts or had to fall back to older driver builds (for example 25.9.1) or perform clean driver installs via DDU. That heterogeneity suggests the mitigation is hardware‑ and configuration‑dependent.

WindowsForum’s internal coverage and aggregated pilot reports likewise flag the same pattern: promising, real‑world stability improvements for a subset of AMD rigs, but no universal guarantee and a few reported regressions tied to the preview build’s dark‑mode changes.

---

Why results vary: the technical anatomy of these crashes​

Understanding why the patch helps some users but not others requires a brief look at the moving parts:

• WDDM + Driver Interaction: Windows exposes GPU capabilities and mode‑sets through the WDDM/DirectX stack and via Device Driver interfaces. If the OS reports an expected capability incorrectly, a driver may fall back to a different codepath (or vice versa), which influences timing and synchronization between CPU and GPU tasks. Timing differences can reveal or hide latent race conditions in game engines.
• TDR and DXGI errors: The Timeout Detection and Recovery (TDR) subsystem cancels a GPU operation when a device fails to respond in time, producing DXGI errors like DXGI_ERROR_DEVICE_REMOVED or DXGI_ERROR_DEVICE_HUNG. These symptoms are often the end result of many upstream causes (power draw anomalies, driver deadlocks, firmware glitches, or misaligned API calls).
• Driver UI and bundled runtime components: Adrenalin includes overlay/telemetry/tuning components. Many users reported fewer crashes when installing the driver only package (excluding Adrenalin’s UI). That observation points to components in the userland tooling affecting timing or hooking graphics APIs in ways that can amplify issues.
• System variability: BIOS/UEFI firmware, motherboard drivers (chipset/PCIe), PSU health, and overclock/tuning settings all alter the operating envelope. Community reports show undervolting, underclocking, or rolling back to older drivers improved stability for some rigs — a sign that the problem interacts with power/timing margins.

Because of this complexity, a single OS fix can help many configurations but still leave edge cases unresolved.

---

Correcting errors and clarifying claims​

Several widely circulated summaries misstated or simplified technical details:

• Build number mismatch: some summaries conflated the preview build numbers from KB5070311 (26200.7309 / 26100.7309) with the final cumulative build numbers in KB5072033 (26200.7462 / 26100.7462). Microsoft’s support page shows those numbers explicitly. Treat claims that KB5072033 yields the .7309 build strings as inaccurate.
• “AMD fixed it” vs. “Windows fixed it”: community posts that attribute the entire remediation to AMD’s driver releases are incomplete. The evidence indicates the December preview introduced OS‑side detection changes that materially improved stability in many cases; AMD’s drivers remain a factor, and AMD’s own notes don’t claim the OS change as part of their release. Avoid stating one vendor “fixed everything” — the reality is joint and configuration dependent.

Where claims cannot be verified — for example, a blanket assertion that every RX 9070 XT installation will now be crash‑free — label them as anecdotal and encourage testing.

---

Practical guidance: what gamers and power users should do now​

If you’re a Windows 11 gamer or maintain a high‑performance desktop, follow a careful, test‑driven approach rather than rushing to a blanket upgrade. Here’s a tested, sequential plan:

• Verify your current state
• Confirm OS build: Settings > System > About and Windows Update. Know whether you’re on 25H2 or 24H2 and the exact build string.
• Note your current AMD driver version: open Adrenalin or run dxdiag/device manager to capture the driver revision.
• Create a rollback plan
• Download a known‑good driver package (for example 25.9.1 if it was previously stable).
• Save the offline KB package from the Microsoft Update Catalog if you prefer manual control. Microsoft provides .msu offline installers for administrators and power users.
• Install KB5072033 (recommended path)
• Let Windows Update deliver the mandatory cumulative; that’s the simplest method.
• Alternatively, use the Microsoft Update Catalog .msu if you need an offline or targeted install.
• Update or re‑install AMD drivers the right way
• If you experience crashes after updating drivers, try a driver‑only install (skip the Adrenalin UI) or perform a full DDU (Display Driver Uninstaller) clean and reinstall. Community reports show driver‑only installs reduce certain UI‑related problems.
• If problems started with Adrenalin 25.11.1 and persist after KB5072033, consider temporarily rolling back to the last stable AMD driver you used while AMD and Microsoft investigate.
• Test with your games
• Run the specific titles that triggered crashes for you (use an extended session and from‑menu stress points like map changes or high‑load scenes).
• If you have a test rig or spare PC, pilot changes there before applying to your main system.
• Mitigations to try if crashes persist
• Disable overlays and recording/Instant Replay in Adrenalin.
• Try a conservative undervolt or underclock (temporary) to see if stability improves.
• Update motherboard BIOS and chipset drivers — timing and power delivery changes can expose or mask driver‑level bugs.
• When to involve vendor support
• If crashes persist after clean installs and OS updates, collect logs (minidumps, Event Viewer entries, device manager errors) and open a support case with AMD and Microsoft — cross‑vendor troubleshooting helps when root causes sit at the OS/driver boundary.

This staged approach gives the best chance of restoring stable gameplay while keeping options to rollback or pivot quickly.

---

Advice for IT administrators and small business deployments​

For admins and labs managing many machines, a conservative deployment plan is essential:

• Pilot ring: test KB5072033 and the target driver versions on a small, representative set of devices (including AMD and NVIDIA systems, high refresh displays, and any specialized hardware).
• Use Microsoft’s Known Issue Rollback (KIR) policy if you encounter a regression that requires temporarily disabling a change. Microsoft publishes KIR Group Policy packs for some updates; be prepared to use them while waiting for a corrected build.
• Prefer controlled offline .msu installs for imaging or air‑gapped systems and follow Microsoft’s guidance for SSU+LCU ordering to avoid servicing stack mismatches.
• Communicate with application/game vendors if you run validated software stacks — coordinate driver and OS updates where product teams publish compatibility guidance.

---

Risks, known regressions and what to watch for​

While the December rollup looks helpful, these risks remain:

• Visual regressions: Microsoft acknowledged a white flash in File Explorer dark mode in preview notes and continues to monitor it; environments that rely on dark themes should test visually.
• Partial coverage: Microsoft’s KB explicitly mentions fixing misflagged unsupported GPUs rather than guaranteeing resolution of every timeout or crash scenario. That’s an important distinction: many scenarios are still hardware, firmware, or driver dependent.
• Vendor silence or omission: AMD’s release notes for Adrenalin 25.11.1 do not call out Microsoft’s KB as a resolution, so assume coordination is partial and expect further driver or OS updates as the vendors continue to investigate.
• Mixed community reports: some users report complete remediation after KB5070311/KB5072033, while others still experience driver timeouts; treat early positive reports as encouraging but not definitive.

Flag any unsupported or single‑thread claims (for example, “this fixed all RX 9070 XTs everywhere”) as anecdotal until corroborated by multiple vendor statements or broad telemetry.

---

Final analysis: a pragmatic, evidence‑based verdict​

The December Windows 11 cumulative (KB5072033) represents a meaningful and measurable step toward improved AMD GPU stability for many users. Evidence from Microsoft’s KB entries, independent coverage, AMD’s own driver notes, and community testing paints a consistent picture:

• Microsoft fixed a compatibility/detection issue that in practice removed a trigger for some driver‑level crashes; that change is now in the mandatory December cumulative.
• AMD’s drivers remain an essential part of the equation; their Adrenalin 25.11.1 release notes do not claim this OS patch as their remediation, and some users still need driver rollbacks or configuration changes to regain consistent stability.
• The result is situation‑dependent: many gamers report smooth sessions after installing KB5070311 or KB5072033 plus an appropriate driver workflow; others still face issues and must apply mitigations.

Recommended posture: if you’re affected, test KB5072033 plus the latest vetted AMD driver on a representative system, maintain rollback options, and pilot broadly only after verifying stability. If you’re not affected, allow early adopters to validate the update for a few days to uncover regressions (for example, dark‑mode flash) before updating critical machines.

---

Microsoft, AMD and the PC gaming community are converging on a pragmatic fix path: coordinated OS + driver hardening, but not a single authoritative “one‑and‑done” patch. That’s progress — and it’s exactly the kind of incremental, evidence‑based remediation modern PC ecosystems need to restore stability without sacrificing feature work.

---

Source: PCWorld Windows 11's big December update fixes AMD GPU crash issues and more