Looks like a lot of m'shaft customers could be thinking of moving over to Linux.
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: Most helpful
-
Anonymous
2018-06-10T07:50:02+00:00 -
Anonymous
2018-06-10T07:39:43+00:00 Fully agree. All these ridiculous updates are not only time consuming but device consuming too.
I'm sure the vast majority of Windows users just want to be able view websites, use their email client and print stuff off. They certainly don't need all these fancy 'feature' updates that MS thinks we need to enhance our lives and it's got to the point where MS are effectively cyberattacking their own machines. It's ludicrous.
Goodness knows what hassle business users are going through.
-
Anonymous
2018-06-10T01:53:08+00:00 Thank you for getting back to us. The device manufacturer has the tools to look for your hardware concern. It would be best if you contact them for further diagnostics and troubleshooting.
If you have any questions or things you'd like to clarify, feel free to ask.
Regards.
This is a typical pass the buck copout from M/Soft. Instead of passing the buck to the device manufacturer try fixing the problems that Microsoft is creating with it's generic Windows 10 updates (1803). One size does not fit all! I can see a lot of Microsoft users bailing out and moving to Linux.
-
Anonymous
2018-05-29T01:35:19+00:00 Just updated My Sony Viao VGN-240E to Winows 10 1803 and had this problem.
This thread was spot on, the registry fix didn't work but re-naming the file did. I didn't name it back and deiced to just leave it as a .old file
Thank you MaBow, MikeMiCal, SamuelLazarin and Rainer Germany.
The walk-through on taking permission of the file to rename it was especially helpful.
After a reboot everything started working except for just 2 unknown devices and a quick google search of
VEN_104C&DEV_803B
Took me to this thread, Link
IDCam replied on
I know this is an old thread however I've put Win10 on a Sony Vaio VGN-FZ11M and came across this missing driver.
After a search I came across this link:
ftp://ftp.vaio-link.com/PUB/VAIO/ORI...R\_2.0.0.19.ZIP
Download extract and then run the setup.exe
Driver now installed although I've not tested yet.
a Second search of
ACPI\SNY5001
Lead to me downloading the Sony Firmware Extension Parser Driver right from the Sony support website.
There are no windows 10 drivers available for these but so far so good with installation of the windows 7 drivers.
Cheers and thank you!
-
Anonymous
2018-04-21T13:48:28+00:00 Sebastian,
In case you were wondering,
Overwriting the pcmcia.sys caused a page fault and the system wouldn't boot. Now to restore the system (from the restore point I created before I overwrote the pcmcia.sys), rename the pcmcia.sys back to old and call it fixed.
Thanks
Jodi