Sign in with
Sign up | Sign in
Your question

Is Gigabyte core unlocker now disabled?

Tags:
  • Chipsets
  • Unlock
  • Processors
  • Gigabyte
  • Motherboards
Last response: in Rooting, Jailbreaking & Unlocking
Share
December 8, 2011 2:26:10 AM

I'm running an AMD Phenom II X2 555 BE processor on a Gigabyte GMA-880-UD2h Revision 2.0 board. This is my second GMA-880-UD2H Rev 2.0 board. On the first board, I was able to unlock all 4 cores on my 555 BE processor, stable, no problems. The first board however, after about 4 months, ended up with a bad DIMM slot. I RMA'd it to Gigabyte and after the second repair attempt, they just sent me a new board altogether. Exactly the same model number and revision number, but a new board because the serial # was different. Since I've gotten the new board, my 555BE will NOT unlock whatsoever. The additional cores don't even appear in the BIOS when I try to use Core Unlocker. We're talking the BIOS only "sees" 2 cores.

This makes no sense to me because I would assume that core unlocker would at least see the other 2 cores (for a total of 4) even if they were faulty. I know they aren't faulty because that processor has been successfully unlocked before. I've tried upgrading AND downgrading the BIOS to no avail. The bios only ever sees 2 cores.

Does anyone know of, I dunno, maybe a jumper setting I need to change? Or does anyone have a copy of the BIOS for this board that hasn't come from the Gigabtye website recently? I was wondering if maybe Gigabyte quietly disabled the feature, even though it still shows up in the bios menu? (I read a thread on Gigabyte's website that others may have been having trouble with this too. Most of the replies that people are getting from gigabyte are along the lines of "your processor can't be unlocked because it's faulty...") Do I need to change another setting in the bios for it to recognize extra cores beyond just using Core unlocker? Is there another way to unlock cores on this processor?

Am I missing something here?
THANKS in advance.

More about : gigabyte core unlocker disabled

a c 435 V Motherboard
December 8, 2011 11:47:31 AM

Did you write down the bios file number your old board was running with? Could be the new board has a newer bios file that has changed one or two settings so your 555 won't unlock. I would check the bios settings carefully; you may need to go back to an older bios file to get your cpu unlocked again.
m
0
l
a b V Motherboard
December 8, 2011 12:09:25 PM

Is your GB a DualBIOS motherboard ??

Verify that the primary and secondary BIOS are the same version -- if not, it sometimes runs wacky.

Otherwise, I've never run into a situation where a chip on the same OEM version will unlock on one board but not another, but I s'pose it can happen. GB is normally quite good at unlocking.

m
0
l
Related resources
December 8, 2011 12:19:04 PM

Unfortunately, I did not. I actually never expected them to send me a new board so I didn't even think about doing that. Should I up the CPU voltages slightly? Think that would make the extra cores visible?

Or, better yet, any idea where I can get an older bios file than what is available on the Gigabyte website?

I really don't want to get a new board...

m
0
l
December 8, 2011 12:28:34 PM

Wisecracker said:
Is your GB a DualBIOS motherboard ??

Verify that the primary and secondary BIOS are the same version -- if not, it sometimes runs wacky.

Otherwise, I've never run into a situation where a chip on the same OEM version will unlock on one board but not another, but I s'pose it can happen. GB is normally quite good at unlocking.


I forgot ALL about the dual bios thing. That could be the issue. Unfortunately, I don't know how to check that. I only ever see the one Bios version.

Any ideas or a link on how to utilize the dual bios thing would be extremely helpful.

THANKS.
m
0
l
December 9, 2011 2:18:22 AM

Wisecracker said:
Updating Backup BIOS to same revision as Main BIOS

I didn't read the manual, either :lol:  and until I found this I couldn't unlock my sweet 555BE on my GA-990FXA-UD3!


Okay, I was able to get my primary and back up BIOS to match. I've downgraded both to a previous version which, on my last board, worked at unlocking the processor. However, my BIOS still does not see the other two cores.

Should I maybe remove the processor and then re-seat it? Would that accomplish anything other than wasting more thermal paste? Is there a jumper setting I need to change?
m
0
l
a b V Motherboard
December 9, 2011 10:55:09 AM

What 'unlocker' setting are you using? Auto or Per Core?

And from time-to-time, 'crap' simply piles up and corrupts your BIOS even though you 're-flash' -- unless you clear the CMOS as part of the flashing process.

If you did not clear the CMOS as part of your 'flash' you should make note of your current BIOS settings, and then clear your CMOS.

You may then 'load optimized defaults' and re-install your previous BIOS settings -- and give the unlocker a try.


edit --- re-setting your CPU won't help unless your feel your temps are getting wacky and effecting performance ....

m
0
l
December 9, 2011 4:57:04 PM

Wisecracker said:
What 'unlocker' setting are you using? Auto or Per Core?

And from time-to-time, 'crap' simply piles up and corrupts your BIOS even though you 're-flash' -- unless you clear the CMOS as part of the flashing process.

If you did not clear the CMOS as part of your 'flash' you should make note of your current BIOS settings, and then clear your CMOS.

You may then 'load optimized defaults' and re-install your previous BIOS settings -- and give the unlocker a try.


edit --- re-setting your CPU won't help unless your feel your temps are getting wacky and effecting performance ....


I've tried using the AutoUnlock feature set on both auto and manual. No luck.

I guess I may need to pop the battery out and clear the CMOS, although I've been (supposedly) clearing the DMI data every time I've flashed the bios, which I thought took care of that.

I didn't think re-seating the CPU would help, just thought I'd ask. Helps me to know that someone agrees with me.

Supposedly there is a 6E bios update coming soon. Hopefully that will fix it...
m
0
l
Tom’s guide in the world
  • Germany
  • France
  • Italy
  • Ireland
  • UK
Follow Tom’s guide
Subscribe to our newsletter
  • add to twitter
  • add to facebook
  • ajouter un flux RSS