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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2017-11-30T17:50:30+00:00

    I am having the same issue on my old Toshiba Vista capable laptop. Win 10 1607 works fine. Clean installs of 1703 or 1709 blows up device manager with Code 12's.

    Was this answer helpful?

    0 comments
  2. 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
  3. 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
  4. 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
  5. Anonymous
    2017-11-17T19:40:05+00:00

    The responses for Drivers continue to be baffling on here when people come on with older hardware.

    The users has an Intel 945 Express based system probably built around 2005-2007 or so when that chipset was used a ton in devices around the end of XP and beginning of the Vista and 7 Era. 

    Anyway, this chipset has worked fine in Windows 10 up until the 1703 update. Once 1703 or 1709 is installed, The device manager looks like a bomb went off and a bunch of devices have the yellow exclamation point on them with most all having the Error Code 12. Another weird bit is there are multiple of the same device showing (so normally 1 945GM Graphics device, now shows 3 with 1 working, and 2 that should not be there, with the errors as described showing). 

    So far I have yet to find a working fix and while restoring to a previous 1600 based build is a temporary solution, it really isn't an optimal one as the devices may be old, but are in no way incapable of running Windows 10 all this time before this update came along and shotgunned the device manager and made the device run immensely worse because of it.

    I will keep this thread updated if I find a fix. If Windows 10 intentionally breaks all the hardware running on the 945 chipset, that is going to be a huge number of older but still capable devices completely abandoned for no other reason than "Just Because" at this point.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments