Or maybe it is the CPU, not the bios, causing the hard locks. After all, 2 cores were locked for a reason, one of them might have been unstable cores :shrug:Quote:
Originally Posted by shadow_419
Printable View
Or maybe it is the CPU, not the bios, causing the hard locks. After all, 2 cores were locked for a reason, one of them might have been unstable cores :shrug:Quote:
Originally Posted by shadow_419
This is true it could be the cpu, but just about everyone that's posted x2 550 unlocked has the same problem with this board. Some of the posters in the x2 550 thread even showed the same chip unlocked on other boards running fine.
Anybody running 8GB of those Ballistix Tracer DDR3 PC3-10600 on their gd70?
Got mines yesterday and would like to get a rough idea of what to expect when i'll get a gd70 next week when i return from that rock festival week-end.
If you can not find the animals then look for the 1600 AMD edition, same IC type just slightly different BIN...they do pretty much the same clocks.
I am trying to come up with a 6-6-6-24 1600 kit not using Hypers, it may have to go to 7-6-6-24 though but they will feature Blade HS and be branded for AMD use.
more soon
That would be awesome! Love the lower profile yet stylish Blade HS.Quote:
Originally Posted by Tony
Aye looking forward to these if they hit the UK in time for my new build.Quote:
Originally Posted by Tony
For anyone still having issues with 550 unlock stability, check out the new 1.51 BIOS posted by Toppc in this thread. :up:
I haven't tried it yet, but may give it a go tonight..
EDIT: Works great :)
http://www.xtremesystems.org/forums/...1&d=1247870515
Finally my 4th core from my X3 720BE is now stable..!!
Kudos to the person who made the 1.51B BIOS!!!
Now gonna see how far this chip can go...
http://i23.photobucket.com/albums/b3...4/Untitled.jpg
Three hours blend stable at stock clocks and volts. Next up how low can she go.
http://img21.imageshack.us/img21/8049/x4b50test2.jpg
have any of the new BIOSes released fixed OC stability? I'm on 1.3 and I'm back at stock speeds because of random BSODs that I couldn't trace down to anything :shrug: :(
I've never had any overclock instability with 1.3 or the 1.4betas. I haven't tried any over clocking with this bios yet but I'll report back.
Just got the gd70 and the 720 unlocks with the new 1.51b bios...am now at stock...and have the OCZ 1600 kit...any help to OC would be great.
Ok am unable to boot with anything over 1066 on the ram...any help????
EDIT: now its at 1333, but with very low timings....someone please help..I have installed the ram in slots closest to the cpu.
9 hours blend completed :hehe:
http://img36.imageshack.us/img36/923...d4core3000.jpg
Leave your HTLink and NB Frequency at auto (HT1600/NB2000) for now and give it a shot.Quote:
Originally Posted by mav2000
Seems some people are having issues with HTLink pushed to 2000 on this bios. Wont boot and stuck at FF. I had the same issues running the new bios off the bat with my usual settings and its currently fine with HT1600/NB2000 with 4 cores overclocked to 3.4ghz on my 720BE on low speed air.
I will start to tweak settings one by one to isolate the issue.
Thanks...did just that and am able to now boot and run prime at 1333 Mhz 6-6-6. Seems to be stable. Now to the next level...anyway what do u use to check temps with the cores unlocked?? Am not able to get a temp reading out of any program..
mav2000, try increasing the cpu-nb vid to at least 1.25v
Ok will try that and report back...
Hey guys,
Just grabbed myself one of these boards and a phenom X4 955 to play around with and had a quick question - hopefully not too noobish, but ive been trying to clear it up in my head before i push voltages etc.
What is the difference between CPU VDDC and CPU VID? Now im guessing that CPU VID is just vcore, not so clear on VDDC. Now, I noticed VDDC in overdrive, but in the bios does this relate to CPU VDD? I just ask because after increasing CPU-VID in bios a couple of notches, overdrive reads it as CPU VDDC increasing, where as everest reads it as vcore increasing.
Alternatively if anyone can link me to some good voltage/bios guides on this board i'd be more than happy to do a bit of reading! :)
cpu vddc is an offset applied to cpu vid, default setting is cpu vddc = cpu vid but you can change that in bios (it's called cpu voltage)
Ok upped the voltage on cpu nb to 1.25 loads and gets to the windows start and bsods. Any help, going higher to 1.26 on cpu nb does not help. Do I need to go lower?
Thanks mate,Quote:
Originally Posted by beta
just to make sure, am i right in thinking that the CPU vddc and CPU VID are one and the same voltage? (i.e equivelent to vcore) Its just u are effectively adjusting the CPU VID which then u offset +/- voltage via vddc? hope that makes sense.
Is this the same with the CPU-NB VDD and CPU-NB VID?
try increasing it one step a time, anything below 1.425v is considered safeQuote:
Originally Posted by mav2000
cpu vddc = cpu vid + offsetQuote:
Originally Posted by MikeMK
By default the offset is zero, that's why their values match.
yep, it's the same with cpu-nbQuote:
Is this the same with the CPU-NB VDD and CPU-NB VID?
Ok, will try higher then, thanks. By the eay as far as vddc is concerned why do they have this extra setting? Is it oc over 1.55?
EDIT: went all the way to 1.35 but no go....let me try with 3 cores to see if thats the issue.
EDIT: Nope it has nothing to do with unlocked cores...so its something else...I am using 7-7-7-24-30 as settings and am keeping the ram at 1.66, still no luck...I am sure I am missing something but dont know what..
Brilliant, thats great... thanks for clearing that up m8... had me a little confused for a second there!Quote:
Originally Posted by beta