Those are 1920 x 1080 max at 60 hertz.  For the same price you can get 3840 x 2160 support (item looks identical) on eBay here: https://www.ebay.com/itm/HDMI-Display-port-Dummy-Plug-4K-Display-MINING-3840-2160-60Hz-Headless-Emulator/222825303024?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649 shipping from the US (Texas, I think?) or if you have plenty of time the same item is $2.79 shipped from China (same meaning also 3840 x 2160 or "4K" support) here: https://www.ebay.com/itm/HDMI-Display-Emulator-Dummy-Plug-Headless-Ghost-1-4-DDC-EDID-for-PC-Mac-Devices/202212531225?ssPageName=STRK%3AMEBIDX%3AIT&var=502180406403&_trksid=p2057872.m2749.l2649.

Second "-dpool" is messing you up. Should be "-dwal", right?

Dummy 4K "headless" emulator / adapters: has anyone found situations where you have to use them?  I see these for anywhere from $3 to $8 for HDMI and $8 and up for true DisplayPort - both of those being the 4096 x 2180 (i.e. "4K UHD") resolution adapters with 60Hz refresh rate.  I see less expensive versions for 1920HD.

I suppose that I am always linking to my ViewSonic XG2704 240MHz refresh display, so I haven't run into the need for them, but I was talking to a friend last night that absolutely insisted that - in order to get the best hash rate - you really should have them for your display-less GPU cards.

Claymore:

Do you make some kind of intelligent checkpoint at the one hour point?  (59 minutes and whatever seconds, maybe?)  I see an inordinate amount of logfiles that are precisely 59:xx long with no apparent reason for the exit.

After removing overclocking, you still get this error for both - or one?  What are the cards and what's the base clock (and what you were using for OC)??

OK, I am confused: you show commands that look like they are stored in a CONFIG.TXT parameter file, but then you show what appears to be a command-line with parameters.

You can't have both: if there are parameters on the command-line, the CONFIG.TXT file is ignored / not used.  Since "-etht 200" is the default, adding it in CONFIG.TXT or on the command-line just adds one more step to the preparation phase.  Why are you asking it to use "qtminer" mode (-esm 1)?

I think the main problem is that you appear to be shooting for a solo mining configuration, as far as I can tell?  You don't show anything about a process running on your own port 8080 - which normally would be a web-based protocol.  Whassup?

For sure, but since they are all being 'feed' identical parameters, seems easier to just use "-cvddc 930 -cclock 1150 -mvddc 930" instead of giving each of them separately.  Unless they are different, really no reason to list them out like that.  No need to count them out or change when you add another card (unless of course it needs different parametersa).  My Sapphire RX 580 4GB Nitro+ goes just a little higher, but not much.

The "-di" parameter works either with or without commas, #11, 12, 13, etc are "A", "B", "C", etc. (actually I don't remember if it is CaSe SeNsItIvE - probably not, I would guess).

