PC Graphics

[edoroom]

Uploaded it also here -

Vega 64 Crash? / Watercooling works? - Systems - Tom's Hardware

MSI X370 XPOWER GAMING TITANIUM

RYZEN 1800X

ASUS MG279 Freesync monitor with the "overclock" to freesync 57-144 range

ASUS RX VEGA 64 STRIX

Corsair RM750X PSU

You can see in the middle of the benchmark the temps are fine..

And in the middle of that benchmark crash happened..

https://youtu.be/GjVwFhWNN4Q

+

https://i.imgur.com/Vsho27j.jpg

I did another benchmark after restarting to see if maybe it's temp issue,

https://i.imgur.com/ZmveKls.jpg

When it crashed temps of the VR Soc/VR Mem was the same like the other crash..

Doing now another benchmark to see if it's really something there..

But if someone have any idea what may causing it will apperciate!

Drivers,BIOS everything updated.

Edit-

Did another benchmark

https://youtu.be/YLg8N9f_o9M?t=167

Minute 2:47

It's seems again to crash when it's on 70-67 VR Soc/VR Mem Temp,

Not sure if it's 100% due to that..

Any idea?

[theacclaimed · Accepted solution]

Remove the overclock on the freesync monitor and retest. I would also suggest changing to a different power supply if possible (much higher wattage). Otherwise, it could be a hardware problem but in my experience with testing Vega 64, it really needs a high wattage power supply for max stability. Previously when I testing with both a 850w Corsair and a 1000w Seasonic power supply. The computer would randomly restart or it would shut off completely due to over current protection on the power supply. This was tested on two different computers using Vega 64 with FFXV opening fire scene. The computer would shut off completely as if there was a power outage. It can also randomly reboot while playing a game or idling.

There is a discussion about Vega's transient power spikes while gaming over at Seasonic Prime triggered by sudden power increases - jonnyGURU Forums

There the issue is more about the Seasonic PRIME 1000w not being able to handle the transient spikes from Vega 64 but different power supplies might handle the situation differently, so your issue might be related.

In my case I fixed the issue by upgrading to a Corsair HX1200 watt power supply.

[edoroom]

Tested without freesync "overclock" but same results..

It's seems more in the temps then PSU..

I mean why 750W wont be enough?

Still..I will indeed check on my other PC..

But..

How I was using for 6 month the Vega 64 with no issue till it died,

And why this new vega which only in use for 2 month starting probably to die also..

What is wrong there ;/

[elstaci]

According to AMD, the Minimum PSU you need for the Vega64 is 750 Watts. With a high power Ryzen CPU which has a TDP Wattage of 95 it is possible under heavy loading the PSU is not supplying enough power to your computer hardware.

[edoroom]

Interesting..

Uhmm,I really hope it's just the power supply and not the GPU it self..

Will test it tommorow and update,

Thanks!

[theacclaimed]

If you don't have another power supply to test preferably a 1000w or 1200w, then you can lower the the power limit by 30 or 50% and see how it runs then.

[edoroom]

Just made a retest using my other computer powersupply (It was connected only to the vega when the other powersupply where for the system..)

Tested again and no crash,

Was thinking that it's indeed the powersupply..

Tested again with my own powersupply to see it crashing again to double confirm it's the powersupply and it didnt crash..

Which made me thinking again what's the difference (The test was on my other computer monitor)..

So is it really the monitor fault?

Returned the computer back to it's MG279Q Monitor and discovered that I  never  really disabled the freesync "overclock" even that I thought I did..

Had to use CRU Reset function..

Went again to benchmark and no crash!

So it's indeed was due  to the famous MG279 Freesync "overclock" and not due to PSU/GPU..

Weird that everyone who is using that overclock never encoutered my issue but well..At least it's now fixed!

Thanks for  the help!

Hope anyone who encouter the same issue to see this thread