Pages:
Author

Topic: Issues with my new mining setup! Seeking advice (Read 2410 times)

newbie
Activity: 42
Merit: 0
It works perfectly with this KB.
Thank you.
Will post the info on telegram group for my mining pool.
Happy mining
newbie
Activity: 42
Merit: 0
Hi,
All my rigs with asrock H81 pro BTC R2 have the same issues with differents GPU since automatic fucking windows upgrade lol...
So will try this KB and let all of you know if it works well.
Thanks to all for the post. I hope it wall work Smiley
newbie
Activity: 21
Merit: 0
hi, russellvb.

please refer this thread.
https://bitcointalk.org/index.php?topic=2401059.0;all

Windows Update on Jan/3/2018[KB4056892] might fix this problem!
You no longer need HackFlags nor Disable Audio Devices!

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.

ty
newbie
Activity: 19
Merit: 0
Hi p1r473,

Your error could likely be due to a recent Windows update.  After windows rolled out the CPU bugfix a couple weeks ago, one of my GPUs stopped working again.  If you roll back this windows update, it may work.  (Uninstalling the windows update got me all 6 GPUs again).  Note you should be careful what you use the machine for if you remove the windows update patch.

Good luck,
Russell
copper member
Activity: 10
Merit: 0
I have the same board and am having the same issues. I've tried everything
Enable /disable igpu in bios and device manager
Disable audio HD in device manager
HackFlags 600
The knowledge base article
Enabled/disabling rendering in bios

Why wont anything work....
newbie
Activity: 9
Merit: 0
Hey guys, I figured mine out.  In Device Manager, I selected "View" > "Devices by connection".  The 1 card with a yellow bang was then listed next to an audio device.  I disabled the audio device and IMMEDIATELY the 6th card started working.  Ahhhh thanks everyone for the help.

haggyy, try the registry patch above, then try viewing in Device Manager and disabling any devices in the same connection/folder, I'd like to hear that yours is working...

This worked for my Asrock H81 PRO BTC R2.0 with 2x1060 and 1x1080ti cards! Thanks a lot!!
newbie
Activity: 19
Merit: 0
Yoledo,

