I have the same problem - everything worked fine until Creators update. Post-update resources in device manager show no conflicts (i.e., device has a unique PCI allocated) but WIndows Creator update insists it cannot use Nvidia 1070 GPU because "not enough resources". I change PCIE slots, resources are reallocated but continue to have the same problem. The Microsoft response to use the troubleshooter does not work because no troubleshooter option exists. The uninstall / reinstall drivers also does not work. Drivers I am using are latest from manufacturer and I have completely uninstalled (i.e., removed all copies of old drivers and cleaned registry) and reinstalled. The lament that it is the device manufacturers problem is simply not correct - everything worked before the update but does not work after.
Multiple device failure (Code 12) after Windows 10 Creators Update
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.
107 answers
Sort by: Oldest
-
Anonymous
2017-12-26T22:15:38+00:00 -
Anonymous
2018-01-11T22:43:13+00:00 Same here with a Toshiba Equium A200 laptop 32 bit. Device manager looks like a set of road works, Qualcomm wireless network adapter AND Realtek PCIe FE Family Controller out of action so can't get on the net to do anything, although I did a couple of times after uninstalling the driver and scanning for hardware changes, then even that fix gave up the ghost.
USB ports out of action too and some PCI to PCI Bridges, and some universal host controllers just to make the numbers up.
Machine was fine before update.
-
Anonymous
2018-01-12T21:14:11+00:00 We are multiple users with the same problems.
I would like to know the solution of Microsoft to this.......
-
Anonymous
2018-01-12T22:03:01+00:00 I uninstalled the creators update, that in itself fixed the code 12 but in turn now the, security services keeps stopping. the only thing i can find is that the creators update acts like it updates the firmware to 64 bit, and try or tries to put 64 bit on a 32bit system and that's why there is code 12, as after removing the update there are files with 64 bit firmware that was not removed in unistal. there could be a problem with the windows registry on update. but i'm not a wiz with computers software just fixing the boards etc to much binory for me but file sizes are very similar in 32 bit and 64 bit.
-
Anonymous
2018-01-12T22:12:27+00:00 Quite agree, Microsoft need to issue a software download to put this right - they have transformed my previously serviceable laptop into a door stop that lights up.
This is not a driver issue (good job, because Toshiba has removed them all from the archive section of it's website support page), there seems something in the OS update that is preventing these devices from starting.
I'm trying not to smell a rat here, I really am (cough, Apple, cough).