09-21-2018 10:59 AM
Have just bought a ThinkPad P52s
Have setup a multiboot with Windows 10 (64-bit), Windows 7 (64-bit) and Windows 7 (32-bit)
and have 3 issues: (3 of 3 ) : Code 12 (This device cannot find enough free resources that it can use)
One of the key purposes of getting this Laptop was to use Thunderbolt 3 to connect an express card adapter to enable a firewire cardbus and a SCSI cardbus to the laptop to enable us the repair/maintain some legacy scanners. These scanners are 32/16 bit devices and will generally only work with 32-bit OS.
A firewire adapter connected directly to the thunderbolt works OK in both Windows 64-bit and 32-bit.
but . . both the expresscards (firewire and scsi) fail to connect with code 12 errors.
Can you please help me resolve this
Solved! Go to Solution.
09-21-2018 06:19 PM
Welcome to the community forums.
Just to verify, when you connect the expresscards, is the drivers showing up in device manager? If yes, does it show working correctly?
For basic troubleshooting for the error you are getting. Check this linl: https://windowsreport.com/device-cant-find-enough-free-resources-error-code-12/?CID=ww:lenovosocial:...
09-22-2018 01:36 AM
The code 12 only arises in Windows 7 (both 32-bit and 64-bit).
The firewire and SCSI expresscards install OK in windows 10 and work correctly (limited testing).
Note: there is an issue with the SCSI card as only fully works in a 32-bit environment.
However your suggestion to look at "FIX: This device cannot find enough free resources to use (code 12)" gave me an idea.
I used msinfo32.exe to try to get some indication there appear to be no IRQ conflicts but may be an issue with sharing/conflicting memory address with the 'PCI express standard . . ports'
PS not sure if this post (+ the other 2) should be moved to ThinkPad: P and W Series Mobile Workstations
09-29-2018 07:51 AM
This issue appears to occur because of the initial state of the PCI Express bridge device in the expansion chassis. By default, when you start or reset PCI Express bridge devices, the initial values of the limit register for the bridge resource window are less than the initial values of the base register for the bridge resource window.
My issue was resolved using the suggested workaround please see: