• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

The Radeon VII Owners Thread

@northun_munky Hi, they are all fine, I've fitted them to the block and they stuck in there :) was easier that way. but then now, IDK, I'm not taking any futher action. This sample is nothing special in terms of ocing, I'll stick around 1950/1100/1100mV and that's it. This past year with the card I can say 30% of the time I was DDUing some driver, or something like that, and 70% enjoying it. I don't think this is a RMA case. When I was with the stock cooler the card was fine doing it's sustained 105C, but I could prove it's not a good one for oc, I set the rig in the window to get really cold air and after 1165mV it starts to glitch even with lower JT.

Ah ok, just looked from your photo that the pads were missing on some of the smaller VRMs. Seems an odd problem then mate. Did you say that you replaced the stock cooler and it was the same? Topping g out well before 110c?
 
@northun_munky Hi, yes, I indeed replaced the stock cooler and got sustained 105C while running heaven benchmark. It's really strange. However the card does not do any good past 1165mV, so I'm not going to do RMA only to breach some 3dmark scores. ATM I'm running at 1950/1050/1100mV and is being grate for gaming.
 
@northun_munky Hi, yes, I indeed replaced the stock cooler and got sustained 105C while running heaven benchmark. It's really strange. However the card does not do any good past 1165mV, so I'm not going to do RMA only to breach some 3dmark scores. ATM I'm running at 1950/1050/1100mV and is being grate for gaming.

Yeah, that's about where I settled for 24/7 use. 2000/1150/1108mV. With the older drivers I remember having to have to ramp up the voltage to get much above 2025 but it's been months since I messed about with it due to the driver issues. Only last week with your help I discovered MPT and just dialed in my last know stable OC. Until they sort out Ocing that's where they will stay
 
Last edited:
@northun_munky I'm glad I could help :) about the ocing capabilities within wattman, I don't think that will ever work again, IIRC is broken from 19.7.5 onwards. There's plenty of people complaining about, reports, topics, reddit, here, there, everywhere, and they just don't fix it..
 
Last edited:
Hi guys,
Just catching up on the last week or so after been away in New York for half term.
I tried the fan trick this morning and got the same behaviour as before, hold the higher clock for a few seconds/ mins and fell off.
Jim @ AdoredTV did an interesting video which I've been having a chat with him regarding what I've said on this group. He uses a VII himself. Might be worth a watch for some of you?
https://www.youtube.com/watch?v=Wpudz_co_zM
 
Hi guys,
Just catching up on the last week or so after been away in New York for half term.
I tried the fan trick this morning and got the same behaviour as before, hold the higher clock for a few seconds/ mins and fell off.
Jim @ AdoredTV did an interesting video which I've been having a chat with him regarding what I've said on this group. He uses a VII himself. Might be worth a watch for some of you?
https://www.youtube.com/watch?v=Wpudz_co_zM

First off, LOVE that guys accent! :D

Good vid, he makes some very valid points although you have to say you can't blame AMD for playing it safe really. The press, and us as consumers are ruthless and had AMD employed tactics such as what he suggested surrounding the Auto undervolt for the press drivers, AND be found out..... Well, they'd be crucified...

Does beg the question though as to why if their Auto UV software in the drivers can reduce the voltage even by a minor amount, but to a degree that has such an affect on fan speed, and therefore noise it isn't done out of the box. I get that they are worried about stability, and silicon degradation but surely with a healthy undervolt, that should reduce the rate at which the silicon degrades?

I'd not had an AMD card for a while, and although I knew from reviews that the vii was loud, it didn't have to be as mine happily sits at stock clocks at 983mv. Seems crazy really.
 
Finally, all that bandwidth paying off! :cool:

19548
 
Hi All, after a bit of help if poss.

Been happily gaming away over the last month or so either at a nice UV of 983mv with stock clocks or more recently, 2000mhs core and 1112mv. Had no issues. Life has been good.

Then a few days ago, I started getting CTD's when I was away from my pc. It was either left in game, or just left running for a while whilst I was doing something else.

Event Log shows event 41, kernel power implying that the system didn't shut down cleanly and restarted. This always used to point to a dodgy CPU O/C back when I had a 2500k so I assumed that maybe the O/C on the Vii was causing issue. Took it off and went back to my know working Under volt. Seemed ok then happened again, And again....

