Quote from: pietro31@gmail.com on July 12, 2018, 05:01:06 AM

Quote from: yhoga45 on July 11, 2018, 09:06:45 PM

Quote from: ethernaly on July 10, 2018, 08:57:21 PM

Hi guys, I'm using 5 GTX 1060 6GB (ZOTAC AMP!) with the following variables and 16GB of page files.

GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100

I'm mining with this server from january 2018 and until today I've no problem. During the claymore restart I noticed a strange error:

- CANNOT create dag file error 11 (something similar)

I tried to remove the updated driver and re-install the tested one: 372.54, but at the end I'm using -eres 0

Why is this necessary? I Read this:
-eres this setting is related to Ethereum mining stability. Every next Ethereum epoch requires a bit more GPU memory, miner can crash during reallocating GPU buffer for new DAG.
To avoid it, miner reserves a bit larger GPU buffer at startup, so it can process several epochs without buffer reallocation.
This setting defines how many epochs miner must foresee when it reserves GPU buffer, i.e. how many epochs will be processed without buffer reallocation. Default value is 2.

So can I set to 1? or it's better 0?

Server spec:
- Windows 10 64Bit
- SSD 60GB
- 4GB RAM
- 5x GTX 1060 AMP Edition Zotac 6GB
- Claymore 10

As I said I've no problems until today. (What's -eres 0? Can someone explain this setting?)

EDIT:
This server is used in "Solo Mode" (Ethereum) with ethermine

EDIT2:
GPU #0: GeForce GTX 1060 6GB, 6144 MB available, 10 compute units, capability: 6.1
GPU #1: GeForce GTX 1060 6GB, 6144 MB available, 10 compute units, capability: 6.1
GPU #2: GeForce GTX 1060 6GB, 6144 MB available, 10 compute units, capability: 6.1
GPU #3: GeForce GTX 1060 6GB, 6144 MB available, 10 compute units, capability: 6.1
GPU #4: GeForce GTX 1060 6GB, 6144 MB available, 10 compute units, capability: 6.1
ETH: GPU0 24.015 Mh/s, GPU1 24.122 Mh/s, GPU2 24.138 Mh/s, GPU3 24.109 Mh/s, GPU4 24.139 Mh/s (same result at the moment)

What version did you use? If you used old version maybe that's the problem because I had this problem too, then I upgraded to the new version (not the latest) and the problem was gone. Maybe if you used old to try to change to the new one especially 11.9 has released

I also got the same problem with 2 rigs of 5 1080 ti was claymore go good for 2 months today give the same error message as you memory dag ca not locate, I try to set baffer seting 0 1 2 any n. will no work

Have you tried using the newest Claymore which is 11.9? When I got this message I used the old one (Claymore v.10) If you haven't tried the new one you should try it.