Yep, I agree.  I had a 3GB 1060 that went tits up, so I was looking for a reasonably priced replacment back around early December and was purposefully looking for a good OC'ing 6GB card.  The one I picked had to fit in the tight spot the generic 3GB HP card came out of the Pavilion Power 580-023w I bought for $499 from Walmart around mid-October, since there's no extra room or spare slot, because I have a SoundBlaster SBX Pro "Z" in that rig.  I selected the Gigabyte single fan "ICX" version, which is a good overclocker and a short slot (7,5" length) double wide jobbie.  I patiently waited for the card to get under $300.  Right now they are more like double that - when you can find one for sale.

The one I picked was a good runner in the silicon lottery derby, and I can easily run +240 with graphics programs and test / benchmark programs, but while I had been running +220 this week, it's been getting a slightly lower hash rate.  I just cut it back to +215 for now to see how it rides, and it's steady as a rock.

Here's the new GPU-Z shot:


and my "nVidia Inspector" settings:


It rarely ever goes beyond 80C, but I have it opened up just in case it gets hotter during the summer.  Right now it's steady on 78C bit it was 80C when I did the snapshot.

Are they all AMD cards?

1060 w/3GB RAM should do about that, maybe 21Mh/s if you get things just right.  My Gigabyte card likes 70% power limit, about +220 GPU speed offset and +1000 memory offset.  Not all cards will do that, I have Hynix VRAM, also.  Some might get a little more, but I don't know of any way to set the memory more than +1000 offset.  My card will hold a stable +240 GPU, but I get crappy shares relative to what I get at +220.  Every single card is just a little different unless they came out of the same batch, same model from the same maker.  I have my temp max at 80C which is about what it does when I'm dual mining (and yes, about 350Mh/s for Verge / XVG is what I get, although you can tweak -dcri up to the best your card will do without impacting your ETH hashing much (I limit it to 1% impact) then you might be able to get 400+Mh/s but in my experience it messes things up and I get recycles way too often instead of it running the clock out (-r 239) at four hours, which is my self-imposed limit before I restart the miner.  I was using -dcri 70 which seemed to be the sweet spot for intensity on my specific card.  The other rig is a GTX1080 with RX 580's, all 8GB mostly Asus OC/ROG/Strix models with one Sapphire Nitro+ 580 OC.

Some people insist on just letting it run forever, but my machines seem to grow a minds of their own after a few hours, so 4 hours is what I picked.  For the GTX1060 memory ramped up to 10K speed, I build the DAG in between 8 and 9 seconds.  No big woop...  I am back to single mining ETH for now, I just get too darned squirrelly dual mining.

You can not change the nVidia GPU BIOS for GTX10x0 cards, it's encrypted and won't boot if you mess with it (which is assuming you are truly a crypto genius and can figure out the encryption, which nobody else has - so far, anyway), so you are stuck with mods using AfterBurner or nVidiaInspector, etc because Claymore doesn't do memory tweaks for nVidia (or fans, temps or power limits) like it does for AMD cards.

Great!  Like I said, I have asked here and in the 1060 thread if that works because I don't have a 3GB card to try, but already suggested that was the fix.  As long as it's not pci(1:0:0) then it should be fine, which is what you're saying, right?  My 3GB 1060 is off for repairs or I would try it myself.  If you have imbedded graphics in your mobo, it shouldn't be a problem, either.

Just to show what I was talking about the other day WRT how Windows 10 will allocate and use portions of you VRAM memory on your primary GPU other than that reported which causes GTX1060's with 3GB to crap out with the latest slightly enlarged DAG, here's the graphic showing the nVidia control applet in the system tray:



Here you can see that Windows is using video memory to host "Outlook", "Windows Store", (windows) "Photo", etc - and it never asks, you can't enable/disable it (as far as I know) and there's nothing really telling you that it's happening.  This doesn't include the 666MB (again, so I am told) that the latest Windows 10 version sucks up on your primary video card (pci 1:0:0 address).

I have asked if moving a 3GB GTX1060 anywhere other than the primary GPU works - which it should - but my card is off for repair, so I can't test that myself.

It can be set per GPU, so I would try
but this is just a sample, replace "20,10,20" with what you want for GPU0, GPU1 & GPU2. Do the same thing for - fanmax and if you want all of them to be the same use "80,80,80" for example.

It is in there. It takes some searching to find, but it is 16, and if you try a higher number the error message is not that obvious - and it is ignored.

You can't. It would be so inefficient nobody would ever make a bitpenny.

The whole point is to be efficient, and if the DAG isn't completely stored in memory the program would run so slow it would be useless.

Here goes nothing: my batch file, FWIW: (named "GetIt.BAT")
This is identical to my other rigs, but it's for a solo GPU GTX1060 6GB card.  The "NVI.exe" is nVidiaInspector renamed for ease of use.  (Claymore can tweak clock, voltage and fan settings for AMD cards, but not for nVidia GPUs)

Basically, it just sets the voltage and clocks then echos the command-line and runs Claymore, afterwards that "Echo ^G" sounds a bell on the console so I realize then the logfile archiver is running, and the program is getting ready to restart.  "-r 359" is six hours, at which point I want to insure everything gets reset.

You asked for "keccak", and I thought I had kept my example for that, but this is for Verge / XVG dual mining with ETH.  Everything is pretty much the same except the port and subsite you point to as well as the coin name and wallet.  I run directly from the nVidia 9.1 Cuda directory, saves a split second loading because it is going there anyway.  I also archive / compress the 15*log.txt files using WinZip command-line with redirection to NUL so it doesn't show on the display.  About once a day I rename ETHER_TXT.ZIP using the day/month digits and move it to my NAS storage in case I want to go back and take a look, but honestly I might as well turn logging off at this point, I regularly run to that 5 hours 59 minutes limit and the logfile is about 2MB in size.

If your rig is running well, all you see are shares, fan temp/speed and new jobs from the server.  Simple enough, nothing special.  You don't see the "SETX" commands because I put those environent settings into Windows permanently to save a little time.

First of all, SETX is a Windows registry variable setting program, not part of Claymore. I set those environment variables permanently on my systems, so it doesn't need to be done at runtime. Use Control Panel and look for Environment Variables. You DON'T want to put those commands in the CONFIG.TXT file.

I am out eating dinner with the wife, but when I get home I will post my batch file. It's nothing special, but I do have a recursive call (to itself) so if Claymore stops for any reason (including timeout after 240 minutes using "-r 239" parm) it restarts. I am back to ETH single mining for now, but my batch file has the extra part of the command-line REM out.

My Nitro+ (8gb) prefers to be undervolted.  Each card is it's own microcosm, I have never found generic answers for RX 580's.  Even my Asus RX 580 is very different.

Depends on what cards you have, of course.  If nVidia, try power limit around 65-75%, and around that.  For me, 70% seems to be the sweet spot and keeps my temps down, also.

16 is the limit for ETH Intensity.