Interesting, why the timeout 15?
Note, the exe string needs to be single line, no c returns, or line breaks etc.
Also, 2 things you could try on the problem rig.
-mode 1
-dbg 1
I'd try stripping that to the minimum, (also make sure you set your virtual memory to at least 16GB!!!)
setx GPU_FORCE_64BIT_PTR 1
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool eu1.nanopool.org:9999 -ewal wallet.rig/email -epsw x -mode 1
BUT.....I just checked, and it looks like nonopool servers are different to what you have above.
Should be
eth-eu1.nanopool.org
Are you 100% sure, the server you are using is correct?
Cheers
The timeout is just so msi afterburner will spin up the fans before the mining starts. I have the rig on wifi sometimes and it need some more seconds to reconnect to
It was in a single line, just automatic line break in notepad when i copied it. Same on both machines too. Virtual memory was 16gb but after a while it finally said that dag creation failed. I need 29 GB virtual memory to fill DAG on 6x gtx 1070 and 1x gtx 1060 card. I have put 32-40GB virtual memory now instead. The machine was reinstalled to with 10 pro instead of 10 pro n. Shouldn´t do anything i guess.
You are right, the server is wrong but eu1-nanopool.org actually works too
It seems that the problem was solved with virtual memory, i used 5x 1070 before and added two cards today.
Nice going, and thanks for taking the time to feedback results.
I was wondering about that nanopool address, it's possible they used eu1.nanopool.org:9999 previously, but have changed the servers/names and have various aliases. The problem with that can be, the routers in between, DNS cache and arp tables will have duplicates. This stuff is self healing, but can actually take days to settle down, and in the mean time, things, (like name resolution, routing etc) can take longer than expected, (expected as in, longer than the time out limits your end, or along the path etc), and as you're essentially on the far end of a long chain, all those "little" delays can add up, and the application will appear to hang your end, while in reality, it's just waiting.
Hopefully, setting the log to debug, you will see a bunch of additional entries, like "waiting... etc etc" if you don't see anything logging, then probably claymore is hung. (Don't forget, if you're using notepad to view the live log, you need to refresh/reopen it, to see new entries.
Hitting f5 in explorer, should show you the log file size increasing, is another method to determine if anything is logging.
(don't forget to disable debug log when you're stable)
Virtual memory. It's far from clear what claymore is doing with that, and although 16GB is the minimum, I'd suggest it's never a good plan to aim for the bottom!!
It's only VM anyway, set it as high as you like, (although to be safe, less than free space on disc, plus some headroom).
Suppose you have 100GB free, setting VM to 60GB should be pretty safe, assuming your rig is dedicated for only mining.
Ok, afterburner.
Less than ideal to use that imho, any application can crash, what damage can happen if afterburner crashes? I'd rather not find that out the hard way.
Did you spot in 11.7, Nvidia temperature control is now supported?
added temperature management and overclock support for recent Nvidia cards in Windows: "-tt", "-powlim", "-cclock", "-mclock", "-tt", "-fanmax", "-fanmin" options are supported for Nvidia too. I'd suggest using it. That way, if claymore crashes, (no more work is pushed to GPUs), and at least your GPUs revert to bios control, cool down etc.
Right now, if your afterburner crashes, and claymore carries on, you're going to potentially cook those cards, or force them to their hardware trip point, (probably something scary like 100C plus).
NOT GOOD.
Remember, mining is a bit extreme for GPUs.
Like anything engineered, they are designed for a purpose, and have a duty cycle to match.
It's not expected under typical use, that GPUs are running, flat out, 24/7, this means they will probably have a shorter lifespan than if they were used for gaming.
Render farms, (not so dissimilar from mining), are constantly swapping out/in cards, and usually have failovers and backup nodes to pick up the slack.
So the key here is stability, steady temperature control, depending on the fan type, probably constant rotation, speed regulation, rather than on/off/on is going to be preferable. Think of it like trying to avoid the extremes, and flatten out the peaks and troughs.
Mechanically, we have to consider these GPUs are getting hot! Parts are MUCH hotter than 100C, very reliant on cooling, and different materials expand/contract at different rates. Copper is one of the more extreme examples, but any such mechanical expansion is also going to reduce life, contribute to increase failure. It's the CHANGE, (expansion), that causes mechanical stress. Avoiding that as much as possible, will extend life.
If you're in this for the long run, ROI etc, then it's a good idea to consider these angles, and imho, get cards with a well engineered cooling scheme, active and passive, reduce voltages/current etc, set the upper cut limits lower, (e.g 98C to 88C), set a reasonably LOW target temp, (60C), if it means you work the fans harder, so be it, those are cheap to replace compared to a GPU.
(Find some stable settings, and customise your BIOS to reflect that). That way, if all else fails, the hardware will self protect.
Last advice, wifi.
I was amazed at how many instabilities evaporated when I switched that off.
Part of the problem is, these days, wifi routers are doing all kinds of (for open rigs, nasty stuff), like beam forming, and essentially flooding the space with microwaves, as are of course all the devices trying to connect, like phones etc.
In your typical PC, it's in a metal box, microwaves don't travel well through flat/sheet metal, and wifi antennas are OUTSIDE the PC case, (even in laptops, antennas are as far away from the motherboard as possible.
Now we have open mining rigs, no casing, (shielding) and worse still, we have a LOAD of wire stands running all over the place. Cables from PCIe cards to risers, (should be shielded, but who knows), but also we have a lot of single strands, power lines to the GPUs, and normally ALL this stuff is further shielded inside a metal computer case. Furthermore, all components in there will share a common shield ground.
While microwaves, (and any "radio" band waves for that matter), well those LOVE single strands of wire, those being brilliant antennas, being it receiving or transmitting.
So, what all this adds up to is TROUBLE, when exposing open rig, no common ground, worse still, multiple floating grounds, multiple power supplies lots and lots of microwave sucking antennas.
As recently as 2 weeks ago, (after months of mining), I finally got around to hard-wiring LAN to all my rigs.
This comes after months of chasing down gremlins, timeouts, dropped sockets at pool, (while still having local internet access), random lockups, crashes, you name it, it's a long list, and a LOT of time.
I'd say, I'd fought hard to tune out 50~60% of events, reduced frequency for sure, but once every 7~10 days, I'd have a succession of dropped connections, resulting in stale shares down the line.
Since eliminating wifi, (and 1 rig on powerline LAN), I'm amazed at the difference, (and kicking myself, as I know better), I guess it had become a bit of a campaign, which with hindsight, was a lost cause :-)
What one needs to consider is, steady, steady, steady is the key to mining.
Eliminate as many of the potential risks to that, and you're set up to go steady :-)
Good luck.
