Biostar MCP6P M2+ - Code 12 - not enough resources

ChilliConCarnage

Junior Member
Jun 21, 2007
24
0
61
I have a Biostar MCP6P M2+ with a Athlon II X4 630, 4GB Patriot DDR2-6400, and a Radeon 4980, running Win7 Ultimate 64.

I can put nothing into the PCI slot without getting the yellow exclamation point in device manager. It says Code 12 - not enough resources.

At first, I had a Gigabit NIC in there, which I replaced with two others - all gave the same error. So I just gave up on it for a long time.

But today, I tried installing a SATA card (because I was attempting to install a second optical drive and found out that one of the SATA ports doesn not seem to work). Guess what - code 12 again.

I've disabled everything in the BIOS, but nothing gets me resources to use any card in the only PCI slot that's showing, due to the size of the Radeon 4980. And I can't edit the resources it tries to use in device manager.

Any ideas?
 

tcsenter

Lifer
Sep 7, 2001
18,893
544
126
Update the BIOS if applicable. If nothing changes, its a BIOS issue/bug. Contact BIOSTAR.
 

ChilliConCarnage

Junior Member
Jun 21, 2007
24
0
61
Already updated to latest BIOS. Contacted Biostar months ago - their suggestion:

"Could you install another OS and see if you can replicate the problem on a non enterprise edition of win7?"

I don't really want to do a full re-install, and it isn't worth it for this machine. I use it just for Movie-Ripping / transcoding. But it takes so much longer to xfer files to the media server over 10/100 - I'd love to get a gigabit card working in there! So I was hoping somebody else had a similar problem w/this mobo, and had figured out a solution.
 

ChilliConCarnage

Junior Member
Jun 21, 2007
24
0
61
Not an upgrade - built it and installed Win7 and have never done a re-install or upgrade.

Just for kicks, I swapped videocards this morning to see if that made a difference - replaced the Radeon HD4870 with a Radeon HD4850 , then an Geforce 8800GTS. Still get code 12.
 

tcsenter

Lifer
Sep 7, 2001
18,893
544
126
This is almost always a BIOS bug. Keep pestering BIOSTAR support (politely). Ultimately, I don't expect you'll get anywhere. Might be time for another cheapo motherboard that is actively supported.