Topic: AMD Mem Tweak XL - Read/modify timings/pp/straps on the fly - page 44. (Read 58906 times)

DEAD CARD DETECTION--

My Vega64 rig was stable for 2 days mining CNr on NiceHash with TeamRedMiner (2.2kH/s per GPU), but I noticed that poolside hashrate varied a lot, both on the NiceHash dashboard (wild swings +/-), and on the TRM console (more steady but low).  I thought to experiment with ETH.

Switching to ETH from CNr, TRM to PhoenixMiner, I initially achieved 48MH/s ETH per card.  But, very shortly 1 GPU was reported dead and not hashing.  The rig generally began behaving badly and I eventually pulled that GPU.  I tried ETH overnight with the remaining 3 cards but woke to a zero hash rate.

Unplugging and replacing the "dead" GPU a few times brought no better results, and switching back to TRM mining CNr still wound up with a dead GPU detected and failed launches.

So, I commented out my call to AMDmemtweak in my "custom.sh" file (a script file run at boot by ethOS to launch utilities and such).  After that I configured the rig to mine VertCoin (lyra2v3) with TRM.  Lyra2v3 is a compute heavy algorithm, and I have my memory clocked low (500mhz).  TRM booted just fine, both without and with my "undead" GPU.  The cards are hashing VTC at about 100MH/s each.

I sincerely expected to RMA the card last night.  Today it works fine mining Lyra2v3, but at a higher wattage (250+W/GPU) than when mining CNr (200W/GPU) and ETH (150W/GPU).

I need to do some more reading about the strap values, I think.  Any tips or comments left on the matter will be appreciated.       --scryptr

When I tried to scribble down a new Vega tuning guide to include in the TRM 0.4.4 release, I was debating if I should have mentioned this or not. I opted not to, that text was long enough already anyway.

However, I know more than a few skilled and knowledgeable Vega tuners that ALL have been stuck with old PPTs from the fall of 2017 (brnsted, Hellae) that for some reason all have 1200 for SoC. At the time, I guess it was considered highly beneficial for stability. Fast forward a few years to times where you don't make $10/day/Vega and power draw is a crucial part of your setup, this trade-off no longer holds.

In the common Google sheet (https://docs.google.com/spreadsheets/d/1-rhYsaRXO1ahk3PyrEgT9gXzs7ImAzh-sbqtgwy8HQg) used for PPT tweaking you can edit the SOC clk value but guess what: it doesn't change any nrs in the PPT, the cells aren't connected(!!!). You have to change the SOC clk value in cell AE26, then manually copy cells AG-AI:26 to T-V:11. You can probably guess why I may sound a little pissed off  .

Oops... I made a quick check with HWtool and yes... I really have SOC max @ 1199Mhz. I have used the Hellae 920mV PPT and then adjusted with Overdrive Ntool the Core P7 and Mem P3. I havent touch the SOC. After memory timings my rigs are pulling like 1420-1500w from the wall per rig. My rigs run like 150w w/o GPUs and after OverdriveNtool the wattage is ~250w before the miner starts and all the GPU led lights are fully on.
This sounds to me like 1270 to 1350w with 6 GPU and on avg. like 210 - 225w/GPU. :O

Thanks for pointing out the SOC. I need to drop to 1107.

For those having issues with running the tool as admin and from a bat file. Please keep in mind that you have to run the bat file itself as admin, otherwise the tool will open in another cmd instance and you won't see any otput (if run as admin is set in the tool's properties). Also you must use full path to the tool or first cd to the folder because admin cmd always starts from system32 folder.
I hope there won't be any more question in this matter as it makes this thread very noisy.

I know this post is for Vega, but can anyone timing for Rx 580 (appreciate) or process how-to play with the tool to get the best time for the cards. Github is with commands which we are not familiar.

I'm on linux, and only use PPT (no additional settings.)  But you won't be able use my PPTs on windows.

Not sure why my pause .bat files did not work, but just tried doing this and im able to use WinAMDTweak and change the setting from there. Now i can get to work on this.

Oh ! I'm far above that number too.
Could you share your PPT tables  and settings ?
Thanks

Anyone cares to share some tunes for Vega FEs?
My test one runs as follows, does stable 2.2k on CNR:

GPU 0:  Vega 10 XTX [Radeon Vega Frontier Edition]      Memory state: 0x11C (1000MHz)
Timing 1          CL: 17          RAS: 33         RCDRD: 16       RCDWR: 10
Timing 2          RCAb (RC): 47   RCPb (RC): 47   RPAb (RP): 14   RPPb (RP): 14
Timing 3          RRDS: 4         RRDL: 6         RTP: 5
Timing 4          FAW: 16
Timing 5          CWL: 6          WTRS: 4         WTRL: 9
Timing 6          WR: 16
Timing 7          RREFD: 8
Timing 8          RDRDDD: 3       RDRDSD: 2       RDRDSC: 1       RDRDSCL: 3
Timing 9          WRWRDD: 3       WRWRSD: 2       WRWRSC: 1       WRWRSCL: 3
Timing 10         WRRD: 1         RDWR: 17
Timing 12         REF: 3900
Timing 13         MRD: 8          MOD: 15
Timing 14         XS: 270
Timing 16         XSMRS: 8
Timing 17         PD: 8   CKSRE: 10       CKSRX: 10
Timing 20         RFCPB: 160      STAG: 7
Timing 21         XP: 8   CPDED: 2        CKE: 8
Timing 22         RDDATA: 16      WRLAT: 4        RDLAT: 14       WRDATA: 1
Timing 23         CKESTAG: 2
RFC Timing        RFC: 350

That’s an insane voltage range, and I can’t fathom how 970mv could possibly be necessary. Between 9 64s and a flashed 56, I run avg 834mv, none over 850, for similar clocks/timings.  That puts me @ 178w per GPU at the wall.

At 970, you’re running at least 35% higher power, meaning over 240w per card.

It sounds like you have some ppt issues or something, maybe you’re running your SOC @ 1200mhz unnecessarily (it should be 1107 @ your clocks.)  Although, even then, you prob shouldn’t need much more than 925mv.

I have now run ~72 hours w/o any issues with 24 Vega64 GPUs(good and bad ones) mixed in 4 separate rigs ... CNR with core 1407Mhz /860-970mV , Mem 1080-1100Mhz/860-970mV.

I would say this is pretty stable setup. Pool side 24h avg hashrate fluctuates in the range 54,1-54,4 kH/s

--CL 19 --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --REF 15600 --RFC 250

I am happy and have in my mind... "dont touch when things go smoothly".

Haha, ok ok, you convinced me ;-)

Check OP

And thank you!

Get yourself one, I'll be happy to mine some XMR for you

all you have to do is open cmd as admin and navigate to the folder where your memtweak is located

that would be:

cd path to folder

once you got into the folder, you just type in WinAMDTweak.exe --current

Something in mind ? ^^

Admin Rights. Only way is to open cmd as admin and type it manually.

Dude, if it was that simple, i wouldn't be asking. Running the WinAMDTweak.exe file opens a new window that closes immediately in a flash. It cannot be paused by the pause function in the batch file.

This below in the bat file doesn't work.

c:\\WinAMDTweak.exe --current
pause

Add pause to the batfile as I already said.
Getting a little kindergartenish.

Got it. Thanks! The screen flashes in an instant. Any ideas how to get a readout from --current?