Multiple device failure (Code 12) after Windows 10 Creators Update

Anonymous
2017-09-03T11:49:17+00:00

Hi all,

I was given a computer to fix that showed multiple 'This device cannot find enough free resources that it can use (Code 12)' errors in the Device Manager. It is a quite old Sony VAIO VGN-N29VN.

I reinstalled Windows from scratch but the problem reappeared after applying the Creators update. As of now, multiple devices show the Code 12 error and are unusable. In some cases, there are multiple errored entries and one good entry for a given device (e.g. Intel 945 integrated GPU). In other cases, there is only one errored device and the device isn't working (e.g. WiFi or wired network adapters.)

The peripherals showing the errors are the following:

  • Mobile Intel 945 GPU
  • Intel 82801G ATA controller
  • Texas Instruments 1394 OHCI controller
  • LAN-Express AS 802.11g PCI-E adapter
  • Marvell Yukon 88E8036 PCI-E Fast Eth controller
  • HD audio controller
  • various PCI to PCI bridges
  • three Inter 82801G USB controllers

Some of them are usable (as they appear twice or three times in the Device Manager, others are not.) It looks like the update broke something, as this happened twice and I haven't added or removed any internal or external peripherals. What can I do to fix the problem?

Thank you.

Moved From:

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

107 answers

Sort by: Most helpful
  1. Anonymous
    2018-02-19T22:59:20+00:00

    At last something that works! simply renaming pcmcia.sys to .old and all the code 12s disappeared. Well done and thank you.

    2 months I've been waiting for a solution to the code 12 problem and nothing from microsoft. Surely they must accept it is their problem now and provide a proper fix!

    Annoyingly I ran sfc /scannow to fix other problems and it put back the pcmcia.sys!

    Now all I have to fix is 100 % cpu all the time and missing selection boxes when I right click on some tasks! FCU worst ever microsoft update.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-01-29T17:43:48+00:00

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-01-27T12:32:46+00:00

    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

    "

    • Error 1:

    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:

    1. 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

    "

      1. Exit Registry Editor.
    1. If the HackFlags registry entry is present, follow these steps:
      1. Right-click HackFlags, and then click Modify.
      2. In the Value data box, type 400, click Hexadecimal in the Base area, and then click OK.
      3. 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 :-)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-01-14T12:30:04+00:00

    Same issue for my ACER 9410.

    • Mobile Intel 945 GPU
    • Intel 82801G ATA controller
    • Texas Instruments 1394 OHCI controller
    • LAN-Express AS 802.11g PCI-E adapter
    • Marvell Yukon 88E8036 PCI-E Fast Eth controller
    • HD audio controller
    • various PCI to PCI bridges
    • three Inter 82801G USB controllers

    They do not solve and this is very suspicious. They simply reveal their purpose:

    FORCE PEOPLE TO REPLACE OLD DEVICES so new devices will be sold, more Windows will be sold etc etc etc.

    A problematic software THAT HAS BECOME WORST THAN SILLY ANDROID. And the worst is that Microsoft is paid for this and paid too much. New programmers hired by Microsoft know nothing in comparison to their predecessors.

    The only possible solution is to temporarily ?? stop Update v1703 by using:

    http://download.microsoft.com/download/f/2/2/f22d5fdb-59cd-4275-8c95-1be17bf70b21/wushowhide.diagcab

    and uncheck the box "Apply Repairs Automatically" then Next, then wait for a while and from list uncheck "Feature update to Windows 10, version 1703 or 1709"

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2018-01-13T20:21:49+00:00

    Mr. Bar

    Why is the update causing so many instances of "Corrupted system files..."?  If I could understand why, then perhaps I can deal with the issue...  Is this update still being pushed out to us?  If so, how do I turn it off / prevent it from installing on the other machines on my system?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments