Ping problems since 12/8? Radeon upd8 could be the cause

Technical Support
What I can confirm, is that is happening depending on which card do you have. Here at home, as I originally posted, the problem only presents in my pc which happens to have the r9 390.

The other two (r9 280 and r7 265) are not having this problem.
Can confirm there's something wrong with the 16.12.1 driver. With it installed, I had 200+ms making the game a pain to play. Going back to 16.11.5 my ping is back to the 40-50ms range. So there is definitely something wrong with the new driver. I haven't done any tweaking but it's good to know Blizz isn't responsible for the high ping.

Edit: I'm running on rx480 so maybe it's the higher models that are having problems?

Edit2: Big update. Reinstalled 16.12.1 driver but NOT the Relive recording software. This eliminated the high ping problem I've been having. Would love to know if this helps others too.
AMD RX480 user here.
I can confirm that after I installed the AMD Crimson ReLIVE 16.12.1 drivers that I have begun having latency issues with Overwatch. I would get pings from 200ms to 500ms.

I have various computers in my house, another with a GTX 750ti, a laptop with a GTX 950m. BOTH do not have latency issues when playing overwatch on the same connection. I use a 5.0Ghz connection and would usually get pings of 17ms.

I will rollback....or I will uninstall the Crimson ReLIVE software.
12/11/2016 10:22 AMPosted by Thinkawack
Hey PatientMango,

With 2 players reporting really similar circumstances with rolling back the AMD drivers that definitely starts to sound like there may be some issues there. If possible, I'd recommend running the MTR tests as well if you can, both with and without the new drivers installed so we can see if those are somehow causing connection trouble. While graphics drivers shouldn't cause issues with the connection, it is possible that some new settings like the new AMD streaming/recording feature implemented in the new AMD Crimson ReLive may be interfering.

Information on how to run an MTR test for Windows:

1. Download [url="http://www.softpedia.com/get/Network-Tools/Network-Testing/WinMTR.shtml"]WinMTR[/url]
2. Unzip the WinMTR.zip file to the Desktop.
3. Open the WinMTR folder and select the 32 or 64 bit version. Choose whichever one corresponds to your version of Windows.
4. Run the WinMTR.exe
5. Type the IP address you want to trace in the "Host" field. You can find the needed IP address [url="https://battle.net/support/article/7871"]here.[/url]
6. Click on "Start" and then launch the game. Once you notice the connection issue, play for about 10 more minutes, minimize the game and click on "Stop".
7. Click on "Export TEXT" and save the file to your desktop.
8. Add the resulting file results in your next post.


Can confirm this is also happening on the R9 270, rollback solved it immediately
Another confirmation here. Update was destroying my enjoyment. The rollback fixed it immediately.
Went ahead and ran tests with both drivers using WinMTR for further data. Not sure if someone did this already, but worth posting just in case.

Here's what it looks like when ReLive recording software is installed.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 1 | 729 | 728 | 1 | 165 | 1917 | 6 |
| - 1 | 721 | 717 | 2 | 163 | 1915 | 12 |
| No response from host - 100 | 158 | 0 | 0 | 0 | 0 | 0 |
| 173-219-229-78 - 1 | 727 | 726 | 10 | 181 | 1928 | 13 |
| 173-219-241-242 - 1 | 715 | 710 | 0 | 180 | 1926 | 31 |
| 173-219-227-53 - 14 | 487 | 419 | 210 | 398 | 2206 | 260 |
| Destination network unreachable. - 100 | 158 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 162 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 165 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 162 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 172 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 162 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 166 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 167 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 158 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 162 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 166 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 158 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 162 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 173 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 173 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 162 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 158 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 162 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 161 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 164 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 162 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 162 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 165 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 164 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Now here's what it looks like without ReLive installed.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 1599 | 1599 | 1 | 4 | 1316 | 5 |
| - 0 | 1599 | 1599 | 2 | 7 | 1328 | 10 |
| No response from host - 100 | 321 | 0 | 0 | 0 | 0 | 0 |
| 173-219-229-78 - 0 | 1599 | 1599 | 10 | 17 | 1339 | 21 |
| 173-219-241-242 - 1 | 1570 | 1563 | 14 | 21 | 1344 | 20 |
| 173-219-152-141 - 37 | 657 | 420 | 14 | 26 | 181 | 34 |
| Destination network unreachable. - 100 | 335 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 329 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 329 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 325 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 329 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 327 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 325 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 328 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 331 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 329 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 325 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 325 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 333 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 329 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 321 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 321 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 329 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 328 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 325 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 325 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 329 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 329 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 321 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 329 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
12/11/2016 12:19 PMPosted by Thinkawack
Hey there FearlessAce,

From those connection results normally I would definitely recommend switching to a wired connection, as the kind of high latency spikes and data loss we are seeing early on in the test generally indicate interference trouble.

192.168.1.1 - 1 | 693 | 688 | 2 | 64 | 512 | 5


If the driver rollback does help, please get a fresh MTR test after the fact so we can confirm if that is the issue here, since this would definitely be a major bug in the graphics drivers if they are causing connection problems.


Hello!
I rolled back the driver, but did not reinstall the software. Overwatch now runs like normal. Here's the new MTR. There was a brief lag spike upon logging in, which explains the 'worst' of these values, but it was smooth sailing after that:

192.168.1.1 - 1 | 621 | 618 | 2 | 30 | 505 | 6
24.105.62.129 - 1 | 612 | 607 | 40 | 70 | 560 | 245

I made no changes at all besides rolling back the driver.
Both of my MTR's were taken with 1 quick play game exclusively.
And again, for clarity, it ran so wonderfully after the rollback -- the 505 in my IP line could only have been the longer login time, because my game experience once logged in was normal and satisfying.

I hope this helps!
Bumping to keep it active as this is still happening
I can confirm the OP's theory that AMD's latest software package is the problem. I tried disabling desktop recording, then ReLive entirely, then killed the Radeon process directly in task manager, then rolled back the drivers with AMD's uninstall, and still had no luck.

Then I finally used DDU to completely wipe any remnants of the update and it worked! Now I'm riding a smooth 40ms ping on the Crimson 16.9.1 package. This thread was a big part of staying sane... who knew a GPU driver/software update could kill your latency?!
It's the first time ive known such a thing to happen, and ive been online gaming for 20 years
I am happy to've been able to help.
Can confirm this works. I was having issues with unusually high ping in WoW then got on OW today and was having the same issues. Tried downloading something on Steam and it was still high, so I figured it had to be my internet. Saw this post and uninstalled the new AMD driver and my latency is back to normal. Thanks OP.
I have asked amd about this on twitter but no response yet
12/12/2016 04:41 PMPosted by Serialchillr
Can confirm this works. I was having issues with unusually high ping in WoW then got on OW today and was having the same issues. Tried downloading something on Steam and it was still high, so I figured it had to be my internet. Saw this post and uninstalled the new AMD driver and my latency is back to normal. Thanks OP.


You are more than welcome. Happy to help.
I also have been having latency issues since the AMD 16.12.1 update.
I am also having lagging/latency issues too after updating to 16.12.1 AMD Update. It has to be something with that update. I have an ASUS R9 380 graphics card.

Thanks for all this information and I will update my post later today when I'm home to debug this issue but still... Posting to show it's not just a few people!

EDIT1: I stopped the Radeon Settings service in my Task Manager and the ping rate is back to where it was before (~20-25ms). Might still roll back the drivers though.
After the new patch today I had rollback drivers to 16.11.5 and my ping was under 20ms.

Me being stupid, decided to install the 16.12.1 drivers again, I get ping issues

I even tried an ipconfig /release /renew /flushdns.

I'm definitely rolling back now
There is a reddit thread going on right now.
WE'RE NOT ALONE GUYS!

https://www.reddit.com/r/Amd/comments/5ht9bg/why_are_the_r9390_and_rx480_with_relive/

Join the Conversation

Return to Forum