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-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-06T02:57:17+00:00

    It works!!!!!

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  3. Anonymous
    2018-02-18T15:01:04+00:00

    It works. Thank you @MaBow. I renamed the pcmcia.sys driver file and reboot the laptop. No longer see conflict on the network adapters. 

    I'm not going to use PCMCIA card. So this work around is good for me.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  4. Anonymous
    2018-02-05T14:25:20+00:00

    Like many other users I have been experiencing the exact same problem with 2 identical Gateway laptops. They may be Visa 32 vintage but each were quite happy running Windows 10 64 bit ver 1607.

    I would stick with 1607 and have managed to defer feature updates for 6 months. What is more irksome is that the 1703 or 1709 improvements are now regularly offered and installed. I waste a lot of time reverting to the previous build which works.

    Frankly, if I'm going to remain stuck in this loop it seems Windows has run its course and I should consider migrating to Linux. I'm not inclined to stick with Windows 7 simply because primary support for that system will soon cease.

    If Microsoft insist on pumping out feature updates once or twice a year, the least they can do is ensure they work with legacy equipment that ran 1607 or cease imposing these updates on us.  Microsoft seem to be deliberately rendering hardware no longer fit for purpose and forcing people to buy new equipment.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  5. Anonymous
    2017-11-26T21:05:33+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.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments