Topic: TT-Miner 2022.4.1 KAWPOW, PROGPOW, ETHASH, ETCHASH, EPIC, SHA512256D, GHOSTRIDER - page 65. (Read 132189 times)

New release 18.10.46.35

   - command line version shows now the calculated values for CUDA gridsize and CUDA blocksize (these values are calculates for TT-Miner and may not perform well with other miners!)
   - minor adjustments for the new epoch 4 for Bitcoin Interest (ProgPoW)

Happy mining

Hi Xman69

I've just fixed an bug reported by an other user and uploaded the new release. Please retry if your problem is fixed too? If not can you please give me more information what the problem is please? Which pool do you use, which algo? Maybe you can share (or PM me) your command line?

Thanks.

Hello, I v got error : could not find entry point

any idea ?

The current release is 18.10.44.32

   - improved algorithm to calculate CUDA grid & block size (ProgPoW & Ethash).

This version will give you better hashrates compared to older version of the TT-miner if you do not set the CUDA grid or block size yourself in the command line. This improvement works for Ethash as well as ProgPoW algo.


Happy mining

The current release is 18.10.44.32

   - improved algorithm to avoid stale shares @ nicehash
   - show information if OC settings are detected as too tough

The miner shows if a GPU kernel couldn't run. In most cases the reason for this problem are the OC settings for that GPU, as a result the other GPUs will report errors as well. In this sample the OC settings for GPU#3 is so strong that the kernel failed to launch. As a result all other GPUs show the same issue. I recommend to lower the settings for GPU#3 first and run a test before you change the settings for the other GPUs. Unfortunately I cannot tell if the Core or the Mem setting causes the problem - if at all. Please keep in mind that GPU#3 is most likely GPU4 in MSI-Afterburner.


13:47:09 Received new job#: 0x87da2996d66b96613436324bf35dd1205f7813f1c13a2fc7d21494c5d31a3c65
13:47:10 Error: GPU[3] Cannot launch kernel. Please check OC settings for this GPU. GPU disabled.
13:47:10 Error: GPU[4] Cannot launch kernel. Please check OC settings for this GPU. GPU disabled.
13:47:10 Error: GPU[0] Cannot launch kernel. Please check OC settings for this GPU. GPU disabled.
13:47:10 Error: GPU[2] Cannot launch kernel. Please check OC settings for this GPU. GPU disabled.
13:47:10 Error: GPU[1] Cannot launch kernel. Please check OC settings for this GPU. GPU disabled.
13:47:10 Error: GPU[5] Cannot launch kernel. Please check OC settings for this GPU. GPU disabled.
13:47:10 Error: All GPUs are disabled. TT-Miner cannot continue and will exit now


Download:
https://TradeProject.de/download/Miner/TradeTec-Miner.zip

VirusTotal:
https://www.virustotal.com/#/url/0ec02fd95005c025162168c49c0442659268f7930805fd53216a6598a8660a32/detection


Happy mining

Version 18.10.44.31 released

- Fixes an issue when mining on nicehash
- Fixes a bug when the epoch changes

Download:
https://TradeProject.de/download/Miner/TradeTec-Miner.zip

VirusTotal:
https://www.virustotal.com/#/url/0ec02fd95005c025162168c49c0442659268f7930805fd53216a6598a8660a32/detection


Happy mining

Version 18.10.44.30 released

- complete redesign of the software (comes now in a single package for all, GUI & command line, CUDA 9.2 & CUDA 10.0, Ethash & ProgPoW)
- just a single executable for all algos and both CUDA versions (9.2 & 10.0)
- new '-A ALGONAME' option to define the algo you want to use for mining. Values for ALGONAME are:
   - PROGPOW-100
   - PROGPOW-92
   - ETHASH-100
   - ETHASH-92
- new option '-logpool' to enable complete pool-communication logging. You will find the logfile in the logs/miner folder
- new option -cbs, long form --cuda-block-size to define a fixed blocksize the miner should use
- new option -cgs, long form --cuda-grid-size to define a fixed gridsize the miner should use

You will find samples for each algo in the package that you can modify to fit your needs. The sample commandline will look like this:
TradeTec-MinerCmd.exe -A ETHASH-100 -P stratum+tcp://YOUR_WALLET.YOUR_WORKER@POOL_SERVER:POOL_PORT --list-devices

if you do not specify -cbd or -cgs the miner will try to calculate good performing values for grid and block size. Anyway you can play around with these values. Make sure that you use power of 2 values and look for a range for blocksize from 128 to 768.

Download:
https://TradeProject.de/download/Miner/TradeTec-Miner.zip

VirusTotal:
https://www.virustotal.com/#/url/0ec02fd95005c025162168c49c0442659268f7930805fd53216a6598a8660a32/detection


Happy mining

Sounds good. Please stay tuned, I will release a new package later today.

I tried my batch file and added :loop goto loop and for now its working. Will report if it crashes again.

Sorry- didn't noticed that you run the CUDA 10 release:

:loop
TradeTec-CmdProgPoW-C10.exe -P stratum+tcp://[email protected]:3910 --list-devices
goto loop

Tried your batch, got this. https://imgur.com/a/b7Aivcm

Do you use a batch to start the miner like this:

:loop
TradeTec-CmdProgPoW-C92.exe -P stratum+tcp://[email protected]:3910 --list-devices
goto loop


I'll check luckypool later today and let you know if I find any issues in the miner.

It just crashes, the miner shuts down. No it does not. When it was Equihash it was working fine, I used BCI official pool no issues.

Hi,

the screenshot looks good so far. Can you tell me more about what happened when the system crashes? Does the miner restart? I the meantime I will check if there are any issues if the miner points to luckypool. Have you tried any other pool in the past? Same issues?

https://imgur.com/a/j2v2DDx

I'm on LuckyPool

Hi Matico1,

Error: Code: 20 - Message: bad share: result hash is over share boundary (2): not accepted

is not an indication of a crash. This is just an error message that the share that was sent to the pool was output of the specs. Can you show a screenshot please? Can you please let me know which pool you're using?

I was playing a bit with settings PL 70-75%, CC and MC set to 0 and then tried to find the right spot, but couldnt make it stable, it keeps crashing. Got this message: Error: Code: 20 - Message: bad share: result hash is over share boundary (2): not accepted

Its funny that both miners are crashing.

I run my own 1060 at power 75% and core/mem both set to 0. I have not tried to OC them. If I need to OC then I would start to set mem tp +50 or maybe +100 any see how it works, until I have the sweet spot for mem. After that I would try to add some MHz to core. Please monitor not only the stability but also the hashrate. I noticed in the past that the hashrate may drop - even if you user higher frequencies.

TT crashed. Do you maybe have any idea how should I set things?

Wow. That's almost 20%! Anyway, if the miner crashes (doesn't matter which one) I guess that your OC settings are to high.