It may not make a difference, but have you tried disabling "NVIDIA High Definition Audio" instead of disabling the controller?  (or maybe try to disable both, starting with the child device.

Other than that, you could try the other suggestions further up the thread and see if that helps..

Russell
newbie
Activity: 23
Merit: 0
GREAT NEWS! I've got it working!! 3 GPU's running successfully, wow cant thank you all enough for the help.

Russel I literally done what you said, went onto device manager and sorted by connection and disabled the audio adaptor to the GPU that was flagged with the yellow exclamation mark and then BOOM it worked. I can finally relax... And now look to get 3 more GPU's added to the works.. Thanks again to everyone to helped  Grin Grin

I'm getting the same problem with one of my 3 cards showing up under an audio controller, but even if I disable the audio controller, it still shows code 12
https://imgur.com/a/xKXcL
newbie
Activity: 19
Merit: 0
Woo hoo! Great news haggyy! Glad it worked.
full member
Activity: 602
Merit: 106
GREAT NEWS! I've got it working!! 3 GPU's running successfully, wow cant thank you all enough for the help.

Russel I literally done what you said, went onto device manager and sorted by connection and disabled the audio adaptor to the GPU that was flagged with the yellow exclamation mark and then BOOM it worked. I can finally relax... And now look to get 3 more GPU's added to the works.. Thanks again to everyone to helped  Grin Grin

Great to hear that! Smiley
newbie
Activity: 29
Merit: 0
GREAT NEWS! I've got it working!! 3 GPU's running successfully, wow cant thank you all enough for the help.

Russel I literally done what you said, went onto device manager and sorted by connection and disabled the audio adaptor to the GPU that was flagged with the yellow exclamation mark and then BOOM it worked. I can finally relax... And now look to get 3 more GPU's added to the works.. Thanks again to everyone to helped  Grin Grin
newbie
Activity: 21
Merit: 0
haggyy,

Unfortunately, we had a tomboy ..
Just now, I hope you will solve it well.

good luck.

update:

If disabling "some unnecessary PCIE device" does not solve the problem,
"PCIE device enumeration buffer" may not be the only problem.
and It may also be a problem of TOLUD.

Just had a reply from ASRock Support:

Hello,
 
1. Please try to borrow more RAM to test with.
 
2. Try increasing virtual memory in Windows to at least 16GB.
 
3. The Molex power connectors on the motherboard must be used, even with powered risers. I know you tried this already.
 
4. Please try to test with Windows 10 version 1703.
 
Any change?
 
Kind regards,
ASRock Support


Trying this now

1 or 2 is suspicious.

Even if you disable "some unnecessary PCIE devices",
It may not be enough with only 4GB RAM to drive several GPUs.
newbie
Activity: 29
Merit: 0
Thanks so much for all the useful information guys, I am going to attempt to work on the rig sometime this evening or tomorrow and I will report back asap!
newbie
Activity: 21
Merit: 0
hi, guys.

Both G1840 and G3260 belong to Haswell.

Also,
I looked into the details of HackFlags.

Unlike my expectation,
This option works to increase the limit register of "buffer size of enumerating PCI Express bridge devices"  from the initial value.

For example,
If you install an unusual number of video cards (like mining rig) with the default limit register value,
"PCIE device enumeration buffer" overflows due to too many PCIE devices,
Code12 exception seems to occur.

In addition to setting HackFlags,
disabling "some unnecessary PCIE devices" will reduce the occurrence of overflow.

Perhaps, Updating the "PCI Express root port" driver may also help you.
(ASRock H81 Pro BTC R2.0's "PCI Express root port" have more fit driver at WindowsUpdate named "intel(r) 8 series/c220 series pci express root port".)

Update: Sorry. Maybe this does not matter.

ty
sr. member
Activity: 462
Merit: 258
Small Time Miner, Rig Builder, Crypto Trader
My CPU is a Intel Celeron G1840 Processor.  It was recommended on a mining forum.  I don't have a different one to swap with, but I could buy a better one.  Would you suggest an i3?

no i3 is just waste of money, get yourself a intel Pentium cpu dual core one, and make sure its the skylake and not the kabylake cpu
sr. member
Activity: 462
Merit: 258
Small Time Miner, Rig Builder, Crypto Trader
hi, guys.

By the way,

I examined the difference between G1840 and G3260.
They had the same number of PCIE lanes.

So, I guess that the problem of PCIE coming from the difference between these two CPUs can be ignored.

they both kabylake or skylake? it does make a difference, if it did not there wouldn't have been numerous people reporting problems with the kabylake cpus
sr. member
Activity: 462
Merit: 258
Small Time Miner, Rig Builder, Crypto Trader
The processor here there is nothing. I am sure that if you replace it then you have the problem not solved. Error code 12 is a problem with the driver. You need to pay attention to software. If you modified the BIOS of your GPU then you will not fit a standard driver. At me such problem was with one card but after updating the driver everything works fine.

actually that's not true, and if you read he hasn't even had a chance to mod the bios, code 12 can relate to a few things, ram being one of them, the cpu being another I use a skylake intel Pentium dual 3ghz cpu, the kabylake cpus are crap if you browsed the forum youd find lots of posts of people having issues with the kabbylake cpus only handling 4 gpus while the skylake ones can handle the full 6+. the problem is people like you giving people like him shitty ass information
newbie
Activity: 21
Merit: 0
hi, guys.

By the way,

I examined the difference between G1840 and G3260.
They had the same number of PCIE lanes.

So, I guess that the problem of PCIE coming from the difference between these two CPUs can be ignored.
newbie
Activity: 19
Merit: 0
haggy, your registry setting looks good.

Your screenshot shows an Intel Display Driver.  Go ahead and uninstall that driver and remove the driver files, it isn't helping anything (onboard graphics should be disabled in bios anyhow).

In device manager, did you try sorting "by connection"?  That will hopefully show you the conflicting device using the same IRQ or port/memory address.

I'm cheering for you to get up and running...
newbie
Activity: 21
Merit: 0
hi, haggyy.

Hey guys, I figured mine out.  In Device Manager, I selected "View" > "Devices by connection".  The 1 card with a yellow bang was then listed next to an audio device.  I disabled the audio device and IMMEDIATELY the 6th card started working.  Ahhhh thanks everyone for the help.

haggyy, try the registry patch above, then try viewing in Device Manager and disabling any devices in the same connection/folder, I'd like to hear that yours is working...

IRQ is limited resources.
You can try allocate IRQ to video cards by disabling "some devices consuming IRQ".

update: Sorry. It seems to be a problem of memory mapping, not IRQ.

ty
Pages:
Jump to: