As I was also was forced to rollback 1709 to latest 1703 some days ago.
A machine running with 5 nvidia GPU (1x 1060 + 4x 1070) because 2 cards didn't start up with a "ressource 12 error".
Analyitics:
-> 1703 (build 15063.850) operates fine -> no hardware damage
-> the 2 devices that were not able to start sitting at the PCI-E slots/lanes [4 and 5] even though the other gpus (lanes 1,2,3) were (pysically!) removed - these devices were not recognized
-> It does not help to disable other devices in devicemanager (onboard LAN, oboard sound, sound devices of the recognized gpu's) to free IRQ/Mem Areas (In 1709 there were dozens of system devices detected/installed - all hooking irqs/mem areas )
-> (Cross check) The 2 devices worked fine on other PCI-E ports (1,2,3) but then the other device fails to start up
-> Complete driver removal (took me ~2hours) and installation of latest nvidia drivers did not solve the probelm.
-> in safe mode all 5 gpu's were one time recognized (after driver removal)
Conclusions:
with/in 1709 either the ressource assigment (IRQ+Mem) is buggy
or - what I guess is most the root cause - the PCI-E lane assigment is down (as ports 4+5) were affected
technical details:
MB is Asrock H81 pro BTC 2.0 manufactured 4/2017 latest bios version is installed
hooked a Intel Celeron G1840
and as said ASUS GTX 1060 + 4x AUSUS GTX 1070 - all operating stock firmware
Update: Luykily found:
via http://www.tomshardware.co.uk/answers/id-3563884/code-time.html ->
https://bitcointalk.org/index.php?topic=2401059.0;all
points to
https://support.microsoft.com/en-us/help/942959/error-message-when-you-attach-a-pci-express-expansion-chassis-to-a-com
"
This device cannot find enough free resources that it can use. (Code 12)
....
Workaround for error 1 Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot
guarantee that these problems can be solved. Modify the registry at your own risk. To work around this issue, follow these steps:
- Click Start
, type
regedit in the Start Search box, and then click regedit in the Programs list.
If you are prompted for an administrator password or for confirmation, type the password, or click
Continue.
2. Locate the following registry subkey, and then click it:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PnP\Pci
3. If the HackFlags registry entry is not present, follow these steps:
1. On the Edit menu, point to New, and then click
DWORD (32-bit) Value.
2. Type HackFlags, and then press ENTER.
3. On the Edit menu, click Modify.
4. In the Value data box, type 400, click Hexadecimal in the Base area, and then click OK.
"
REMARK: users in both linked forums reported that it worked for them with 600 @ windows 10 1709
"
-
- Exit Registry Editor.
- If the HackFlags registry entry is present, follow these steps:
- Right-click HackFlags, and then click Modify.
- In the Value data box, type 400, click Hexadecimal in the Base area, and then click OK.
- Exit Registry Editor.
"
REMARK: users in both linked forums reported that it worked for them with 600 @ windows 10 1709
Can someone test if this also works for your laptop scenarios?
Maybe I can test tomorow. Nevertheless MS should fix the problems root cause :-)