I notice ZM sometimes freezes when I clic in the terminal.
Now, I avoid to click inside and I click on the top of the window to get the terminal in front
It is pretty obvious when I use ipad with distant desktop app.
Topic: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows) - page 107. (Read 224961 times)
November 20, 2017, 04:06:32 PM
November 20, 2017, 03:58:51 PM
Hi, miner ran stable for 2 days, now it crashes immediatly on start, any ideas?
Thks
Rig 6 GTX 1070
Thks
Rig 6 GTX 1070
November 20, 2017, 03:56:39 PM
I think that we need more work on polishing and killing bugs dstm, cause still we have some questions about stability
if the question of stability really important, then your miner lose, unfortunately at the moment
if the question of stability really important, then your miner lose, unfortunately at the moment
ZM had never stability issues (except a reconnection bug). Some users use it for about 3 months without issues this is also the case on my systems.
November 20, 2017, 02:14:36 PM
I think that we need more work on polishing and killing bugs dstm, cause still we have some questions about stability
if the question of stability really important, then your miner lose, unfortunately at the moment
if the question of stability really important, then your miner lose, unfortunately at the moment
ZM had never stability issues (except a reconnection bug). Some users use it for about 3 months without issues this is also the case on my systems.
November 20, 2017, 01:40:06 PM
I think that we need more work on polishing and killing bugs dstm, cause still we have some questions about stability
if the question of stability really important, then your miner lose, unfortunately at the moment
if the question of stability really important, then your miner lose, unfortunately at the moment
Idk about that. If your rig is solid there shouldnt be any issues. Im at 7 days straight uptime on a 1060 rig.
November 20, 2017, 01:33:36 PM
I think that we need more work on polishing and killing bugs dstm, cause still we have some questions about stability
if the question of stability really important, then your miner lose, unfortunately at the moment
if the question of stability really important, then your miner lose, unfortunately at the moment
November 20, 2017, 01:13:31 PM
Miner works 5-6 minutes, then crashes at the same settings with ewbf. Gtx 1080x8
This is most likely due to overclocking. You have to readjust it - zm puts a different load on your GPUs.
I completely removed the overclock from my cards, and i still get issues after a few seconds after launch, i think there is something else, and it's across 10 rigs so...
I was wondering how do you deal with intensity inside your miner ? to decide how hard you go on the GPU's ? maybe if you include custom setting per gpu we could find the sweet spot for any GPU depending on making & brand. You miner seems to push extremely hard the gpu's, and maybe "lower" tier ones even of the same model could need some tweakings even if they're not overclocked i dunno. For example i have EVGA's cards that work with your miner as stated in a post before that i consider to be higher tier than the other rigs that use KFA2's, they're both 1070 but the KFA's perform lower than the EVGA's but the rigs consume less power so it all balance out.
Concerning intensity: There is no such thing like intensity which I'm setting to make the GPUs run faster, if this is what you're thinking about. The performance depends mainly on how well you've designed your algorithm and how well the program that implements it is able to utilize the GPU.
If I understood you right, zm fails on cudaMemcpy on some of your rigs. Does a particular GPU fail or do they fail all at once?
November 20, 2017, 11:50:38 AM
Miner works 5-6 minutes, then crashes at the same settings with ewbf. Gtx 1080x8
This is most likely due to overclocking. You have to readjust it - zm puts a different load on your GPUs.
I completely removed the overclock from my cards, and i still get issues after a few seconds after launch, i think there is something else, and it's across 10 rigs so...
I was wondering how do you deal with intensity inside your miner ? to decide how hard you go on the GPU's ? maybe if you include custom setting per gpu we could find the sweet spot for any GPU depending on making & brand. You miner seems to push extremely hard the gpu's, and maybe "lower" tier ones even of the same model could need some tweakings even if they're not overclocked i dunno. For example i have EVGA's cards that work with your miner as stated in a post before that i consider to be higher tier than the other rigs that use KFA2's, they're both 1070 but the KFA's perform lower than the EVGA's but the rigs consume less power so it all balance out.
November 20, 2017, 10:43:58 AM
Miner works 5-6 minutes, then crashes at the same settings with ewbf. Gtx 1080x8
This is most likely due to overclocking. You have to readjust it - zm puts a different load on your GPUs.
I had to lower my clocks just a little bit but its still faster than ewbf, test it out.
November 20, 2017, 07:24:43 AM
Miner works 5-6 minutes, then crashes at the same settings with ewbf. Gtx 1080x8
This is most likely due to overclocking. You have to readjust it - zm puts a different load on your GPUs.
November 20, 2017, 05:24:39 AM
Miner works 5-6 minutes, then crashes at the same settings with ewbf. Gtx 1080x8
This is most likely due to overclocking. You have to readjust it - zm puts a different load on your GPUs.
November 20, 2017, 05:23:54 AM
Since updating to 0.5.5, on Windows 10 (clean install), when the miner encounters various errors, the error will sometimes appear in a Windows message box and blocks the miner from continuing to mine until I hit "Ok." Was this version accidentally built as Debug instead of Release (i.e. in Visual Studio)?!?!!
I'm not using the visual studio ide or it's buid system, the release process is automated - it wasn't build with debugging symbols enabled.
This might be useful
https://bitcointalksearch.org/topic/m.24811400
November 20, 2017, 05:21:16 AM
Trying to mine Zclassic on ny1.minez.zone:3054 get the following error:
https://minez.zone
Press CTRL+C to quit ...# zm 0.5.4
# GPU0 + GeForce GTX 970 MB: 4096 PCI: 0:5
# GPU0 connected to: ny1.minez.zone:3054
# GPU0 server set difficulty to: 0000ccccccccccccd0000000...
protocol version 01000020 not supported
Tried 0.5.5, same error
Press CTRL+C to quit ...# zm 0.5.5
# GPU0 + GeForce GTX 970 MB: 4096 PCI: 0:5
# GPU0 connected to: ny1.minez.zone:3054
# GPU0 server set difficulty to: 0000ccccccccccccd0000000...
protocol version 01000020 not supported
https://minez.zone
Press CTRL+C to quit ...# zm 0.5.4
# GPU0 + GeForce GTX 970 MB: 4096 PCI: 0:5
# GPU0 connected to: ny1.minez.zone:3054
# GPU0 server set difficulty to: 0000ccccccccccccd0000000...
protocol version 01000020 not supported
Tried 0.5.5, same error
Press CTRL+C to quit ...# zm 0.5.5
# GPU0 + GeForce GTX 970 MB: 4096 PCI: 0:5
# GPU0 connected to: ny1.minez.zone:3054
# GPU0 server set difficulty to: 0000ccccccccccccd0000000...
protocol version 01000020 not supported
Thx, will check if there are any major differences for 01000020.
November 20, 2017, 05:18:54 AM
dstm, what to do if overall process is not shown (pic)?
I've tried to relaunch the miner and reboot the system - the same.
I've tried to relaunch the miner and reboot the system - the same.
Could you pls post the way you start zm?
November 20, 2017, 05:17:37 AM
Hi DSTM, miner for card AMD? 
I have no plans to work on AMD cards.
November 20, 2017, 05:16:19 AM
There was a windows update that stops the miner from running. Back to EWBF until this is resolved.
. I also experienced a lot of issues after recent windows update. Using zm 0.5.4 , few miners ran into some loop at random times , also had to lower memory clocks on cards although they ran for month straight without any issues . Also performance is lower I was getting around 10170 sole now 10000 and loweranyone had this loop with version 0.5.4 ?
There is something wrong with your cuda installation. ZM fails to enumerate the devices - however the loop is a bug - zm should exit with an error message in this situation.
November 20, 2017, 05:14:40 AM
this miner is almost there, but still needs hash rate improvements with every upcoming version, only then can it finally surpass the EWBF miner which has stopped updating...
When can we expect a hash rate increase in the upcoming versions ?..
When can we expect a hash rate increase in the upcoming versions ?..
This is something I can't predict.
November 20, 2017, 05:13:33 AM
There was a windows update that stops the miner from running. Back to EWBF until this is resolved.
It's running fine for me after the update, could you pls provide more information?
November 20, 2017, 05:11:35 AM
Quote
I have this error
2017-11-16 11:54:22|gpu_id 1 2 000000052AB60400 unknown error
2017-11-16 11:54:22|gpu_id 3 2 000000055F600000 unknown error
2017-11-16 11:54:22|gpu_id 4 0 0000000579C00000 unknown error
2017-11-16 11:54:22|gpu_id 0 0 000000050DEB0200 unknown error
2017-11-16 11:54:22|gpu_id 2 6 00000005450420C0 unknown error
2017-11-16 11:54:22|gpu 2 unresponsive - check overclocking
2017-11-16 11:54:22|cudaMemcpy 1 failed
2017-11-16 11:54:22|gpu 4 unresponsive - check overclocking
2017-11-16 11:54:22|cudaMemcpy 1 failed
2017-11-16 11:54:22|gpu 1 unresponsive - check overclocking
2017-11-16 11:54:22|cudaMemcpy 1 failed
2017-11-16 11:54:22|gpu 0 unresponsive - check overclocking
2017-11-16 11:54:22|gpu 3 unresponsive - check overclocking
2017-11-16 11:54:22|cudaMemcpy 1 failed
2017-11-16 11:54:22|cudaMemcpy 1 failed
2017-11-16 11:54:22|gpu_id 1 2 000000052AB60400 unknown error
2017-11-16 11:54:22|gpu_id 3 2 000000055F600000 unknown error
2017-11-16 11:54:22|gpu_id 4 0 0000000579C00000 unknown error
2017-11-16 11:54:22|gpu_id 0 0 000000050DEB0200 unknown error
2017-11-16 11:54:22|gpu_id 2 6 00000005450420C0 unknown error
2017-11-16 11:54:22|gpu 2 unresponsive - check overclocking
2017-11-16 11:54:22|cudaMemcpy 1 failed
2017-11-16 11:54:22|gpu 4 unresponsive - check overclocking
2017-11-16 11:54:22|cudaMemcpy 1 failed
2017-11-16 11:54:22|gpu 1 unresponsive - check overclocking
2017-11-16 11:54:22|cudaMemcpy 1 failed
2017-11-16 11:54:22|gpu 0 unresponsive - check overclocking
2017-11-16 11:54:22|gpu 3 unresponsive - check overclocking
2017-11-16 11:54:22|cudaMemcpy 1 failed
2017-11-16 11:54:22|cudaMemcpy 1 failed
I get the exactly same error with 0.5.5. All 4 rigs crashes between 1minute to 30minutes. Switched back to 0.5.3 and it works flawless again. I use 1080ti's
Edit: Its on Windows. Tested on my main computer, crashes alot on gtx 1070 too.
There are no differences between 0.5.3 - 0.5.5 with respect to this.
November 20, 2017, 05:09:57 AM
Hello dstm, may I suggest add failover pools feature like in ewbf and cgminer, thanks.
This was requested several times, will add.
No there aren't any performance improvements between 0.5.3 - 0.5.5.
Jump to: