That's not good. Can you confirm my findings by OCing in BIOS and testing, ensuring no OC software is loading on startup?I'm using Ryzen master for my OC. Wonder if OCing in windows is causing some glitch.
That's not good. Can you confirm my findings by OCing in BIOS and testing, ensuring no OC software is loading on startup?I'm using Ryzen master for my OC. Wonder if OCing in windows is causing some glitch.
That's not good. Can you confirm my findings by OCing in BIOS and testing, ensuring no OC software is loading on startup?
So this issue is limited to ASUS boards? Don't believe anyone else has reported this for other boards. And it happens with sound card, not just onboard!Yup, as soon as I disable my Ryzen Master OC the audio works fine. The audio continues to work with a light OC in the BIOS.
That's one of the most stupid replies I've seen in ages.If this audio issue you are having is happening only when you overclock your CPU then there's your answer. If you want your system to run reliably you should not be overclocking anyways and it complicates the troubleshooting process.
The problem occurs if I overclock my 1700 to 3025MhzHe probably means to Not say Ryzen has an issue if it's overclocked beyond the factory validated auto specs. XFR is an auto-spec not manual overclock.
ASUS has a similar app but it causes the same problem and was actually how the issue was first discovered.I had the same issues with ryzen master and a Gigabyte Gaming 3. OC in Bios only is not an option for me because it doesn't OC my Ram at all there. I can only OC my Ram to 2933 mhz in windows.
I seem to have solved the issue by using EasyTune instead. I don't know if that works with non-gigabyte boards or if asus has a similar app.
I was considering that. What would be the best place to report it to AMD?I can confirm this issue also. I'll add to the EA thread. I'm going to report the issue to AMD as well.
I was considering that. What would be the best place to report it to AMD?
Yep it started affecting a lot more people and a year later EA finally acknowledged the thread existence and sent it to their engineers. Next AGESA fixed the issue as people replied to my thread and my video advising it was working now after BIOS update.It's the AGESA code version. Try updating your bios to a version with 1.0.0.3b. That's what fixed it for me and my 1600. Experiment though to find what works for you.