Random freezes when no interactions

[DcR-NL]

Basic information

• Type of the CPU.
  • Intel Core i7 6700K
• Type of the GPU (if you try to miner with the GPU).
  • CPU only
• Version and OS
  • v2.2.0 on Windows 10 Pro

Stability issue

• Is the CPU or GPU overclocked?
  • No
• Is the Main memory of the CPU or GPU undervolted?
  • No

Miner occasionally freezes when not interacting with it. Moving console window sometimes fixes it. Other times I need to interact with it (e.g. press 'c', 'h' or 'r') to make it continue.

Additional facts

• It happens almost every (other) day, sometimes multiple times a day and it can happen within minutes of launching (but multiple hours is more common).
• Once I noticed it after 12 hours (additional proof of the need for interaction to make it continue)
• Doesn't appear to happen when using the system (only when AFK)
• Haven't experienced this issue with same version on Fedora 27 (different PC, older i7)
• Friend has same issue with his AMD Ryzen CPU on Windows 10

Log output

Miner stopped responding at 21:31:50 (1 minute after launching) and continued an hour later (22:31:37) because I moved the console window. Checked pool; no results/hash-rate for an hour.

[2018-01-16 21:31:33] : Difficulty changed. Now: 15190.
[2018-01-16 21:31:33] : New block detected.
[2018-01-16 21:31:40] : Result accepted by the pool.
[2018-01-16 21:31:50] : Result accepted by the pool.
[2018-01-16 22:31:37] : Result rejected by the pool.
[2018-01-16 22:31:37] : Your miner was unable to find a share in time. Either the pool difficulty is too high, or the pool timeout is too low.
[2018-01-16 22:31:37] : Fast-connecting to pool.itnspool.net:7777 pool ...
[2018-01-16 22:31:38] : Fast-connecting to pool.intensecoin.net:7777 pool ...
[2018-01-16 22:31:38] : Difficulty changed. Now: 5000.
[2018-01-16 22:31:38] : New block detected.
[2018-01-16 22:31:38] : New block detected.
[2018-01-16 22:31:38] : New block detected.
[2018-01-16 22:31:38] : New block detected.
[2018-01-16 22:31:38] : New block detected.
[2018-01-16 22:31:38] : New block detected.
[2018-01-16 22:31:38] : New block detected.
[2018-01-16 22:31:38] : New block detected.
[2018-01-16 22:31:38] : New block detected.
[2018-01-16 22:31:38] : New block detected.
[2018-01-16 22:31:39] : New block detected.
[2018-01-16 22:31:39] : New block detected.
[2018-01-16 22:31:39] : New block detected.
[2018-01-16 22:31:39] : New block detected.
[2018-01-16 22:31:39] : New block detected.
[2018-01-16 22:31:39] : New block detected.
[2018-01-16 22:31:39] : New block detected.
[2018-01-16 22:31:39] : New block detected.
[2018-01-16 22:31:39] : New block detected.
[2018-01-16 22:31:40] : New block detected.
[2018-01-16 22:31:40] : New block detected.
[2018-01-16 22:31:40] : New block detected.
[2018-01-16 22:31:40] : New block detected.
[2018-01-16 22:31:40] : New block detected.
[2018-01-16 22:31:40] : New block detected.
[2018-01-16 22:31:40] : SOCKET ERROR - [pool.intense.hashvault.pro:3333] RECEIVE error: A blocking operation was interrupted by a call to WSACancelBlockingCall. 
[2018-01-16 22:31:40] : Pool pool.intensecoin.net:7777 connected. Logging in...
[2018-01-16 22:31:40] : Difficulty changed. Now: 10000.
[2018-01-16 22:31:40] : Pool switched.
[2018-01-16 22:31:40] : Pool pool.itnspool.net:7777 connected. Logging in...
[2018-01-16 22:31:40] : Difficulty changed. Now: 10000.
[2018-01-16 22:31:40] : New block detected.

Settings

Mining Intensecoin (Monero). Multi-pool. Didn't touch connection settings the first couple of times (tried doubling timeout later, but didn't help).

config (only changed settings compared to default; removed wallet address)

