Crashes? Performance Issues? Read this!


#1

The future is now. Are you with us?

We’ll be using this thread to track known system and performance issues throughout launch. If you’re encountering some problems check out the list below and give the steps a try before you create a new topic. Don’t forget, the more bug-related issues can be found in the Bug Report Forum’s Known Issues List.

Crashes
Crash - Intel Drivers, Laptops with Switchable Graphics
Crash - I click Play, but Nothing Happens!
Crash - Overclocked Memory
Crash - No Compatible Graphics Hardware Was Found
Crash - Unknown Error!
Crash - Rendering Device Lost

Performance Issues
Performance - TV Displays Cutting Off Borders
Performance - Running Slow While Multitasking (6-core CPUs or lower)
Performance - Long Load Times, High Latency (Proxy/VPN/Network Optimizer)
Performance - I Only Hear Sound Out of One Headphone
Performance - Black Screen with only HUD Visible
Performance - Troubleshooting Low Frame Rates


Game crashes solved but voice chat bugs
#2

Crash - Intel Drivers, Laptops with Switchable Graphics

Players with an Intel HD Graphics card may experience a crash when launching Overwatch, even if you have a second video card that is used when playing games (Nvidia or AMD card). Updating your Intel Drivers to the latest version will resolve this issue.

If your laptop manufacturer does not have an updated driver, you can try Intel’s generic driver from their Support Site. If the generic driver is not compatible, please contact your laptop manufacturer for assistance!


#3

Crash - I click Play, but Nothing Happens!

Crashes can be caused by several conflicting software, but most often Malware and Viruses. The below points should help resolve these issues:

  • Malware - Try running a scan for malicious programs using Malwarebytes, or other options in our Running a Virus Scan article.

  • Antivirus - Make sure your antivirus programs are up to date (see your specific antivirus program’s support site for instructions). You can also test to see if your Antivirus Program is causing an issue by temporarily disabling the software. If the game launches when antivirus is disabled, please contact your provider’s service team for assistance.

  • Background Programs/Overlays - Some background processes like Curse Voice, Discord, Overwolf, etc. may prevent the game from launching. Try disabling these applications. If the issue persists, a full Selective Startup should resolve this issue as well.


#4

Crash - Overclocked Memory

Players who overclock their memory in their BIOS settings will inevitably encounter a crash during the course of the match. To resolve this, players can restore their BIOS settings and memory clock speeds to default.

Note: This issue is only caused by manually changing your clock speeds in your BIOS. If you have not modified your memory clock speeds, check out our other crash causes before posting!


#5

Crash - No Compatible Graphics Hardware Was Found

This error can show if the computer does not meet our Minimum System Requirements, or if you are missing the most recent drivers and Windows Updates. If the issue persists, please create a new forum topic with your Dxdiag.


#6

Performance - TV Displays Cutting Off Borders

Some televisions have unsupported resolutions or aspect ratios that cause Overwatch to display incorrectly. Please try changing your TV’s display resolution and matching it with a supported in-game resolution from the Overwatch Graphic Settings menu. Additionally, you can use your TV’s Auto Adjust feature to try and resolve display issues.


#7

Performance - Running Slow While Multitasking (6-core CPUs or lower)

Overwatch will utilize up to 6 CPU cores. If your CPU has less than 6 cores available, multitasking (such as broadcasting, streaming web content, or running messaging applications) may cause additional performance degradation. Closing other processes will improve game performance.


#8

Performance - Long Load Times, High Latency (Proxy/VPN/Network Optimizer)

The below services are known to cause issues with Overwatch Network Traffic. If you encounter high latency or load times, please try disabling/uninstalling the application to see if it resolves your issue:

  • Gigabyte, RealTek, etc. LAN Optimizer

  • KillerNIC (killerservice.exe)

  • Asus GameFirst III or IV

  • Hamachi VPN

  • Specific Router Quality of Service options

If you have tried disabling the above programs and continue to experience trouble, please try disabling all background processes and see if the latency issues persist.

If you have a router with Quality of Service (QoS) packet shaping, please see your manufacturer’s website for assistance in disabling QoS services or configuring it for use with Overwatch.


#9

Performance - I Only Hear Sound Out of One Headphone

Dolby Atmos is designed for use stereo headphones, but some modern headsets attempt to simulate surround using their own software which can result in various conflicting behaviors. Try disabling supplementary audio software utilities. If the issue persists, also try updating your drivers for your audio device.


#10

Crashes - Unknown error!

Some variations of this crash can be resolved by changing some sound settings in the Settings_v0.ini file in this folder:

C:\Users\myName\Documents\Overwatch\Settings

  1. Make a backup of the Settings_v0.ini file first.
  2. Start up Overwatch, and click on Options, then Sound.
  3. Change the Master Volume to 42.
  4. Exit completely out of Overwatch.
  5. Open the Settings_v0.ini file with Notepad or Wordpad.
    You should see this in the last section:

[Sound.3]
MasterVolume = “42.000000”

  1. Add this line after that, at the end:

PreferXAudio2 = “0”

  1. Save the file.
  2. Go back into Overwatch, and set the Master Volume to what you had it before.

Note:

PreferXAudio2 = “0”

This will force the Sound system to use WASAPI instead of XAudio; setting this to 2 will force it to DirectSound:

PreferXAudio2 = “2”

Delete this line to return back to defaults.


40% Volume in OW
Rendering device lost since new patch
#11

Crashes - Rendering Device Lost

The “Your Rendering Device Has Been Lost” crash error message shows up when Windows reports a Timeout Detection and Recovery (TDR). Windows TDR errors can have a variety of causes.

Two of the main causes for this crash error currently concerning Overwatch is a known issues with the AMD graphic card (GPU) drivers and BIOS/Chipset drivers for Ryzen CPUs.

Beyond these two specific causes there can be a variety of other reasons this type of crash occurs. It could take trying several troubleshooting steps to find out what is causing this error on a specific computer. Below are some of the most common troubleshooting steps to try that can help stop this type of crash.

Reset the Overwatch settings as some setting maybe incompatible with some graphics cards or monitors.This type of crash can be caused by overclocking, overheating, software conflict and corrupted or missing Windows system files. If Windows Superfetch is disabled this type of crash can occur.

  • Press Windows Key + R.
  • Type services.msc into the Run window.
  • Click OK.
  • In the Name column, locate and right-click Superfetch.
  • Select Properties.
  • Under the Startup Type dropdown menu, select Automatic.
  • If Service Status does not show Running click the Start button
  • Click OK.Note: You need to restart your computer to apply these changes.

If the graphic card is not receiving sufficient power. Generally, this seems to be caused by, Insufficient PSU (power supply unit), Failing PSU or improperly seated GPU.

  • Check to make sure the PSU has enough wattage to power the hardware in the PC, especially when the GPU is under load.
  • Make sure the GPU is properly seated.
  • A local computer tech can test the PSU to see if it is failing.

Your rendering device has been lost. Still an issue 1 year later
Your rendering application has been lost issue!
Rendering device Lost
Your rendering device has been lost
Please fix my not broken rendering device
Game Crashes = Suspension
Game starting to crash randomly
Your rendering device has been lost
"Rendering Device Lost" Can I get some help please?
"Your rendering device has been lost" error, getting increasingly severe penalties, please help!
Rendering device has been lost
Rendering device has been lost
Your rendering device has been lost
Rendering Device Lost - Again
Your rendering device was lost, then found, now its lost
Rendering device has been lost
Your rendering device has been lost
Rendering Device has been lost (only after match ends)
Nvidia display driver crash mid Copa Lucioball match
#12

Performance - Black Screen with only HUD Visible

This issue appears to come up more frequently when video memory is being pushed/overclocked. Otherwise, corrupt driver installations and custom DPI settings have also been reported as causing this anomaly to occur.

Troubleshooting:

  • Lower in-game settings.
  • Make sure all components are set to default, manufacturer-recommended settings. It may be necessary to underclock the GPU in some cases. Please contact the device manufacturer for assistance checking or making changes to these settings.
  • Make sure all unnecessary background applications are shut down. In particular, shut down any software that has video or game “optimization” settings or can be used to overclock hardware.
    Additional Troubleshooting:
  • Set DPI Scaling to 100%:
    Right-click on the Desktop
    Choose Display Settings
    Make sure “Change the size of text, apps, and other items” is set to 100%
  • Clean re-installation of the graphics driver:
    [ul]Uninstall the current driver (consider using a driver cleaning software like DDU)
    Reinstall the driver directly from the manufacturer’s website (Nvidia - AMD - Intel)

#13

Performance - Troubleshooting Low Frame Rates

If you have encountered a system performance problem that has led to lower than expected frame rates in Overwatch, please try these troubleshooting steps. Note there are several additional steps listed under Advanced Troubleshooting.

If you have tried those steps and still require assistance, please create your own thread and include the following information:
A DxDiag file (please use the code blocks option to post the information inside a scrollable window)

  • Observed CPU and GPU temperatures
  • Any running background applications/processes
  • Any other information you feel may be relevant (time the issue began, any recent changes to the computer, etc.)