Quote from: phase2 on October 30, 2017, 03:30:58 PM

Quote from: greatauror28 on October 30, 2017, 01:16:26 PM

Quote from: leonix007 on October 30, 2017, 08:49:57 AM

Quote from: greatauror28 on October 27, 2017, 07:45:44 PM

I have the same problem but my rig consists of 8x 580 Nitro+.

I have a constant core clock on all of them (1200), set in Claymore config.txt as well as cvddc and mvddc of 857mV. But I have varied memory clocks starting at 2025 and goes up to 2100.

The main problem is that only one card crashes. Good thing the -minspeed argument is working and it restarts my miner should one card crash (together with -wd 0) and everything goes back to hashing a total of 244 Mh/s again. This is dual-mining by the way.

I wanted this issue to be resolved although judging by other's experiences, I'm on the lucky side as my rig still mines and restarts on it's own.

P.S. I used to have an 8x Gaming X 580 rig and it doesn't have this issue. Same board and components.

P.P.S It is not a specific card that is crashing. 4 out of 8 cards takes their turn crashing, one at a time.

Thoughts?

What is powersupply rating? Dual mining is power hungry, ensure that your psu can handle and supply power for all gpus, would suggest psu to have at least 10-15% allotted extra power from the wall.

I'm running twin EVGA G3 850w gold so i'm pretty sure power isn't the problem

And i've fixed the issue yesterday by updating to win10 fcu and 17.10.3 driver.

How long your rig runs with 1200 cclock and 857 cvddc?

It's still running now approaching 22 hours. It could've been longer if not for my son who accidentally tripped over the network cable and disconnected my router.

EDIT: I failed to mentioned I toned the core clock down to 1150 for more power savings and it didn't even affected the hash rate.