I'm also having this very same issue with multiple mining rigs



Nothing is helping so far. I do suspect it's a HW problem with a single card/riser/MB slot

I'm having 8 card rigs (mostly)
Win10 1709 EN Pro heavily modified for mining (working like a charm on tons of rigs)
18.1.1 drivers with compute mode enabled
PageFile set to 64+GB size (8 cards per 8GB)
OC & UV is being done with Overdriven batch file, also tried stock clocks
Claymore's miner from 9.8 to 11.4

I've tried everything .. hardly to get rid of this error
(cloning the SSD, DDU, reinstalling the drivers, changing all posible values)

I think Claymore itself should bring some light into this problem

By example:

12:21:03:200   17cc   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
12:21:03:200   17cc   
12:21:03:200   17cc   b501
12:21:03:419   17cc   ETH: 1 pool is specified
12:21:03:419   17cc   Main Ethereum pool is eth-eu1.nanopool.org:9999
12:21:03:419   17cc   DCR: 0 pool is specified
12:21:08:326   17cc   OpenCL platform: Intel(R) OpenCL
12:21:08:326   17cc   OpenCL platform: AMD Accelerated Parallel Processing
12:21:08:326   17cc   OpenCL initializing...

12:21:08:326   17cc   AMD Cards available: 10
12:21:08:326   17cc   GPU #0: Ellesmere (Radeon RX 580 Series), 8192 MB available, 36 compute units (pci bus 1:0:0)
12:21:08:341   17cc   GPU #0 recognized as Radeon RX 480/580
12:21:08:341   17cc   GPU #1: Ellesmere (Radeon RX 580 Series), 8192 MB available, 36 compute units (pci bus 2:0:0)
12:21:08:341   17cc   GPU #1 recognized as Radeon RX 480/580
12:21:08:341   17cc   GPU #2: Ellesmere (Radeon RX 580 Series), 8192 MB available, 36 compute units (pci bus 3:0:0)
12:21:08:341   17cc   GPU #2 recognized as Radeon RX 480/580
12:21:08:341   17cc   GPU #3: Ellesmere (Radeon RX 580 Series), 8192 MB available, 36 compute units (pci bus 4:0:0)
12:21:08:341   17cc   GPU #3 recognized as Radeon RX 480/580
12:21:08:341   17cc   GPU #4: Ellesmere (Radeon RX 580 Series), 8192 MB available, 36 compute units (pci bus 8:0:0)
12:21:08:341   17cc   GPU #4 recognized as Radeon RX 480/580
12:21:08:341   17cc   GPU #5: Ellesmere (Radeon RX 580 Series), 8192 MB available, 36 compute units (pci bus 9:0:0)
12:21:08:341   17cc   GPU #5 recognized as Radeon RX 480/580
12:21:08:341   17cc   GPU #6: Ellesmere (Radeon RX 580 Series), 8192 MB available, 36 compute units (pci bus 11:0:0)
12:21:08:341   17cc   GPU #6 recognized as Radeon RX 480/580
12:21:08:341   17cc   GPU #7: Ellesmere (Radeon RX 580 Series), 8192 MB available, 36 compute units (pci bus 12:0:0)
12:21:08:341   17cc   GPU #7 recognized as Radeon RX 480/580
12:21:08:341   17cc   GPU #8: Ellesmere (Radeon RX 580 Series), 8192 MB available, 36 compute units (pci bus 13:0:0)
12:21:08:341   17cc   GPU #8 recognized as Radeon RX 480/580
12:21:08:341   17cc   GPU #9: Ellesmere (Radeon RX 580 Series), 8192 MB available, 36 compute units (pci bus 14:0:0)
12:21:08:341   17cc   GPU #9 recognized as Radeon RX 480/580
12:21:08:341   17cc   POOL/SOLO version
12:21:08:341   17cc   Platform: Windows
12:21:08:404   17cc   start building OpenCL program for GPU 0...
12:21:09:154   17cc   done
12:21:09:373   17cc   start building OpenCL program for GPU 1...
12:21:09:607   17cc   done
12:21:09:842   17cc   start building OpenCL program for GPU 2...
12:21:10:076   17cc   done
12:21:10:311   17cc   start building OpenCL program for GPU 3...
12:21:10:545   17cc   done
12:21:10:780   17cc   start building OpenCL program for GPU 4...
12:21:11:014   17cc   done
12:21:11:249   17cc   start building OpenCL program for GPU 5...
12:21:11:483   17cc   done
12:21:11:717   17cc   start building OpenCL program for GPU 6...
12:21:11:952   17cc   done
12:21:12:186   17cc   start building OpenCL program for GPU 7...

