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
    2018-07-01T21:49:52+00:00

    I got it 

    Thanks done

    But sometimes the mouse hang for a minute then work again

    But when I insert USB drive the computer hang completely after 5 minutes 

    Do you have a solution 

    Hany

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-07-01T20:24:41+00:00

    Have a look at the stream I had replied to:

    .

    .

    Solution by registry hack*:*

    (Update 07.04.2018 from a reply by Le Hobo Bob:

    "A much simpler way that won't get undone by sfc or corruption repair and doesn't require complicated steps to take permissions on files would be to disable the driver service in the registry, I've tested this on Toshiba Satellite A135 and it works (well, other than my SD card reader which uses pcmcia not working anymore, everything else was fixed):

    * hit start

    * type regedit, hit enter

    * accept prompt

    * navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\pcmcia on the left

    * Double click "Start" on the right and change the value to 4 (the default is 0)

    * Reboot"

    //End Update)

    .

    .

    .

    Good day.

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments
  3. Anonymous
    2018-07-01T13:24:34+00:00

    What you mean by hack registry! !?

    Was this answer helpful?

    0 comments
  4. 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
  5. Anonymous
    2018-06-26T01:15:07+00:00

    MaBow,  You are right that this is not just a laptop motherboard issue.  But it is not isolated to a driver issue with the 945GM chipset.  This is happening across the entire segment of both laptops and desktops and I believe at a level below the device driver.   I can reload older drivers and the problem persists.  Given that it relates to the resource allocation of the devices and that adding another device appears to reorder the device load, I'm suspecting it's a problem with the HAL.  So, it is as we have been saying all along, it is a problem originating in Redmond and not at the device manufacturer's sites.  I do have confidence that, like all problems originating there, it will be fixed...in 3-5 years time.

    Was this answer helpful?

    0 comments