Intel Arc Graphics Driver Crashing on Lunar Lake: How to Fix It

Your Lunar Lake laptop’s screen flickers, freezes for a few seconds, then recovers — or the app you were using vanishes and Event Viewer blames the Intel graphics driver. These Timeout Detection and Recovery (TDR) crashes are Windows catching a hung GPU and resetting it before the whole system goes down. Annoying, but survivable — and usually fixable.

Intel Arc graphics on Lunar Lake (Core Ultra 200V series) are capable but driver-sensitive: the platform is newer, the driver stack is still maturing, and version churn from Windows Update keeps stirring the pot. The fixes below stabilize it in the order a technician would work: driver first, then the app and system layers.

Why this happens

• Driver version churn: Windows Update, Intel DSA, and the OEM installer compete to install graphics drivers. Mixed or rapidly changing versions destabilize the Arc driver stack.
• Known driver bugs in specific versions: Some Intel graphics releases have regressions affecting Lunar Lake specifically — a version that is fine on Meteor Lake can crash on Lunar Lake.
• Overheating or power limits: Sustained GPU load with blocked vents pushes the chip into thermal or power throttling; an unstable edge case in the driver can turn throttling into a TDR crash.
• Problematic app or game: One app’s rendering path can trigger a driver bug reliably. If crashes cluster in a single program, the app is the trigger even though the driver crashes.
• Corrupted driver installation: Interrupted updates or mixed remnants from multiple installer sources leave a driver that mostly works and occasionally collapses.
• Unstable memory overclock/XMP: On laptops this is rare (memory is usually fixed), but aggressive BIOS performance profiles can push the shared-memory GPU subsystem past stability.
• Background GPU contention: Heavy concurrent GPU users — screen recording, AI workloads, hardware video encode — can expose race conditions; the same contention class behind Defender performance interactions on busy systems.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Check the crash pattern in Event Viewer and Reliability Monitor

Random crashes and app-specific crashes have different fixes. Two minutes of log reading tells you which you have.

1. Open Event Viewer > Windows Logs > System and filter for nvlddmkm-style Intel sources — look for “Display driver igfx stopped responding” events and note their timestamps.
2. Open Reliability Monitor (perfmon /rel) and look at the timeline: do crashes cluster around one app, or are they spread across everything?
3. If one app dominates, update that app first and try lowering its graphics settings (especially ray tracing, XeSS upscaling modes, or hardware acceleration toggles).
4. If crashes are spread across the system, the driver itself is the problem — continue to Fix 2.
5. Note the driver version in the crash details; you will compare it against known-good versions in the next steps.

Fix 2: Clean-install the latest Intel graphics driver

A clean install — full removal, then the latest Intel driver — resolves the majority of Arc TDR crashes on Lunar Lake.

1. Download the latest Intel Arc & Iris Xe Graphics driver for Lunar Lake from Intel’s driver support page (the Intel Driver & Support Assistant finds it automatically).
2. In Device Manager > Display adapters, right-click the Intel Arc Graphics entry, choose Uninstall device, and check “Attempt to remove the driver for this device”.
3. Restart — Windows loads the Basic Display Adapter fallback temporarily.
4. Run the Intel installer as administrator, choose a clean installation if the installer offers it, and restart when prompted.
5. Verify the new driver version in Device Manager, then stress-test: run the apps that crashed before and watch for TDRs over the next day of normal use.

Fix 3: Block Windows Update from replacing the driver

Intel’s driver fixed it; Windows Update’s older driver can unfix it within days. Prevent the regression.

1. After the clean install, run Microsoft’s “Show or hide updates” troubleshooter and hide any Intel graphics driver update Windows offers.
2. For stronger protection, enable “Do not include drivers with Windows Updates” via Group Policy (Pro) or the registry value on Home — documented on Windows support .
3. Confirm in Windows Update > Check for updates that no graphics driver is pending.
4. Update the Arc driver manually from Intel’s page going forward — monthly checks are plenty.
5. If crashes return after a Windows feature update, check the driver version first: feature updates are the most common block-reset event.

Fix 4: Rule out overheating and power issues

A GPU that only crashes under sustained load is telling you about thermals or power, not (only) software.

1. Install a hardware monitor (HWiNFO64 has an ARM64/x64 build that runs on these laptops) and watch GPU temperature during the workload that crashes — sustained temperatures at the thermal limit before a crash implicate cooling.
2. Clean the vents with compressed air and ensure the laptop sits on a hard flat surface — soft surfaces smother intake vents.
3. In Settings > System > Power & battery, set Power mode to Best performance while plugged in for testing — aggressive power saving can starve the GPU during boost.
4. Check your maker’s control app for fan profiles and set it to Performance/Balanced (not Silent) during testing.
5. If crashes stop with better cooling or full power, thermals were the trigger — keep the vents clear and consider a cooling stand for heavy workloads.

Fix 5: Reset graphics-related app settings and disable overlays

Overlays and app-level graphics tweaks inject themselves into the rendering pipeline and are a classic TDR trigger.

1. Disable in-game overlays: Discord overlay, Xbox Game Bar (Settings > Gaming > Xbox Game Bar), and any FPS-counter overlays — test with all of them off.
2. In the crashing app, toggle off hardware-accelerated GPU scheduling experiments, exotic upscalers, or custom shader caches; reset the app’s graphics settings to defaults as a test.
3. In Intel Graphics Software (or Arc Control), reset all custom settings to defaults — a bad custom profile (overclock, custom fan curve) can destabilize the driver.
4. Disable Hardware-accelerated GPU scheduling in Settings > System > Display > Graphics > Change default graphics settings as a test — re-enable it afterward if it made no difference.
5. Reintroduce overlays and custom settings one at a time to identify the specific trigger. Keep the blame in the right layer while you do: unrelated AI-feature gaps — like Click to Do’s missing Open-with option — are app-level issues, not driver crashes.

Fix 6: Test with the OEM driver and check for hardware faults

If Intel’s latest driver still crashes, the OEM’s validated driver — or the hardware itself — is the remaining question.

1. Clean-uninstall the Intel driver (Fix 2’s removal steps) and install the graphics driver from your maker’s support page (Dell , HP , Lenovo ) — OEM validation sometimes catches platform-specific instability Intel’s generic driver misses.
2. Test for a day. If the OEM driver is stable, stay on it and report the regression to Intel via their support channels.
3. Run your maker’s built-in hardware diagnostics (usually in the BIOS or a pre-boot menu) with the full GPU/video test — artifacting or failures here mean hardware.
4. Try an external monitor: if crashes happen only on the internal panel, the panel’s embedded DisplayPort link or its driver path is suspect rather than the GPU core.
5. Persistent crashes across both drivers with clean thermals point to a defective GPU or board — contact your maker’s support with your Event Viewer logs. And keep scope discipline: unrelated creative-app crashes like Blender GPU render issues deserve their own investigation, not a driver blame reflex.

Closing

Intel Arc TDR crashes on Lunar Lake are a driver-maturity problem more than a hardware problem: clean-install Intel’s latest graphics driver, block Windows Update from regressing it, rule out thermals and overlays, and fall back to the OEM’s validated driver if needed. Stable Arc drivers exist — the job is getting one installed and keeping it there.

Frequently asked questions