Thought it might be driver related as had recently upgraded to 2.3.1 so rolled back to 2.1.3. Still happened. Tried DDU and clean install of 2.1.3, and left manual volts at stock of 1083mv, again still happened.

So I've gone back to adrenaline 2019 19.7.1 to be sure it isn't drivers and left everything on auto.

What I've found is that whilst my Vii's stock Voltage was always 1083mv, on auto it's now drawing 1100mv... I only clicked on Manual after launching Heaven just to check the stock voltage was still the same. Sorry for the massive photo:

qwAt0hj.png

Is this normal for stock voltage to increase like this? I mean it was quite happily sat at stock clocks at 983mv so why would it now need to draw 1100? It seems quite happy running away as I type but I suppose what I'm asking is, is this a fault with the card?

Or is degradation over time (less than a year old) and then requiring a bump in voltage to stay stable normal?

Sorry for the ramble but keen to get your opinions.

EDIT: Oh yeah, forgot to say that Wattman is reporting some spectacular clocks for GPU and Mem.... Assume they are erroneous though.
 
Last edited:
CPUID HWMonitor has always given me funky readings. Use GPUz or/and HWiNFO to get your readings and RTSS to display them in game if you like to, so you can actually see it while playing - and not just checking HWiNFO later on the Maxium tab, as it could have been just a spike.
My stock GPU voltage was also 1083mV for a long, long time, and I've always checked same way you are doing, the mV value at the end of the curve. Turns out that if I run the card stock, and use GPUz/HWiNFO it shows 1118mV, note that was even without opening Wattman, no settings touched. I don't believe I got a jump from 1083 to 1118mV, I was reading it wrongly. Seems that for some people the mV by the end of the curve is in fact their stock voltage, but not for me.
I've seen people reporting their stock voltage changed, but they were 0.002-3mV cases.
Driver-wise, I can not tell you much, any 2020 drivers cause CODMW and BF5 to freeze after 5-10 minutes of gameplay. 19.5.2, 19.7.5 and 19.12.2 work great.
 
CPUID HWMonitor has always given me funky readings. Use GPUz or/and HWiNFO to get your readings and RTSS to display them in game if you like to, so you can actually see it while playing - and not just checking HWiNFO later on the Maxium tab, as it could have been just a spike.
My stock GPU voltage was also 1083mV for a long, long time, and I've always checked same way you are doing, the mV value at the end of the curve. Turns out that if I run the card stock, and use GPUz/HWiNFO it shows 1118mV, note that was even without opening Wattman, no settings touched. I don't believe I got a jump from 1083 to 1118mV, I was reading it wrongly. Seems that for some people the mV by the end of the curve is in fact their stock voltage, but not for me.
I've seen people reporting their stock voltage changed, but they were 0.002-3mV cases.
Driver-wise, I can not tell you much, any 2020 drivers cause CODMW and BF5 to freeze after 5-10 minutes of gameplay. 19.5.2, 19.7.5 and 19.12.2 work great.

Thanks mate, I'll check the voltages again this morning with HWiNFO as you suggest and compare. It definitely wasn't a spike though, ran at the displayed voltage for 3 hours or so. Annoyingly, CODMW wouldn't run on the older drivers, made me update to newer ones so I'm hoping that it just was a case of voltages ones way or another.

If things stay stable on Auto voltage then I'll fiddle about with increasing the O/C voltage slightly and see if it stays that way. When i first got it, i used the same software HWMonitor to compare things to Wattman as I hadn't used wattman before. Max voltatage was never higher on HWInfo than the 1083mv displayed in wattman.

For one reason or another, it looks like my Vii requires a bump to stay stable. Just a bit worrying given i haven;t had it that long. And it's only been ran at a O/C to 2000 @ 1112mv for the time it took me to complete control and get into MW, so 3 weeks? Not long at all. Just a bit odd, and mildly worrying.
 
So by way of an update, I downloaded HWiNFO (great bit of software BTW) and within 5 mins of running heaven, got a CTD again. Must have got lucky with last nights gaming sesh with 2020 drivers...

Have gone back to the last 2019 driver I could find, 19.12.1 and so far, haven't had an issue.

Card is happily drawing 1.093 - 1.100mv though at stock. Not sure that's the issue though as it was with the 2020 drivers.

Did see an interesting thread on AMD support forum with a LOT of other Vii owners having exactly the same CTD issues either in game or when idle using ANY of the 2020 driver. ALL said that they were stable using 19.12.##

Hope that I'm the same. About now, I just want stable gaming. It's about the only thing keeping me sane is a nightly gaming sesh with the mates whilst under lockdown...

Be interested to know if any other Vii owners are having the same issues.

Just seems random that it developed suddenly. Although it did start to happen within a day of installing 2.3.1..... odd
 
Having some issues playing half life : alyx. Seems to be potential game issues but often crashes. Been trying various drivers including the latest and it's not really fixed the problem. Only change is that with 2020 drivers when it crashes it crashes the whole pc. The 2019 drivers crash to desktop and recover, and once I've restarted the VR stuff I'm up playing again.

Currently using 19.11.3 drivers, believe they were the latest before Catalyst 2020? Been running 3d mark extreme stress tests, memtest etc and have passed with no issues, so think it's a game issue in this case but interesting how the crash handling changed between drivers.

Already posted about an issue I had with 2020 drivers where machine would bsod and reset when on desktop and seeking through video files. I wonder if it's coincidence that the VII isn't mentioned in notes anymore for 2020 drivers?
 
Last edited:
Having some issues playing half life : alyx. Seems to be potential game issues but often crashes. Been trying various drivers including the latest and it's not really fixed the problem. Only change is that with 2020 drivers when it crashes it crashes the whole pc. The 2019 drivers crash to desktop and recover, and once I've restarted the VR stuff I'm up playing again.

Currently using 19.11.3 drivers, believe they were the latest before Catalyst 2020? Been running 3d mark extreme stress tests, memtest etc and have passed with no issues, so think it's a game issue in this case but interesting how the crash handling changed between drivers.

Already posted about an issue I had with 2020 drivers where machine would bsod and reset when on desktop and seeking through video files. I wonder if it's coincidence that the VII isn't mentioned in notes anymore for 2020 drivers?

Hope you get the crashes sorted mate, I literally cannot wait until I win the lottery to be able to afford all the VR gear to be able to play Alyx lol!

Is funny how the crashes differ between 2019 and 2020 drivers. I've rolled back to 19.12.1 and haven't had an issue since. Stressed my rig all day yesterday with a couple of hours of gaming, a few hours of heaven and time spy extreme stress test and was rock solid. Even ran absolutely fine for a further couple of hours with my Undervolt applied so figuring it must be driver related sadly.

I was resigning myself to dismantling the loop, swapping out the psu and hours of trying to diagnose what the hardware fault was so in a way, in glad its drivers. Also, it's a pain that its drivers as it doesn't look like AMD are doing anythingnto help support us Vii owners anymore.

How is Alyx BTW? Everything I hope and dream it will be lol?
 
Hope you get the crashes sorted mate, I literally cannot wait until I win the lottery to be able to afford all the VR gear to be able to play Alyx lol!

Is funny how the crashes differ between 2019 and 2020 drivers. I've rolled back to 19.12.1 and haven't had an issue since. Stressed my rig all day yesterday with a couple of hours of gaming, a few hours of heaven and time spy extreme stress test and was rock solid. Even ran absolutely fine for a further couple of hours with my Undervolt applied so figuring it must be driver related sadly.

I was resigning myself to dismantling the loop, swapping out the psu and hours of trying to diagnose what the hardware fault was so in a way, in glad its drivers. Also, it's a pain that its drivers as it doesn't look like AMD are doing anythingnto help support us Vii owners anymore.

How is Alyx BTW? Everything I hope and dream it will be lol?

Bar the crashes, really enjoyed it. Just finished it at about 15 hours gameplay according to steam, but that probably includes reloads from crashing and me dying in game so probably nearer 10 . Quite short for the cost, but a great game. Very immersive and plenty of great moments which I won't spoil.

Managed to play for a couple of hours last night without issues, only quitting for food. Later, it crashed pretty often, especially towards the end. :( I have noticed that even though the drivers "recover", I can't open up the AMD control panel (just get a window outline) and when playing again the gfx clocks don't boost, or stay low - don't go above 800mhz or so according to hwinfo. So a reboot is needed anyway - but at least it's cleaner that a bsod.

Tried underclocking the card but that made no difference. Temps in hwinfo seem fine - card was hitting about 76c, with hot spot in the 90's. Gpu mem usage hit almost 12GB. All well within specs for the card though. Card run hotter during 3dmark stress tests and they complete fine.
 
I got the Black screen error again today... while browsing the web using Brave Browser.

Faulting application name: Radeonsoftware.exe, version: 10.1.2.1788, time stamp: 0x5e713cb8
Faulting module name: Radeonsoftware.exe, version: 10.1.2.1788, time stamp: 0x5e713cb8
Exception code: 0xc0000005
Fault offset: 0x0000000000412917
Faulting process ID: 0x156c
Faulting application start time: 0x01d608d9c7b43bdf
Faulting application path: C:\Program Files\AMD\CNext\CNext\Radeonsoftware.exe
Faulting module path: C:\Program Files\AMD\CNext\CNext\Radeonsoftware.exe
Report ID: 6e71b3a0-592e-4d54-9655-9ab19c98ea8f
Faulting package full name:
Faulting package-relative application ID:

AMD Support are useless sent 2 tickets and no reply so far... and in the AMD Forums there are other users which have the same issue https://community.amd.com/thread/249261

Anyone here please can provide some suggestions?
 
I got the Black screen error again today... while browsing the web using Brave Browser.

Faulting application name: Radeonsoftware.exe, version: 10.1.2.1788, time stamp: 0x5e713cb8
Faulting module name: Radeonsoftware.exe, version: 10.1.2.1788, time stamp: 0x5e713cb8
Exception code: 0xc0000005
Fault offset: 0x0000000000412917
Faulting process ID: 0x156c
Faulting application start time: 0x01d608d9c7b43bdf
Faulting application path: C:\Program Files\AMD\CNext\CNext\Radeonsoftware.exe
Faulting module path: C:\Program Files\AMD\CNext\CNext\Radeonsoftware.exe
Report ID: 6e71b3a0-592e-4d54-9655-9ab19c98ea8f
Faulting package full name:
Faulting package-relative application ID:

AMD Support are useless sent 2 tickets and no reply so far... and in the AMD Forums there are other users which have the same issue https://community.amd.com/thread/249261

Anyone here please can provide some suggestions?
Disable hardware acceleration in the web browser.

It could be a bug though, please can you try to reproduce the issue consistently and let me know the steps you follow? I can then file a ticket but the reproduction steps need to be clear and precise.
 
@northun_munky let me tell you something.. Until two days ago, since I started using 20.3.1, I've got zero crashes. I used all 2020 drivers before including 20.3.1 and I was having crashes within 5-10 minutes of BF5 and CODMW as well. I was stuck with 19.5.2|19.7.5|19.11.3 all the time. I had a reason to be swapping in between them, I just don't remember now, but I can say they were stable at BF5, 3DMark, and other games, and mainly stable with CODMW - 19.5.2 was rock solid all over.
And as I said before, any 2020 driver was giving me crashes, freezes, system hang ups. Until I decided to run ramtest from Karhu, why not? BAM, around 1 hour and 11 minutes of test I got an error. But wait, HCI, TM5, AIDA, and some other stress tests, all passed. HCI is really reliable, but did not catch anything. So I've increased my ram voltage (from 1.450V to 1.465), and plim-plim, the error at ramtest was gone, and straight away I connected that to all my ramdom freezes using 2020 drivers, as unstable RAM ruins any heavy demanding game. So I DDUed all, installed 20.3.1 two days ago, and so far, not-a-single-crash.
So, might be worth DDUing all there, reinstalling a driver (20.4.1 has just been released), and upping your ram voltage by a bit, even if you are sure the ram is 100% stable, as I thought mine was. If you are on AMD cpu, and overclocked, try that with stock settings. Or if you are stock on the cpu, make sure is on all auto(no negative offset etc, pbo/xfr off etc), to conduct this test. I hope this helps, every case is different, but looks like my problems was my RAM was not 100% stable.
Let's see now if I'm right, I just installed 20.4.1. I'll report back.

EDIT

For my surprise, and to reassure my instability was caused by unstable ram, I've played two whole rounds of bloody money and no crash. After dinner will try BF5 and will report back.

EDIT 2

Yep, even BF5 is running no issues, two conquest 64 played, butter smooth
 
Last edited:
Back
Top Bottom