Why does Steam keep crashing, and how do I fix it?

Steam usually keeps crashing because its web cache or client files are damaged, steamwebhelper.exe is failing under GPU acceleration, or an overlay, security tool, driver or interrupted update is interfering. End every Steam process, clear the web cache, test without GPU rendering and background utilities, then repair the client while preserving your games.

Is Steam crashing, or is the simulator crashing?

The process that closes identifies where troubleshooting should begin. Steam can remain open after a game crashes, so returning to the Library does not mean the Steam client caused it.

If only the aircraft simulator or train simulator is closing, use our simulator-crash diagnostic sequence instead. Windows Reliability Monitor can also reveal whether the faulting application was Steam, steamwebhelper.exe or the game's executable.

How do you fix a Steam client that keeps crashing?

Work through these fixes in order, testing Steam after each one so that you know what changed. The menu names and cache path below apply to Windows; the same diagnostic order works on macOS and Linux, but their per-user paths differ.

1. Close Steam completely. Open Task Manager and end Steam and its related Client WebHelper processes, then restart Windows. Several WebHelper processes are normal; the problem is repeated termination or relaunching accompanied by a blank interface.
2. Launch the installed client directly. Run steam.exe from the Steam installation folder instead of an old desktop or taskbar shortcut. Remove any Windows compatibility setting and do not leave Steam permanently configured to run as administrator; mismatched privileges can interfere with games, overlays and input tools. If Steam now produces no window at all, follow our recovery steps for a Steam client that will not open.
3. Test the web interface without GPU acceleration. If Steam remains open long enough, open its Interface settings and disable GPU-accelerated rendering in web views, then restart the client. A temporary Windows test with -cef-disable-gpu can also identify this problem: add the switch after the closing quote in a Steam shortcut's Target field, launch that shortcut, and remove the switch after testing. If this works, update or roll back the graphics driver rather than treating the switch as the permanent fix.
4. Rebuild the Steam web cache. Exit Steam and rename %LOCALAPPDATA%\Steam\htmlcache to htmlcache.old if that folder exists. Steam creates a fresh cache when it starts. Do not respond to every cache-related guide by deleting userdata, the whole config folder or unrelated files; those destructive changes rarely isolate the fault.
5. Leave the Steam client beta. If a crash began after joining a client beta, return to the standard client through Steam's beta-participation setting. Use Clear Download Cache under the Downloads settings only when the failure involves an update or the Downloads page; it can require another sign-in but should not remove installed games.
6. Remove software conflicts. Temporarily close third-party overlays, frame-rate displays, capture programs, RGB utilities, hardware-monitoring tools and audio-enhancement software. A Windows clean boot is the clearest test. Check security-software quarantine records as well, but do not disable protection permanently or whitelist an entire folder without confirming what was blocked.
7. Repair the Steam client. First copy the steamapps and userdata folders somewhere safe, including any Steam library folders held on other drives. Run the official Steam installer over the existing client location to replace damaged program files. Steam's Verify Integrity command repairs individual games, not the Steam client itself.
8. Check Windows and the hardware. Install stable operating-system and graphics-driver updates, confirm that the Windows system drive and Steam drive have free space, and check the file system if crashes coincide with disk errors. If browsers and other applications are also failing, test memory, storage and graphics stability rather than repeatedly reinstalling Steam.

Why does steamwebhelper.exe keep crashing?

steamwebhelper.exe renders Steam's Library, Store, chat and other web-based panels. Repeated WebHelper failures usually point to a corrupt HTML cache, GPU-accelerated rendering, an injected overlay or a graphics-driver fault rather than damaged game files.

Black panels, flickering menus or a crash triggered by opening the Store strongly support this diagnosis. Clear the HTML cache and perform the GPU-disabled test first. If only one Windows account is affected, its per-user cache or permissions are more likely than a system-wide Steam installation failure.

Can you repair Steam without redownloading games?

Yes, provided the game libraries are preserved before repairing or removing the client. Never assume Steam Cloud contains every save, configuration file or screenshot.

• steamapps: contains installed game data, Workshop content and the app manifest files Steam uses to recognise installations.
• userdata: contains account-specific local data, screenshots and settings for some games.
• Additional library folders: may be on other drives and should not be deleted. After repairing Steam, add those existing locations through its Storage settings if they are not detected automatically.

Reinstalling the client over its existing directory is less disruptive than uninstalling it first. A clean removal should be the last software step and only after the libraries and local data have been copied elsewhere.

What if Steam still crashes after a clean repair?

A crash that survives a repaired client and a clean boot is usually tied to the Windows profile, a driver or unstable hardware. Test Steam from a separate local Windows account: success there points to per-user cache or permission damage, while the same crash in both accounts indicates a system-wide cause.

Review Reliability Monitor and the Steam installation's logs directory for the failing executable and time of the crash. A generic module such as ntdll.dll does not by itself prove Windows is at fault, but repeated errors naming a graphics, overlay or security component provide a useful lead. Crashes shared by unrelated applications make storage, memory and GPU testing the priority.