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

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.

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.

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!

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.

hi WickedPigeon.

Perhaps, FallCreatorsUpdate(1709) triggered a malfunction of GPU driver installation.
If you are going to install 1709 cleanly, please try disabling HD audio before installing the GPU driver.

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

hi, guys.

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

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

If you are doing exactly the same edits and your rig does not run yet.
I want to know the cause. Please tell me about your rig composition.

ty

Hi, Scippylisp.

About the screw of PCI bus number.
There may be no problem if the numbers are not overlapped each other.
These are automatically numbered, it may be a consecutive number or not be so.

Physical Slot2(PCIEx16) of this MOBO is different from other PCIEx1.
It seems that it is directly connected to the CPU.

You can find it under "Intel (R) Xeon (R) processor E3-1200 v3 / 4th Gen Core processor PCI Express x16 Controller".
Not "Intel (R) 8 Series / C220 Series PCI Express Root Port".

However,
It seems that "the behavior of PCIE assignment to memory" was surely changed in version 1709.
Combining version 1709 with "this MOBO with less memory" seems to make the problem serious.

By the way,
6GPUs on my rig running with windows10 1709 now.

OS: Windows10pro 64bit 1709 (Clean install from USB media. Then edit HackFlags turn on)
MB: ASrock H81 BTC Pro R2.0 (BIOS v1.20, Setting is "load default".)
CPU: Intel Celeron G1840
RAM: DDR3 8GBx2 (16GB)
GPUs
 PCIE1: GTX1060 6GB
 PCIE2: GTX1080
 PCIE3: GTX1070
 PCIE4: GTX1070
 PCIE5: GTX1070
 PCIE6: GTX1070

(All GPUs connected via riser card. and Disabling HD audio devices in device manager.)

When turn off HackFlags and enable audio devices,  Three GPUs indicate code12.

hi, djtappage.


Yes.
If TOLUD setting to "Auto" (like ASRock H81 BTC Pro R2.0)
"The amount of resources that can be allocated for GPUs" will Adjusted by physical RAM amount automatically.

So, If the rig have less physical RAM.
We must makeshift with fewer resources.
(like disabling some HDMI audio on video devices.)

A simple way to reduce the problem is to add physical RAM.
But, I have seen the case of driving 3GPUs with 4GB RAM. It seems possible.

The Haggyy's rig with 3GPUs and 4GB physical RAM finally started running.
https://bitcointalk.org/index.php?topic=2307023.0;all

Aside from this.
"HackFlags" increases limit of "the number that Windows can enumerate PCIE devices".
"devices not enumerated" also indicate CODE 12.
Perhaps, I think that initial limit value has changed to less value in FallCreatorsUpdate. Or Update have bugs.

be careful.
The problems of TOLUD and LimitRegister are independent each other.

Hi, guys.

Yes. Specific operations in the device manager are as follows.

hi, Yoledo.

oh, Editing the registry at your own risk..
..Did you enter it with DEC?
Plz care, The flag value must be on HEX, not DEC.

By the way,
if your MOBO is ASRock H81 BTC Pro R2.0,
Unfortunately, It have no TOLUD option. (TOLUD is fixed to "Auto")
but, You can try secondly method. (Disabling some unnecessary PCIE devices)

I wish you good luck.

hi, Yoledo

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

Besides,
You also should care TOLUD(Top Of Lower Usable Dram) problem, when your rig has less main memories.
This problem occur due to insufficient memory address space for accessing PCIE devices.

You can try reduce TOLUD value in BIOS menus ("Auto" does not help you), If there is such item. or
You can try disabling "some unnecessary PCIE devices (like HDMI audio on video cards)" in device manager.

And also if your MOBO has Buggy PCIE 3.0 (Gen3),
This method may help you.
check it.
https://www.nicehash.com/news/128

hi, simpie10.

This thread might help you.
https://bitcointalk.org/index.php?topic=2307023.0;all

When the rig has less main memory,
In order to access too many PCIE devices, allocation to the IO memory map may not be enough.

You can try disabling "some unnecessary PCIE devices" (like HDMI audio on a video card) in device manager.

ty

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.


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.

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

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.

hi, haggyy


Your editing is okay.

Also, you need to try disabling "some IRQ consuming devices".
(e.g. Disable iGPU in BIOS settings, right click and disable on HDMI audio on video card in device manager, etc)

update:
Sorry. It seems to be a problem of memory mapping, not IRQ. but, disabling "some unnecessary PCIE devices" is valid.

ty

hi, haggyy.


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

hi, Flyerstarter.

It's hidden option to avoid InterruptReQuest(IRQ) confliction, it made by microsoft.

However, I don't know how it behaves.
..but maybe, this option might make assign IRQ in Windows instead of BIOS.

ty

update:
sorry, I misunderstood about the behavior of this option.