Bitcoin Forum
April 26, 2024, 12:56:47 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 [4] 5 6 »  All
  Print  
Author Topic: ASRock H81 Pro will not accept more than 2 GPU's (Code 12)  (Read 4123 times)
Sn1p3r
Newbie
*
Offline Offline

Activity: 48
Merit: 0


View Profile
December 22, 2017, 12:21:00 AM
 #61

hi, guys.

I have same trouble. but this method can remove it in my case.

make new key "HackFlags" as (DWORD 32) type value 0x600 600 as (Hex) in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PnP\Pci\

and reboot.

ty

update:
Sorry. That's right. I made a mistake in expression.
Since this is a "32bit value", the "numbers of zeros" after "0x" has significance.

See source information.
https://support.microsoft.com/en-us/help/942959/error-message-when-you-attach-a-pci-express-expansion-chassis-to-a-com

Correct screenshot is here.
https://bitcointalk.org/index.php?topic=2307023.msg24696485#msg24696485



You sir are my hero!

Well I did a little bit digging for this issue and I can confirm 100% that it's cause by Windows Update 1709, and this helped my issue.
I had 6x 1060 GB cards, and I had two not working.

After I applied that one started to work, and just went to Device Manager disabled HD Audio for the second graphic and it magically started to work! Smiley
1714093007
Hero Member
*
Offline Offline

Posts: 1714093007

View Profile Personal Message (Offline)

Ignore
1714093007
Reply with quote  #2

1714093007
Report to moderator
1714093007
Hero Member
*
Offline Offline

Posts: 1714093007

View Profile Personal Message (Offline)

Ignore
1714093007
Reply with quote  #2

1714093007
Report to moderator
1714093007
Hero Member
*
Offline Offline

Posts: 1714093007

View Profile Personal Message (Offline)

Ignore
1714093007
Reply with quote  #2

1714093007
Report to moderator
"Your bitcoin is secured in a way that is physically impossible for others to access, no matter for what reason, no matter how good the excuse, no matter a majority of miners, no matter what." -- Greg Maxwell
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714093007
Hero Member
*
Offline Offline

Posts: 1714093007

View Profile Personal Message (Offline)

Ignore
1714093007
Reply with quote  #2

1714093007
Report to moderator
1714093007
Hero Member
*
Offline Offline

Posts: 1714093007

View Profile Personal Message (Offline)

Ignore
1714093007
Reply with quote  #2

1714093007
Report to moderator
1714093007
Hero Member
*
Offline Offline

Posts: 1714093007

View Profile Personal Message (Offline)

Ignore
1714093007
Reply with quote  #2

1714093007
Report to moderator
jovanoty
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
December 23, 2017, 07:21:56 PM
 #62

I would like to share my experience with that problem! I had the same problem, the 3rd gpu was giving me the same error. I did pretty much everything i found online, increase the virtual memory, updated the bios, change the registry, updated the windows to 1079, switch all the hardware, and im not exactly sure what was the problem but the last thing i did is to disable the audio attached to each card and now everything is working properly. 3 more cards to go will see how will go. Thanks everybody
geck
Member
**
Offline Offline

Activity: 145
Merit: 10


View Profile
January 02, 2018, 03:58:44 PM
 #63

hi Guys,

Today,
I tried to clean installation again on this MOBO. (BIOS 1.20, Using default settings)
The successful procedure is below.

1. Using "Media Creation Tool", prepare the latest USB installation media. (Version 1709)

2. Install the OS without connecting to the network.

3. Please still be offline after installation. Make sure that all of your GPUs are visible in Device Manager. (The NVIDIA driver has not been installed yet.)

4. Disable all HD audio devices. (Optionally, set HackFlags and reboot.)

5. Connect to the network. Install the driver automatically in device manager, or install Nvidia genuine. (Keep all HD audio devices disabled even after driver installation.)

6. If HackFlags does not set and Code12 still indicated, try HackFlags and reboot.

But I do not know if this is effective with AMD's GPU.
Can anyone verify it.

ty

Followed your steps to the T with th exception of installing 1703 and all 4 gpus were detected.

I also did not install the intel graphics driver and have left the pci-e 16x slot vacant. I have a feeling i am going to have troubles when my fifth and sixth card arrives. Will probably need to disable the igpu but this would be troublesome as the cards are inside a server case. But we will cross that bridge when i get ther 😬

Thanks so much for taking the time to write it all down!
q43a0ef061ej
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
January 03, 2018, 11:36:31 AM
 #64

