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-06-26T07:52:13+00:00

    Solution by registry hack worked. Much appreciated! I have been fighting this nuisance for a long time rolling back and forth unwillingly(update I mean) on SONY VAIO VGN-FE11S. Thanks, great solution!!!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-03-21T12:13:26+00:00

    Thank you MaBow

    Renaming pcmcia.sys solved my problem on

       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 Intel 82801G USB controllers

    Also disabled this device in device manager and chose No on Advanced system settings-Device Installation Settings-Select the second option titled No, let me choose what to do option, so that Windows Defender will give no risk warning.

    As I wrote before, Microsoft programers after XP, know nothing about programing in comparison to their predecessors.

    In our almost 2 years case, THEY SEE for almost a whole month that A DRIVER, a SPECIFIC DRIVER called pcmcia.sys causes this issue and they do nothing. Mabow, as a chance occurrence, using a PCMCIA module found out that this was causing the issue. And they do nothing. They gave a new Update to 1709 and they did not solve.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-01-12T21:14:11+00:00

    We are multiple users with the same problems.

    I would like to know the solution of Microsoft to this.......

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2017-11-29T06:36:37+00:00

    Yes I have a Windows 10 Vaio VGN-N31M with the same exploding Device Manager resulting in no Internet Connection due to code 12 errors and multiple entries.

    Hi Keith,

    Just to check, are you still getting Error Code 12 in Device Manager?

    We're looking forward to your reply.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2017-11-26T19:21:00+00:00

    I completely agree with you.

    I have the same problem,,several devices are not working because of the code 12 problem.

    This devices were running correctly in 1607 versión and not not in 1709 or 1703

    We need a solution to the problem.

    It is not a Windows 10 problem.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments