trexminer / T-Rex

T-Rex NVIDIA GPU miner with web control monitoring page
2.63k stars 438 forks source link

6 card do a couple of GH/s Ethereum #505

Open BizWithBruce opened 3 years ago

BizWithBruce commented 3 years ago

I don't know if this is a problem, but every time this happens I restart t-rex and it is then changed to more expected hashes Sometimes my GTX1080 card thinks it is crazy and runs at a couple of GH/s which does not make sense when everything else is running at MH/s. I am scared the 1080 will DIE or commit suicide if this happens and I miss it and do not restart the miner manually. As far as I know I am mining Ethereum to ethermine.org 1 card is not suppose to do this at a couple of GH/s You should see the spikes on the graph on ethermine.org every time this happens.

Below is a copy of the file that was generated before I restarted the miner. I don't know if you would require any other info apart from this. I am only a NOOB YouTube crypto miner, I only deleted my wallet address from the below and my rig name, I don't know if this could be used by anyone, LOL

Please help if you can.

C:\Windows\system32>C:\Users\RigIntel\Downloads\t-rex-0.20.4-win\t-rex.exe -a ethash -o stratum+tcp://eu1.ethermine.org:4444 -u -p x -w rigamd --dag-build-mode 2,0,0,0,0,0 --fan t:65,t:55,t:55,t:65,70,65 --mt 0,0,0,0,6,2 --pl 60,53,58,56,50,75 --cclock -502,-502,-502,-502,135,0 --mclock 1150,950,950,950,750,400 20210614 07:45:06 T-Rex NVIDIA GPU miner v0.20.4 - [Windows] 20210614 07:45:06 r.acd264734a65 20210614 07:45:06 20210614 07:45:06 NVIDIA Driver v466.63 20210614 07:45:06 CUDA devices available: 6 20210614 07:45:06 20210614 07:45:06 WARN: DevFee 1% (ethash) 20210614 07:45:06 20210614 07:45:06 URL : stratum+tcp://eu1.ethermine.org:4444 20210614 07:45:06 20210614 07:45:06 Starting on: eu1.ethermine.org:4444 20210614 07:45:06 Using protocol: stratum1. 20210614 07:45:06 Authorizing... 20210614 07:45:06 Authorized successfully. 20210614 07:45:06 ApiServer: HTTP server started on 127.0.0.1:4067 20210614 07:45:06 --------------------------------------------------- 20210614 07:45:06 For control navigate to: http://127.0.0.1:4067/trex 20210614 07:45:06 --------------------------------------------------- 20210614 07:45:06 ApiServer: Telnet server started on 127.0.0.1:4068 20210614 07:45:06 ethash epoch: 421, block: 12633183, diff: 4.29 G 20210614 07:45:06 ethash epoch: 421, block: 12633183, diff: 4.29 G 20210614 07:45:07 GPU #0(002600): ASUS NVIDIA GeForce RTX 3060 Ti, intensity 22, auto-fan 65C, mclock 1150MHz, cclock -502MHz, pl 60% 20210614 07:45:07 GPU #1(002100): MSI NVIDIA GeForce GTX 1660 Ti, intensity 22, auto-fan 55C, mclock 950MHz, cclock -502MHz, pl 53% 20210614 07:45:07 ethash epoch: 421, block: 12633184, diff: 4.29 G 20210614 07:45:08 GPU #2(002500): MSI NVIDIA GeForce GTX 1660 Ti, intensity 22, auto-fan 55C, mclock 950MHz, cclock -502MHz, pl 58% 20210614 07:45:08 GPU #3(002800): ASUS NVIDIA GeForce GTX 1660 SUPER, intensity 22, auto-fan 65C, mclock 950MHz, cclock -502MHz, pl 56% 20210614 07:45:09 GPU #4(002900): NVIDIA GeForce GTX 1080, intensity 22, mtweak 6, fan 70%, mclock 750MHz, cclock 135MHz, pl 50% 20210614 07:45:09 GPU #5(002700): MSI NVIDIA GeForce GTX 1060 6GB, intensity 22, mtweak 2, fan 65%, mclock 400MHz, pl 75% 20210614 07:45:12 GPU #5: generating DAG 4.29 GB for epoch 421 ... 20210614 07:45:12 GPU #4: generating DAG 4.29 GB for epoch 421 ... 20210614 07:45:12 GPU #3: generating DAG 4.29 GB for epoch 421 ... 20210614 07:45:12 GPU #2: generating DAG 4.29 GB for epoch 421 ... 20210614 07:45:12 GPU #0: generating DAG 4.29 GB for epoch 421 ... 20210614 07:45:12 GPU #1: generating DAG 4.29 GB for epoch 421 ... 20210614 07:45:19 ethash epoch: 421, block: 12633185, diff: 4.29 G 20210614 07:45:20 ethash epoch: 421, block: 12633186, diff: 4.29 G 20210614 07:45:23 GPU #0: DAG generated [crc: 0318aa8f, time: 11550 ms], memory left: 2.70 GB 20210614 07:45:26 GPU #4: DAG generated [crc: 0318aa8f, time: 13786 ms], memory left: 2.75 GB 20210614 07:45:29 GPU #5: DAG generated [crc: 0318aa8f, time: 17492 ms], memory left: 832.31 MB 20210614 07:45:34 GPU #1: DAG generated [crc: 0318aa8f, time: 21752 ms], memory left: 767.81 MB 20210614 07:45:34 GPU #3: DAG generated [crc: 0318aa8f, time: 22299 ms], memory left: 771.56 MB 20210614 07:45:35 GPU #2: DAG generated [crc: 0318aa8f, time: 23106 ms], memory left: 767.81 MB 20210614 07:45:36 GPU #4: using kernel #4 20210614 07:45:40 GPU #0: using kernel #4 20210614 07:45:45 ethash epoch: 421, block: 12633187, diff: 4.29 G 20210614 07:45:45 GPU #5: using kernel #4 20210614 07:45:51 GPU #1: using kernel #4 20210614 07:45:51 GPU #3: using kernel #4 20210614 07:45:52 GPU #2: using kernel #4

