Quote from: r3lentleSs on December 06, 2017, 03:57:52 PM

DSTM miner gets killed due to low hashrate average, even tho i've set the hashrate errors to 99

Code:

[wo 06/12/2017][16:15:00] Config.bat loaded.
[wo 06/12/2017][16:17:39] Miner was started. v.1.8.1.
[wo 06/12/2017][16:21:55] Abnormal hashrate. Average: 1839/1840 Last: 1818/1840.
[wo 06/12/2017][16:22:22] Abnormal hashrate. Average: 1836/1840 Last: 1828/1840.
[wo 06/12/2017][16:23:16] Abnormal hashrate. Average: 1835/1840 Last: 1823/1840.
[wo 06/12/2017][16:23:43] Abnormal hashrate. Average: 1834/1840 Last: 1808/1840.
[wo 06/12/2017][16:24:10] Abnormal hashrate. Average: 1832/1840 Last: 1819/1840.
[wo 06/12/2017][16:24:40] Low hashrate. Average: 1832/1840 Last: 1819/1840.
[wo 06/12/2017][16:24:40] Miner restarting... Miner ran for 00:09:06.
[wo 06/12/2017][16:25:16] Process zm.exe was successfully killed.
[wo 06/12/2017][16:28:11] Config.bat loaded.
[wo 06/12/2017][16:28:34] Config.bat loaded.
[wo 06/12/2017][16:29:14] Miner was started. v.1.8.1.
[wo 06/12/2017][16:43:54] Low hashrate. Average: 1826/1820 Last: 1816/1820.
[wo 06/12/2017][16:43:54] Miner restarting... Miner ran for 00:14:46.
[wo 06/12/2017][16:44:30] Process zm.exe was successfully killed.

Windows 10 PRO
6X P106-100 GPU's

Core + 225 MEM + 200 POW limite 67 TEMP 68

I'm using 1830 as ~

DSTM miner always start with a higher hashrate, and starts to drop. Thats why i'm getting alot of hashrate erros.
So how to fix this, i've set 99 hashrate error, and after 20 minutes. zm.exe miner gets killed
http://prntscr.com/hjxkyp
Why doest it say "hashrate error = 0/99 and then 57/99
Should i set it to 1000 or what?

Hello there, try lowering the average speed to 1780-1800 on the config.bat then u will not have any problems (script sensing avg hashing speed is below the normal), you dont need to mess with the hashing errors at all.

hope this help you.