Since using NBMiner 41.x (lhr full unlock) my Gygabyte 3060ti with Hynix memory is very unstable. It starts with 55 MH/s but after 10-30 minutes it descends to 18 MH/s.
Same graphic card with Samsung memory works flawlessly at 61 MH/s
I tried very conservative OC values with no success
Yes.
I switched all the raisers and cables and even put the graphic card directly on the motherboard PCI slot, same instability.
The only thing I did not do was to rewrite HiveOS image, seemed a bit overkill to me since I have latest updates and NVidia drivers (510.73.05)
I kept the core clock as high as possible (1300) while lowering the memory OC to 800.
I also adopted version 42.2 with arguments “lhr-mode”: “2”, they claim it solves some instability issues.
I observed better stability with lolminer, core OC 1300 and memory OC 800-900 (conservative, could be slightly increased). Running for more than 2 hours
well, ive tried absolutely everything (updating kernel, reflashing new hiveos, lowering overclocks you name it) and im still getting the same error. It looks like im not the only person whos having errors with their 3060tis tho
My reply about the screenshot was to the other guy, but your clocks could use a little work to be optimal.
Remove power limits (not needed with locked core clocks)
Find the highest stable mem clock (if it’s not stable, reduce it)
Find the lowest core clock that maintains full hashrate (don’t reduce this after finding the optimal value)
Finally ended up with something stable. If anyone else is having issue the thing that worked for me was 1500 core clock and 1500 mem clock. Hope this helps someone
No effect here.
I’m all updated (online update, no msata/ssd reflash).
One of my rigs uses a b250c mobo and 12x GPUs. I rechecked every single usb cable and riser, was able to change the 20mhs from GPU #9 to GPU#7, replaced the 3060TI with a 1660TI and the issue reapeared in other 3060TI GPU. And the 3060TI that was taken out, was working at 61 MHs in other RIG as it’s second 3060TI.
So seems to me that is more related to 3060TI processing and not with the rig hw.
I did no changes or updates in the motherboard and it started few days from the 1st LHR fix.