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 No comments

107 answers

Sort by: Oldest
  1. Anonymous
    2018-03-21T12:13:26+00:00

    Thank you MaBow

    Renaming pcmcia.sys solved my problem on

       ACER 9410

    • 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 Intel 82801G USB controllers

    Also disabled this device in device manager and chose No on Advanced system settings-Device Installation Settings-Select the second option titled No, let me choose what to do option, so that Windows Defender will give no risk warning.

    As I wrote before, Microsoft programers after XP, know nothing about programing in comparison to their predecessors.

    In our almost 2 years case, THEY SEE for almost a whole month that A DRIVER, a SPECIFIC DRIVER called pcmcia.sys causes this issue and they do nothing. Mabow, as a chance occurrence, using a PCMCIA module found out that this was causing the issue. And they do nothing. They gave a new Update to 1709 and they did not solve.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-03-31T22:32:21+00:00

    Same problem at my VAIO PCG-7X2L.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-04-04T17:18:42+00:00

    These hacks work:

    (Original 04.04.2018) Thank you MaBow and MikeMiCal - I worked with your suggestions.

    (Updated 07.04.2018) Thank you SamuelLazarin for having confirmed that it's working.

    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)

    COMMENT: By resetting the registry value back to default and rebooting, the pcmcia service might work again without causing the failure. Should be tried.

    Aparently it also should help to shove in any PCMCIA card, though in my case that solution didn't help. However, renaming files did the job and the update from Windows 10 version 15xx/16xx to the creatore's update versions 1703, 1709 and 1803 is operating well. After your Windows 10 got updated and your network hardware gave up while the device manager went to apocalypse by showing multiple device failure / errors (code 12) try this hack:

    Solution by renaming pcmcia.sys*:*

    Before starting, make sure you are logged in with an account having administrator permissions ascribed. Also, you need to enabled 'all files visible' and 'file extensions visible' in the file explorer. If you don't know what this is or how to do it, ask a technican to guide you through and rather don't continue alone.

    1.) Open the folder: c:\windows\system32\drivers and find the file pcmcia.sys

    2.) Change the file access permission to 'full control' as follows:

    2a.) Right mouse click on pcmcia.sys - choose 'properties' - choose the tab 'Security' - click button 'Advanced' for special permissions - a new window opens called 'Advanced Security Settings for pcmcia.sys'

    2b.) In the new window you see 'Name' in the first line and 'Owner' in the second*.*In the owner line Click 'Change' - a new window opens called 'Select User or Group' - click button 'Advanced...' - a new window opens also called 'Select User or Group'- click 'Find Now' - in the lower part of the window you see 'Search results' - Scroll to the 'Name' that equals your user name and that shows your PC name under 'In Folder' - click (highlight) your name and click 'OK' - the current window closes -you returend to the first 'Select User or Group' window - click 'OK' - window closes and you are back to 'Advanced Security Settings for pcmcia.sys' - check whether the owner now is your user name and click 'OK' - you might get ask for confirmations and get system info pop-ups which all need to be acccepted or confirmed.

    2c.) You are back in window 'pcmcia.sys properties' - in the list 'Group or user names:' choose your 'Users (PC-Name\Users)' - in the lower part of the window change the 'Permissions for Users' by ticking the check- boxesto 'Full control' and 'Modify' - then click 'OK' - confirm the corresponding security warnings.

    3.) Rename pcmcia.sys to pcmcia.sys.old - Reboot windows

    Either problem solved or continue with 4:

    4.) Open folder *c:\windows\system32\driverstore\filerepository* and find the folder *\pcmcia.inf_amd64_(hashtag)* - Right click and change permissions for the user 'Everyone' to enabled 'Full control' and 'Modify' - you might have to go through the process of step 2a-c.

    5.) Open folder c:\windows\system32\driverstore\filerepository\pcmcia.inf_amd64_(hashtag) - rename pcmcia.sys to pcmcia.sys.old- rename pcmcia.inf to pcmcia.inf.old - Reboot windows

    The multipe device failures (Code 12) should have disappeared. The WLAN/LAN should be functional and connect again.

    After all this completed, I have renamed all three files to their original name, then rebooted and it STILL WORKS including the PCMCIA card**.** I also recommend to change all permissions of files and folders back to the original setting.

    Further help: The following website explains how to get the required rights: https://www.drivereasy.com/knowledge/you-require-permission-from-trustedinstaller-error-fixing-guide/

    Please let us know whether it has helped.

    Best regards and good luck,

    Rainer & Sebastian

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-04-06T02:57:17+00:00

    It works!!!!!

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more