Getting Started June 13, 2026 Forza Horizon 6

FH6 PC Crash Fixes: FHC01, FHD01, Stutter and VRAM Errors

A safe, ordered troubleshooting routine for Forza Horizon 6 on PC — fix FHC01/FHD01 errors, stutter, VRAM problems and crashes after long sessions. Overlays, ray tracing, VSync, temps and launch fixes.

FH6 on PC has a more annoying problem than plain frame drops: the “I don’t even know why it crashed” category. FHC01, FHD01, VRAM weirdness, stutter that creeps in after a long session — these are real, and there’s no single fix for any of them yet. What follows is an ordered, safe routine drawn from what players report and what the community has found. Don’t expect one magic toggle. Work through it in order and, above all, change one thing at a time — that’s the difference between fixing the problem and making your system messier.

Step 1: Close every overlay

Overlays are the first suspect, and the easiest to rule out. Close all of these before anything else:

MSI Afterburner
RivaTuner Statistics Server
Discord overlay
NVIDIA GeForce Experience overlay
Your game launcher / platform overlay
Any other FPS, temperature or screen-recording overlay

Don’t underestimate these. An open-world game like FH6 constantly swaps maps, runs race results screens and opens menus, and overlays love to misbehave during exactly those transitions. Shut them all down, confirm the game is stable, then re-enable them one by one to find the culprit.

Step 2: Kill ray tracing, drop textures

Players report FHC01 specifically when closing the world map and dropping back into gameplay, and several eased it by lowering settings. Touch these first:

Turn ray tracing off
Drop texture quality one notch
Set DLSS / FSR / XeSS to a performance-leaning preset
Don’t max reflections, shadows and environment detail yet

If you’re tight on VRAM, texture quality is the most valuable thing to lower. VRAM trouble rarely announces itself as “out of memory” — it shows up as gradually worsening stutter, scene-change crashes and hitchy loading. See the PC performance settings guide for a full settings pass.

Step 3: Move VSync to the driver

Players report that turning VSync off in-game and enabling it for FH6 in the GPU driver control panel cut down FHC01 noticeably. It doesn’t work for everyone, but it’s worth a try — especially if your frame rate runs to 150 or 170 yet your frame times feel uneven. A cap can feel smoother than a high, jittery number.

My suggested setup:

Turn VSync off in-game
Enable VSync for FH6 in the driver control panel
Set a frame cap just below your monitor’s refresh rate
Test with half an hour of free roam plus a couple of events

Stability beats peak frame rate every time.

Step 4: Watch temps, especially on laptops

Some players report the winter map being nearly unplayable, and others point to a thermal wall or VRAM bottleneck. Laptop owners should pay the closest attention. Check:

Is it plugged in?
Is it in performance / high-power mode?
Is the GPU temperature too high?
Is the CPU throttling (downclocking)?
Are the fans and vents blocked?
Is VRAM near its limit?

NVIDIA users can hit Alt+R to watch resource usage. When temps are high, don’t blame the game first — lower the settings and test again.

Step 5: Won’t launch? Verify, then escalate

If the game won’t open at all, this basic but effective order helps. Do each step on its own:

Verify the game files through your launcher / platform.
Open the install folder and run the EXE as administrator.
Toggle Hardware-accelerated GPU scheduling (try it the other way), then reboot.
Update or roll back your GPU drivers.
Confirm Xbox / Gaming Services is installed and working.

Again: one change at a time. The worst move is flipping ten settings at once — even if it works, you’ll never know what fixed it.

My stability test routine

After any change, this is how I check it actually held:

Free roam for 20 minutes
Open and close the map several times
Run two or three events
Go in and out of the garage and menus
Watch for crashes or any obvious increase in stutter

Some FH6 problems don’t surface at launch — they show up only after you’ve played a while. A clean short test doesn’t mean you’re fully stable.

The bottom line

FHC01 and its siblings have no universal cure right now. The reliable approach is to reduce conflict sources: close overlays, drop the high-risk visual settings, control your frame rate and watch temps. Until a patch lands, don’t trade stability for a few extra effects — a corrupted save or a crash is far more painful than one less reflection.

Frequently asked questions

What causes the FHC01 error in Forza Horizon 6?

There's no single confirmed cause. Players report it most often when switching scenes — closing the map, returning to gameplay, loading menus — which points to overlay conflicts, ray tracing or VRAM pressure rather than one bug. Work through the steps below one change at a time to narrow it down.

Why does Forza Horizon 6 stutter or crash after playing for a while?

Late-session stutter and crashes usually mean heat or memory, not a startup fault. The community has found that high GPU temps, thermal throttling (especially on laptops) and creeping VRAM use show up after 20-30 minutes. Lower texture quality, cap your frame rate and check temps before blaming the game.

Will lowering ray tracing and textures actually fix the crashes?

It may help, and it's the safest thing to try first. Turning off ray tracing and dropping texture quality eases VRAM pressure, which several players link to scene-change crashes. It's not guaranteed, but stability is worth more than a few reflections.