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

107 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-04-11T23:19:35+00:00

    Renaming the pcmcia.sys worked for me also,

    This brought my 2006 custom built laptop up-to-date.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-04-14T15:36:27+00:00

    I have a system here with almost the same hardware as the above. I have the same issue.

    After a long search to find this very helpful and extremely difficult to find post I was able to restore the devices!

    Now after updating the Fall Creators update via Windows update and rebooting I find myself back in the same situation. Its as if the update reverted the changes. I hope this is isn't going to be a pattern for future updates. 

    Don't get me wrong I am glad that the Solution by registry hack*: worked but*

    I have not yet found a permanent solution for this issue but I am looking at the file permissions fix and will post the result.

    Thank you Rainer & Sebastian for the post!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-04-14T21:11:05+00:00

    I see this hack having to be applied with every major update.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-04-15T17:20:20+00:00

    I see this hack having to be applied with every major update.

    Since my last reply the system became unusable and would not boot past the Windows startup ring... 

    I wiped the drive and re-installed the original Windows 10 pro. No issues! I spent a couple of hours gathering and reinstalling all my programs. I spent the better part of the night and completely  re-configured the system.  Overnight Windows auto update updated this system 1709  OS Build 16299.125 and I'm back to Multiple device failure (Code 12) after Windows 10 Creators Update.

    This is so frustrating.

    I renamed  Renamed pcmcia.sys to pcmcia.sys.old - Rebooted windows.

    Devices restored, windows is updating again. We'll see what happens after the updates.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-04-16T17:21:38+00:00

    Yes agreed, but surely Microsoft could provide a simple fix to the update code applying to these pcmcia card drivers. How many people have trashed perfectly good laptops thinking they have been rendered obsolete by Windows 10 updates. I guess the emphasis is on buying replacements. There is little motivation for MS to provide a permanent fix for older PCs. 

    Anyway many thanks to those on this forum who have figured out the workarounds. It's great that there are still those of us that like to keep old, but perfectly decent, PCs in use for as long as possible.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments