EWBF's CUDA Zcash miner

[sublimus]

Hi
Sorry for my Eng  
When i start nheqminer 0.5c on computer with win 10, i7 6 core and Asus Strix gtx1070 all work fine.
When i start this program on my old computer with win 10, c2q and gtx750 ti I must add -cv 1 and work (slow, but working)
When i put to my old computer new MSI gtx1070, install new graphic driver, i have this error "CUDA error 'misaligned address' in func 'eq_cuda_context::solve' line 988"
I try reinstall drivers, rebooting systems, update system, using another version nheqminer, using all -cd, cv, cx etc, kissing my computer, kicking my computer, and all time is this error...
And i was downloading your's program to test, and I have:
(For me problem is with drivers, because on this computer with GTX750 Ti all was fine, but do you have any suggestion?)


EWBF's Zcash CUDA miner. 0.3.3b         |
+-------------------------------------------------+
INFO: Server: eu1-zcash.flypool.org:3333
INFO: Solver Auto.
INFO: Devices: User defined.
INFO: Temperature limit: 90
INFO: Api: Disabled
---------------------------------------------------
INFO: Target: 00083126e978d4fd...
INFO: Detected new work: ce839587b04bebd120f6
CUDA: Device: 0 GeForce GTX 1070, 8192 MB
INFO: Detected new work: c005a82f3de9a9f7d31f
CUDA: Device: 0 Selected solver: 0
CUDA: Device: 0 Thread exited with code: 77
Temp: GPU0: 39C
GPU0: 0 Sol/s
Total speed: 0 Sol/s
Temp: GPU0: 41C
GPU0: 0 Sol/s
Total speed: 0 Sol/s
Temp: GPU0: 42C
GPU0: 0 Sol/s
Total speed: 0 Sol/s
ERROR: Looks like GPU0 are stopped. Restart attempt.
INFO: GPU0 are restarted.
CUDA: Device: 0 User selected solver: 0
CUDA: Device: 0 Thread exited with code: 46
Temp: GPU0: 41C

Kill your computer. 

[1714093802]

1714093802

[1714093802]

1714093802

[1714093802]

1714093802

[1714093802]

1714093802

[wojzet]

Kill your computer. 

I'm thinking about this
But first i would like start Zcash miner on this
I don't have idea what is wrong... On new computer work, on old with this same system dont work... But when was gtx 750 ti on this computer all was fine...

I start this program
miner.exe --server eu1-zcash.flypool.org --user xxxxxxxxxxxxxxxxxx.pecet1070 --pass x --port 3333 --cuda_devices 0
Config is:
C2Q 2.88 ghz 4 core
7 gb ram (working on this since 2010 )
hdd 250 gb
OCZ Modular 650W for gaming
Gigabyte GA-EP35-ds3l (Intel P35)
Fresh instalation and full update Windows 10 Pro
in this moment MSI GTX 1070 (when was MSI GTX 750 Ti all was fine)
Graphics driver is 382.53

[Rodger9]

wojzet

Your clocks are too high, hence your miner turns off right away. Adjust the clocks to lower speed and you should be fine.

[Taxidermista]

Yes teamviewer uses gpu power to render the desktop.  If you change your API address to the actual IP of the mining rig and view the api from another pc, with teamviewer not connected, you will find that your hash goes back up. 

I've used --api in my nvidia rigs but I cannot connect remotely using my network ips, only with 127.0.0.1 at same the rig.

[nUm81]

Yes teamviewer uses gpu power to render the desktop.  If you change your API address to the actual IP of the mining rig and view the api from another pc, with teamviewer not connected, you will find that your hash goes back up. 

I've used --api in my nvidia rigs but I cannot connect remotely using my network ips, only with 127.0.0.1 at same the rig.

you need to use --api xxx.xxx.xxx.xxx:42000 in your command line. 

xxx.xxx.xxx.xxx needs to be replaced with the actual local IP address of the miner, if you have DHCP you will need to fix the address so it does not change.

Using 127.0.0.1 restricts the API to local host only which is what happens if you only specify --api

[sreg0r]

Yes teamviewer uses gpu power to render the desktop.  If you change your API address to the actual IP of the mining rig and view the api from another pc, with teamviewer not connected, you will find that your hash goes back up. 

I've used --api in my nvidia rigs but I cannot connect remotely using my network ips, only with 127.0.0.1 at same the rig.

you need to use --api xxx.xxx.xxx.xxx:42000 in your command line. 

xxx.xxx.xxx.xxx needs to be replaced with the actual local IP address of the miner, if you have DHCP you will need to fix the address so it does not change.

Using 127.0.0.1 restricts the API to local host only which is what happens if you only specify --api

Try using a wildcard mask.

Code:

-–api 0.0.0.0:42000

[cryptobob88]

I am getting 0 Sol/s on my 1080TI asus strix.... I reinstalled the drivers 4-5 times now

used different pool, nothing. the card is on stock settings. I tried all version of the miner, and nothing... what am I doing wrong?

please let me know

Edit: I'm getting: Thread exited code 77 miner, whenever I start the miner.

The card is not overclocked, it's on stock settings.

[kanawut]

I have a problem. While running the EWBF for about 20 hours it just freeze and stop working with no reason. Is there any way that can be use to restart the software every 2 hours?

[toptek]

