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-19T16:14:21+00:00

    If you've already successfully renamed the pcmcia file, it sounds like you already have permission.

    Otherwise.... https://m.youtube.com/watch?v=el0gaP8K4qY

    'Rename file that needs permission from Trusted Installer'

    PS, I fixed my missing Mass Storage Controller driver using 'driver easy'.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-19T16:02:04+00:00

    PHILIPCLARIDGE,  have renamed the pcmcia file but am running into the issue of configuring the access permission.  Can you give us the "how to" on that step.  Thanks....

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-19T09:29:09+00:00

    And when I tried KB4073291-x86 it said 'The update is not applicable to your computer'.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-18T12:44:46+00:00

    I've googled it and all results indicate your renaming fix is for Vista kit being upgraded to Win7.

    Although my machine was originally Vista, then 7, now 10 - are you sure this fix is appropriate for the issues we are experiencing with shot-gunned device managers?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-02-18T07:29:08+00:00

    I am having the identical problems with a Sony VAIO VGN-N220E after the feature update to W10, version 1709. OS build 16299.125.  On top of the issues with the Device Manager which has knocked off both the WIFI and Ethernet communications, it has also eliminated the Restore Points and any means of restoring previous versions.  So the computer is dead in the water with no means of communications other than the optical drive.

    Microsoft, if you listening, you have caused this issue.  The computer was working fine until the last update, it is now a brick.  Now fix it or tell me how,  how to solve the multiple entries in the Device Manager or how to revert back to a previous version.  This is your issue, now fix it, please.

    I am at the same stage as you. The only way to wake up one of my two network adapters is to shut down the laptop (a restart doesn't seem to do it) wait about a minute, boot it up, go into device manager, uninstall the Realtek PCIe FE Family Controller (without deleting), go to Action at the top and scan for hardware changes. The device manager refreshes three times and hey presto, the yellow triangle is gone and I'm back online to try even more futile 'fixes'.

    Was this answer helpful?

    0 comments No comments