"pool_list" :
[
    {"pool_address" : "pool.intense.hashvault.pro:3333", "wallet_address" : "WALLET", "pool_password" : "x", "use_nicehash" : false, "use_tls" : false, "tls_fingerprint" : "", "pool_weight" : 100 },
    {"pool_address" : "pool.itnspool.net:7777", "wallet_address" : "WALLET", "pool_password" : "x", "use_nicehash" : false, "use_tls" : false, "tls_fingerprint" : "", "pool_weight" : 20 },
    {"pool_address" : "pool.intensecoin.net:7777", "wallet_address" : "WALLET", "pool_password" : "x", "use_nicehash" : false, "use_tls" : false, "tls_fingerprint" : "", "pool_weight" : 50 },
],

"use_slow_memory" : "never",

cpu (only changed settings compared to default)

"cpu_threads_conf" :
[
    { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 },
    { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 2 },
    { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 4 },
    { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 6 }
],

[seminarian]

I'm having similar issues on windows 10 on my mining rig! It stops pushing results until I push a button. If I push a button it tries to push results but in many cases it gets rejected cuz it's too late. Please help!

[DcR-NL]

Happened again on a different pool (pressed 'h' at 12:44:12):

[2018-01-20 12:01:39] : Result accepted by the pool.
[2018-01-20 12:44:12] : Difficulty changed. Now: 6270.
[2018-01-20 12:44:12] : New block detected.
[2018-01-20 12:44:12] : New block detected.
[2018-01-20 12:44:12] : Result rejected by the pool.
[2018-01-20 12:44:12] : Your miner was unable to find a share in time. Either the pool difficulty is too high, or the pool timeout is too low.
[2018-01-20 12:44:12] : Fast-connecting to pool.intense.hashvault.pro:3333 pool ...
[2018-01-20 12:44:12] : Fast-connecting to pool.intensecoin.net:7777 pool ...
[2018-01-20 12:44:12] : New block detected.
[2018-01-20 12:44:12] : New block detected.
[2018-01-20 12:44:12] : New block detected.
[2018-01-20 12:44:12] : New block detected.
[2018-01-20 12:44:12] : New block detected.
[2018-01-20 12:44:13] : New block detected.
[2018-01-20 12:44:13] : New block detected.
[2018-01-20 12:44:13] : New block detected.
[2018-01-20 12:44:13] : New block detected.
[2018-01-20 12:44:13] : New block detected.
[2018-01-20 12:44:13] : New block detected.
[2018-01-20 12:44:13] : New block detected.
[2018-01-20 12:44:13] : New block detected.
[2018-01-20 12:44:13] : New block detected.
[2018-01-20 12:44:14] : New block detected.
[2018-01-20 12:44:14] : New block detected.
[2018-01-20 12:44:14] : New block detected.
[2018-01-20 12:44:14] : New block detected.
[2018-01-20 12:44:14] : New block detected.
[2018-01-20 12:44:14] : New block detected.
[2018-01-20 12:44:14] : New block detected.
[2018-01-20 12:44:14] : New block detected.
[2018-01-20 12:44:14] : New block detected.
HASHRATE REPORT - CPU
| ID |    10s |    60s |    15m | ID |    10s |    60s |    15m |
|  0 |   73.7 |   73.7 |   73.7 |  1 |   77.6 |   77.6 |   77.6 |
|  2 |   75.7 |   75.7 |   75.7 |  3 |   75.6 |   75.6 |   75.6 |
-----------------------------------------------------
Totals:    302.6  302.6  302.6 H/s
Highest:   321.9 H/s
[2018-01-20 12:44:14] : SOCKET ERROR - [pool.itnspool.net:7777] RECEIVE error: A blocking operation was interrupted by a call to WSACancelBlockingCall.
[2018-01-20 12:44:14] : Pool pool.intensecoin.net:7777 connected. Logging in...
[2018-01-20 12:44:14] : Pool pool.intense.hashvault.pro:3333 connected. Logging in...
[2018-01-20 12:44:14] : Difficulty changed. Now: 20000.

[JerichoJones]

TURN OFF QUICKEDIT

[DcR-NL]

@JerichoJones Thank you for the tip. It seems like this might be a solution (How and why does QuickEdit mode in Command Prompt freeze applications). I will try disabling this mode globally and report back in a couple of days with the results.

BTW, apparently there are programmatic approaches to disable QuickEdit mode (e.g. C#).

[seminarian]

I can confirm that disabling QuickEdit mode for me it has fixed the issue!

[DcR-NL]

Same, disabling QuickEdit Mode has solved my issue. Thanks again. :grinning: Closing this one.

[zeke29]

hello where I can find Quick Edit mode?

[PNunesDev]

@zeke29 Hi there, just go to the properties of your .exe file or the shortcut of it. Then go to options tab and disable the Quick mode.