DS3 Overclock Troubles

F

Foz2001

[H]ard|Gawd
Joined
Aug 25, 2001
Messages
2,029
So this 'great' board is wanting me to take it and throw it in the lake. Everytime an OC doesn't work it wont boot and I have to reset the cmos. Secondly Im not getting anywhere OCing, when the OC works and seems stable I shut it down and it wont boot up again.

I disabled all the enhancements, overvoltage protection crap etc.
Set FSB to 349X8 (2792)
Memory Divider to 2 (698)
Set PCI-E to 101
vcore to 1.35
ram to +0.3 (because I think stock is 1.8 on the board correct?)


I dont have any aftermarket cooling except a 120mm intake and a 120mm exhaust in an antec sonata. But I figured I'd be able to hit 3.0ghz regardless. What am I doing wrong?

Specs in sig.

Thanks,

Foz
 
RMA it, with the trouble listed as Machine will not retain bios settings on Cold Boot.


We can go thru a lot of stuff, someone replaced the battery and that helped, someone upped the PCI-e voltage and that solved it, temps, etc etc. latest bios, but if you are absolutely sure your heatsink is installed properly and your temps are under control and its doing that, you have the dreaded "cold boot" issue. There is no reliable fix I know of.
 
What bios are you using? I got a rev 3 board with I think the F9 bios. That issue went away after changing to 10. Now it only happens if I set the fsb over 400.
 
I also had the same issue with the F9 bios, after going to F10, no more boot issues.
 
use F7 or F10

fsb 400
pcie 110
2.00x ram
vcore 1.425
vmch +0.3v
vpcie +0.1v
vdimm +0.4v
vfsb +0.2v

see if that works first.
if it does,

either bring pcie down to 105 if youre not comfortable or keep it at 110 (no harm in 110)
vcore, there's a lot of droop involved, so you'll have to play with this to find what load vcore gives stability. luckily, there's easytune5 that lets you change vcore in windows
vmch, this is probably what's causing a lot of the cold boot issues. although it won't completely fix it, it does help to statically assign it a value. For some reason, gigabyte doesn't give +0.0v as a setting. Auto will rise it automatically, and usually once you get into the fsb's you'd want to run, it'd be +0.3v anyway. However, +0.3v does run the chipset extremely toasty so you need to either glue a 50mm fan blowing down or switch to a better heatsink. you may be able to get away with +0.1v if it ends up stable, but a lot of people report 1.55v as required to reduce cold boot symptoms.

vpcie, you can probably leave this to auto, although I never bothered measuring if it keeps it at 1.5v or if it auto-raises it as well. If it does, you might as well set it to +0.1v instead of being afraid it increases it more, since it's really not necessary.

vfsb, again, it might auto-raise on auto. with dual core core2s, you shouldn't need too much vfsb until you get to the higher 400's, so setting to +0.1v after you've found stability might be a-ok.

vdimm, you can use speedfan to look at vcore2. it's actually vdimm. I've found from the few ds3's I've used that there's a lot of variance here, so see what it's setting it to. A lot of people suggest no more than 2.1v without a fan blowing over the modules. However, this also does depend on what ram ic's you have. I didn't look at your sig so I don't know which you have, but for sake of testing, you can give +0.4v, and see what it gives.

Also, make sure you're defining your ram timings (hit ctrl+f1 in bios). Setting to spd gave some pretty erratic behavior. 5-5-5-15 would be fairly conservative. Then work your way down. The ds3 sets subtimings extremely loosely iirc, so once you've found stability, you'll want to fiddle with them quite a bit. Trfc is the most important one. I recall it having a value of "0" which generally sets worst 53. If you don't have d9's, you can probably scale it down to 35, or even 30. If you have d9's, you can try 28, 25, and if they are ok, even 20.
 
You must log in or register to reply here.
Back
Top