hi, geck.

Sadly, iGPU will be the obstacle.

If iGPU is enabled on my rig,
Code 12 will be indicated even if the registry is turned on and all audio devices are disabled.
q43a0ef061ej
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
January 04, 2018, 07:18:43 PM
 #65

hi, Guys!

It is Great News!
Windows Update on Jan/3/2018[KB4056892] might fix this probrem!

You no longer need HackFlags nor Disable Audio Devices! Grin
geck
Member
**
Offline Offline

Activity: 145
Merit: 10


View Profile
January 04, 2018, 08:06:16 PM
 #66

Bought another gpu, so rearranged the existing gpus to fit, and changed the slots. Now only 3 cards are detectable. 4th one if detected throws up a code 43 error  Angry

hackflags, uninstalling using ddu, swapping cards, resetting bios, adjust bios settings to no avail. Going to try reinstalling windows now

I hope the asus z270-a board for my 2nd rig isn't going to be such a pita
q43a0ef061ej
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
January 04, 2018, 08:33:47 PM
 #67

hi, geck.

The default BIOS setting will not cause problems.

After clean installation using Fall Creators Update media,
Please patch up to [KB4056892]. That is all you need today.
geck
Member
**
Offline Offline

Activity: 145
Merit: 10


View Profile
January 05, 2018, 01:58:37 AM
 #68

Finally got it working.

You are right, default bios is all that is needed.
I cleared the cmos, reinstalled windows and started plugging in my cards (without installing nvidia drivers yet) one at a time
Found one faulty riser card instantly (riser got too hot to touch, mosfet failure probably).
Replaced another riser that was causing a card to be working intermittently.

5 gpus working now; 2x1080ti, 2x1070ti and 1x1070. Going to call it a day with this rig until volta comes along
Sn1p3r
Newbie
*
Offline Offline

Activity: 48
Merit: 0


View Profile
January 05, 2018, 03:51:07 PM
 #69

hi, Guys!

It is Great News!
Windows Update on Jan/3/2018[KB4056892] might fix this probrem!

You no longer need HackFlags nor Disable Audio Devices! Grin

Can anyone confirm this aswel?
neemaj
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
January 05, 2018, 10:53:11 PM
 #70

hi, Guys!

It is Great News!
Windows Update on Jan/3/2018[KB4056892] might fix this probrem!

You no longer need HackFlags nor Disable Audio Devices! Grin

Can anyone confirm this aswel?

Hey guys, I can confirm it worked for me too. I actually used the above tips (including the registry edit) to run 5 GPU rig. Yesterday, after the update, my 5th GPU stopped working. After removing the edited registry, it works flawlessly, now even with 6 cards.
kuttysark420
Newbie
*
Offline Offline

Activity: 19
Merit: 0


View Profile
January 06, 2018, 12:59:44 AM
 #71

Thank you very much for the HACKFLAGS. got my rig up and running again and I fucking disabled windows update PERMANENTLY.

PIECE OF SHIT AUTO UPDATING WINDOWS 10
Sn1p3r
Newbie
*
Offline Offline

Activity: 48
Merit: 0


View Profile
January 06, 2018, 04:38:23 AM
 #72

Thank you very much for the HACKFLAGS. got my rig up and running again and I fucking disabled windows update PERMANENTLY.

PIECE OF SHIT AUTO UPDATING WINDOWS 10

Try Windows Update on Jan/3/2018[KB4056892], they have fixed it in newest update.
ncminer2018
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
January 07, 2018, 02:12:11 AM
Last edit: January 09, 2018, 02:09:16 PM by ncminer2018
 #73

Thanks to this thread I have successfully used 4 GPU (Gigabyte 1070) for mining on ASRock H81 Pro rev2. It took maybe 8h mostly installing OS and update (so slow). If you are crazy enough like me and want to try Linux and thinking it's going to be easier let me stop you right now. I failed miserably trying Linux but your mileage may vary.

code 12 is your best friend because it means your hardware is most likely installed correctly (all plugged correctly) and working. Code 43/45 are your enemies: double check cables and connections.

Summary solution:

1) Install Windows 10 1709. Install all latest windows update. Disable all audio device on the video card by sorting the view by connection in device manager. At this point you should already see all your video cards.
2) If you have any GPU that has error code 12 do HackFlags (400) fix. Reboot.
3) If GPU has error code 43 make sure all connectors are attached tightly. Ex: power issue (connector not properly inserted for example), I suspected heat but looking at afterburner app it's not the case.
4) If GPU has error code 45 make sure riser cable/adapter are working fine. Ex: riser issue, (code 43 or 35 are mostly hardware related)
5) If you still see error code 12 sort view by connection and disable some un-used device like a USB device (make sure it's not being used; I used a USB hub and disabled another un-used one).
5b) It doesn't hurt to run search "troubleshoot" and select "Hardware and Devices", I would not enable auto driver update feature when asked, and select device not in this list option and proceed, it might fix something. In my case it was able to find my last GPU when it was hidden (but second time this happened it didn't help).
6) Reboot and see if all GPU are detected correctly. If so start mining and see if you get VIDEO_TDR_FAILURE (BSOD).
6b) If TDR BSOD, try TdrDelay registry workaround first (reboot). MSDN: https://docs.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys. Reddit mentioned about this: https://www.reddit.com/r/nvidia/comments/79nncg/driver_38813_faqdiscussion_thread/. You may download a tool (in that link) to change the TDR registry. I would just skip to next step first.
6c) If #6b failed try mining with one algorithm only (forget dual mining). This is what made my rig stable. I was BSOD very quickly (few minutes into mining). This method worked for 4 GPU. When I added a 5th one TDR issue re-surfaced again. I am still debugging this issue. [update] I used that that tool (in previous link) to disable TDR. Let's hope it can last till tomorrow. Ideally it's better to increase delay because at least in worst case machine will reboot and you can auto start your miner [update, overnight no issue but this morning it froze without any crash; had to reset]. If you disable TDR and it fails it will freeze your machine (this is good for me right now).

If in doubt use Display Driver Uninstaller (DDU, http://www.guru3d.com/files-details/display-driver-uninstaller-download.html) in safe mode (run msconfig and select safe mode, it will ask to reboot, once in safe mode run DDU). You only need to do this if you have already installed latest driver. I had everything detected by OS and working with driver provided by Windows 10 (so until step #6 I didn't install any driver). It's possible that you don't even need to install latest display driver depending on the situation. Once I got BSOD I ran DDU and installed latest driver but the problem was elsewhere for me.

Next rig I will use better riser: https://www.amazon.com/Ubit-Express-Graphics-Extension-Ethereum/dp/B076KLJR2Y/ref=sr_1_1?s=home-garden&ie=UTF8&qid=1515290286&sr=8-1&keywords=pcie+riser+ubit with LED hint to help identify hardware issue.

[Update]
KERNEL_SECURITY_CHECK_FAILURE - FAIL_FAST_LIST_ENTRY_CORRUPT BSOD (nvlddmkm involved) after being stable for less than 3h.
I set up a batch script that launches the miner and put it in the startup folder and disabled password login. So after startup it will start miner automatically. Hopefully it can survive the night (update: crashed once in 12h).

[Update2]
Added a 5th GPU and TDR issue came in full force. See #6 for info. Essentially I disabled TDR with a tool (mentioned in link reddit link above), but you may try TdrDelay and other settings and have auto start on reboot to avoid down time. Only down side to this approach is that if you BSOD very often it's best to fix the issue in a more permanent way to avoid hardware damage. I am in the process of trying out different drivers (390 is out) to find the most stable one.

[update3: trying drivers]
Device Installation Settings: disable auto device update before doing DDU and installing older driver. Disable device driver update (somehow windows still updated nvidia driver with this setting disabled only) and disable windows update in group policy.
Completely disable windows update - https://www.windowscentral.com/how-stop-updates-installing-automatically-windows-10
Disable device update itself - https://www.itechtics.com/disable-automatic-driver-updates-windows/
Disable device update search - https://technet.microsoft.com/en-us/library/cc730606%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

I am using nvidia driver 385.69 now no BSOD (it's possible other version can also work). Make sure to disable update or it will get auto updated to newer driver (it will eventually happen if you don't disable it).

Another issue I got which is puzzling is my 5th GPU stopped working (afterburner shows 0 for all sensors) after sometime even when not mining. What I ended up doing is set power limit to 80%(my other settings are temp limit 80%, core 100, memory 350). All temperatures were below 70c (67-68c). If it can run for 1 month without issues I can call it stable but for now I am happy.

Don't give up!
theDistrict11
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
January 17, 2018, 04:02:17 AM
 #74

Confirmed - the HackFlags [600] worked for me. I initially tried HackFlags [400] but that didn't work.

Rig Specs:
  • OS: Win 10 1709 with the latest update (update alone didn't work)
  • Mobo: Gigabyte Z270p-D3
  • GPU: 6x 1080 ti

Thanks all for the hours of troubleshooting and sharing your findings.
Mineability
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
January 17, 2018, 06:54:05 PM
 #75

I contacted Asrock support.

They say for some HackFlags solution works on Windows Installations (1709).
But it didnt work for me.

The solution for me was windows 10 (1703), the version before creators update.
My 4 cards (Gtx 1070s) are working with this Windows version, when i update to 1709 only 3 cards are working. So i dont update for now.

The support said its a problem which occur on Windows 10 (1709) versions. So microsoft needs to fix this in a coming update.

Hope it helps, cioa.


I did find the old version over here:  http://windowsiso.net/windows-10-iso/windows-10-creators-update-1703-download-build-15063/windows-10-creators-update-1703-iso-download-standard/  So if you needed, i did not tested them yet. So i dont know if those files are clean use at your own risk, just did find this source ..
Mineability
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
January 17, 2018, 09:02:32 PM
 #76



After lots of troubleshoot now all is also working good.  Microsoft Windows 10 1703  did resolve all problems !!!  Kiss

Only message this board give at start:     please install the psu's 4-pin power cables to the 4-pin power connector on your motherboard

While all cables are connected, and the rise cards and GPU has power directely from my 1200 watts unit. Is this something to worry about ?
Are is the board only telling you , that you have 3 cards or more  Huh
q43a0ef061ej
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
January 18, 2018, 04:02:17 PM
Last edit: January 25, 2018, 08:32:16 AM by q43a0ef061ej
 #77

hi, guys.

If you try install 1709 and patched up to [KB 4056892] and the rig successfully recognized the GPUs well without HackFlags,

I no longer recommend you to use 1703.
giveen1
Newbie
*
Offline Offline

Activity: 70
Merit: 0


View Profile
January 24, 2018, 02:39:11 AM
 #78

Hackflag didnt work for me originally with default bios. Had to set to Gen2, install latest CU for Windows, remove hackflags, and then reinstall drivers.
Swiss_Danny
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
January 24, 2018, 01:34:11 PM
 #79

Just registered to come and say thanks for this thread.  It helped me get 3x1080ti (1x16channel, 2xRisers) going on my H81 Pro, even though it was not plug and play.

As I was just happy to get them going, this is not a full "debug", but some things that seemed to help, or didnt at least harm the process

  • AS Rock H81 Rev2.0 with 1.20 BIOS.  I turned off everything I didnt need to be using, and maximised the compatibility/stability settings
  • 4gb DDR3 RAM, Pentium G3260. Increased the pagefile to 16gb, as NiceHash was getting out of memory errors even after first two card up and running.
  • Window 10 Pro. Build 1609.  I did the hackflag registry fix "just in case" but actually the second card was found when I removed the hackflag key again.
  • NVIDIA drivers 388.43.  I just kept doing a clean install of just the drivers once another card on another PCie channel was found.
  • Getting a single card going in any of the channels was not a problem. I used this process to make sure I had two working risers to eliminate the "bad riser" risk, and then left the first card in the mobo slot.
  • I finally got a second card working on one of the risers.  Not really sure how I managed that, but lots of rebooting, bios flashing etc.
  • But the the third card would not work and a third slot, until I took out the second card, got the third card working, then added the second card back in.

So in summary, if I had to start from zero I would try this to make it work with less trial and error, basically adding cards one at a time, but only adding card N to a slot that was already working with N-1 cards:

  • Get one card/riser going in one slot.  Install the drivers.
  • Use the same working card/riser combo in a second slot to "activate" that slot. Install the drivers
  • Hopefully get two cards running on the two "active" slots.
  • Move one of the cards to a third slot to "activate" it. Install the drivers
  • Add the third card, using all three "active" slots. Etc...

Hope this helps someone else, and for my 4th card once the damned riser arrives...

Danny
simpie10
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
January 27, 2018, 12:36:31 PM
 #80

hi, guys.

If you try install 1709 and patched up to [KB 4056892] and the rig successfully recognized the GPUs well without HackFlags,

I no longer recommend you to use 1703.

This is true! I installed a fresh w10 1709. 1 Card had code 12. Then i update, en finally get the [KB 4056892] patch. After reboot my 4 cards are working fine! No tweaks in registry or else. Seems Microsoft patched it for us Smiley
Pages: « 1 2 3 [4] 5 6 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!