Ok I'm totally flummoxed now. I tried the PC out on a Sony TV and it works absolutely fine. I've tried a different PC on my LG TV and it works absolutely fine. But the 5700xt PC with the LG TV does not work. Now there are differences, for example the Sony TV is not HDR, but I've tried disabling HDR when connecting to the LG TV and it still doesn't work. Some kind of compatibility issue?
At this point I've no hope this will ever be solved.
Hey its me again,
just wanted to make sure we are all on the same page for this Problem, some said they didnt installed the newest audio driver within the setup, but what exactly was showing inside the Windows Sound Setup?
i noticed, even without installing the driver package for sound there was an old driver presaved (dated 2017)
i had to remove this completly in the "advanced settings" "Einstellungen ändern"
now only the
is now only showing, but the Problem still persists (not as heavy but still there), does this mean not the AMD driver ist faulty, but something else is? Maybe a broken GC, problems inside the GC Bios? Windows?
im running a MSI 5700 XT 8G (Base Model with blower style) on a X570 Carbon Pro Wifi with all updates possible installed.
Maybe we can get a clearer picture of the problem this way
What are your thoughts?
Possible solution found.
I've had my fill with this issue and I may have found a solution that actually works at an acceptable level.
I run my main monitor using Display Port cable.
My TV is using HDMI goin through a Yamaha receiver and from there to my TV, like most of you guys, I had 0,5 seconds of audio drops quite often, sometimes up to 30-40% of playback duration.
It's obvious to say that it was quite unwatchable.
I read earlier in this thread, someone trying to install and use a different HDMI driver and that got me thinking of a similar issue I had with my RX 580 using an older driver. At one point, AMD made en update that broke it for me and I waited for over a year for them to fix it and in the meantime I simply stopped updating me drivers for that year.
Old driver + working is much better then New driver + broken.
I just wanted to go back to an old 17 or 18 driver, but they don't actually support Navi, so yeah. Problem.
So, this is what I did:
1. Uninstall current driver. (I didn't use DDU or anything fancy, just simply remove and reboot)
2. Download and start the 19.9.2 adrenalin driver installation.
3. Make sure you choose the userdefined installation and not just default, make sure to uncheck and NOT install the HDMI driver.
4. Finish installation and reboot.
5. Download and start the 19.1.1 adrenalin driver installation.
6. Run a user defined installation again and make sure to only check and install the Display-driver and the HDMI-driver (you can't uncheck the display driver, but it will not override a newer driver anyway, so it makes no difference, what we need is the HDMI driver).
7. Finish and reboot.
Alright, this worked for me, I put on a media on my TV and HDMI ran fine. I even loaded Rise of the Tomb Raider on my main monitor at the same time, because this is where I had most problems where audio and even the video would start to stutter and lag and get worse and worse and sometimes stop completely and crash.
Now, it ran for 40+ minutes, fine.
Note how I use "fine" and not "Perfect".. I still get an audio 0,5 second cutout every now and then, but it's something like once every 5-7 minutes at most. and this was still while running RotTR at the same time.
For now, I'm happy. I would LOVE to see AMD acknowledge this issue and fix it.
This is not a permanent solution and who's to say that the next driver release will play well with this workaround.
Either way, try it out fellas. It may just work for You as well.
I also did this before and thought it was fixed. After a while audio stops for 0,5 sec. again. This is NOT a fix for me.
I use AMD graphic cards since 1998. I Like the UI, I like performance / price. I like Mantle/Vulkan and TrueAudio. But if I can`t use it to watch a simple video via HDMI on TV WITH SOUND WHICHT DOESN`T CUT OFF, well *.*. I`ll switch to nvidia card which I really hate. But it works at last!
Dangs I'm sorry this didn't work for you. You said you thought it was fixed, but still no ? How long did it take for the issue to turn back up on your system?
I only got to test for those odd 40'ish minutes on my rig last night, before I had to get some sleep before work. If that be the case, it may just show its ugly face on my system again too.
I'll test some more and report back.
Before this 5700XT I had a RX580 for about a year and a half, I think, and this too had some issues at first, but those all got fixed eventually and has run flawless for (on top of my head) at least a year.
I cannot live with my TV/receiver not working, I'm OCD like that. If it comes down to it, I'll throw my RX 580 back into my system and put the 5700XT on a shelve till drivers get fixed.
Sorry I wasn't trying to say it's LG only. But it certainly isn't a problem on my Sony TV so there's something to do with both the graphics card and specific TVs
AMD is not responding to the issue at hand either with mail or on their reddit page. And to have issues with a certain type of producer is out of the question, every hdmi device doesnt do this kind of up problem unless its defective. Im done here and going back to nvidia, im done testing evaluate and testing again, the RMA is ready and out for business.
And lets just say this is a Problem with a certain producer, how do they intend to do this? Im running at MS driver for HDMI audio and its still present. Make a new revision of the Cards? VBios? Blame the producer and say "its your problem to deal with, theres nothing wrong on our side"?
Im done because there is no feedback, instead of just saying "well, seems like theres a defective line of cards, u should RMA it" or anything else.
I would doubt it is just LG either, but there is no doubt there are far more LG users complaining about issues in these forums that any other specific maker. All saying the same things that prior AMD cards had worked fine and that Navi does not. I have yet to see anyone come up with a real fix.