Pool: crazypool
TBMiner --algo ethash --hostname eu.crazypool.org --port 3333 --wallet %ETH_WALLET% --worker-name %computername% --api --api-ip 127.0.0.1 --api-port 1024 --xintensity 192 working fine. No changes in the syntax. Perhaps the port you are using is busy? 2 intances of the miner? Click on the example scripts: tbminer_crazypool_eth.bat tbminer_crazypool_etc.bat |
|
|
|
|
1. You can check in the logfile, or just restart the miner. If you don't want to autotune, specify the kernel manually with --kernel (0-7)
2. If your card trottle, increase the templimit or/and power
|
|
|
|
Does the kernel value determine the number of shares submitted per minute?
Think of it as 8 different programs in one. With different properties and strenghts, some are good on old cards, some are good on new cards. --kernel 0-2 are similar to lolminer, trex and gminer, 3-4 claymore-phoenix miner, and 5-7 Team black v1.00-v1.15. Written from scratch. Team black is a team of opensource developers, and the work on the newest LHR kernels might be opensourced. I'm running rtx 3080 now on the 1.17 with intensity of 200.
Your coreclock in too low. Run the program as admin and use --lock-cclock [1200,1200], then --lock-cclock [1300,1300] .. With autotune it will look something like this:  |
|
|
|
I did not specify a kernel speed as I was allowing the miner to select the best one.
Depends on the tdp(power), intensity, memory type and clocks. start it a few times and see what number is the best for the card.
--kernel 0 seems to best on gtx 1080 and 1080ti with the pill. default intensity (192) --kernel 7 crashing 41MHASH on the 1080ti, 34++ on 1080 [moderator's note: consecutive posts merged] |
|
|
|
708m [2021-10-20 04:48:36.749] GPU2 Cpu verification failed. Share not sent to the pool. Rejected!
Are these messages an indicator that the Memory Overclocks are too high for these two cards?
Yes, but instead of dropping the memclock you can try a lower kernel number --lock-cclock is helping for stability as well. |
|
|
|
835m [2021-10-20 06:57:14.476] GPU1 3060Ti 353.21 kH/W. 64.99 MH/s 64.99 MH/s 228/3/0 (98.70)
835m [2021-10-20 06:57:14.476] GPU2 3060Ti 423.85 kH/W. 64.85 MH/s 64.91 MH/s 253/6/0 (97.68)
Check the clocks on these cards, you shouldn't normally get rejected shares on this pool. Search in the log for cpu verification errors. Reduce the clocks. TBM will not send shares to the pool that fail CPU verification, but they will show as rejected in the stats. Here is a live test on v1.17 with default intensity (192), ~21 hours:  |
|
|
|
Is xintensity 192 still the recommended value for miningpoolhub?
For nvidia it should be good. Testing it now on miningpoolhub. The payout was lower than normal the last 24hours, but pool luck was bad as well. Ethereum difficulty has rised to new heights. Previous tests show that higher xintensities are better. f.ex 400 |
|
|
|
|
Linux build of 1.17 added
|
|
|
|
|
Does miningpoolhub pay for stale shares while mining ethereum and ethereum classic?
In the PPLNS STATS is sometimes see this:
(1 level stale 3.94%)
|
|
|
|
I can't push any of the cards higher or they will crash in T-rex. They all max out at different frequences.
Is there a clear answer to which kernel is the fastest (on a given card) or does that depend on core/memory speed?
This is not T-Rex. core/memory/power/xintensity/kernel the maximum speed depend on 5 variables. Why don't you try yourself And then there is mining pool and stale shares as well |
|
|
|
any solution for this? seem hashrate not read correctly on
Change to flexpool? Submit a bug to the ethermine team. you just wrote that after 5 minutes the reported hashrate was showing
if the hashrate is dropping, check the miner log for timout messages or restarts. Perhaps the cards are crashing because they are clocked to high, and the watchdog keep resetting. v1.17 has 8 kernels with different properties. low number more stable on high oc [moderator's note: consecutive posts merged] |
|
|
|
The memory speeds range all the way from 10180 to 11240 as you can see, thereof the different hashrates. All the cards are at their maximum memory speed.
maximum in msi afterburner? Or crash? On the 1660 bios mod, only kernel 0 is running stable at the highest clockrate. --kernel 0 |
|
|
|
RTX 3070 and 3060Ti still seem to not accept the same level of memory overclocks. They have to be adjusted down -100 to -250 MHz to get past the DAG generation phase and the decrease shows in the effective hashrate.
The easy fix is to run the lock-cclock, lock-mclock, power-limit after the dag buffer has been generated. But then you need to run the miner as admin, and let us clock the cards for you. The delayed clocking might be included in v1.17 |
|
|
|
HELP! It seems that --worker_name is no more recognized in ver 1.16
I got this error on startup and miner won't start
rename --worker_name to --worker-name |
|
|
|
But when you reach memory speeds of around +1500 or higher you need to push the core above 1200Mhz to reach maximum speed. I found you need atleast 1470Mhz for the GPU not to bottleneck the memory when the memory is at +2000.
you can try to play with the --kernel number. Low kernel number, stable on higher clocks |
|
|
|
When you lock the card in MSI Afterburner you override the powerlimit. The powerlimit doesn't effect the powerconsumption at all. It's basically the same thing as using --lock-clock in TBM or with nvidia-smi. All the cards are locked in MSI Afterburner.
TBMiner v1.16 support setting the powerlimit too. If you set the lock clock too high, the core will trottle. Higher coreclock more heat, more cooling needed, so you want stable clocks, stable fanspeeds. |
|
|
|
|
Your card use less power and heat with locked core clock
to lock the clocks run the miner as admin and add this:
--lock-cclock [[1200,1200],[1200,1200],[1200,1200],[1200,1200],[1200,1200],[1200,1200]]
you need to find the correct lock clockrate at the right powerlimit
When testing you should also check in the logfile if one of the gpu's times out and restarts, or the miner is restarting. A timout can cause a 3 minute ++ loss of hashrate
|
|
|
|
 I just started it for the image but it's above 111MH/s on atleast one of the GPUs (MSI Ventus 3080). Still doing the serious mining on T-rex for now but might change for a new test soon. That is a really good hashrate.  |
|
|
|
Gives around 111.5MH/s (reported speed).
That would be a new record hashrate. Why don't you upload a screenshot? Poolside has also been improved on many pools with --xintensity 192 (default) My mixed card rig 1070ti x 3, 3060 x 1 , 2060 x 1 running on v1.16 is doing the same speed with --xintensity 192 --xintensity 400 in v1.15. ' Less stale shares, more profit. On AMD the last --xintensity change wasn't included in the build, so use manual tuning. Default -1 can be unstable. |
|
|
|
|
Show Posts
