RTX 3080TI just detect lhr everytime ETH hash below 70

Nvidia driver updated, HiveOS updated, command line:

i tried trex, nbminer, lolminer, gminer, i just get LHR detect with ALL miners, tried lhr tune1, 2, lhr mode 3,4,8 with Trex.

when i mine ERGO i get full hash 260 with no problem.

RTX 3080 ti Vision Gigabyte

Please help me <3

That is how LRH works. The card is detecting the ETH algo and is trying to limit it. The miner lowers tries to trick the card by lowering the hash rate, then it will increase it afterwards. If you are getting constant triggering of LHR then you need to adjust your overclocks.

use a locked core clock around 1500mhz, offsets let the core clock bounce around and triggers LHR.

i already tried 1100 core clock and 1500 core clock, both in these range activated the LHR =/

how is the procedure to test clocks with hive os?
i do this: stop miner, change overclock, then restart the miners.

is that ok?

with 950 lock core clock and 2000 memory clock, lhr detect too…=/

thats normal, the miners will continue to decrease the percentage until the lock stops happening. trex 24.7 has the highest hashrates currently. make sure youre on latest drivers too.

I can only tell you my tune, only one of which has to be adjusted to try and avoid lhr.

My EVGA 3080 TI FTW3 does 86-87+ mh without ever hitting lhr with CC=1300, Mem= 2800, PL=290(using about 250w)
My EVGA 3080 TI XC3 does 78-80 mh generally hitting 73.5 lhr within a half hour with CC=1300, Mem=2450, pl=290(using about 257w)

With the XC3 the core clock seems to be the trick to avoiding lhr lock.

Im with latest driver and miner and hiveos…any clock and mclock activate lhr, the lhr goes below 70 everytime :confused:

These are my settings, I had to play around with the core clock to avoid locks.

--lock-cclock 1450 --mclock 1200

Hope it helps.


Screenshot 2021-11-30 at 07-19-48 Ether 3 ethash 162 8MH s - Ether

1 Like

So the the “lhr-reduce-value”: “0.4” keeps it from dropping LHR at all (so you can adjust tune till it stops hitting lhr lock)?
or is it the value argument of 0.4?

Either way it’s brilliant. I’ve went from 423-426mh total, to 428-434+. Still working out the kinks though.

these are for windows? i dont know how to put this with hiveos, maybe nvidia msi command?

i just do everything like yours, but its just activating LHR from starting =/

has a chance that my rtx 3080 ti has some defect?

The only difference is that you double the memory in HiveOS.
So you would put 2400 for the memory value for the 3060 Ti.

Looks to me like you’re setting the 3080 ti to lhr mode 2, and then to 72%

I’d lose the “lhr-mode”: “2,1,1” command and set all the gpus to “lhr”: “75,75,75”

And I’d start the 80 ti mem at 2000, and try 1900 for a few minutes before you go the other way.

btw, my 3060ti is set at Core=1400, Mem= 2600, and PL at 135 (45+ mh)
my 3060’s are at Core=1500, Mem=2500, and Pl at 120 (36.4 mh)
Both with lhr set to 75%. I think the core being locked and it’s level has the most to do with setting off the lhr lock.

1 Like

Yep.
U can make a fine tune for every single LHR gpu by using this method. Key is locked core clock. If it is not, ur chance to get locked again increases because of high volatalite on mV which will drive miner to locked state again.
Also you may decrease the value once more by changing it until u see there is no “locked” state left.
After change your LHR% by increasing %0.1 and if u see u did not get locked nor decrease hashrate u may add another 0.1 to lhr.

Lock your cores and dont give them PL, they will find optimum mV by themselves.
and 2700 mem is too much. reduce it to 2.5k at the start and increase it 50 by 50 every 2 mins if you did not get locked.

2 Likes

in hiveos i just set the cclock and mclock, this is lock, i tried to put the cclorck and mclock command in T-rex but show a error that in Linux this command dont work