Overwatch Crashing Fix (PC): Launch Crashes & Device Lost

Overwatch crashes on PC are usually fixed by one of five things: a clean boot to find background software that interferes with the game, an antivirus exclusion for Overwatch.exe, a clean GPU driver install for “rendering device has been lost”, stock memory and GPU clocks, or a discrete graphics card if you’re on integrated graphics. These come from Blizzard’s own known-issues threads and Overwatch technical-support threads from 2026, where they fixed launch crashes, mid-match crashes and the long-running device-lost error. The game dropped the “2” on 10 February 2026, so everything here applies whether your launcher says Overwatch or Overwatch 2.

According to the Overwatch forum’s Tech MVP, Blizzard ended its courtesy technical support about two and a half years ago, and its forum is now a player-to-player troubleshooting area with volunteer Tech MVPs. Its support articles sit behind a Battle.net login. So the fixes below are the ones confirmed on Blizzard’s forums, and each one says where it comes from.

Match your crash to the fix

What happens	Likely cause	Fix
Overwatch closes seconds after Play, no window (since the 20 Oct 2026 update)	Antivirus or security software	Antivirus exclusion
Overwatch has crashed. Please wait while debugging information is gathered.	Background software, driver, or files	Clean boot, then Scan and Repair
Your rendering device has been lost! Application closing!	GPU driver, overclock or undervolt	Driver, then the API and display mode
EXCEPTION_INTERNAL_ERROR 0xE1D04F02, crashes even in the menu	Software interfering with the GPU driver	Clean boot
Random crashes mid-match, worse after the first one	Overclocked memory (XMP/EXPO), or background apps	Stock clocks
Never launches on a laptop or mini PC with no graphics card	Integrated GPU below minimum requirements	Integrated graphics
Freeze, black screen, then the whole PC restarts	Heat, power or an unstable overclock	Full-PC restarts
No crash, but RAM climbs and the game stutters	Client memory use	Stuttering fix

1. Add an antivirus exclusion for Overwatch.exe

If Overwatch started closing a few seconds after you press Play on or after 20 October 2026 (game version 2.25), check your security software first. In a forum thread from 21 October, a player analysed four crash dumps that all showed the same failure: c0000005 / SOFTWARE_NX_FAULT in Overwatch_loader.dll, on both the Battle.net and Steam installs. Reinstalls, a new Windows user profile and a clean boot didn’t help. Adding Overwatch.exe to the antivirus exclusion list fixed it reproducibly. Their antivirus was F-Secure’s DeepGuard, but any security suite that watches program behaviour can do the same thing.

1. Open your antivirus or Windows Security.
2. Add an exclusion (or “allowed app”) for Overwatch.exe in your install’s _retail_ folder. Excluding the whole Overwatch folder is the broader version.
3. Launch from Battle.net or Steam again.

Windows Reliability Monitor logs this crash as BEX64 with exception code c0000005, so if you see that pair, start here.

2. Do a clean boot to find background software

A clean boot starts Windows without third-party services and startup apps. If Overwatch stops crashing in a clean boot, something you normally run is the cause, and you turn things back on in groups until the crash returns.

1. Press Win + R, type msconfig, and open the Services tab.
2. Tick Hide all Microsoft services, then click Disable all.
3. Open Task Manager → Startup apps and disable every startup item.
4. Restart and play.

This is how the October 2026 0xE1D04F02 thread was solved. The player had crashed at random for nine months, even on the main menu. Overwatch ran for hours in a clean boot, and the culprit was Razer AppEngine.exe, which keeps running after you close Razer Synapse. Disabling it in Task Manager → Startup apps fixed the crashes completely. Razer software has been on Blizzard’s own known-issues list for years, so check it first if you have it.

Other background software the forum’s Tech MVP suggested removing or closing in October 2026: virtual audio, camera and streaming drivers (Steam Streaming drivers, virtual webcam apps), audio control apps, and extra audio devices (leave one input and one output enabled). Overlays and recorders are worth closing too, though one player who closed Discord’s overlay and Medal still crashed, so they’re rarely the whole story.

3. Fix “rendering device has been lost”

Your rendering device has been lost! Application closing! means the GPU driver stopped responding to the game. Blizzard has listed it as a known crash for years, and a 2026 forum thread shows it on both AMD (RX 7800 XT, RX 9060 XT) and NVIDIA (RTX 4070) cards, often only in Overwatch.

1. Clean-install the GPU driver with DDU instead of installing over the old one: see how to clean install GPU drivers with DDU.
2. Try an older driver if the newest one still crashes. The Tech MVP’s advice in an October 2026 thread where most errors pointed to the GPU driver was exactly that.
3. Remove GPU overclocks and undervolts, including factory “OC mode” profiles in vendor software. A curve that’s stable in benchmarks can still fail in Overwatch.

One RTX 4070 player saw the crash while the game loaded Play of the Game, either crashing to the title screen or showing the device-lost message. That pattern points to the same driver fixes.

4. Switch the Graphics API or display mode

Two different fixes worked for different players in the 2026 device-lost thread, so try them one at a time:

• Set Display Mode to Fullscreen. One player on an RX 7800 XT went five days without a single device-lost crash after switching from borderless to Full-screen mode.
• Switch the Graphics API. In Options → Video, find Graphics API and choose DirectX 12, then restart the game. A player on an RX 9060 XT fixed frequent crashes at the start of matches this way. The option only appears on GPUs that support DirectX 12 Ultimate (feature level 12_2).

The DirectX 12 option is labelled beta, and another player in the same thread found it less stable. If DirectX 12 makes things worse, go back to DirectX 11 and leave it there. If the game takes a while to settle on DirectX 12, let it sit in the menu for 5–10 minutes the first time so shaders finish compiling.

5. Scan and Repair the game files

Damaged files cause crashes at launch and when loading maps, and a repair only checks what’s already installed.

• Battle.net: select Overwatch, click the gear icon next to Play, choose Scan and Repair.
• Steam: right-click Overwatch → Properties → Installed Files → Verify integrity of game files.

If a repair finds nothing and the crash stays, a full reinstall rarely helps on its own. Most players in the 2026 threads reinstalled several times before finding the real cause in steps 1–4.

6. Put memory and GPU clocks back to stock

Blizzard’s own crash list says players who overclock their memory “will inevitably encounter a crash during the course of the match,” and the fix is to restore memory clocks to default in the BIOS. In October 2026 the forum’s Tech MVP still suggested disabling XMP while troubleshooting a launch crash.

XMP and EXPO are memory overclocks that are usually stable, so turn XMP/EXPO off as a test, not for good. If Overwatch stops crashing, your memory needs more voltage, a lower speed or a BIOS update, and you can turn it back on after that. The XMP/EXPO guide shows where the setting lives on each board. Do the same for CPU overclocks and GPU tuning profiles.

7. Integrated graphics aren’t supported

If your PC has no graphics card (a laptop or mini PC running on AMD Radeon or Intel integrated graphics), Overwatch is unsupported. In two October 2026 threads, the forum’s Tech MVP confirmed that a discrete GPU is required. That has been true since Overwatch 2 launched. Integrated GPUs that ran the game before can stop launching after any patch, and Blizzard won’t fix that, because the hardware is below the minimum. There is no setting that brings it back.

On a laptop that does have a graphics card, make sure Overwatch runs on it rather than the integrated chip: Settings → System → Display → Graphics, pick Overwatch, and set it to High performance. Blizzard’s older crash list also notes that out-of-date Intel graphics drivers crash Overwatch on switchable-graphics laptops even when the game uses the NVIDIA or AMD card, so update the Intel driver as well.

8. If the whole PC restarts

A game can’t restart Windows on its own. If Overwatch freezes, the screen goes black and then the PC reboots, the hardware has stepped in to protect itself. The usual causes are heat, an unstable overclock or undervolt, or a power supply that can’t hold the load.

• Return CPU, GPU and memory to stock (step 6).
• Watch temperatures while playing. A GPU that’s fine at idle can overheat under load.
• Cap your frame rate in Options → Video so the GPU isn’t running flat out, and see whether the reboots stop.
• If the reboots only started recently, check whether a Windows update, BIOS update or new driver arrived at the same time.

Several players reported this pattern on AMD and NVIDIA systems in late October 2026, and one connected it to a Windows update. Blizzard hasn’t confirmed a game-side cause, and the forum’s answer was to point to a Blizzard support article rather than a game fix, so treat it as a hardware or driver problem until proven otherwise.

Fix Overwatch performance, not just crashes

Once the game stays open, set it up properly. The Overwatch stuttering fix covers frame spikes and RAM creep, best Overwatch settings for FPS covers every video option, and the Overwatch lowest input lag settings cover Reflex, frame caps and latency. Tier1Suite can check Windows for the usual stability problems (power plan, overlays, Game Mode, HAGS) in one pass.

The short version

Fix	When it applies	Source
Antivirus exclusion for Overwatch.exe	Closes seconds after Play, Overwatch_loader.dll c0000005	Player fix, Oct 2026 forum thread
Clean boot, disable Razer AppEngine.exe	0xE1D04F02, random crashes even in menus	Player fix, Oct 2026; Razer on Blizzard’s known-issues list
DDU clean driver install, older driver	Rendering device lost	Blizzard known issue; Tech MVP advice
Fullscreen mode or DirectX 12	Rendering device lost, crashes at match start	Player fixes, Mar 2026 thread
XMP/EXPO and overclocks off (as a test)	Random crashes mid-match	Blizzard crash list; Tech MVP advice
Discrete GPU	Integrated graphics won’t launch	Tech MVP, Oct 2026

Related guides

• Overwatch stuttering fix
• Best Overwatch settings for FPS
• Overwatch lowest input lag settings
• 0xc0000005 access violation crash fix
• How to clean install GPU drivers with DDU
• Marvel Rivals crashing fix