The application crash every 5 hours

[Jonas21]

I have 4 graphic cards (RX 580 Series Ellesmere 8GB). Windows 10 pro, SSD and 16GB RAM. The computer works with resources to spare. The drivers are the ones that correspond, with the old CMD it worked perfectly for me. Since the probe nanominer are constant drops of the application. I have tested version v1.2.0 and it lasts for about 4 days on average and version v1.2.1 only lasts a few hours open. I want to know if there is a solution or I directly put the old system to work.

Thank you.
#13

[Grumpy-Dwarf]

What algorithm are you running with nanominer?

[Jonas21]

I'm mining Ethereum, Ethash with pool eth-eu1.nanopool.org:9999.

[Grumpy-Dwarf]

Thanks. Are there any unusual messages in log files stored in logs/ after miner crash? Did it report some GPU hang or zero hashrate?
Maybe miner occupies GPU for more than two seconds for some reason and windows reloads the driver. Could you please increase TDR (Timeout Detection and Recovery) Delay to 20 seconds instead of default 2 seconds to see if it is the root of the problem? You can do this by running this register script and rebooting.

[Jonas21]

I did what he told me and the same problem keeps happening.
I show you some of the logs before the application closes.

2019-04-24 07:11:41: [Statistics] Ethereum - Total speed: 141.044 MH/s, Total shares: 2618 Rejected: 6, Time: 2d 06h 19m 53s
2019-04-24 07:11:41: [Statistics] Ethereum: GPU 0 28.044 MH/s, GPU 1 28.161 MH/s, GPU 2 27.556 MH/s, GPU 3 27.556 MH/s, GPU 4 29.727 MH/s
2019-04-24 07:11:41: [Statistics] Ethereum last 10 min - GPU 0: 28.041 MH/s, GPU 1: 28.158 MH/s, GPU 2: 27.557 MH/s, GPU 3: 27.554 MH/s, GPU 4: 29.726 MH/s. Total: 141.036 MH/s.
2019-04-24 07:12:07: [Ethash] ~~~~~~ DevFee end ~~~~~~

[Grumpy-Dwarf]

Does it always crashes right after DevFee end?

[Jonas21]

Not always

[Grumpy-Dwarf]

But every time it crashes it is right after fee, isn't it?

[Jonas21]

Only a few times, not always

[Jonas21]

2019-04-25 05:59:48: [Statistics] Ethereum - Total speed: 141.023 MH/s, Total shares: 991 Rejected: 6, Time: 22:04:19
2019-04-25 05:59:48: [Statistics] Ethereum: GPU 0 28.041 MH/s, GPU 1 28.156 MH/s, GPU 2 27.554 MH/s, GPU 3 27.552 MH/s, GPU 4 29.721 MH/s
2019-04-25 05:59:49: [Statistics] GPU0 t=74°C fan 36% power 132.00W, GPU1 t=75°C fan 39% power 125.51W, GPU2 t=75°C fan 43% power 119.73W, GPU3 t=75°C fan 41% power 120.55W, GPU4 t=74°C fan 27% power 94.57W. Total power: 592.37W
2019-04-25 06:00:19: [Ethash] ~~~~~~ DevFee end ~~~~~~

Its true, always crash in DevFee end.

Would it be possible to start up for when it closes?

[Grumpy-Dwarf]

While we are investigating this bug here is a workaround - you can run miner in a script that relaunches it. Put it in a file, say, run.bat and execute instead of miner:

:start
nanominer.exe
echo crashed, restarting
goto start

Of course this is only a workaround while we are trying to reproduce and solve this bug.

[Grumpy-Dwarf]

We've simulated similar crash and have fixed it. Please check if latest nanominer 1.2.4 works fine on your system now.

[Grumpy-Dwarf]

Hope this was exactly same bug we've reproduced and fixed with 1.2.4 version.

[Jonas21]

The constant crash continue every day. Use 1.3.2 and 1.3.3

Maybe you need more information. Could my config.ini be more optimal with my graphics?
Sapphire Pulse Radeon Rx 580 8GB. I have 5 in my rig.

My config.ini without emails and wallets:

[Ethash]
wallet = *
rigName = KingWorker
email = *
pool1 = eth-eu1.nanopool.org:9999
pool2 = eth-eu2.nanopool.org:9999
pool3 = eth-us-east1.nanopool.org:9999
pool4 = eth-us-west1.nanopool.org:9999
pool5 = eth-asia1.nanopool.org:9999
pool6 = eth-jp1.nanopool.org:9999
pool7 = eth-au1.nanopool.org:9999

[RandomHash]
wallet = *
paymentId = *
rigName = rig1
email = *
pool1 = pasc-eu1.nanopool.org:15556
pool2 = pasc-eu2.nanopool.org:15556
pool3 = pasc-us-east1.nanopool.org:15556
pool4 = pasc-us-west1.nanopool.org:15556
pool5 = pasc-asia1.nanopool.org:15556

2019-05-31 23:11:26: [Ethash] ~~~~~~ DevFee begin ~~~~~~
2019-05-31 23:11:27: New job from commission host
2019-05-31 23:11:27: [Statistics] Ethereum - Total speed: 141.607 MH/s, Total shares: 1458 Rejected: 0, Time: 1d 04h 46m 45s
2019-05-31 23:11:27: [Statistics] Ethereum: GPU 0 28.021 MH/s, GPU 1 28.157 MH/s, GPU 2 28.155 MH/s, GPU 3 27.553 MH/s, GPU 4 29.721 MH/s
2019-05-31 23:11:27: [Statistics] GPU0 t=74°C fan 55% power 125.51W, GPU1 t=74°C fan 50% power 130.91W, GPU2 t=75°C fan 60% power 120.64W, GPU3 t=74°C fan 56% power 120.92W, GPU4 t=74°C fan 33% power 96.98W. Total power: 594.95W
2019-05-31 23:11:27: New job from commission host
2019-05-31 23:11:27: [Statistics] Ethereum - Total speed: 141.607 MH/s, Total shares: 1458 Rejected: 0, Time: 1d 04h 46m 45s
2019-05-31 23:11:27: [Statistics] Ethereum: GPU 0 28.021 MH/s, GPU 1 28.157 MH/s, GPU 2 28.155 MH/s, GPU 3 27.553 MH/s, GPU 4 29.721 MH/s
2019-05-31 23:11:33: New job from commission host
2019-05-31 23:11:33: [Statistics] Ethereum - Total speed: 141.606 MH/s, Total shares: 1458 Rejected: 0, Time: 1d 04h 46m 51s
2019-05-31 23:11:33: [Statistics] Ethereum: GPU 0 28.025 MH/s, GPU 1 28.155 MH/s, GPU 2 28.154 MH/s, GPU 3 27.554 MH/s, GPU 4 29.718 MH/s
2019-05-31 23:11:33: [Statistics] GPU0 t=74°C fan 55% power 124.78W, GPU1 t=74°C fan 50% power 133.67W, GPU2 t=75°C fan 60% power 121.18W, GPU3 t=74°C fan 56% power 121.30W, GPU4 t=74°C fan 33% power 97.44W. Total power: 598.36W
2019-05-31 23:11:47: Ethereum - SHARE FOUND (GPU: 2, nonce: 0x36c5170b4c25a814).
2019-05-31 23:12:04: [Statistics] Ethereum - Total speed: 141.636 MH/s, Total shares: 1458 Rejected: 0, Time: 1d 04h 47m 22s
2019-05-31 23:12:04: [Statistics] Ethereum: GPU 0 28.037 MH/s, GPU 1 28.159 MH/s, GPU 2 28.158 MH/s, GPU 3 27.557 MH/s, GPU 4 29.725 MH/s
2019-05-31 23:12:04: [Statistics] Ethereum last 10 min - GPU 0: 28.028 MH/s, GPU 1: 28.159 MH/s, GPU 2: 28.159 MH/s, GPU 3: 27.556 MH/s, GPU 4: 29.723 MH/s. Total: 141.625 MH/s.
2019-05-31 23:12:30: New job from pasc-eu1.nanopool.org:15556
2019-05-31 23:12:30: [Statistics] PascalCoin - Total speed: 269.331 H/s, Total shares: 593 Rejected: 4, Time: 1d 04h 47m 48s
2019-05-31 23:12:30: [Statistics] PascalCoin: CPU: 269.331 H/s
2019-05-31 23:12:30: New job from pasc-eu1.nanopool.org:15556
2019-05-31 23:12:30: [Statistics] PascalCoin - Total speed: 269.331 H/s, Total shares: 593 Rejected: 4, Time: 1d 04h 47m 48s
2019-05-31 23:12:30: [Statistics] PascalCoin: CPU: 269.331 H/s
2019-05-31 23:12:35: [Statistics] Ethereum - Total speed: 141.631 MH/s, Total shares: 1458 Rejected: 0,
Time: 1d 04h 47m 53s
2019-05-31 23:12:35: [Statistics] Ethereum: GPU 0 28.028 MH/s, GPU 1 28.159 MH/s, GPU 2 28.159 MH/s, GPU 3 27.558 MH/s, GPU 4 29.727 MH/s
2019-05-31 23:12:35: [Statistics] GPU0 t=74°C fan 55% power 128.69W, GPU1 t=74°C fan 50% power 135.14W, GPU2 t=74°C fan 60% power 121.87W, GPU3 t=74°C fan 57% power 122.33W, GPU4 t=74°C fan 33% power 97.83W. Total power: 605.86W
2019-05-31 23:12:38: New job from pasc-eu1.nanopool.org:15556
2019-05-31 23:12:38: [Statistics] PascalCoin - Total speed: 242.222 H/s, Total shares: 593 Rejected: 4, Time: 1d 04h 47m 55s
2019-05-31 23:12:38: [Statistics] PascalCoin: CPU: 242.222 H/s
2019-05-31 23:12:39: [Ethash] ~~~~~~ DevFee end ~~~~~~

[broadfashow]

I use nanominer 1.6.2,

Mining Eth using pools:
eth-us-west1

Single card mining using RTX 2080.
Nvidia Driver version 441.41

I am experiencing consistent crashing and restarting of the miner. Nothing out of the ordinary in the logs output. Has this issue been fixed? If so how/what solution?

[Grumpy-Dwarf]

Does miner restart itself? If yes, it prints message to log (stored in logs/ folder) prior to restart. This can be something like GPU hang or minimum configured hashrate not reached.

[broadfashow]

Yes the miner restarts itself...

2019-12-11 09:59:42: System exception:
2019-12-11 09:59:42: device: 0; an illegal memory access was encountered
2019-12-11 09:59:42: Can't work on device: 0
2019-12-11 09:59:42: Miner has already been restarted 2 times
2019-12-11 09:59:42: Self-restarting miner process.

[broadfashow]

2019-12-11 09:57:59: System exception:
2019-12-11 09:57:59: device: 0; unspecified launch failure
2019-12-11 09:57:59: Can't work on device: 0
2019-12-11 09:57:59: Miner has already been restarted once
2019-12-11 09:57:59: Self-restarting miner process.

[Grumpy-Dwarf]

This is usually some hardware related issue like overclocking or bad riser of whatever. This is how miner workarounds hardware-specific problems and if it works it is fine.