Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v10.1 (Windows/Linux)

EthDcrMiner64.exe -epool stratum+tcp://us.ubiqpool.io:8008 -ewal 0xc86bb711033e00abd01b197a57be42421678a987 -epsw x -eworker rig1 -allcoins 1 -dpool stratum+tcp://dcr.suprnova.cc:3252 -dwal neverrazor.1 -dpsw x

Your hashrate is at ~50% of your's equipment normal performance. I thought that mining intensity was set wrong (ethi and dcri). After runing a short test, I found that GTX1060 are not very sensible to dcri level (at least DCR). Cranking DCR intensity from 40 to 130, the DCR hashrate increased 190% and ETH hashrate decreased 10%. Such dcri level, to halven the ETH hashrate, should be within 200-300 range, that is either stupid or unsupported by Claymore miner.
Better define explicitly your ethi and dcri, say 16/40, 16/50.
Check your BIOS settings - enable Above 4G decoding/TOLUD (works only in UEFI-enabled systems) and PCI-E speed - switch it to Gen1 or Gen2.

i enabled 4g ... and tried different pci-e gen speed all same results ... the problem is ONLY in the hashrate of eth ... .. i tried another eth miner ... same problem

I seem to be having the same issue on my Asus Z270 board with 5 Rx 580's hashing all at around 23mg/h each, another one of my rigs with same config but older asrock H81 board and 6 rx 480 is 31mg/h each.

What version of Claymore do you use?
What AMD driver do you use?

Claymore Ver 10, Win 10 pro with latest Blockchain drivers. In fact prior to blockchain drivers I was only getting 21mg/h per card. I wonder if I'm only running 5 cards on a asus z270 if its still necessary to change bios settings on the motherboard? I'm thinking probably yes, which I did anyways. Also if I turn up settings in AB the cards go down to 18-19mg/h each

Assuming all mobo settings are correct, no issue with hardware and you have properly done bios mods, I think the only missing in the equation is AMD's latest 17.10.3.

I can personally vouch for this driver as this fixed my OpenCL issues (totally different topic). It's worth a try considering you probably have done lots of troubleshooting already.

Also, consider updating to Win10 Fall Creator's Update if you're already in the brink of reinstalling your Windows just like me. Who knows if that would magically fix your issues like what happened to me.