conroe - overclocking

GinG · 30 Jul 2006 at 08:34

Hi All,

I have been trying to get my conroe to overclock just a tiny bit more! However it blue screens anywhere after 2.8 - which i am happy about, would just be nice to be able to hit the 3.0ghz mark.

The blue screen says something like - esq_driver_not_equal or something like that.

Im running a DS3 board with corsair memory. Everything in bios has been kept to stock, running 400 fsb with the memory thingy on 2.00.

Is there anyway of splitting it so the memory doesnt go up aswell?

What volts would i need to change to get to the memory?

Just want to add cant believe for a £130 chip you get almost the same performance once overclocked that the £600+ one

cheers all

GT

GinG · 30 Jul 2006 at 09:00

Sorted it

Managed to get just over the 3.0ghz step!

http://valid.x86-secret.com/show_oc?id=108567

sweeeeet!!

however what is safe tempertarures - i am only running one fan in my antec sonata2 untell i recieve my 120mm fan to stick in the front.

I am reaching temps of 50 - 52 when doing the PI test - is this too hot?!

cheers

smids · 30 Jul 2006 at 12:00

Should be ok temps - what is a dual prime temp though?

Also, sort out those RAM timings!!! 3-6-6-20 - OUCH!

Drop to CAS4 (Tcl or CAS latency) and then try Trcd 5, Trp 5, Tras 15. Those timings must be losing a whole lot of bandwitdh....just so loose. If you need some help with setting up the memory properly, just post back but looking good so far on the clocking front.

GinG · 30 Jul 2006 at 12:11

update - wasnt that great at 3.0ghz kinda broke my xp

if you wouldnt mind helping me on the memory front i would much appreciate it!!

thanks

MTS · 30 Jul 2006 at 12:14

I have pretty much identical settings to you.

http://valid.x86-secret.com/show_oc?id=108600

But in the 3DMark06 HDR/SM3.0 Graphic tests (ie. Canyon Flight and Deep Freeze) Im getting a lot of artifacts, mostly in the latter test. Fancy trying it to see if youre getting the same problem?

smids · 30 Jul 2006 at 12:14

So basically it was completely unstable :rolleyes:

. OK, what vCore were you running...no wait, have you even overclocked before? Are you using auto overclocking or did you just up the FSB to 400mhz leaving everything else on auto?

MTS · 30 Jul 2006 at 12:49

smids said:
Drop to CAS4 (Tcl or CAS latency) and then try Trcd 5, Trp 5, Tras 15. Those timings must be losing a whole lot of bandwitdh....just so loose. If you need some help with setting up the memory properly, just post back but looking good so far on the clocking front.

I tried that (I have the same memory as him by the looks of it) and it wouldnt boot.

This would though:
Left CAS latency as auto then Trcd 5, Trp 5, Tras 12.

http://valid.x86-secret.com/show_oc?id=108607

smids · 30 Jul 2006 at 13:21

Hey, CAS3 is better than CAS4 so if it works on CAS3, then that's just fine!

MTS · 30 Jul 2006 at 14:20

Still doesnt get rid of the artifacts though, even when I go back down to 2.8GHz (400 FSB).

Jokester · 30 Jul 2006 at 14:21

Artifacts are likely caused by you're graphics card.

Jokester

MTS · 30 Jul 2006 at 14:23

Hmm, ok, thanks. Thats strange though because I havent even messed with that.

Its a Sapphire 1900xt.

I suppose I better go driver hunting. See if we can fix that.