• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Code 12 on evga 680i SLi

N

Namrepus221

n00b
Joined
May 23, 2008
Messages
14
OK my brother just built a new PC and he's using an evga 680i SLi mobo. Intel Quad Core chipset (don't know the exact kind off by hand)

Well his network adaptors are showing up as "Code 12" which of course means "not enough resources"

We don't know why this is causing this. I've heard that it's possibly the ACPI setting (which is set to off on my brothers mobo). But they are already disabled in the BIOS.

He's running XP Professional if that's any consolation.

Any help would be greatly appreciated, and if you need any more information. Please ask and I will try my best to get it from him.
 
have you updated the bios to the latest revision? i think it was P23 and after that fixed alot of the corruption problems... i believe the most recent is p32 so..try and update the bios and see what happens. the 780i used to do the same thing with the asus D2X(code 12) and was fixed with a bios update..:)http://www.evga.com/forums/tm.asp?m=36748
 
if possible go into your bios and turn off unused devices like serial port, parallel port, firewire, spare nic, if the mobo has 2 different sets of sata ports then turn off one set etc, turn off a lot of stuff that is not gunna be used and that will free up irq's and resources, whether that will fix your problem i dont know, it could be more likely a bios issue especially when reading the second post from savidge, but you can also try turning shit off in the bios and see if that helps.
 
Well we got it fixed.

EVGA said there was an issue with the chipset drivers. Which was then updated and stuff started working, we updated the BIOS as well to make sure.

Thanks for all your help guys.
 
You must log in or register to reply here.
Back
Top