Low hashrate only with the 3060 Ti LHR (Vr.2) MSI Gaming X (two fans) #910
Comments
|
i had a same card with the same issue, try Ventus BIOS. |
|
You mean to do a BIOS mod? I have seen a few videos on youtube, but I cannot replicate the steps because I saw them incomplete. |
|
The easiest way:
1) Install Rave OS
2)Save original bios to the PC folder as backup
2) flash Ventus bios (any of them d3/d2)
3) Yes , you can return it back even if results is NG
…Sent from my iPhone
On 6 Dec 2021, at 00:58, Rodkl ***@***.***> wrote:
You mean to do a BIOS mod? I have seen a few videos on youtube, but I cannot replicate the steps because I saw them incomplete.
Do you have the instructions or the step by step to do it? There are many BIOS versions of the ventus x2.
The risk of applying the wrong one is great, right? It can be replaced by the previous one in case the wrong one has been applied, right?
I used the --pl because it helps prevent high energy peaks.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
|
it Works GREAT! amazing! i flash them with BIOS's from TechPowerUP (Version: MSI.RTX3060Ti.8192.210519). |
|
One more detail that I did not mention, I did it from windows, deactivating the antivirus and antispyware, and disabling all the GPUs (I don't have a cpu with integrated graphics) from the "Device Manager". |
|
It’s a bit complicated, it is working for some cards, normally with same TDP (I think it is related to q-ty of PCI power connectors , where one 8pin =200w) .
I tried to flash asus TUF using ROG bios with no success.
Well, speaking about EVGA bios , are you going to apply MSI bios to EVGa in order to decrease consumption? I haven’t catch the idea😀
Personally , I am looking for good bios with Hynix timings, I see Some new card can perform up to 48 mm/s but this is mostly because of high memory overclock, or maybe result of good silicon
Lottery.
…Sent from my iPhone
On 6 Dec 2021, at 07:46, Rodkl ***@***.***> wrote:
it Works GREAT! amazing! i flash them with BIOS's from TechPowerUP (Version: MSI.RTX3060Ti.8192.210519).
I have one more question for you:
I have seen that the consumption fell practically 25 - 28 watt and with 43.5 - 44.20 mh / s. I wonder if I could update the BIOS of the EVGA that is giving me between 45.8 - 47.10 mh / s looking to lower the consumption ... BUT, I see in TechPOwerUp that the BIOS version for the EVGA 3060 Ti XC is the same that I have, Will it be useful to update trying to obtain less consumption, even if it is the same?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
|
I can confirm that the high Hashrate (moderately stable) is due to the manufacturer of the vRam, in the case of my EVGA it is Samsung, for this reason I understand that it reaches 47 mh / s.
|
|
Right, i didn't realize the number of fans could matter! Next weeknd (maybe XMAS) i will take 6 pack of beer and do some study)) "I am interested in knowing if you can "mix" the BIOS between manufacturers" - definitely you can! good example is 1660S, there two good BIOS for Hynix memory which give you about 35 Mh/s , one is from Palit another from MSI and looking on forum pages about 90% all vendors have been successfully flashed with this BIOS . Bad side of this some mistakes like wrong power consumption data and fan settings. But this is working 100% |
|
Well, under the same concept that the BIOS of different manufacturers or assemblers can be mixed; "Then I could update the BIOS of the EVGA 3060 ti XC LHR (2 fans and 1 8-pin connector) by the BIOS of the MSi 3060 Ti Ventus X2 OCV1LHR (2 fans and 1 8-pin connector) in search of reducing consumption and temperature of the EVGA XC ?. Here comes an important new detail: in TechPowerUp, although the BIOS of the EVGA LHR does not exist, my EVGA LHR has Samsung vRam, and I am not sure if only EVGA can handle Samsung vRam. The Bios of the MSi 3060 Ti Ventus X2 OCV1 LHR if handle Samsung, micron, Hynix (picture attached). Why ask? Because EVGA XC has a poor heatsink, then I would love to bring the power of the MH / s (45.90 - 47.10) from the EVGA towards the 2 MSi Gaming X that have a very good heatsink.
|
|
I found it, I understand that if this BIOS (EVGA) could be applied towards the MSI Gaming X gpu, because the EVGA BIOS supports hynix memories, and vice versa it could also. It matches everything with the BIOS of my EVGA. |
Hi there Rodkl, how are your cards running with flashing the Ventus bios? I have 8 off the same cards you're using and they totally just Mac out at 37/38 Mh 😞 |
|
Hello detroy! They turned out very well, but you should "test" in an "almost perfect" way which is the correct OC/UV for each one, because they tolerate in a very different way ... in one it gave me between 43.68 - 45.10 mh/s when Before, it gave me between 40 - 41.50 mh/s. So I decided to "sacrifice" 2 mh/s to find stability with the following OC/UV: --kernel 4 --lhr-tune 75.4 --lock-cclock 1245 --lock-cv 750 --mclock 700 --fan t : 55 [30-75] --temperature-limit 62 --temperature-start 50. I think that you must first find the crash limit and maximum temperatures according to the ambient temperature, then gradually reduce it. In my case in my city, in 80% of the year the temperatures are very high, between 33 ° to 45 ° (under shade), but I always manage to keep them between 55 ° and 60 ° (maximum), but in the same way the miner "pauses" the process until the GPU cools down |
Maybe)) |
|
@Rodkl When you flashed your Gaming X with Ventus BIOS, did you have the same warning/error: |
|
Of corse , use force flash option
…Sent from my iPhone
On 13 Dec 2021, at 19:17, Alexey S. ***@***.***> wrote:
@Rodkl When you flashed your Gaming X with Ventus BIOS, did you have the same warning/error:
WARNING: Firmware image PCI Subsystem ID (1462.C972) does not match adapter PCI Subsystem ID (1462.3973).
C972 is from the one that you suggested: https://www.techpowerup.com/vgabios/236055/msi-rtx3060ti-8192-210519
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
|
Sorry for the delay in responding. It is correct that this warning message appears, update the BIOS without problems, it will stay working. And to be even more precise, the best BIOS that suited my MSI 3060 Ti Gaming X (LHR) GPU was the PALIT Dual OC (LHR) GPU, it gives 10% more mh / s than the MSI. Ventus X2 and consumption is a little better (lower). |
|
@Rodkl Thank you for your help. I tried both roms that you proposed. With MSI Ventus the card was super hot, I basically got burnt when touched the backplate. I am trying Palit now, the card is much colder. Btw, Both ROMs report incorrect power consumption. In reality they pull around 150W with --lock-cclock 1305 |
|
No problem @stralex7 ! Ask, how did you get the real consumption data in 150w? with the GPU-Z? Because keep in mind that the GPU BIOS is the one that "reports" the watt consumption to the GPU-Z app. I mean, actually the only way to check the actual consumption is by using a consumption meter, the kind that measure consumption from the wall. Did you verify it with one of those meters? |
|
@Rodkl The real power consumption through an electricity meter off the wall. Removed the card from the rig and added it back. |
|
I had the same suspicion as you, but you saved me the trouble of measuring it, I was about to buy 1 to test them. |
|
Thanks, I might give it a try, but rather just sell the card :) About clocks, I lock them at 1305 Mhz and it does not move from there, compare to the original rom where the core clock fluctuates, so you need to specify the maximum, similar to non-LHR 30s |
|
Given all this talk about overclocking I though that it will be good to share a tool we developed to assist miners with testing various settings. See demo video @ https://youtu.be/rfgHEE5komM Link to software @ https://github.com/MOCO-MHz We were able to map out profitability for a number of oc settings
|
|
@stralex7, you right. If trex is reporting incorrect then MOCO profit calculations are incorrect. We have been thinking of linking the software to a $15 sonoff pow R2 power off the wall device to get a rigs full usage and then optimize accordingly. Possibly room for development later on...... Anyone seen the post on LHR 100 invaild share trip? We need someone to reolicate that in windows! |
|
Hi, i was using msi rtx 3060 ti gaming x LHR with ventus bios. i had no problem for today. Now some cards is not working on hiveos. They are working on windows with 47 mh. i changed their bios from ventus to original but they are working about 37 mh with original bios. Does anyone have same issue? |
|
Hello guys, after LHR unlock, how yours hashrate now? |
|
Wonderfully High! Only gpu 1 has vRam Hynix Rev. 1. |
|
3060ti msi gaming x and original bios? |
No, it is not the Original BIOS. At the beginning of this topic, I explain what I did and the improvement I got by modifying the BIOS. I think I also attached the Bios used (Msi Ventus x2 OC) |
|
it does not work with original bios, i tried and i could not pass the LHR. it could reach about 45-46 mh with trex and nbminer. i am still using msi rtx 3060 ti gaming x LHR (2 fans) with Ventus bios. With ventus bios 59.5 mh it takes. |
Me too |
Having issues with Palit 3060TI dropping hashrate to 20MHs and it's being one card after another. Can you get a fresh copy of that BIOS ? I'm running original 94.04.6B.00.F4 . |
You can try to get MSI Ventus X2 OC BIOS from TechPowerUp official website: https://www.techpowerup.com/vgabios/236055/msi-rtx3060ti-8192-210519 |
|
I'm having the same issue. I tried flashing it with Ventus BIOS. Works great at first, but after a rig reboot it shows gpu MALFUNCTION and I cannot do anything to make it work. I flashed back the original bios for now and it's working again but didn't fix my hashrate issue. Any help? |
Hi everyone!!
I have the problem that only with the MSI gaming X 3060 ti lhr, they give low hashrate.
The gpu "2" generates 37.7 - 38.6 mh / s at 125 - 130 watts with the following settings: --lhr-tune 74.9 -d 2 --lock-cclock 1380 --lock-cv 768 --mclock 420 --pl 80 --kernel 4 --fan t: 55 [30-75] --temperature-limit 62 --temperature-start 50. This Gpu has Hynix memories
If I modify the "Mclock" to this gpu to 980, the hashrate decreases. If I modify the --pl or the --Lock-cclock there is no change at all ... even if I only leave the "Mclock" and the --lhr-tune with the values described above without "caring" abo
Low hashrate only with the 3060 Ti LHR (Vr.2) MSI Gaming X (two fans).pdf
Low hashrate only with the 3060 Ti LHR (Vr.2) MSI Gaming X (two fans).pdf
ut the consumption, but apparently the miner It uses the GPU resource inefficiently, the same does not happen if I use NBminer, only the hashrate is even lower than if I use T-rex.
I will attach an image of how the MSI GPU "processes" compared to the EVGA, I see a great fluctuation of the GPU the MSI Gaming X (The Msi ventus is not the same) but I can not find a way to correct it.
Similar situation is repeated with another Gaming X but with the following configuration: --lhr-tune 75.2 -d 0 --kernel 4 --lock-cclock 1380 --lock-cv 737 --mclock 800 --pl 104 - fan t: 55 [30-75] --temperature-limit 62 --temperature-start 50.
It generates between 40.90 - 41.85 mh / s, also with Hynix memories.
BUT totally different situation happens to me with an EVGA XC with Samsung memories: - lhr-tune 75.7 -d 1 --kernel 4 --lock-cv 750 --lock-cclock 1380 --mclock 1400 --pl 72 --fan t: 58 [30-80] --temperature-limit 62 --temperature-start 50.
This gpu generates from 45.8 - 47.10 mh / s.
ANOTHER different situation happens to me with a PALIT with Hynix memories, with the following Configuration: --lhr-tune 75.7 -d 3 --kernel 4 --lock-cv 775 --lock-cclock 1380 --mclock 830 --pl 72 --fan t: 58 [30-80] --temperature-limit 62 --temperature-start 50.
This Gpu generates from 43.20 - 44.74.
The text was updated successfully, but these errors were encountered: