V0.5.2 + Added 'verushash' for GPU mining + 'verushash' on CPU optimised a little bit + 'ethash' on GPU optimised a little bit + Optimised algorithm redirecting with CPU mined algorithms + Removed 'MTP' algorithm + Bug fixes
|
|
|
On 0.4.7 you mine 1 algorithm, 0.5.1 - 2 algorithms. Have you tried 0.5.1 epic only? Im curious.. Also i am/was expecting bugs with the new multi algo mining feature, but not the ones you have
|
|
|
First case looks like a hang/crash, the second one a bug. You could try using '--max-no-share-sent' parameter it might solve the second issue.
--max-no-share-sent 600[2020-09-16 12:52:41] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-16 12:52:46] CPU result accepted [62ms][1] [2020-09-16 12:53:10] New job ignored [1], block height 608627[0] [2020-09-16 12:53:40] New job ignored [2], block height 608627[0] [2020-09-16 12:54:10] New job ignored [3], block height 608627[0] [2020-09-16 12:54:29] New job received [0], block height 608628[0] [2020-09-16 12:54:58] New job received [1], block height 608628[0] [2020-09-16 12:55:28] New job received [2], block height 608628[0] [2020-09-16 12:55:58] New job received [3], block height 608628[0] [2020-09-16 12:56:19] New job ignored [0], block height 608629[0] [2020-09-16 12:56:19] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-16 12:56:23] Last valid share sent more than 1 minutes ago! Miner will restart[11] [2020-09-16 12:56:28] New job received [0], block height 608630[0] [2020-09-16 12:56:48] New job received [0], block height 608631[0] [2020-09-16 12:57:15] New job ignored [0], block height 608632[0] [2020-09-16 12:57:15] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-16 12:57:45] New job ignored [1], block height 608632[0] [2020-09-16 12:58:15] New job ignored [2], block height 608632[0] [2020-09-16 12:58:45] New job ignored [3], block height 608632[0] [2020-09-16 12:59:15] New job ignored [4], block height 608632[0] [2020-09-16 12:59:28] New job received [0], block height 608633[0] [2020-09-16 12:59:58] New job received [1], block height 608633[0] [2020-09-16 13:00:06] New job ignored [0], block height 608634[0] [2020-09-16 13:00:06] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-16 13:00:35] New job ignored [1], block height 608634[0] [2020-09-16 13:01:05] New job ignored [2], block height 608634[0] [2020-09-16 13:01:16] New job received [0], block height 608635[0] [2020-09-16 13:01:35] New job received [0], block height 608636[0] [2020-09-16 13:02:04] New job received [1], block height 608636[0] [2020-09-16 13:02:08] New job ignored [0], block height 608637[0] [2020-09-16 13:02:08] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-16 13:02:36] New job received [0], block height 608638[0] [2020-09-16 13:03:05] New job received [1], block height 608638[0] [2020-09-16 13:03:35] New job received [2], block height 608638[0] [2020-09-16 13:04:05] New job received [3], block height 608638[0] [2020-09-16 13:04:35] New job received [4], block height 608638[0] [2020-09-16 13:04:38] New job ignored [0], block height 608639[0] [2020-09-16 13:04:38] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-16 13:04:50] New job received [0], block height 608640[0] [2020-09-16 13:04:55] New job received [0], block height 608641[0] [2020-09-16 13:05:06] New job ignored [0], block height 608642[0] [2020-09-16 13:05:06] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-16 13:05:36] New job ignored [1], block height 608642[0] [2020-09-16 13:06:02] New job received [0], block height 608643[0] [2020-09-16 13:06:31] New job received [1], block height 608643[0] [2020-09-16 13:06:57] New job received [0], block height 608644[0] [2020-09-16 13:07:27] New job received [1], block height 608644[0]
Do you have an antivirus that could kill threads of the miner process? That would explain why it kept getting jobs but not doing anything else. Also the restart sequence just got ignored, which in normal cases can't happen.
|
|
|
Stuck again. This how look console after it happened: It also happened on my another PC (first time after few days), but sorry there is no log file, only console output: [2020-09-15 22:28:55] New job received [d4ce], block height 25352[1] [2020-09-15 22:29:01] ============================================================== [2020-09-15 22:29:01] [0] [randomepic] [2020-09-15 22:29:01] CPU : 2904.65 H/s [2020-09-15 22:29:01] Total: 2904.65 H/s [2020-09-15 22:29:01] ============================================================== [2020-09-15 22:29:01] [1] [yescryptr16] [2020-09-15 22:29:01] CPU : 0.00 H/s [2020-09-15 22:29:01] Total: 0.00 H/s [2020-09-15 22:29:01] ============================================================== [2020-09-15 22:29:06] New job received [7], block height 607806[0] [2020-09-15 22:29:34] New job ignored [0], block height 607807[0] [2020-09-15 22:29:34] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 22:29:36] CPU result accepted [58ms][1] [2020-09-15 22:29:50] New job received [d4cf], block height 25352[1] [2020-09-15 22:29:52] CPU result accepted [57ms][1] [2020-09-15 22:30:04] New job ignored [1], block height 607807[0] [2020-09-15 22:30:34] New job ignored [2], block height 607807[0] [2020-09-15 22:31:04] New job ignored [3], block height 607807[0] [2020-09-15 22:31:34] New job ignored [4], block height 607807[0] [2020-09-15 22:32:04] New job ignored [5], block height 607807[0] [2020-09-15 22:32:34] New job ignored [6], block height 607807[0] [2020-09-15 22:33:04] New job ignored [7], block height 607807[0] [2020-09-15 22:33:26] New job received [0], block height 607808[0] [2020-09-15 22:33:56] New job received [1], block height 607808[0] [2020-09-15 22:34:26] New job received [2], block height 607808[0] [2020-09-15 22:34:56] New job received [3], block height 607808[0] [2020-09-15 22:35:10] New job received [0], block height 607809[0] [2020-09-15 22:35:40] New job received [1], block height 607809[0] [2020-09-15 22:36:05] New job ignored [0], block height 607810[0] [2020-09-15 22:36:05] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 22:36:30] New job received [0], block height 607811[0] [2020-09-15 22:36:52] New job ignored [0], block height 607812[0] [2020-09-15 22:36:52] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 22:37:22] New job ignored [1], block height 607812[0] [2020-09-15 22:37:52] New job ignored [2], block height 607812[0] [2020-09-15 22:37:58] New job received [0], block height 607813[0] [2020-09-15 22:38:04] New job received [0], block height 607814[0] [2020-09-15 22:38:07] New job ignored [0], block height 607815[0] [2020-09-15 22:38:07] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 22:38:11] New job received [0], block height 607816[0] [2020-09-15 22:38:41] New job received [1], block height 607816[0] [2020-09-15 22:39:11] New job received [2], block height 607816[0] [2020-09-15 22:39:41] New job received [3], block height 607816[0] [2020-09-15 22:40:04] New job ignored [0], block height 607817[0] [2020-09-15 22:40:04] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 22:40:34] New job ignored [1], block height 607817[0] [2020-09-15 22:41:04] New job ignored [2], block height 607817[0] [2020-09-15 22:41:34] New job ignored [3], block height 607817[0] [2020-09-15 22:41:54] New job received [0], block height 607818[0] [2020-09-15 22:42:10] New job ignored [0], block height 607819[0] [2020-09-15 22:42:10] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 22:42:15] New job received [0], block height 607820[0] [2020-09-15 22:42:45] New job received [1], block height 607820[0] [2020-09-15 22:43:15] New job received [2], block height 607820[0] [2020-09-15 22:43:45] New job received [3], block height 607820[0] [2020-09-15 22:44:15] New job received [4], block height 607820[0] [2020-09-15 22:44:45] New job received [5], block height 607820[0] [2020-09-15 22:45:15] New job received [6], block height 607820[0] [2020-09-15 22:45:19] New job ignored [0], block height 607821[0] [2020-09-15 22:45:19] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 22:45:46] New job received [0], block height 607822[0] [2020-09-15 22:46:16] New job received [1], block height 607822[0] [2020-09-15 22:46:46] New job received [2], block height 607822[0] [2020-09-15 22:47:16] New job received [3], block height 607822[0] [2020-09-15 22:47:46] New job received [4], block height 607822[0] [2020-09-15 22:48:16] New job received [5], block height 607822[0] [2020-09-15 22:48:20] New job received [0], block height 607823[0] [2020-09-15 22:48:50] New job received [1], block height 607823[0] [2020-09-15 22:49:16] New job ignored [0], block height 607824[0] [2020-09-15 22:49:16] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 22:49:45] New job ignored [1], block height 607824[0] [2020-09-15 22:50:15] New job ignored [2], block height 607824[0] [2020-09-15 22:50:33] New job received [0], block height 607825[0] [2020-09-15 22:50:42] New job received [0], block height 607826[0] [2020-09-15 22:51:11] New job received [1], block height 607826[0] [2020-09-15 22:51:41] New job received [2], block height 607826[0] [2020-09-15 22:52:11] New job received [3], block height 607826[0] [2020-09-15 22:52:14] New job ignored [0], block height 607827[0] [2020-09-15 22:52:14] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 22:52:44] New job ignored [1], block height 607827[0] [2020-09-15 22:53:09] New job received [0], block height 607828[0] [2020-09-15 22:53:33] New job ignored [0], block height 607829[0] [2020-09-15 22:53:33] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 22:53:48] New job received [0], block height 607830[0] [2020-09-15 22:53:53] New job received [0], block height 607831[0] [2020-09-15 22:54:23] New job received [1], block height 607831[0] [2020-09-15 22:54:53] New job received [2], block height 607831[0] [2020-09-15 22:55:23] New job received [3], block height 607831[0] [2020-09-15 22:55:53] New job received [4], block height 607831[0] [2020-09-15 22:56:23] New job received [5], block height 607831[0] [2020-09-15 22:56:53] New job received [6], block height 607831[0] [2020-09-15 22:57:03] New job ignored [0], block height 607832[0] [2020-09-15 22:57:03] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 22:57:05] New job received [0], block height 607833[0] [2020-09-15 22:57:35] New job ignored [0], block height 607834[0] [2020-09-15 22:57:35] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 22:58:05] New job ignored [1], block height 607834[0] [2020-09-15 22:58:35] New job ignored [2], block height 607834[0] [2020-09-15 22:59:05] New job ignored [3], block height 607834[0] [2020-09-15 22:59:35] New job ignored [4], block height 607834[0] [2020-09-15 23:00:05] New job ignored [5], block height 607834[0] [2020-09-15 23:00:35] New job ignored [6], block height 607834[0] [2020-09-15 23:01:05] New job ignored [7], block height 607834[0] [2020-09-15 23:01:06] New job received [0], block height 607835[0] [2020-09-15 23:01:17] New job received [0], block height 607836[0] [2020-09-15 23:01:47] New job received [1], block height 607836[0] [2020-09-15 23:02:17] New job received [2], block height 607836[0] [2020-09-15 23:02:28] New job ignored [0], block height 607837[0] [2020-09-15 23:02:28] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 23:02:58] New job ignored [1], block height 607837[0] [2020-09-15 23:03:26] New job received [0], block height 607838[0] [2020-09-15 23:03:33] New job ignored [0], block height 607839[0] [2020-09-15 23:03:33] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 23:03:42] New job received [0], block height 607840[0] [2020-09-15 23:04:12] New job received [1], block height 607840[0] [2020-09-15 23:04:42] New job received [2], block height 607840[0] [2020-09-15 23:05:12] New job received [3], block height 607840[0] [2020-09-15 23:05:42] New job received [4], block height 607840[0] [2020-09-15 23:06:12] New job received [5], block height 607840[0] [2020-09-15 23:06:42] New job received [6], block height 607840[0] [2020-09-15 23:07:12] New job received [7], block height 607840[0] [2020-09-15 23:07:42] New job received [8], block height 607840[0] [2020-09-15 23:08:12] New job received [9], block height 607840[0] [2020-09-15 23:08:42] New job received [10], block height 607840[0] [2020-09-15 23:09:12] New job received [11], block height 607840[0] [2020-09-15 23:09:31] New job received [0], block height 607841[0] [2020-09-15 23:09:47] New job ignored [0], block height 607842[0] [2020-09-15 23:09:47] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 23:10:15] New job received [0], block height 607843[0] [2020-09-15 23:10:45] New job received [1], block height 607843[0] [2020-09-15 23:11:09] New job received [0], block height 607844[0] [2020-09-15 23:11:34] New job ignored [0], block height 607845[0] [2020-09-15 23:11:34] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 23:12:04] New job ignored [1], block height 607845[0] [2020-09-15 23:12:34] New job ignored [2], block height 607845[0] [2020-09-15 23:13:04] New job ignored [3], block height 607845[0] [2020-09-15 23:13:34] New job ignored [4], block height 607845[0] [2020-09-15 23:14:04] New job ignored [5], block height 607845[0] [2020-09-15 23:14:11] New job received [0], block height 607846[0] [2020-09-15 23:14:41] New job received [1], block height 607846[0] [2020-09-15 23:15:00] New job ignored [0], block height 607847[0] [2020-09-15 23:15:00] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 23:15:30] New job ignored [1], block height 607847[0] [2020-09-15 23:16:00] New job ignored [2], block height 607847[0] [2020-09-15 23:16:30] New job ignored [3], block height 607847[0] [2020-09-15 23:17:12] New job ignored [4], block height 607847[0] [2020-09-15 23:17:30] New job ignored [5], block height 607847[0] [2020-09-15 23:18:00] New job ignored [6], block height 607847[0]
But here miner continue to output data in console. First case looks like a hang/crash, the second one a bug. You could try using '--max-no-share-sent' parameter it might solve the second issue.
|
|
|
Nothing, just nothing, it work about hour or more without printing any info in console and without any log out. [2020-09-15 14:25:36] json_receive[0][977]: {"id":"Stratum","jsonrpc":"2.0","method":"job","params":{"algorithm":"randomx","block_difficulty":[["cuckoo",925173],["randomx",405146916],["progpow",1134306013231]],"difficulty":[["cuckoo",4],["randomx",240000],["progpow",1000000000]],"epochs":[[607060,608060,[189,249,241,239,124,69,63,137,6,70,101,111,111,105,48,107,89,145,41,190,155,76,30,247,211,142,31,43,92,3,63,89]]],"height":607323,"job_id":0,"pre_pow":"0006000000000009445b000000005f60a4b220d1ea6168becadcfea30c27db5df3e36242f59b6866ed126841b870baf7fd756da369eb48b646c6f94fc5cf8ccd6aae0064d2b51315240bb1b5c0f67e2566b13b523c733c74dce04fd8bb85fe87754bfb4423693547c336d8965ed92ffc714e50c4a6846c4edf3d87fc04188e082b9e1bebe5d4a5e1adee5c94db4a70c87beaa4d4d049ea138ae7c6aa8e77b142f2d578ce053fe506c0e514c88c38d6e28ea14e2aa26f89c52a7858d62b670c4bf02e646ce7a9acba9d241e74df1d69b4a80100000000001ca5ca000000000013cb070000000000000004000000000000251170010000005bf111b02c020000d5ef387463f30304977804ebd347d0fff19005","xn":"b812"}} this is last line in log file. That's strange , looks more like the app hanged totally, if nothing was even logged. Just reinstalled win on one of my rigs, going to run epic+ys16 for a day to see if something like this happens (it did not in the 2 week test period)
|
|
|
Ok, miner just stop to generate shares without any errors, but continue to load processor (randomepic+yescryptr16). Last few minits from log: [2020-09-15 14:24:23] json_send[0][246]: {"id":"685","jsonrpc":"2.0","method":"submit","params":{"height":607320,"job_id":0,"nonce":13263913708700985062,"pow":{"RandomX":[0,0,27,171,139,116,36,168,81,229,254,155,162,251,58,209,172,123,196,85,152,131,215,205,9,30,255,103,29,170,72,92]}}} [2020-09-15 14:24:24] json_receive[0][73]: {"id":"685","jsonrpc":"2.0","method":"submit","result":"ok","error":null} [2020-09-15 14:24:24] CPU result accepted [393ms][0] [2020-09-15 14:24:29] json_receive[1][636]: {"id":null,"method":"mining.notify","params":["d278","e76f08ddb592438c1d4d8ba00641ed5124ce2c4494c5fb637429f764a46d716c","01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff4d02af62046fa4605f08fabe6d6d00000000000000000000000000000000000000000000000000000000000000000100000000000000","0f706f6f6c2e72706c616e742e78797a00000000020000000000000000266a24aa21a9edd569dece71b510717aa44fef8d1b2cac74e4e20d24feaf541e81ceb72004301680cc0003000000001976a91488d5378e77ed4b8c0d9c1ccf2ccfcdebfe49497288ac00000000",["51cbd87429ba1559314e547a5878dd8449e1784696d5ee76239cfae4832b0187"],"20000000","1d0b6df7","5f60a46f",true]} [2020-09-15 14:24:29] New job received [d278], block height 25263[1] [2020-09-15 14:24:36] json_receive[0][977]: {"id":"Stratum","jsonrpc":"2.0","method":"job","params":{"algorithm":"randomx","block_difficulty":[["cuckoo",925173],["randomx",402405965],["progpow",1141197364249]],"difficulty":[["cuckoo",4],["randomx",240000],["progpow",1000000000]],"epochs":[[607060,608060,[189,249,241,239,124,69,63,137,6,70,101,111,111,105,48,107,89,145,41,190,155,76,30,247,211,142,31,43,92,3,63,89]]],"height":607320,"job_id":1,"pre_pow":"00060000000000094458000000005f60a476cb3ce94887fe8cf596e040b97d6de7e1009567af2e9ba04536268c7b3bbb6919b946af0709a1b2e11b597814571c78807fb9bd6be8259723a6c393676ea4077c00893df9c0e0591bc2a442321df6fa448377d3916a9f8008770ca7da8e6d51eb9e11f7ae9bffe98b38b290b1ed0af3c079cc185a20dd9c005da6d5e872047f45919a1d4dbc1c7f778e9cfea9dfa6c5160c8268faf461cfab8fab752a3460389b4e2aa26f89c52a7858d62b670c4bf02e646ce7a9acba9d241e74df1d69b4a80100000000001ca5c6000000000013cb000000000000000004000000000000251164010000005bf0e7564d020000d5eeefdf10df03049774eb03590b59fb7c3977","xn":"b812"}} [2020-09-15 14:24:36] New job received [1], block height 607320[0] [2020-09-15 14:24:37] [0][randomepic] [2020-09-15 14:24:37] CPU: 6043.80 H/s [2020-09-15 14:24:37] Total: 6043.80 H/s [2020-09-15 14:24:37] [1][yescryptr16] [2020-09-15 14:24:37] CPU: 0.00 H/s [2020-09-15 14:24:37] Total: 0.00 H/s [2020-09-15 14:25:01] json_receive[0][977]: {"id":"Stratum","jsonrpc":"2.0","method":"job","params":{"algorithm":"progpow","block_difficulty":[["cuckoo",925173],["randomx",406299384],["progpow",1141197364249]],"difficulty":[["cuckoo",4],["randomx",240000],["progpow",1000000000]],"epochs":[[607060,608060,[189,249,241,239,124,69,63,137,6,70,101,111,111,105,48,107,89,145,41,190,155,76,30,247,211,142,31,43,92,3,63,89]]],"height":607321,"job_id":0,"pre_pow":"00060000000000094459000000005f60a48f0165e1cc65a101d78fc7caa811af11ff05564c3e8327a5dd2d46487bc4c28b6ad1d4758081fd182831ea5d72df1827ae3b242b19ef3033f8218a8920048b4cef702166fbd4a85ee8cefc0afca2f881e33e28ff9482a6314f1b58783285f1056053fe08d1c8fdec245df0aaf5302712761a0285b321eb5a7dc58474649e4235fa0753efe0da658809d90436917a67e1a494aab2694b7e9e809da2d42044575aa04e2aa26f89c52a7858d62b670c4bf02e646ce7a9acba9d241e74df1d69b4a80100000000001ca5c7000000000013cb020000000000000004000000000000251168010000005bf0f57442020000d5ef0816b3d703049775f4b802e772ffddbb6c","xn":"b812"}} [2020-09-15 14:25:01] New job ignored [0], block height 607321[0] [2020-09-15 14:25:01] Redirecting jobs from algorithm 1 to algorithm 0 workers [2020-09-15 14:25:22] json_receive[0][977]: {"id":"Stratum","jsonrpc":"2.0","method":"job","params":{"algorithm":"randomx","block_difficulty":[["cuckoo",925173],["randomx",406299384],["progpow",1134306013231]],"difficulty":[["cuckoo",4],["randomx",240000],["progpow",1000000000]],"epochs":[[607060,608060,[189,249,241,239,124,69,63,137,6,70,101,111,111,105,48,107,89,145,41,190,155,76,30,247,211,142,31,43,92,3,63,89]]],"height":607322,"job_id":0,"pre_pow":"0006000000000009445a000000005f60a4a4bbfae9328e9b3346f4a163d02d05d0c5b6a9d91470535bd68dd3f58b4c8fe553d4b3ba2559622efad83861a85a2249dac3298649c995b3c269b26fccfb5456341a16ff0f7e861ff859989753ae0961b356129d97a8421e3129a25368e82e94617da0e3d6d41af089270e60f7ac8e8feed8687a1c2d7cdbafabd336eff896f5a28ffff0ebf7affb4f8902a47445cd4980171ddb7f68a8caf9c1421c11be6d50164e2aa26f89c52a7858d62b670c4bf02e646ce7a9acba9d241e74df1d69b4a80100000000001ca5c9000000000013cb03000000000000000400000000000025116c010000005bf1039237020000d5ef204e56cf03049776fcd1eb17a1fb7c34b0","xn":"b812"}} [2020-09-15 14:25:22] Allocated 2048 kB in large-page memory[0] [2020-09-15 14:25:22] Allocated 2048 kB in large-page memory[0] [2020-09-15 14:25:22] Allocated 2048 kB in large-page memory[0] [2020-09-15 14:25:22] New job received [0], block height 607322[0] [2020-09-15 14:25:22] Allocated scratchpad [CPU worker 9][H] [2020-09-15 14:25:22] Allocated scratchpad [CPU worker 3][H] [2020-09-15 14:25:22] Allocated scratchpad [CPU worker 8][H] [2020-09-15 14:25:22] VM created [CPU worker 9] [2020-09-15 14:25:22] VM created [CPU worker 8] [2020-09-15 14:25:22] VM created [CPU worker 3] [2020-09-15 14:25:22] Allocated 2048 kB in large-page memory[0] [2020-09-15 14:25:22] Allocated scratchpad [CPU worker 0][H] [2020-09-15 14:25:22] Allocated 2048 kB in large-page memory[0] [2020-09-15 14:25:22] VM created [CPU worker 0] [2020-09-15 14:25:22] Allocated scratchpad [CPU worker 2][H] [2020-09-15 14:25:22] VM created [CPU worker 2] [2020-09-15 14:25:22] Allocated 2048 kB in large-page memory[0] [2020-09-15 14:25:22] Allocated scratchpad [CPU worker 1][H] [2020-09-15 14:25:22] Allocated 2048 kB in large-page memory[0] [2020-09-15 14:25:22] Allocated scratchpad [CPU worker 7][H] [2020-09-15 14:25:22] VM created [CPU worker 1] [2020-09-15 14:25:22] VM created [CPU worker 7] [2020-09-15 14:25:22] Allocated 2048 kB in large-page memory[0] [2020-09-15 14:25:22] Allocated scratchpad [CPU worker 6][H] [2020-09-15 14:25:22] VM created [CPU worker 6] [2020-09-15 14:25:22] Allocated 2048 kB in large-page memory[0] [2020-09-15 14:25:22] Allocated scratchpad [CPU worker 4][H] [2020-09-15 14:25:22] Allocated 2048 kB in large-page memory[0] [2020-09-15 14:25:22] VM created [CPU worker 4] [2020-09-15 14:25:22] Allocated scratchpad [CPU worker 5][H] [2020-09-15 14:25:22] VM created [CPU worker 5] [2020-09-15 14:25:24] json_receive[1][636]: {"id":null,"method":"mining.notify","params":["d279","e76f08ddb592438c1d4d8ba00641ed5124ce2c4494c5fb637429f764a46d716c","01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff4d02af6204a6a4605f08fabe6d6d00000000000000000000000000000000000000000000000000000000000000000100000000000000","0f706f6f6c2e72706c616e742e78797a00000000020000000000000000266a24aa21a9edd569dece71b510717aa44fef8d1b2cac74e4e20d24feaf541e81ceb72004301680cc0003000000001976a91488d5378e77ed4b8c0d9c1ccf2ccfcdebfe49497288ac00000000",["51cbd87429ba1559314e547a5878dd8449e1784696d5ee76239cfae4832b0187"],"20000000","1d0b6df7","5f60a4a6",true]} [2020-09-15 14:25:24] New job received [d279], block height 25263[1] [2020-09-15 14:25:36] json_receive[0][977]: {"id":"Stratum","jsonrpc":"2.0","method":"job","params":{"algorithm":"randomx","block_difficulty":[["cuckoo",925173],["randomx",405146916],["progpow",1134306013231]],"difficulty":[["cuckoo",4],["randomx",240000],["progpow",1000000000]],"epochs":[[607060,608060,[189,249,241,239,124,69,63,137,6,70,101,111,111,105,48,107,89,145,41,190,155,76,30,247,211,142,31,43,92,3,63,89]]],"height":607323,"job_id":0,"pre_pow":"0006000000000009445b000000005f60a4b220d1ea6168becadcfea30c27db5df3e36242f59b6866ed126841b870baf7fd756da369eb48b646c6f94fc5cf8ccd6aae0064d2b51315240bb1b5c0f67e2566b13b523c733c74dce04fd8bb85fe87754bfb4423693547c336d8965ed92ffc714e50c4a6846c4edf3d87fc04188e082b9e1bebe5d4a5e1adee5c94db4a70c87beaa4d4d049ea138ae7c6aa8e77b142f2d578ce053fe506c0e514c88c38d6e28ea14e2aa26f89c52a7858d62b670c4bf02e646ce7a9acba9d241e74df1d69b4a80100000000001ca5ca000000000013cb070000000000000004000000000000251170010000005bf111b02c020000d5ef387463f30304977804ebd347d0fff19005","xn":"b812"}}
[2020-09-15 14:25:01] Redirecting jobs from algorithm 1 to algorithm 0 workers Might be that it bugged and did not redirect jobs. So it continued hashing the old Epic job. But im curious what happened later because i see it allocated RX stuff after epic randomx job received?
|
|
|
Hi, Doktor. I change my miner algorithmes combination, so i can't now provide you log for randomepic+randomsfx combination, but i can provide you log for another problem. Randomepic+yescryptr16, after 7-8 hours of working miner can no more allocate large pages and start to use RAM:
Windows 10, ryzen 5 3600, 32 mb, 8GB RAM
RAM usage growing from 80MB after start miner to 900MB after 8 hours miner working.
Yes, that's something i got aware later, that's because on every algo switch it free's and re-allocates scratchpads. I will try to make it preserve previous allocations, after that the hugep issue should dissapear. I can only reproduce the mem leak with Verushash (one i knew about before releasing) , tried combinations of multiple algorithms (epic+randomx, randomx+yespower2b, randomx+cryptonight etc..)on 3 different systems and have no mem leaks, and it sends shares normally even after days of running...
|
|
|
Hi, Doktor! I found some strange bug - after 5-8 hours of miner work miner stop generate shares, but continue to load processor. Looks like some kind of dev fee bug. Next time i will try to provide a screenshot. Algos: randomepic+randomsfx.
And looks like there is some memory leaks, coz miner start with using ~72 MB RAM, and after few hours it take around 500 MB RAM.
I would like an extended log, a screenshot isn't too helpful. Please enable logging and add --extended-log flag. Did i manage to fix the previous miner crash issue?
|
|
|
Well why did you disable tellor so I cant gpu mine it, its even in your list am I know stupid enough to mine tellor?
it's not disabled. But looks like tellorpool.org is dead.
|
|
|
I was wondering if anyone could help me configure SRB miner I am using Awesome Miner and it only cpu mines it never uses the GPU's I have 7 AMD GPUS 4/480 2/570 1/470 they are all 8 gb virtual memory is set to 16000 mb but I do have 32 Gb ram.... should I bump that up is that why it crashes sometimes?
As well how do I tell it to GPU mine with all the gpus I configured it and it just cpu mines I tried all the other dialogs with no luck.
Maybe someone that has done this with these cards and yescryptr16 could tell me how to I want to mine goldcash with it.
Hi, yescryptr16 isn't gpu mineable, that's why you can't mine it with GPU's
|
|
|
Then why miner must reconnect if it just need to be ignored (progpow/cuckoo)? Don't it just have to wait for RX job? Ver. 0.4.7 don't have this problem.
Works same in v 0.4.7 btw. It is no difference for you if it reconnects or waits because it wouldnt mine RX anyways But i will see what i can do.
|
|
|
Hi. + Added algorithm 'argon2id_chukwa' + Added algorithm 'argon2d_dynamic' Is it for cpu only? If so then why? There is already exist gpu miners for these algo. Better add progpow and nimiq. And thank you for new version, i testing it right now. Also: Invalid difficulty received is also normal with Epic, its a bug in their node. Sometimes it just sends diff 0, and in that case miner disconnects and tries to reconnect. Don't you think better is to store first value of difficulty (when miner first connect to pool) and then miner receive Invalid difficulty - just use stored value instead of spent time for reconnecting? Or maybe add cmd line option for default difficalty? [2020-09-09 12:59:49] PARSE error: Invalid difficulty received[0] [2020-09-09 12:59:49] Redirecting jobs from algorithm 1 to algorithm 0 workers [a] [2020-09-09 12:59:49] Reconnecting to epic.icemining.ca:4000 in 15 seconds[0] [2020-09-09 13:00:03] Connected to epic.icemining.ca:4000[0] [2020-09-09 13:00:03] PARSE error: Invalid difficulty received[0] [2020-09-09 13:00:03] Reconnecting to epic.icemining.ca:4000 in 15 seconds[0] [2020-09-09 13:00:15] CPU result accepted [335ms][1] [2020-09-09 13:00:18] Connected to epic.icemining.ca:4000[0] [2020-09-09 13:00:18] PARSE error: Invalid difficulty received[0] [2020-09-09 13:00:18] Reconnecting to epic.icemining.ca:4000 in 15 seconds[0] [2020-09-09 13:00:22] CPU result accepted [488ms][1] [2020-09-09 13:00:32] New job received [d630], block height 116005[1] [2020-09-09 13:00:33] Connected to epic.icemining.ca:4000[0] [2020-09-09 13:00:33] Difficulty 240000.00000000[0] Too much reconnects. Invalid difficulty is received when a progpow job is received, so why would i 'store first value of difficulty and use stored value', when it wont be mined at all ? It's not RX. Also you cant just cant use any diff you want when you want it, vardiff doesn't work that way.
|
|
|
Hi, Doktor. Your last cmd line option for exceptions help with miner crushes, but after 8-10 hours of mining miner just stop mining, program continue to work, accept works from pools, but not generate hashes.
Try the latest 0.5.1 release, also without the cmd line option for exceptions, let's see if i managed to fix it.
|
|
|
V0.5.1
+ Added algorithm 'argon2id_chukwa' + Added algorithm 'argon2d_dynamic' + Added parameter '--miner-priority' to set priority of main miner process + Renamed '--cpu-priority' to '--cpu-threads-priority' + Faster hashrate refresh interval for CPU workers + Fixed (probably) crash when mining with 'randomepic' algorithm + Bug fixes
|
|
|
V0.5.0You definitely need to check out HELP and EXAMPLES folders because a lot of things changed from previous version!Total reorganisation, new features etc.. Hope a lot of you find it useful I will make a few video tutorials when i get some free time on how to use the new multi algorithm feature. Until then look in 'Examples' and 'Help' folder to get some clue on how to use the new feature. does the "," (i.e. comma) delineation between gpu not work anymore, or is it now only "!" now. Yes, it's ! now, check the examples folder it contains a bunch of good examples Is there a chance to add the "," back? it's just the "!" is non-standard and not used in any other miners... that i know of. the "!" makes it more difficult for multi-miners that used multiple programs. Also, do you now support NAVI on all gpu algo? I had to use a 'non standard' character because of the password field for example, which is used on a lot of pools to pass additional data, and they are comma separated. That's why i chose ; and ! because those are not used (probably) in wallet address, pool url, password field etc.. Also wanted it to be same for every parameter and not leave comma for gpu-id for example but use ! on others.. Hopefully software that uses SRB will adapt to the new format. Never got an answer on whether you support all algos on Navi now. Maybe you could try it ? I compiled all algorithms except MTP for Navi, but i did not test because i dont have a card. You could try and report back.
|
|
|
Google translate for you So sorry about typos: Log name: Application Source: Application Error Date: 09/08/2020 1:18:16 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic Description: Faulting Application Name: SRBMiner-MULTI.exe, Version: 0.5.0.0, Timestamp: 0x5f54d0dd Faulting module name: SRBMiner-MULTI.exe, version: 0.5.0.0, timestamp: 0x5f54d0dd Exception code: 0xc0000005 Error offset: 0x000000000041a80e Faulting Process ID: 0x11d4 Faulting application start time: 0x01d6854015a01e12 Report ID: 9d73e510-a973-44e4-b2b1-136933c49a16 Bad package full name: Application code associated with the failing package: Xml events: <Event xmlns = "http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name = "Application Error" /> <EventID Qualifiers = "0"> 1000 </EventID> <Level> 2 </Level> <Task> 100 </Task> <Keywords> 0x80000000000000 </Keywords> <TimeCreated SystemTime = "2020-09-07T22: 18: 16.063963500Z" /> <EventRecordID> 14228 </EventRecordID> <Channel> Application </Channel> <Computer> Computer </Computer> <Security /> </System> <EventData> <Data> SRBMiner-MULTI.exe </Data> <Data> 0.5.0.0 </Data> <Data> 5f54d0dd </Data> <Data> SRBMiner-MULTI.exe </Data> <Data> 0.5.0.0 </Data> <Data> 5f54d0dd </Data> <Data> c0000005 </Data> <Data> 000000000041a80e </Data> <Data> 11d4 </Data> <Data> 01d6854015a01e12 </Data> <Data> </Data> <Data> </Data> </EventData> </Event> Exception code: 0xc0000005I need to find where this access violation occurs.
|
|
|
Didn't try single algo on this version, 0.4.7 work fine. Got same error without crash: [2020-09-07 19:46:54] New job received [0], block height 596233[0] [2020-09-07 19:47:12] Socket error : 10054[1] [2020-09-07 19:47:12] Reconnecting to yespower.eu.mine.zergpool.com:6533 in 15 seconds[1] [2020-09-07 19:47:24] New job received [1], block height 596233[0] [2020-09-07 19:47:28] Connected to yespower.eu.mine.zergpool.com:6533[1] and got new error: [2020-09-07 19:50:05] PARSE error: Invalid difficulty received[0] [2020-09-07 19:50:05] Redirecting jobs from algorithm 1 to algorithm 0 workers [a] [2020-09-07 19:50:05] Reconnecting to epic.icemining.ca:4000 in 15 seconds[0] Socket error 10054 is normal , means pool forcibly closed the connection. The crash now, that ain't normal Invalid difficulty received is also normal with Epic, its a bug in their node. Sometimes it just sends diff 0, and in that case miner disconnects and tries to reconnect. It would be good to find out the crash reason. can you dig the error from windows error reporting? i bet its 0xC0000005
|
|
|
does it also crash when running 1 algorithm ? (epic)
|
|
|
Got error with dual mining:
Did you run it as admin or normal user?
|
|
|
|