A PC that freezes only in game menus can be frustrating because the game may run normally once you are actually playing. Menus often behave differently from gameplay: they can render at extremely high frame rates, repeatedly load thumbnails or cosmetic assets, switch audio devices, compile shaders, or trigger overlays. That makes “menu-only” freezes a useful clue rather than a random symptom.
Start by determining whether the entire PC locks up or only the game does. If Alt+Tab works, the mouse still moves, or Task Manager opens with Ctrl+Shift+Esc, the problem is usually software, drivers, overlays, or an unstable game setting. If audio loops, the display stops updating, and the PC needs a power-button restart, investigate GPU stability, memory, temperatures, and power delivery as well.
The steps below prioritize reversible changes. Work through one change at a time, test the same menu for several minutes, and note what changes. This approach is especially useful on modern Windows 11 gaming systems in 2026, where driver features and background overlays can interact in unexpected ways.
Most Common Causes
| Cause | Symptom | Likelihood |
|---|---|---|
| Uncapped menu frame rate | GPU usage, clocks, fan speed, or temperature spike immediately in menus | Very high |
| GPU driver issue or unstable GPU tuning | Freeze, black screen, driver reset, or Event Viewer display error | High |
| Overlay or capture software conflict | Freeze appears when opening settings, store, social, or pause screens | High |
| Corrupt shader cache or game configuration | One game freezes after an update, while other games are stable | Medium-high |
| RAM, VRAM, or storage pressure | Stutter before freezing; high memory use; disk activity during menu loading | Medium |
| Fullscreen, HDR, VRR, or multi-monitor conflict | Freeze occurs while moving between menus, Alt+Tabbing, or changing resolution | Medium |
| USB, audio, or controller device conflict | Freeze coincides with opening audio, controller, or accessibility settings | Lower |
Diagnose Step by Step
-
Confirm whether the PC or only the game freezes
During the freeze, press Ctrl+Shift+Esc. If Task Manager opens, select the game and choose End task. Also try Win+Ctrl+Shift+B, which restarts the Windows graphics driver. A brief screen flicker followed by recovery strongly points to the GPU driver or a GPU stability problem. If neither shortcut responds and the system requires a hard shutdown, record that result for the hardware checks below.
-
Watch hardware behavior while a menu is open
Open Task Manager with Ctrl+Shift+Esc, select Performance, and watch GPU, Memory, and Disk graphs on a second display or in windowed mode. In the game, leave the troublesome menu open. Look for GPU utilization pinning near its maximum, memory use climbing continuously, or disk activity spiking while the game appears stuck. If your GPU software shows temperature, hotspot temperature, power, and clock speed, monitor those values too. Do not change voltages or firmware during diagnosis.
-
Check Windows reliability records
Press Start, search for Reliability Monitor, and open View reliability history. Check the red X entries at the exact freeze time. Also open Event Viewer by pressing Win+R, typing
eventvwr.msc, and checking Windows Logs > System. Display-driver entries, unexpected shutdowns, or application-hang events help separate a driver failure from a single-game problem. -
Test with a frame-rate cap
Set a temporary cap of 60 FPS in the game’s Video or Display menu. If the game has no menu-specific limit, enable V-Sync temporarily or use the GPU control panel. NVIDIA users can open NVIDIA Control Panel, go to Manage 3D settings > Program Settings, select the game, and set Max Frame Rate to 60. AMD users can use AMD Software: Adrenalin Edition under Gaming and enable a per-game Radeon Chill limit. Retest the same menu.
-
Remove background hooks
Close Discord, Steam overlay, Xbox Game Bar, GeForce overlay, AMD overlay, MSI Afterburner, RivaTuner Statistics Server, Overwolf, ReShade, OBS Game Capture, and RGB-control utilities one at a time. For a clean startup test, press Win+R, type
msconfig, select Services, check Hide all Microsoft services, then choose Disable all. In Task Manager’s Startup apps tab, disable nonessential entries and restart.
Fixes by Cause
Uncapped menu frame rate
What causes it: Many games use a lightweight menu scene that is not frame-limited. A powerful GPU can render hundreds of frames per second, creating unnecessary heat, power spikes, coil noise, or instability that does not occur during normal gameplay.
How to check: Open the affected menu and compare GPU utilization, temperature, clock speed, and fan speed against an actual match or gameplay area. If the menu drives the GPU harder than gameplay, this is likely the trigger.
What to do: Enable the game’s Frame Rate Limit, Maximum FPS, or Menu FPS Limit option. Set menu FPS to 60 or match your display refresh rate. If there is no menu option, apply a per-game driver cap. Also test V-Sync on, then test it off with a driver-level cap; some games behave better with one method than the other.
How to undo: Return the in-game limit to its previous value, disable V-Sync, or remove the game-specific maximum-frame-rate rule in NVIDIA Control Panel or AMD Software.
GPU driver corruption or unstable overclock/undervolt
What causes it: A marginal GPU overclock, undervolt, VRAM overclock, or damaged driver installation may fail during unusual menu workloads. Menus can shift clock states quickly, which exposes instability differently than sustained gameplay.
How to check: In Reliability Monitor, look for hardware-error or display-driver events at the freeze time. If you use MSI Afterburner or vendor tuning software, note any nondefault core clock, memory clock, voltage curve, or power limit. Test with every value at stock settings.
What to do: Reset GPU tuning to default. In MSI Afterburner, click Reset and make sure it does not apply a profile at startup. Then reinstall the current GPU driver using the vendor installer’s clean-install option if available. During our research, disable NVIDIA Overlay or AMD in-game overlay. Avoid installing multiple GPU tuning utilities simultaneously.
How to undo: Restore your saved stable tuning profile only after repeated menu tests succeed. If a clean driver install changes nothing, reinstall the prior known-stable driver package rather than repeatedly changing unrelated settings.
Overlay, monitoring, or capture conflict
What causes it: Overlays inject into the game’s rendering process. A freeze can happen when the game changes UI layers, switches display modes, opens a store page, or presents a browser-based menu.
How to check: Disable overlays individually. In Steam, open Library > right-click the game > Properties > General and turn off Enable the Steam Overlay while in-game. In Discord, open User Settings > Game Overlay and turn off Enable in-game overlay. Test after each change.
What to do: Leave the conflicting overlay disabled for that game. Update or remove outdated monitoring tools, especially old RivaTuner Statistics Server profiles. If you need recording, test Windows Game Bar separately from OBS rather than running several capture hooks together.
How to undo: Re-enable only the overlay you need after confirming the game remains stable. Reintroduce tools one at a time so the conflicting application is identifiable.
Corrupt shader cache, game files, or configuration
What causes it: A game update, driver update, interrupted shutdown, or mod can leave invalid shaders or settings. Menus often load UI textures, character models, videos, and cached effects before gameplay begins.
How to check: Determine whether the issue affects one game or several. If only one title freezes, verify its files first. On Steam, use Library > right-click game > Properties > Installed Files > Verify integrity of game files. Disable mods and custom DLL files before testing.
What to do: Clear the DirectX shader cache through Settings > System > Storage > Temporary files, select DirectX Shader Cache, and choose Remove files. Then verify the game files. If needed, rename the game’s configuration folder in %LOCALAPPDATA% or Documents\My Games by adding .backup to its name; the game will usually rebuild defaults on launch.
How to undo: Delete the newly created settings folder and rename the backup folder to its original name. Restore mods only after testing the unmodified game.
Memory, storage, display-mode, or device issues
What causes it: Menu assets can push RAM or VRAM over the edge, while display changes can conflict with HDR, variable refresh rate, or a second monitor. USB controllers and audio devices can also hang when a menu scans devices.
How to check: In Task Manager, check whether Memory is nearly full or Disk active time reaches 100%. Test with one monitor, HDR off, and unnecessary USB devices disconnected. For HDR, go to Settings > System > Display > HDR. For variable refresh rate, check Settings > System > Display > Graphics > Default graphics settings.
What to do: Close browsers and launchers that consume memory, keep at least 15% free space on the game drive, and set the Windows page file to System managed size under System Properties > Advanced > Performance > Settings > Advanced > Virtual memory. Test borderless windowed mode instead of exclusive fullscreen. Update audio and chipset drivers from the PC or motherboard manufacturer.
How to undo: Reconnect devices one at a time, restore HDR or VRR if stable, and return to exclusive fullscreen if it works better. Do not permanently disable the page file unless you have a specific troubleshooting reason.
When to Replace or Reinstall
Consider a clean Windows reinstall only after the problem appears across multiple games, survives a clean GPU-driver installation, occurs with overlays disabled, and remains after testing stock GPU settings. Back up saves first; many games store local data in Documents, %LOCALAPPDATA%, or their launcher cloud-sync folder.
Consider hardware replacement or professional testing when freezes occur outside games, Windows reports repeated hardware errors, the system crashes at stock settings, or the display driver repeatedly resets under different games. Test RAM with Windows Memory Diagnostic by pressing Win+R and typing mdsched.exe, but treat a pass as preliminary rather than absolute proof. Persistent whole-system lockups can indicate failing RAM, GPU, power supply, motherboard, or storage.
FAQ
Why does my PC freeze in menus only but not during gameplay?
Menus may run uncapped, use different shaders, load cosmetic assets, or activate overlays and web-based UI elements. They can therefore stress the GPU driver or a specific software component differently from the game engine during active play.
Can V-Sync fix menu freezes?
Yes, if the menu is rendering without a frame-rate limit. V-Sync is a quick test because it limits output to the display refresh rate. A dedicated menu FPS cap is usually the more precise long-term option.
Is a menu freeze always a GPU problem?
No. GPU drivers and uncapped FPS are common, but corrupt game files, overlays, insufficient available memory, storage stalls, HDR behavior, and controller or audio-device conflicts can produce the same symptom.
Should I reinstall the game first?
Usually not. Verify files, remove mods, reset the game configuration, clear shader cache, and test without overlays first. A full reinstall is reasonable when only one game is affected and those lower-impact steps do not help.