Topic: Custom RAM Timings for GPU's with GDDR5 - DOWNLOAD LINKS - UPDATED - page 32. (Read 155584 times)

It many cases the heatsink plate doesn't span over the memory, so there's no easy way to add thermal interface material.

What are you guys using for TIM pads for memory? Seems as though some cards come without cooling pads for some reason.

I'm doing some testing right now with Claymore 9.0 in Windows 7 x64.

So far what I can tell you, with Hawaii at least, the benefit from timings is negligible. It's probably because the bus is so wide anyway, they are bottlenecked by compute. I got way bigger increases by upping the core frequency. I'll report my findings after some more tests.

I was doing my testing with Samsung (K4G4), and just tried RRD=4 with Hynix H5GC4H24ARJ.  It doesn't work.

But I've already been using RRD = 4 for months because I've been using Stilt's strap. I am going to test both, I just want to know how to modify the output of the tool to change RRD=5 to RRD=4 so I can start testing.

Btw my 290's max mem clock is ~1500 so I probably need tighter than usual timings. The 390s can do over 1625 so they probably need RRD to be higher.

EDIT: nvm I just realized there's a windoze version of the ohgodadecode tool so I'll just check myself.

EDIT2: mmmkay that tool says that TRRD = 0 when i input 77713320000000000839472A50550C0B242045040046C40022BB1C005C0B14204A8900A00000012 0120C211E51192613

I'm guessing it only works for RX timings.

I'm just going to assume my original...uhh...assumption is correct.

Most samsungs handle tRRD=4, hynix and elpida doesn't or only a few probably. I'd suggest stick to tRRD=5 difference in hashrate is minor ~0.02MH but error rate with tRRD=5 is much lower.

Ok but how would I mix the old RRD with the new strap the tool spits out?

Meh.  The message delete function works fine... :-)

I've been experimenting with RRD=4, and at least for ETH mining, I can't see a material difference.  I also don't see a difference in stability or error rate, so it probably doesn't hurt to go with tRRD=4.

K yeah you make a very good point about it being more common and easier to find solutions for. I added another question to my above post.

I've been reluctant to post the link to this thread anywhere so that it (and your inboxes) doesn't get spammed with noob questions, but I did post a link to your fools' tool over on oc.net and told them credit belongs to nerdralph @ bitcointalk but asked them not to spam you. Just thought I should let you know.

I've been using Ubuntu for my mining rigs since I started a little over a year ago.  For the longest time I was more into RPM-based distros like Fedora, but it seems easier to find Ubuntu packages for developer tools than it was with Fedora.  Ubuntu also seems to have a larger user base than debian, so it's easier to find answers online to problems.  I've been using Linux for over 25 years now though, so it's hard for me to say what's the best distro for a noob.

@p4n

Yes the straps are always 48 bytes long. However, it is better to search for the 3-byte strings (see below quote) to find the strap you want rather than searching for 7771. They don't all necessarily start with that. It depends on the type of RAM your GPU has and which frequency range the strap is for.

Also it's possible your GPU's BIOS supports multiple RAM types. So for example, if you want to edit the timings of the 1126-1250MHz strap, and your card supports Elpida BBBG, Hynix AFR, and Hynix BFR, then you will have a strap after 48 E8 01 01, 48 E8 01 02, and 48 E8 01 03.

Make sure you edit the correct strap for the specific RAM ICs your card has (or just edit all 3 of them to be sure).

Also if you load a BIOS in HawaiiBiosReader, and then save it, it fixes the checksum automatically. No need to use a separate tool for that.


@nerdralph

Thanks for the reply! I had started to read up on distros and read something about Ubuntu being based on an unstable Debian distro and having lots of issues, so I was thinking a stable or testing distro might be better...and then installing a GUI like Gnome or something on top if I want to use one. Debian and Arch were recommended in the thing I was reading. So Ubuntu is good for getting to learn the nuts and bolts of linux?

Also, thanks for all the work you do for the community!

EDIT:

Okay so I tried putting Stilt's straps into the tool (among many others) and I noticed Stilt had RRD at 4, but the tool changed it to 5. Stilt did have other timings for FAW and 32AW (like 6) which were changed to 0, so I assume that's an improvement, but I'm wondering if I should leave RRD at 4?

For example, Here is the results for Stilt's strap for Hynix AFR


I bolded the number that I assume is RRD. I'd like to try the new strap, but with Stilt's old RRD. If I just change that 57 back to a 47 would that accomplish it?

Just updated the tool with the R9 code.


For a distro, I'd suggest Ubunutu 16.04.2.

It is a timing string for 1375 strap for Elpida EDW4032BABG in some R9 290x/390/390x/380.
Full timing table looks like this

For which kind of card/memory is that strap?

After reading OC.net hawaii bios editing post, and reading this post a few times, I've tried to learn to do it myself. Before starting to learn about custom timing, i've just copied lower clock timings into higher ones, with gains around 5% at same gpu/mem clocks, not bad. I'll try to explain how I did it, because it's been hard for me to understand at first how to do it, so I hope it helps other ppl.

Everything done under windows (I have ubuntu also, but i find myself more comfortable in windows, dont kill me for it).

First of all, I downloaded both original BIOS using GPU-Z (Button right to BIOS version). Save them as backup.

Then, open the one you want to modify with Hex Workshop
It looks (correct me please if I'm wrong), that some of the Hawaii timings use to start with 77 71 (that's been the case for my Hynix AJR), so I made a search (Ctrl+F) for Hex Values 7771.


Then, look at the 4 pair of numbers before the 77 71 pairs, select them with mouse and look at the right column "Data Inspector" for the int32 value, thats the Mhz of the memstrap
multiplied by 100. If you want to find the rest of the straps, put mouse cursor before 77 and add an offset (Ctrl+G) of 48 bytes (thats the case for my BIOS/memory type, if its not the case, search for the next 77 71 and use 4 pairs before).

For a R9 390X bios with Hynix AJR, straps are 800-900-1000-1125-1250-1375-1425-1500-1625-1750-2000.

So for this BIOS, i chose to copy the 1250 memstrap into the 1375,1425,1500 and 1625 ones. 1250 memstrap for me is this one: 77713320000000008CC5583460550F0F2C94B8070048C50022FF1C085C0F14205A8900A00000012 0120D23287B222D13



After this, you can also mod gpu/mem clocks, voltages and fan speed with HawaiiBiosReader

With all these changes you will need to fix BIOS checksum. Use the .exe OhGodACsumFixer.exe posted in OP by opening it with cmd. Just paste .exe in the same dir as the bios, go there with an administrator plivilege cmd and type OhGodACsumFixer.exe BIOSNAME. Check if checksum is OK using HawaiiBiosReader.



I'm totally a noob at this so please, correct me if im wrong. I haven't tried any bios with more than 1 memory type, that could change some values, so please, be careful.

Does this work using the lazy fools' tool?

On a semi-related note...is Debian stable a good distro to start using linux? Not for doing anything fancy...but just web browsing and email and maybe some mining and folding and more importantly getting familiar with the OS.

Micron:
You can find posts saying you can achieve 30mh with using 1750 strap above 2050MHz, but the micron cards that I tested were all unstable above 1950. No wonder the manufacturers limited even the 8GB versions to only 1650MHz...
Is there such a big variance among micron chips?

Anyone have some idea about Micro memory:
thanks!
i cant touch it more than 2000mhz for 6 card but 1 card is stable!!!

Question to gurus unrelated to timings.
It seems most (all?) RX 460 (not a sane choice for mining) in addition to empty I2C VO also contain GPIO VO of type 2(aka mvddc).
Raw voltage values in this object is 1350/1500 and at least to me it looks like mvddc.
Did somebody already looked at it already?

I've just updated my strapmod utility to handle R9 straps: