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-16T17:21:38+00:00

    Yes agreed, but surely Microsoft could provide a simple fix to the update code applying to these pcmcia card drivers. How many people have trashed perfectly good laptops thinking they have been rendered obsolete by Windows 10 updates. I guess the emphasis is on buying replacements. There is little motivation for MS to provide a permanent fix for older PCs. 

    Anyway many thanks to those on this forum who have figured out the workarounds. It's great that there are still those of us that like to keep old, but perfectly decent, PCs in use for as long as possible.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-03-08T18:56:18+00:00

    Just when you thought it was safe. Rumour has it there's a Spring Creators Update in the pipeline, Ver 1803.

    Device managers at the ready....!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-02-27T21:56:52+00:00

    Renaming C:\Windows\System32\drivers\pcmcia.sys did indeed fix the problem for me. 

    On my Toshiba Satellite A205-S4577 laptop,  I had experienced no network connection at all along with multiple and duplicate device drivers in Device Manager after Creators Update 1703.  I found no solutions, so I blocked the update with Microsoft's Wushowhide utility, keeping the Win 10 version for this computer at 1607.  Then, the Fall Creators Update 1709 resulted in the same problem, so I blocked it again.  However, Microsoft forced Fall Creators Update onto that computer this month.  For common denominator purposes, if anyone is analyzing compatibility data, the Toshiba Satellite A205-S4577 has a Mobile Intel 945GM Express Chipset, Intel Core 2 Duo Processor T5300, and an ExpressCard/34/54 slot.  (Toshiba ended OS support at Windows 8.1.)  So, again, renaming pcmcia.sys has given it a new lease on life.

    There seems to be no ability to permanently block feature updates (and continue receiving security and cumulative updates) when computer hardware reaches the limits of compatibility with the progression of Windows 10 feature updates.  From the user perspective, the critical flaw in the "Windows as a service" model is Microsoft's determination to make users' equipment obsolete by forcing updates that break the equipment, simultaneously denying older equipment a stable Windows 10 operating system.  The long-term effect is to force users to buy new equipment and new Windows 10 licenses.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. 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
  5. 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