SOCKET ERROR - PARSE error: Protocol error 3

[CoUsTeQ]

Hello.

If I leave focus on console and leave it over night, it will mine just fine. The problem appears when I don't have focus on console, so while browsing web, playing games etc. It will simply freeze, not print any output until I set focus on console again and press any key, then it will start printing results super fast and usually throw error that I pasted below:

[2017-06-02 17:58:37] : SOCKET ERROR - PARSE error: Protocol error 3 [2017-06-02 17:58:37] : Pool connection lost. Waiting 15 s before retry (attempt 1).

Screen of miner working:

http://screenshooter.net/103149331/02_06_2017__17_53_33

Config:

config.txt

Any idea what might be the cause? I'm really loving the performance of this miner (getting 590H/s while I'm not using PC and about 400 while I'm doing things on PC), so I don't really want to switch it for different miner.

[psychocrypt]

I will try to reproduce the issue.

btw: please do not mine against the minergate pool see this reddit post

[CoUsTeQ]

Okay, thanks.

This is my network log for today after 6h of mining

Network error log: | Date | Error text | | 2017-06-02 17:50:14 | PARSE error: Protocol error 3 | | 2017-06-02 17:58:37 | PARSE error: Protocol error 3 | | 2017-06-02 18:26:54 | PARSE error: Protocol error 3 | | 2017-06-02 20:14:37 | PARSE error: Protocol error 3 | | 2017-06-02 20:26:05 | PARSE error: Protocol error 3 | | 2017-06-02 22:15:47 | PARSE error: Protocol error 3 | | 2017-06-02 22:48:36 | PARSE error: Protocol error 3 | | 2017-06-02 23:23:18 | PARSE error: Protocol error 3 |

That "freezing" and not doing its job and not printing results happens mostly when I minimize miner.

Also, what pool should I use then? My friend that recommended me mining told me that I should be using dwarfpool, however Poloniex disabled XMR for now and I can't get address for me, so I can't put it in config file for dwarfpool.

[psychocrypt]

Do you running the miner under linux? If so please checkout the latest dev branch and try if the error still exists.

Which shell do you use?

You could find a list of pools here. To create a Monero address which is independent of any exchange service you can use the today announced Monero GUI wallet. You should not store your XMR on an exchange! The the mnemonic on paper and you could rebuild your wallet any time.

[fireice-uk]

@psychocrypt This will be caused by something exotic in the minergate pool implementation. We will need to get a traffic dump to debug this one.

[CoUsTeQ]

I think I found the case. I'm using Windows 10.

When I click and hold on console to select text/whatever, for example this:

http://screenshooter.net/103149331/03_06_2017__13_27_57

Then the printing will stop and if I resume fast enough, it will keep mining and working fine. If I leave it like that for a while, it stops completely and if I "unselect" after some time (to do that I need to click right mouse button OR any key), it throws me Protocol error 3.

It seems the issue is retaled with Windows 10, cmd changes and stuff like that. When I open cmd and use ping and select text in it, it also freezes, completely disabling output. I tried to use "legacy console" mode but it's still the same.

Would be good if you can note that down in FAQ or somewhere, so some people will understand this better.

Also, I'm pretty new to Monero. I was going purely for profit here. My friend recommended me to use my Ryzen 1700 for mining Monero and I'm a bit confused. What's the best option for me to mine Monero and to sell it? I wanted to use Dwarfpool (recommended by friend) and use Poloniex wallet address to get Monero directly here, however Poloniex temporalily disabled Monero and I picked whatever I found. Kinda confused what to do now.