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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-02-20T20:22:22+00:00

    Very well done, at last I got my old Toshiba A100 laptop upgraded from Win 10 1607 to 1709, thanks to your tip. Indeed PCMCIA was the culprit and running shutdown /r made the whole thing running as it should. There is still a PCMCIA card error in the device manager, which is strange because it is a MS driver, but who cares. Many, many thanks again. I hope it will work out for the others as well.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-21T14:52:18+00:00

    I confirm that running sfc /scannow returns the system to its unusable state. The remedy though is as before: rename windows\system32\drivers\pcmcia.sys to pcmcia.old, run shutdown /r, and presto the system is operational again.

    Imho this is the proof that pcmcia.sys, a registered microsoft windows 10 driver, sucks. MS please repair this and provide the community with an update.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-02-24T17:53:40+00:00

    Based on the details provided in this thread, kindly run the Hardware and Device troubleshooter to determine what causes the conflict that triggered the issue. After we determine the conflict, we will need to disable it and see if there are any changes. To run the troubleshooter, follow these steps:

    1. Access Control Panel.
    2. Change View by from Category to Small icons.
    3. Choose Troubleshooting.
    4. Choose Hardware and Sound.
    5. Click on Hardware and Devices.

    If possible, provide us the return message from the troubleshooter so that we can investigate this matter further.

    We'll be waiting for your response.

    Regards.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-25T14:19:49+00:00

    Based on the details provided in this thread, kindly run the Hardware and Device troubleshooter to determine what causes the conflict that triggered the issue. After we determine the conflict, we will need to disable it and see if there are any changes. To run the troubleshooter, follow these steps:

    1. Access Control Panel.
    2. Change View by from Category to Small icons.
    3. Choose Troubleshooting.
    4. Choose Hardware and Sound.
    5. Click on Hardware and Devices.

    If possible, provide us the return message from the troubleshooter so that we can investigate this matter further.

    We'll be waiting for your response.

    Regards.

    First of all, my Toshiba A100 now runs the Dutch version of Win10 32 1709 with 2 errors (yellow ! mark) in the device manager.

    1. The PCMCIA error that originally messed up the 1709 update but by renaming it to *.old at least let me get the update, and 2) a cd/dvd drive error. I thought the latter was a hardware problem, but changing the drive with a new one gave the same problem. I ran the thoubleshooter (probleemoplossing) as suggested and it found these 2 problems (as to be expetcted:

    Clicking on the top and later on the lower problem gave the same answers:

    The problem cannot be established by the trouble shooter (my translation).

    When I then click on feedback, in bothe cases there is a short flash, and the Troubleshooter ends just like that. So, unfortunately no further useful information.

    Regards, Teunis

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-02-25T15:42:29+00:00

    https://imgur.com/71rYeY0

    Kem,

    Above is the result of the troubleshooting process you described.  The laptop in question is a Sony VAIO Model # VGN-N220E.  As with the others, the Device Manager blew up when 1709 was loaded.

    Was this answer helpful?

    0 comments