This is the output of the log file
I'm sure there is a problem with GPU7.. changing the riser, reinstalling the drivers with DDU .. no go
If I try -di 0123456 than it will run without a problem.. card7 itself is working just perfect

There is NO solution for this error nowhere on the Internet!

Watch you language here dude!

1) Awesome.. congratulation! 13 and 25hours considered as stable?
2) what is your point here? look at my post from Saturday morning.. have you invented something in here?
3) WHERE IS YOUR ANSWER ON THIS ONE? Most important part?

Congratulation.. you are running 12 cards, 8 from it with Compute workload enabled, 4 without
It's the best you can get atm from 17.10.2 with Win10-1709, agreed on that one!

Your initial post wasn't showing anything and you shared this prntscr after.
peace!

Well, i strongly disagree. My personal experience (and plenty of others) is completely opposite to yours

1) how can you even say that out loud? that driver is not even 7 days old
2) OverdriveNTool has been working just fine with blockchain drv (23aug)
3) yes, it let you post it in device manager and yes, it let you mine with it.. but do try enable compute workload and see that mess if you are running 12 cards! And loosing 4mh's per card with NO-dag-driver * 12 cards.. hell no !

Please stay away from such a comments, you are fooling others!

Hudge 17.10.2 review from multiple users

https://bitcointalk.org/index.php?topic=2312585.msg23660670#msg23660670

Allright.. these are my results from yesterdays extensive testing

First of all:
AsRock H110, 8x PowerColor RX470 4GB (samsung), Claymore 10

Windows 10 Pro 1703, AMD 17.10.2 with Workload = compute

We had the rig running stable for weeks/month with BlockchainDriver(23aug).. 228MH's on ETH with this crappy cards
We did DDU, installed new driver 17.10.2(oct23) (full installation with GUI) / took like 15 minutes ! restart + PixelPatched + restart
Manually setting Workload = Compute for all the cards .. grrrr!!! after setting all 8, you have to restart the computer !
After start: OverdriveNTool 0.2.0 for aplying OC/UV profiles to the cards..
result is very same like the BlockchainDriver(23aug) .. 228MH's .. stable for 24hours

So my insight on this.. for those running 8 card rig with BlockchainDriver(23aug) there is no point of switching to the 17.10.2 .. there is no improvement, just the pain (aplying Compute ON) to even get the same result

-----
COMPLETE DDU 17.0.7.7

Adding 4 more PowerColor RX470 .. sooo .. 12 Cards in total ()
Windows booted up quickly
Installed full version of 17.10.2 took like 40 minutes !!! Insanly long! restart + patch
All cards has been detected, I saw 12 in Device Manager ()
manualy turned on compute workload (took another 10minutes) + restart
Computer freezes.. restart, freezes, freezes..
After a long while it booted without any changes at all
Saw all 12 cards, modifified Overdrive batch file to OC/UV all my 12 cards + applied this profile
Ran Claymore 10.1 with -gser 2 option
All 12 cards has been recognized by claymore ()
It started mining while still creating DAG for another cards.
I saw that some of the card started mining 28.5 Mh's (that is normal value for my cards)
Than.. Cannot create a DAG file for GPU9 and GPU3.. Claymore restarted.. since than, I was not able to start it over again
After another computer restart I was not able to boot into Windows anymore!!! Windows died!
Disconnected those 4 additional cards and here we go.. windows booted up again..
Ran DDU + restart + back to the BlockchainDriver(23aug) + patch + restart
Cards started to mine ony 14MH's no matter what.. spend like an hour playing with it.. there is some problem with applying cvddc/mclock after DDU uninstalling 17.10.2 and reverting back to Aug23 drivers
Windows installation is obviously corrupted (or the new DDU 17.0.7.7 is leaving some traces behind after uninstalling the 17.10.2(oct23) driver

Had to restore Windows installation image from backup!

So, anyone that don't want to waste the time, stay away from 17.10.2 while running 8+ cards (especially 12!)

To that reg fix..
IojkinKot has been faster, I do agree with his findings.. there are more changes but only that one seems to be relevant to me
If anyone can tripplecheck, here is exported regedit key before/after applying COMPUTE mode. Do the file comparison and please let us know the result
Applying this regedit can save 40min of installation time + another 10 minutes of manually applying compute mode for each GPU
This might actually get very important.. if AMD will stay with such a option of turning Compute mode ON in the future!!!

https://drive.google.com/open?id=0B5E2YhEbdRIxUXZpejNaajNnc2s

And such a nice Friday it was   (6 hours wasted!)

PS: I'm NOT doing this test over again with 1709 Fall creators update !!
PS2: For those who want to say thank you, you've saved my a lot of time and pain, look down bellow the line

Yes, I had version 0.2.0 installed and running with blockchain drivers (23aug).
Just did the DDU, installed new driver (complete suite due to needed workload (compute) change using GUI) .. patched, restarted, changed Workload to compute for all GPU, retarted again ..
OC/UV profile from OverdriveNTool are started automatically (via batch file) when the Windows starts

As I said previously, no performance drop, all working just fine with 8 cards..
Going to play with it tonigh and will try to make 12 or 13 cards works on AsRock H110

PS: Also, will try to setup compute workload using regedit.. I've been suggested a solution so no AMD GUI will be needed if that works

I'm testing these new drivers..

So far no problems at all with 8x RX470 4GB .. rig has been runing 228MH's on ETH on blockchain drivers(23aug), it's running the very same hashrate on 17.10.2(23oct)

All you need to do is change workload type to compute for all GPU (individually, I know, it's pin in the a$$).. restart your rig afterwards and .. you're ready to go
For Overlocking use latest OverdriveNTool 0.2.0 .. everything works like a charm.. Rig is running 30+ hours now

In the evening I'm about to add 4 more cards to achieve 12 (also planing to test 13) and do the testing.. Just wanted to have confirmed that it's runing just fine with the same hashrate on 8 cards.. CONFIRMED !

AsRock H110 BTC Pro+, Windows 10 x64 1703 (no need to update to 1709!), 17.10.2 drivers, OverdriveNTool 0.2.0 with scripts..

Is there a way how to setup Compute type of workload for all GPU? it's lots of clicking and noticed that the value is not saved for the first time
(Win10 + 17.10.2)

Well, I'm not using AB for OC/UV my cards (i'm using OverDriveTool). When I switched off the card in Claymore the OC/UV profile still stays active so I still couldn't identify the card.
(But when I did the profile reset it shows it was the card I tought it will be)
The mechanism I posted above is valid 

Not sure about card ID's while mining Monero

OK community  

Claymore GPU0 = MSI AfterBurn 1:CardXXX
(that means GPU3 in Claymore is MSI AB 4:Cardxxx)

So if you're having problem with let say GPU6 in Claymore, in the MSI AB select the card 7:Cardxxx and SPIN THE FAN to 100%
you will know physically what card it is!

Special thanks to Xeridea and Call_Me_Bambi

I can confirm that this solution DOESN'T work. I had tried this out days ago on 3 rigs, none of disabled GPU fan stop to work.. they still spinning even when disabled and not mining. Waited for 30+ minutes.. not effective way to identify the GPU



This actually might work..
Can anyone test it out? I have no MSI AB installed on my rig..

EDIT: Not working either. Just tried that out on friend's rig! AB still showing the OC/UV values.. not returning back to default when GPUx is disabled in Claymore

PS: I think all of us here could agreed on that solution like "Identify the problematic GPU" should be already implemented in Claymore. (long time ago)

Xeridea, thank you very much for the confirmation!
Claymore> Why not implement a mechanism to identify problematic GPU!? This should be already available! Stop the fan for 3 seconds on problematic GPU by pressing some key, or the other way.. spin it to 100%

Guys, is there a easy way how to identify which GPU is which?
(like having and GPU3 hang-out but have no clue what card is it out of 8 cards!)

Is MSI AB numbering 1-8 equal to Claymore's 0-7 ?
AB1 = gpu0? , ab2= gpu1

I'm using simple method of increasing fan speed to 100% in AB to identify the cards but still not sure if this is the right way
thank you