Quick Answer
On a RTX 5070, Lethal Company crashes are almost never the GPU itself — the game is a lightweight Unity title that any card on this list runs at 100+ fps. Fix it in this order: verify files on Steam, do a clean NVIDIA Game Ready driver reinstall with DDU, disable mod conflicts in the BepInEx folder, and cap the frame rate at 60. That sequence clears the large majority of crash-to-desktop reports we see from SA players.
Verify files and rule out mods first
Right-click Lethal Company in Steam, pick Properties, then Installed Files, then Verify integrity of game files. Most crashes on a RTX 5070 trace back to a broken or out-of-date mod, not the card. If you run MoreCompany, LethalConfig or any BepInEx plugin, temporarily move the BepInEx/plugins folder out and launch vanilla. A clean vanilla launch confirms the hardware and base game are fine and the fault is a mod or config.
Clean driver reinstall and a stable frame cap
Run Display Driver Uninstaller (DDU) in Safe Mode, then install the latest NVIDIA Game Ready build. Lethal Company has no anti-cheat, so a clean driver almost always sticks. Because the game runs so far above your monitor's refresh, an uncapped frame rate can spike power draw and trigger a crash on a high-end RTX 5070 card (1440p tier). Cap it to your panel — 60 for a 60Hz screen, 144 for a 144Hz screen — via the in-game limiter or the driver control panel.
FAQ
Does the RTX 5070 cause Lethal Company to crash?
No. The RTX 5070 has far more power than this Unity game needs and is not the cause. Crashes come from mod conflicts, a corrupt install, or an unstable overclock, not the card.
Will a clean driver reinstall delete my saves?
No. Lethal Company saves live in your Steam userdata, separate from the GPU driver. A DDU wipe and reinstall only touches the graphics driver, so your challenge moon progress is safe.
Should I undervolt or overclock the RTX 5070 to stop crashes?
Leave it at stock first. A factory RTX 5070 never needs an overclock for a game this light, and an aggressive memory overclock is a common hidden crash cause. Confirm stock-clock stability before tuning anything.
persist after a clean driver and vanilla launch, open Event Viewer, find the LiveKernelEvent or APPCRASH entry at your crash time, and check whether memory or the driver is named before you replace any part.