New GTX 760 won't work, "not enough free resources"

neetbed

Reputable
Nov 15, 2014
3
0
4,510
I just recently bought an EVGA GTX 760 and a Rosewill RD600 to upgrade the grahpics on my desktop.

Its a Lenovo k430 IdeaCentre, all stock parts, aside from the 600W PSU I mentioned above, basics are as follows,
- Intel i7 3770
- 8gb DDR3
- stock GeForce GT 620

When I first installed the 760, my system wouldn't boot past the "lenovo" screen and then beep at me. I turned on the Intel graphics and went in and installed the drivers for the 760, so now it shows up under device manager but its flagged with "This device cannot find enough free resources that it can use. (Code 12)" and still won't boot properly, only beep at me.

I've searched a lot for possible solutions, I have tried turning off quick boot and switching the BIOS to legacy with no avail. Both were purchased from Newegg and I could easily return it, but I would rather not resort to that.

Any insight is welcome, thanks in advance.
 
Solution
This is an old query, but the NVidia / "This device cannot find enough free resources that it can use. (Code 12)" thing seems to be a real common problem. So I'm posting what worked for me, in a system with more than one graphics adapter (my other one was a built-in Intel):

1) During Windows boot, interrupt at the very first Windows splash screen ("F8")

2) Choose an "Advanced Option"

3) The option to try is "Enable low-resolution video"

4) Allow Windows to finish booting (The screen will probably be oddly sized at this point)

5) Enable the nVidia driver explicitly in Device Manager (if it's not already). If you're lucky, that works: the nVidia starts up happily(!)

6) Enable the "other" driver explicitly in Device Manager (if it's...

garryw

Reputable
Jan 2, 2015
1
0
4,520
This is an old query, but the NVidia / "This device cannot find enough free resources that it can use. (Code 12)" thing seems to be a real common problem. So I'm posting what worked for me, in a system with more than one graphics adapter (my other one was a built-in Intel):

1) During Windows boot, interrupt at the very first Windows splash screen ("F8")

2) Choose an "Advanced Option"

3) The option to try is "Enable low-resolution video"

4) Allow Windows to finish booting (The screen will probably be oddly sized at this point)

5) Enable the nVidia driver explicitly in Device Manager (if it's not already). If you're lucky, that works: the nVidia starts up happily(!)

6) Enable the "other" driver explicitly in Device Manager (if it's not already)

7) Resize the screen to normal (if it's not already.) That's it.

I would conjecture that the "low-resolution" mode caused my Intel driver loading to be deferred until sometime after the nVidia was loaded. Then, later, when the Intel driver did get loaded, it was able to get out of the way of the resources that the loaded nVidia driver had already claimed. (But when the Intel was loaded first, the nVidia was not clever enough to get out of its way.) The new settings were then recorded in the system registry. It's a lasting effect: subsequent boots did not need to be in "low-resolution" mode, and the "not enough free resources" error was gone "forever". (Or, at least, for the last day, which is approximately "forever"...)

Only resource value that I could see that changed in the Intel driver was its IRQ number -- the nVidia driver ended up with the Intel's original IRQ, and the Intel driver ended up with a new one. (Dunno what "IRQ" actually means on a PCI bus...)

And after the above, I still could not get my new nVidia to actually draw pictures. Sigh. BSOD's whenever I cranked it up. Oh well. After strenuous experiments, I've given up on the new nVidia; I will go back to my old one now and get rid of the new card.
 
Solution