I have a problem. While running the EWBF for about 20 hours it just freeze and stop working with no reason. Is there any way that can be use to restart the software every 2 hours?

you getting ERROR 46 , with my one  GTX 1060 . I'm having the same ISSUE but after 20 mins it stops hashing and says dead in awesome miner but works fine if i mine eth which i don't mine much .


it only stops if I use this software miner ..while mining for no reason i can find .. and it's in a RIG with 4 AMD Rx 470 CARDS ..

[Southy]

Same can only seem to get the 127.0.0.1 api working have tried the workers IP etc.. checked ports, not sure what i might be doing wrong to be able to view on seperate computer, trying to figure it out =/

[Southy]

Same can only seem to get the 127.0.0.1 api working have tried the workers IP etc.. checked ports, not sure what i might be doing wrong to be able to view on separate computer, trying to figure it out =/

Sorry when i opened my my port didn't save but yes if you API to your router you can see all your cards you have running on all computers if you have the API set to the router, amazing , thanks so much EWBF very helpful, Upped the dev fee a little . if anyone is still having problems getting it to show on another computer send a msg and help if i can!

[cryptobob88]

I am getting 0 Sol/s on my 1080TI asus strix.... I reinstalled the drivers 4-5 times now

used different pool, nothing. the card is on stock settings. I tried all version of the miner, and nothing... what am I doing wrong?

please let me know

Edit: I'm getting: Thread exited code 77 miner, whenever I start the miner.

The card is not overclocked, it's on stock settings.

I am getting 0 Sol/s on my 1080TI asus strix.... I reinstalled the drivers 4-5 times now

used different pool, nothing. the card is on stock settings. I tried all version of the miner, and nothing... what am I doing wrong?

please let me know

Edit: I'm getting: Thread exited code 77 miner, whenever I start the miner.

The card is not overclocked, it's on stock settings.

[MikeSmith]

The miner stops after 2-3 hours of mining. It says that 'thread has exited with code 77' and 'GPU0 stopped working'. Then it attempts to restart but without success. However if I manually restart the miner (close the cmd.exe window and start the .bat file) it works fine again. So there is a problem with automatic restart.

[Taxidermista]

Yes teamviewer uses gpu power to render the desktop.  If you change your API address to the actual IP of the mining rig and view the api from another pc, with teamviewer not connected, you will find that your hash goes back up.  

I've used --api in my nvidia rigs but I cannot connect remotely using my network ips, only with 127.0.0.1 at same the rig.

you need to use --api xxx.xxx.xxx.xxx:42000 in your command line.  

xxx.xxx.xxx.xxx needs to be replaced with the actual local IP address of the miner, if you have DHCP you will need to fix the address so it does not change.

Using 127.0.0.1 restricts the API to local host only which is what happens if you only specify --api

Thank you, I'll try that right now.

EDIT: No, that's not working, something is wrong. When I add -–api 192.168.0.209:42000 to one of my rigs the miner starts with INFO: Api: Disabled.

[antex34]

I started to mine on nanopool, and after 12 hours, mining with 1x 1070 GPU at 460 sols:
- my calculation for 1 month gives me 0.007752 per day, total 0.2325 per month.
That's half of the whattomine estimations. sad.

so monitor your actual incomes guys.

[nUm81]

I started to mine on nanopool, and after 12 hours, mining with 1x 1070 GPU at 460 sols:
- my calculation for 1 month gives me 0.007752 per day, total 0.2325 per month.
That's half of the whattomine estimations. sad.

so monitor your actual incomes guys.

Block difficulty has gone from around 2m to 4m in the last 20 days due to the huge increase in miners coming online.  That isn't related to the performance of this miner.

[WhiteCranium]

I've managed to pull 450 Sol/s with GeForce GTX1070 MSI Gaming 8GB DDR5. Nice! 

[ayke99]

Yes teamviewer uses gpu power to render the desktop.  If you change your API address to the actual IP of the mining rig and view the api from another pc, with teamviewer not connected, you will find that your hash goes back up.  

I've used --api in my nvidia rigs but I cannot connect remotely using my network ips, only with 127.0.0.1 at same the rig.

you need to use --api xxx.xxx.xxx.xxx:42000 in your command line.  

xxx.xxx.xxx.xxx needs to be replaced with the actual local IP address of the miner, if you have DHCP you will need to fix the address so it does not change.

Using 127.0.0.1 restricts the API to local host only which is what happens if you only specify --api

Thank you, I'll try that right now.

EDIT: No, that's not working, something is wrong. When I add -–api 192.168.0.209:42000 to one of my rigs the miner starts with INFO: Api: Disabled.

to work 192.168.0.209 must be rig ip .

[wojzet]

wojzet
Have you tried downloading cuda drivers? From here: https://developer.nvidia.com/cuda-downloads . Had a similar problem on older machine, installing cuda drivers apparently fixed it.

I try install this and is this same.

wojzet

Your clocks are too high, hence your miner turns off right away. Adjust the clocks to lower speed and you should be fine.

Only CPU is OC, but with GTX 750Ti all was fine. And in this time, when i switch to only CPU, all is fine. But when i try work on GPU is this error...
But when i test game on this GPU, all is fine, up to 100 fps.

[tpd09]

I've managed to pull 450 Sol/s with GeForce GTX1070 MSI Gaming 8GB DDR5. Nice! 

same here with the EVGA SC

80%, +180, +280