T-Rex 0.26.8 ETHW, ETC (+dual mining) GPU miner

[lttsi]

Help me config P106-100 for x16rt (core,mem,power)
My hashrate is unstable ,speed 12-15M ...not stable hashrate.

[1714241418]

1714241418

[1714241418]

1714241418

[1714241418]

1714241418

[tbearhere]

What I need is  a command  like......  on disconnect disable devices until reconnect. Anyone know? thx  

Make Nicehash as failover pool.

No thx... I want to stay with the pool and on disconnect have the miner spin down until reconnect.

It will reconnect again to the first pool short time after connection became possible.

Thanks... I made this work around.  

:loop
T-REX-0.9.2.exe -a x16rt -d 0 -i 16 --exit-on-connection-lost -o stratum+tcp://us.bsod.pw:2532 -u address  -p x
taskkill -t -f /im T-REX-0.9.2*
timeout -t 15
T-REX-0.9.2.exe -a x16rt -d 0 -i 16 --exit-on-connection-lost -o stratum+tcp://us.bsod.pw:2532 -u address  -p x
goto loop

At first disconnect .. the cards are still hashing. Then t-rex app. tries to reconnect for 20 seconds. Then it shuts down the miners. Next line it tries to reconnect with miners off .. but won't hash again until reconnect.

[tbearhere]

Help me config P106-100 for x16rt (core,mem,power)
My hashrate is unstable ,speed 12-15M ...not stable hashrate.

It's to be expected... but if you put this command in it will smooth out your average reading in the cmd window and doesn't decrease your hashrate at the pool.
--hashrate-avr 20000     It will give you a 6 hour adverage.  

[dragonmike]

I'm getting weird nvlddmkm errors when using T-Rex, every day, several times. They tend to break the miner, which then has to restart.

They all start with this in the event viewer:

The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

the error could then be any of these:

\Device\UVMLiteProcess12
Graphics SM Warp Exception on (GPC 2, TPC 0): Misaligned Address

The message resource is present but the message was not found in the message table

\Device\UVMLiteProcess12
Graphics SM Global Exception on (GPC 2, TPC 0): Physical Multiple Warp Errors

The message resource is present but the message was not found in the message table

\Device\UVMLiteProcess12
Graphics Exception: ESR 0x514648=0x9000f 0x514650=0x24 0x514644=0xd3eff2 0x51464c=0x17f

The message resource is present but the message was not found in the message table

\Device\UVMLiteProcess13
Graphics SM Warp Exception on (GPC 2, TPC 0): Out Of Range Address

The message resource is present but the message was not found in the message table

\Device\UVMLiteProcess13
Graphics Exception: ESR 0x514648=0x108000e 0x514650=0x20 0x514644=0xd3eff2 0x51464c=0x17f

The message resource is present but the message was not found in the message table

Is anyone else experiencing this?
Is it a driver issue or is T-Rex messing something up?

Was just wondering if anybody else had been experiencing this at all.
@Trex, is that something the miner is causing, or is it overclock related?... if at all? I've tried to google it but can't seem to get a proper/decent solution (nor explanation for that matter).

[xlockdownx]

I having a similar problem for 2/3 days , at somepoint the miner seems to freeze and wont hash.
does anyone have this problem ?
or can help me fix it ?
Thx

BTW , im mining Ravencoin

[hustleman]

How to remedy the command line for pools that require a "c=coin" entry to determine what coin to mine???  miner does not accept -c=rvn, ect.

[dragonmike]

How to remedy the command line for pools that require a "c=coin" entry to determine what coin to mine???  miner does not accept -c=rvn, ect.

it's not -c=rvn you have to type.
It's -p c=rvn
That specification is within your password field. You can often add different specs within your password field, eg:
-p mypassword,c=rvn,d=128 (this would specify a password, a payment currency and a fix difficulty).

Look at the exact terminology the pool tells you to specify.

[mitto]

Hello experts,
i'm trying to use t-rex 0.9.2 with nvidia geforce gtx690.
I'm using ubuntu 18.04 bionic
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 418.56       Driver Version: 418.56       CUDA Version: 10.1     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GT 730      Off  | 00000000:01:00.0 N/A |                  N/A |
| 63%   70C    P0    N/A /  N/A |    580MiB /  2001MiB |     N/A      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 690     Off  | 00000000:08:00.0 N/A |                  N/A |
| 30%   24C    P8    N/A /  N/A |     11MiB /  1999MiB |     N/A      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 690     Off  | 00000000:09:00.0 N/A |                  N/A |
| 30%   25C    P8    N/A /  N/A |     11MiB /  1999MiB |     N/A      Default |

when i start t-rex with all the pool parameter i get the error:


20190427 16:30:30 ERROR: Can't initialize device [ID=0, GPU #1], cuda exception in [trexInitializerM, 207], unspecified launch failure
20190427 16:30:30 WARN: Messy shutdown...
20190427 16:30:30 Authorized successfully.
20190427 16:30:30 ERROR: Can't initialize device [ID=1, GPU #2], cuda exception in [trexInitializerM, 207], unspecified launch failure
20190427 16:30:31 Main loop finished.
20190427 16:30:31 ApiServer: stopped listening on 0.0.0.0:4067

what i'm doing wrong?, what i should try to do?
thank you

[sergneo]

T-Rex miner for modern NVIDIA GPUs - Maxwell and newer (Pascal)

[Koltan]

Is it possible to use T-Rex miner over a proxy connecton? I can't find any command line options for that.

[tcostik]

Has anyone noticed any weird behavior on the latest (430.39) Nvidia driver? My 1070ti's and 1080's seem to be working, but my 2060 isn't. Or at least, I don't think it is. It shows up in device manager, afterburner, and t-rex, and it says it mining, but my temps are sitting at idle (~32c), and my output on Minermore reads like it's not mining.

I made a restore point so I'll roll back if I have to, but I want to A. Give a heads up to others, and B. see if anyone else has run into this.

*edit*

It definitely isn't working. Every other card is pulling the appropriate amount of power, but the 2060 is only pulling 52w watts. Time to roll back.

[P00P135]

Has anyone noticed any weird behavior on the latest (430.39) Nvidia driver? My 1070ti's and 1080's seem to be working, but my 2060 isn't. Or at least, I don't think it is. It shows up in device manager, afterburner, and t-rex, and it says it mining, but my temps are sitting at idle (~32c), and my output on Minermore reads like it's not mining.

I made a restore point so I'll roll back if I have to, but I want to A. Give a heads up to others, and B. see if anyone else has run into this.

*edit*

It definitely isn't working. Every other card is pulling the appropriate amount of power, but the 2060 is only pulling 52w watts. Time to roll back.

Updating drivers isnt going to give you magical increased hash speeds.  Just use whats been tested and known to work.

[joseph32]

Has anyone noticed any weird behavior on the latest (430.39) Nvidia driver? My 1070ti's and 1080's seem to be working, but my 2060 isn't. Or at least, I don't think it is. It shows up in device manager, afterburner, and t-rex, and it says it mining, but my temps are sitting at idle (~32c), and my output on Minermore reads like it's not mining.

I made a restore point so I'll roll back if I have to, but I want to A. Give a heads up to others, and B. see if anyone else has run into this.

*edit*

It definitely isn't working. Every other card is pulling the appropriate amount of power, but the 2060 is only pulling 52w watts. Time to roll back.

Since 430 there are few restrictions in the driver. Try to start the cmd with Admin rights and check if it works again. If not, DDU the 430 and install anything below (425 or 419).

[enginama]

phi1612 says its supported but when setting algo at phi1612 miner doesnt recognize. Does the miner auto-recognize phi1612 when you enter phi as the algo?

[Dr_Victor]

We do need miner for HoneyComb, please!

[dragonmike]

I keep getting this error message:

"20190511 14:39:32 ERROR: Can't find share with device [ID=4, GPU #4], cuda exception in [Algorithm::find_shares, 197], an illegal memory access was encountered"

