This can be a fairly complicated issue.  Keep in mind, in 99% of the time, when Windows states "Not enough resources" it is either refering to a IRQ or a Memory block.  These resources are managed by the motherboard internally in tandem with the operating system.  This is most common with video cards.  If this is with a video card, certain devices have issues sharing resources with vodeo cards, but only in one direction.  For istance,your sound card will not share its IRQ with a video card, but if the video card has the IRQ it can share it with the sound card usually without a problem.  What you need to do is isolate what device(s) are having sharing conflicts with the device in question, and see that it gets the resource first and it will, usually, share the resource with other devices.

1)  Goto device manager.  Right click on Computer/My Computer, select Properties, click on Hardware, select Device Manager.

2)  In the top menu, click on "View" then select "Resource by Connection".

3)  The issue will usually reside in IRQ or Memory.  Expand those menues out.  In IRQ, make note of everything that share the IRQ.  Goto Memory and make note of the address range, then check for any other devices sharing the same range. 

4)  If the device in question is a card, power down and remove it, if it is onboard, like integrated sound, onboard ethernet or USB, things of that nature go into BIOS, goto Integrated peripherals and disable them, then boot back into Windows.  See if the Code 10/12 error(s) are gone.  If so, install the device, reboot, then reenable/reinstall the other devices and the issue should be cleared.  If NOT, look to next step.

5)  If the issue persists, reboot, go back into BIOS, and in PCI/PnP Configuration there should be an option for Reset ESCD Data or Reset Configuration Data, set it to enable, the save & exit, this will reset the motherboard assigned resources.

6)  Let the system boot up then check to see if the error persists.  If it has cleared, install the device then reboot amd disable the Reset setting in BIOS, boot back into Windows.  If the issue has remained clear, you can now reenable/reinstall the other devices and your build should be up and running with everything fully installed.