--------------20210614 07:46:06 -------------- Mining at eu1.ethermine.org:4444, diff: 4.29 G GPU #0: ASUS NVIDIA RTX 3060 Ti - 61.16 MH/s, [T:46C, P:119W, F: 0%, E:577kH/W] GPU #1: MSI NVIDIA GTX 1660 Ti - 30.78 MH/s, [T:46C, P: 69W, F:21%, E:496kH/W] GPU #2: MSI NVIDIA GTX 1660 Ti - 29.50 MH/s, [T:44C, P: 74W, F:42%, E:476kH/W] GPU #3: ASUS NVIDIA GTX 1660 SUPER - 30.94 MH/s, [T:50C, P: 82W, F:25%, E:476kH/W] GPU #4: NVIDIA GTX 1080 - 10.70 GH/s, [T:45C, P:122W, F:70%, E:107MH/W] GPU #5: MSI NVIDIA GTX 1060 6GB - 22.75 MH/s, [T:42C, P: 90W, F:65%, E:320kH/W] Hashrate: 10.88 GH/s, Shares/min: 0, Avr.P: 466W, Avr.E: 23.3MH/W Uptime: 1 min | Algo: ethash | T-Rex v0.20.4

20210614 07:46:08 [ OK ] 1/1 - 12.34 GH/s, 174ms ... GPU #5 20210614 07:46:18 ethash epoch: 421, block: 12633188, diff: 4.29 G 20210614 07:46:20 ethash epoch: 421, block: 12633189, diff: 4.29 G 20210614 07:46:23 ethash epoch: 421, block: 12633190, diff: 4.29 G

Crisis83 commented 3 years ago

I have the same issue on a MSI 1080, it will occasionally freak out and report anything between the real hash rate (33-34 MH/s) and 10GH/s. It seems to happen more overclocked than when the core is at stock clocks. I had some stability issues with the card, and still do, but it's much better without any overclock so I keep it like that with just the memory tweak, which unfortunately won't take any level of memory overclock reliably (it starts with +1000 mem off-set every 10 tries so I gave up on the extra 3 MH/s).

It's honestly the only card I have any problems with, the 3080's, 3070 ti's, 2070S's and even a GTX 970 is fine for months at a time. Meanwhile the 1080 is the redheaded stepchild of the bunch reporting crazy hash rates at times or crashing every 3-5 days requiring a rig reboot if I want to bring it back online, thankfully the whole rig doesn't crash.

The card doesn't have a temperature issue (water cooled core, memory has aftermarket heatsinks and fan cooling), it just seems to be what it is. Kind "good" to hear others are having this issue, I have not tested if this reporting insane hash rates is T-rex specific problem or if it happens with other miners.

The reported hash rate shows on the miner console and I can see it on the pool side as well in the history. Shares are not affected, so it doesn't seem to be a GPU crash in a sense, that is probably a separate issue (crashes every 3-5 days)

hash rate 1080

Snip from a test where I ran the 1080 with a 2070S on a separate rig for a while.

trexminer commented 2 years ago

Could you try the latest version of t-rex (0.24.5)? I believe the issue should be fixed now.