For the past few months I have been having issues with overwatch making my second monitor freeze. This has been an issue because I don’t want to alt tab to check discord or to watch a twitch stream or something like that. I have a Ryzen 5 2600x, Radeon rx 580, and 32 gigabytes of RAM. I have checked task manager while it is running and it seems my cpu gets a high of 50% so I don’t think that is the problem. This has only happened while playing overwatch, other games dont cause it. This happens in windowed, borderless windowed, and fullscreen. I have been looking into this for the past week and I’m lost.
Overwatch only has settings for which screen it will appear on, but has no control over the display on your second monitor (where the game isn’t being displayed). I’d check the Reliability History tool, or even the Windows Event Viewer to see what might be triggering the freeze.
I checked both of these applications but I can’t seem to find anything. In the event viewer it does show under “Summary of Administrative Events” OVRServiceLauncher has had 4 errors in the past 7 days but I have no idea what OVRServiceLauncher is and if it has anything to do with overwatch at all. I recently also tried lowering my graphics settings and turning down the max fps but it still freezes my second display.
Hey, fathamburger! OVRServiceLauncher is not related to Overwatch, this is Oculus VR service. Have you tried switching the primary monitor to the secondary monitor test? Then switch back if it helps?
There’s been some issues with certain Windows 10 and secondary displays, and it’ll be helpful to check out what errors might give us some clues to what’s happening here. Let’s gather a DxDiag file. Copy and paste the text file created and paste it between two ~~~ like so:
~~~
DxDiag Here
~~~
If you have issues pasting here, use Pastebin and post the end of the link. (ie. 123456 for pastebin.com/123456)
I just went and changed my display mode to display 2 and back to display 1 and it worked. Thank you!
2 Likes
Sorry for the delay! Glad to hear that helped, let us know if it comes back up again 