Windows 11 24H2 changed enough of the graphics and windowing internals that win32kfull.sys — the kernel driver behind window management — crashes more often than it did on 23H2. The causes are familiar (graphics drivers, overlays, corrupted files), but the 24H2 context changes which fixes to prioritize. Windows 11 24H2 changed enough of the graphics and windowing internals that win32kfull.sys — the kernel driver behind window management — crashes more often than it did on 23H2. The causes are familiar (graphics drivers, overlays, corrupted files), but the 24H2 context changes which fixes to prioritize.

If your win32kfull.sys crashes started with the 24H2 update, start here. These fixes are ordered for the 24H2-specific landscape. If your win32kfull.sys crashes started with the 24H2 update, start here. These fixes are ordered for the 24H2-specific landscape, newest-OS-first.

Why this happens

  • Pre-24H2 graphics driver. Old GPU drivers misbehave under 24H2’s reworked graphics stack.
  • Overlay and recording software. 24H2 changed window-rendering hooks; old overlays crash the stack.
  • A buggy 24H2 cumulative update. Occasional bad updates introduce graphics-stack regressions.
  • Corrupted files from the 24H2 upgrade. The feature update can leave damaged graphics components.
  • Memory integrity interactions. 24H2’s HVCI enforcement catches driver behavior 23H2 tolerated.
  • Overheating GPU. Unchanged by the OS version, but still a real cause worth ruling out.

How to fix it

Work through these in order, from the quickest and most likely fixes to the deeper ones. Stop as soon as the crashes stop.

Fix 1: Install the latest 24H2-aware graphics driver, cleanly

The number one 24H2-specific fix — old drivers are the top trigger. The number one 24H2-specific fix — old drivers are the top trigger, because 24H2’s reworked graphics stack punishes drivers that 23H2 tolerated.

  1. Do a full clean uninstall first: Device Manager > Display adapters, right-click GPU, Uninstall device with Attempt to remove the driver ticked.
  2. Install the newest driver: NVIDIA , AMD , or the Intel Driver & Support Assistant — current releases are all 24H2-validated.
  3. Choose clean/custom install in the installer, restart, and test.
  4. Also update the chipset driver from your laptop maker’s site — 24H2 pairs with newer chipset drivers.

Fix 2: Fully update 24H2 itself

Microsoft fixes 24H2 graphics-stack bugs in cumulative updates — running behind means running buggy. Microsoft fixes 24H2 graphics-stack bugs in cumulative updates — running behind means running buggy, so catch up fully before anything else.

  1. Go to Settings > Windows Update and install everything pending.
  2. Check Advanced options > Optional updates for driver updates Microsoft is offering.
  3. Restart even if it does not ask — some graphics-stack fixes only apply with a full restart.
  4. If a specific cumulative update started the crashes, uninstall it (Update history > Uninstall updates) and pause updates for a week while the fix ships.

Fix 3: Remove or update overlay and screen software

24H2 broke several popular overlays’ hooks into the windowing stack. 24H2 broke several popular overlays’ hooks into the windowing stack — and overlay crashes look exactly like driver crashes in the dump.

  1. Uninstall or update Discord overlay, GeForce Experience overlay, Xbox Game Bar captures, OBS, and screen-recording tools.
  2. Test for two days with all of them gone.
  3. Reintroduce one at a time. The one that brings back crashes needs an update from its vendor — check their release notes for 24H2 compatibility.

Fix 4: Repair the 24H2 upgrade’s files

Feature updates sometimes leave the graphics stack half-migrated. Feature updates sometimes leave the graphics stack half-migrated — SFC and DISM repair what the upgrade damaged.

  1. Open Terminal (Admin) (Win + X > Terminal (Admin)).
  2. Run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth.
  3. Restart. If SFC repaired win32kfull.sys-adjacent files, the 24H2 upgrade had left them damaged. For the general step-by-step version of this fix, see our win32kfull.sys guide .

Fix 5: Check Memory integrity conflicts

24H2 enforces HVCI more strictly, and incompatible drivers crash the graphics stack. 24H2 enforces HVCI more strictly, and incompatible drivers crash the graphics stack — the incompatible-driver message is a free diagnosis.

  1. Go to Windows Security > Device security > Core isolation and note the Memory integrity state.
  2. If it is off with a message about an incompatible driver, that driver is your prime suspect — update or remove it rather than leaving integrity off.
  3. If crashes stop with integrity off but no driver is flagged, update all drivers and re-enable it — running without it permanently is a security downgrade.

Fix 6: Test RAM and thermals

The version-independent causes, ruled out the same way on 24H2. The version-independent causes, ruled out the same way on 24H2 — RAM faults and GPU heat do not care which Windows build you run.

  1. Run mdsched.exe > Restart now and check for problems.
  2. Monitor GPU temps under load with HWMonitor — sustained 90C+ means clean the vents and consider a repaste on older machines.
  3. If the quick RAM test passes but crashes persist, run MemTest86 overnight. Our page fault walkthrough covers deep memory diagnosis.

Fix 7: Roll back 24H2 as a diagnostic, not a solution

Proves whether the issue is 24H2-specific — then fix it properly. Proves whether the issue is 24H2-specific — then fix it properly and come back, because 23H2 is out of support.

  1. Within 10 days of the upgrade: Settings > System > Recovery > Go back.
  2. If crashes stop on 23H2, the issue is 24H2 driver compatibility — identify the driver (usually graphics), update it, and re-upgrade.
  3. Do not stay on 23H2 permanently; it no longer receives security updates. The goal is a working 24H2, not an old Windows.

Closing

win32kfull.sys on 24H2 is mostly a compatibility story: current graphics drivers, current cumulative updates, and 24H2-compatible overlays resolve the large majority of cases. Treat 24H2 as a stricter landlord — drivers that got away with sloppiness on 23H2 need to be current, and once they are, the crashes stop. Treat 24H2 as a stricter landlord: current drivers, current updates, compatible overlays — pay that rent and win32kfull.sys stays quiet.

Frequently asked questions

Why does win32kfull.sys crash more on Windows 11 24H2?
24H2 reworked parts of the graphics and windowing stack and tightened driver validation. Drivers that worked on 23H2 can misbehave under 24H2’s stricter checks — particularly older GPU drivers and third-party overlay software that hooks into window rendering.
Is there a known 24H2 bug causing win32kfull.sys crashes?
Microsoft has shipped cumulative updates addressing graphics-stack crashes on 24H2, so keeping fully updated matters. But most win32kfull.sys cases on 24H2 trace to third-party graphics drivers or overlays rather than a Microsoft bug — update those before assuming the OS is at fault.
Should I roll back from 24H2 to 23H2 to stop the crashes?
Only as a diagnostic step, not a permanent fix — 23H2 is out of support and insecure. If rolling back stops the crashes, you have proven it is a 24H2 driver-compatibility issue; the real fix is updating the incompatible driver, then returning to 24H2.
Do I need 24H2-specific graphics drivers?
Yes, ideally. GPU vendors release drivers validated against current Windows builds, and running a pre-24H2 graphics driver on 24H2 is a known trigger for win32kfull.sys crashes. Always install the latest driver, which will be 24H2-aware.