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-09-03T19:00:55+00:00

    Which version and edition of Windows 10 originally came with the system?

    Because I don't see VGN-N29VN listed as supported:

    https://esupport.sony.com/US/p/os10upgrade.pl? 

    You might want to consider restoring the original version of Windows that came with the system.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-09-03T17:55:02+00:00

    Hi,

    This could be due to a driver which needs to be updated following the Creators Update. To resolve your concern, please provide these information:

    • Which build are the machines currently on?
    • Are the device drivers up-to-date on those machines?

    Regards.

    Was this answer helpful?

    0 comments