Code 12 every time :(

[FredDeb]

I have a ASrock H81 Pro BTC R2.0 mobo with 4gb ram and a Intel Pentium G3258.
I am trying to connect 3 GPU's to the motherboard but i always get a code 12 on one of the cards. If i connect 2 cards, one of them has a code 12. If i connect 3 cards, 2 are working and one of them has a code 12. Mobo bios is up to date. Drivers are up to date... I am using windows 10 and the cards are gtx 1060 6 gb's. I dunno what else i could try, please help, this is driving me nuts 🙁

 

[Gacibula]

Will purchasing a different mobo can potentially fix this problem? Thinking about a biostar mobo with another CPU chipset... at this rate $150 is worth the mental frustration from this code 12. 🙁

 

[w.gr.knight]

did anyone solve it yet? Having same problems, tried everything including clearing cmos, updating bios, changing registery, clean installing windows, etc....nothing works - i have code 12 on the second card and adding 3rd one makes the system frozen during boot up...

 

[Mark RM]

When you say drivers are up to date, do you mean you installed the actual Intel version of the chipset driver or just the inf from Asrock, or just let the Windows driver install?

Did you disable EVERYTHING on the motherboard (sound, network etc), even USB if you have a pc keyboard/mouse.?

 

[w.gr.knight]

I tried to install drivers only for Asrock & my nvidia cards. Many time from different places. Have not tried Intel drivers for the chipset. I have little faith right now it will help, but i will give it a go... And yes, i have tried to disable everything on the motherboard to a point where i could not enter the bios anymore as my keyboard would not boot until windows is running...

 

[EternalWinter]

I’m having the same issue, 4/6 working with error 12 in device manager. I’ve tried everything with no luck. I got Linux going and it sees all 6 cards but my hash rate is a 1/3 what it was in windows. So still frustrated. I’m better off with 4 working cards in windows at 30mhs each than 6 working in Linux at 10mhs each

 

[tinymanversion6]

Windows version 1709 (latest update) seems to be the issue, seen this a few times now, especially with people with Nvidia cards. Windows version 1703 is one way to fix it, and turn off updates (until Microsoft sorts it out.) I'll point people to this forum for another way to fix using a windows key with the hex editor https://bitcointalk.org/index.php?topic=2401059.0;all