T-Rex 0.9.2, mining x16rt (Veil).
5x 1080, +115/-500 85% PL

Any ideas?

[FloppyPurpleGherkin]

I keep getting this error message:

"20190511 14:39:32 ERROR: Can't find share with device [ID=4, GPU #4], cuda exception in [Algorithm::find_shares, 197], an illegal memory access was encountered"

T-Rex 0.9.2, mining x16rt (Veil).
5x 1080, +115/-500 85% PL

Any ideas?

turn the core oc down to +50 or 0 and it'll work.

[trexminer]

I'm getting weird nvlddmkm errors when using T-Rex, every day, several times. They tend to break the miner, which then has to restart.

They all start with this in the event viewer:

The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

the error could then be any of these:

\Device\UVMLiteProcess12
Graphics SM Warp Exception on (GPC 2, TPC 0): Misaligned Address

The message resource is present but the message was not found in the message table

\Device\UVMLiteProcess12
Graphics SM Global Exception on (GPC 2, TPC 0): Physical Multiple Warp Errors

The message resource is present but the message was not found in the message table

\Device\UVMLiteProcess12
Graphics Exception: ESR 0x514648=0x9000f 0x514650=0x24 0x514644=0xd3eff2 0x51464c=0x17f

The message resource is present but the message was not found in the message table

\Device\UVMLiteProcess13
Graphics SM Warp Exception on (GPC 2, TPC 0): Out Of Range Address

The message resource is present but the message was not found in the message table

\Device\UVMLiteProcess13
Graphics Exception: ESR 0x514648=0x108000e 0x514650=0x20 0x514644=0xd3eff2 0x51464c=0x17f

The message resource is present but the message was not found in the message table

Is anyone else experiencing this?
Is it a driver issue or is T-Rex messing something up?

Was just wondering if anybody else had been experiencing this at all.
@Trex, is that something the miner is causing, or is it overclock related?... if at all? I've tried to google it but can't seem to get a proper/decent solution (nor explanation for that matter).

Hi dragonmike, I'm not sure what is causing those errors. What GPU is that?

[trexminer]

phi1612 says its supported but when setting algo at phi1612 miner doesnt recognize. Does the miner auto-recognize phi1612 when you enter phi as the algo?

Yes, phi is an alias for phi1612

[dragonmike]

I'm getting weird nvlddmkm errors when using T-Rex, every day, several times. They tend to break the miner, which then has to restart.

They all start with this in the event viewer:

The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

the error could then be any of these:

\Device\UVMLiteProcess12
Graphics SM Warp Exception on (GPC 2, TPC 0): Misaligned Address

The message resource is present but the message was not found in the message table

\Device\UVMLiteProcess12
Graphics SM Global Exception on (GPC 2, TPC 0): Physical Multiple Warp Errors

The message resource is present but the message was not found in the message table

\Device\UVMLiteProcess12
Graphics Exception: ESR 0x514648=0x9000f 0x514650=0x24 0x514644=0xd3eff2 0x51464c=0x17f

The message resource is present but the message was not found in the message table

\Device\UVMLiteProcess13
Graphics SM Warp Exception on (GPC 2, TPC 0): Out Of Range Address

The message resource is present but the message was not found in the message table

\Device\UVMLiteProcess13
Graphics Exception: ESR 0x514648=0x108000e 0x514650=0x20 0x514644=0xd3eff2 0x51464c=0x17f

The message resource is present but the message was not found in the message table

Is anyone else experiencing this?
Is it a driver issue or is T-Rex messing something up?

Was just wondering if anybody else had been experiencing this at all.
@Trex, is that something the miner is causing, or is it overclock related?... if at all? I've tried to google it but can't seem to get a proper/decent solution (nor explanation for that matter).

Hi dragonmike, I'm not sure what is causing those errors. What GPU is that?

5x EVGA GTX 1080 SC.
It's weird isn't it. Just like something's messing up the driver.
I'll try lowering the core substantially for starters, we'll see if it has any impact on this and the other crashes I'm having.