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: Most helpful
Most helpful Newest Oldest
  1. 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
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. Anonymous
    2018-03-31T22:32:21+00:00

    Same problem at my VAIO PCG-7X2L.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-03-01T19:58:23+00:00

    The long-term effect is to force users to buy new equipment and new Windows 10 licenses.

    Or MS just stop forcing feature updates on us, my Sony Vaio works fine up until 1709 and then no wireless card, selecting defer feature updates and the metered connection makes no odds, poor show on the behalf of MS

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-02-27T16:56:20+00:00

    Renaming PCMIDA driver work great for resolving my issue. MICROSOFT NEEDs to listen to its customers. At least acknowledge the issue instead of passing the blame onto your device partners.

    Was this answer helpful?

    0 comments