• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

***The Official Conroe Overclocking Thread ***

The link is removed. Now I have this another strange problem. I went to disk defragment but when it had analyzed the disk my computer freezed. I couldn't move the mouse or use the keyboard. So I restarted. Same problem again this time it was running on the background while I was using Motzilla. This was with 8x400 so I thought maybe its the fsb. So I changed to 9x356 and now system doesn't freeze but the program freezed. I'm runninh F8i bios could that be the problem?I can't really chance the bios because this is the only one I've tried that works with my x-fi. Both 9x356 and 8x400 are orthos 12h stable.
Update: The 9x356 seems to also freeze the whole system. I'm really starting to think that this board was a mistake. A really bad one. I tried the stock settings with no help still the same problem.
EDIT:I'm not sure if I can fit a fan directly above the heatsink because the tunic tower is so huge. The heatsink doesn't seem that hot. It's slightly hotter than my finger but it's far from burning it.
 
Last edited:
My first serious overclock!

With 4ghz I can boot into windows and run superpi but i think thats probably a bit much for it to take, so ive decided to run it at 3.6ghz as shown in the picture :D
Ran Orthos on Priority 9
stress31.PNG


Any thoughts ?

I know these cpus clock very well, sorta paranoid about running it this fast, after all its 1.2ghz over default! hehe

Edit-
Pic when its onload here
http://www.felucca.co.uk/trox/stress2.PNG

Ive actually just upped the fsb by 1 so it sits at 3601.5Mhz hehe ;) for all a number makes...
http://valid.x86-secret.com/show_oc?id=148671
 
Last edited:
For 3.6ghz its around 1.475vcore and for 4ghz its a little over 1.5v, i cant remember now :o

Only wanted 3.6ghz stable, probably can do more but im pretty happy with it :)
 
easyrider said:
Have you read the post?
He can only get gaming stable at 3.6ghz.

Anyone with a P5B at 500 FSB with a E6600 is talking BS!

Devious was a screen shot,
Not stable and as he has said himself he could only get the P5B stable at 3.6ghz
Click to expand...

500+ FSB prime stable on the P5B is really not a problem. However you NEED a default multi of 8 or below to achieve it. Even then you're pushing it as it would require a 6400 capable of 4ghz stable. (Not a problem for phase, but asuming you mean air/water?)
Dropping the default multi on 965/975 "overclocks" the NBCC (effective core clock of the NB).
E6600 = 9* stock multi. gives a CPU speed of 4.5ghz, with the NB running at 500mhz.
Drop the multi to 8 at the same 500 mhz and you get an effective NB speed of 562.
562 FSB is pushing it a little even for a P5B stability wise. Drop the multi to 7 and the NB's running effectively 600+mhz.
For the Extreme Edition chips, there's no effect on the NBCC of changing the multipler so 500+ fsb at a sensible speed should be possible.

Can run 537 8 hours Orthos stable with 6300 (under water) proving the boards CAN hack it if the CPU can keep up. Pi 32m @ 590 fsb (phase cooled though). Find a 6400 capable of 4ghz stable and you'd see 500FSB from a P5B.

High vMCH isn't required, those running 1.85+ really don't need that much voltage. ~ 1.5 is plenty extra only add's more heat. There will be exceptions to this however, but in general 1.5 is enough for 500-550 fsb clocks.
 
Woohooo, i've made one of my cores going AWOL with 1.475+V 24/7 volts. (Under 50C for all that time)

Errors at stock with 1.45V :o takes hours for this error to come up, so RMA is gonna be interesting.


Could run it in Single Core mode, 1st core gets up to 3.6ghz at 1.45V lol!

But I want both of my cores.

So either 1.475+V into 65nm = not good or I had a weak CPU in the first place. :(
 
I just tested something the other week, lowered my vcore down to 1.3v @ 3600mhz and it passed 9 hours of Orthos on small FTTs...

I set it to blend it would fail after a 20 or so mins, upped the vcore to 1.35v (real) and it just completed a 12 hour orthos blend priority 9, i stopped it :)

The week before i had to use 1.475v (1.43real) which is whats in my screens above.

Well happy :)

3.7ghz @ 1.38v stable
 
Concorde Rules said:
Woohooo, i've made one of my cores going AWOL with 1.475+V 24/7 volts. (Under 50C for all that time)

Errors at stock with 1.45V :o takes hours for this error to come up, so RMA is gonna be interesting.


Could run it in Single Core mode, 1st core gets up to 3.6ghz at 1.45V lol!

But I want both of my cores.

So either 1.475+V into 65nm = not good or I had a weak CPU in the first place. :(
Click to expand...


What are you getting errors in?
 
Devious said:
So you have both cores when runing stock volts ? Should be an interesting RMA like you say...
Click to expand...
No, the volts have killed that core. It errors no matter what volts/clocks it's given. It might be hard to explain, and only errors after a good long time.
 
Are you sure its the CPU? It could be the NB thats overheating. A guy on another forum was having problems with an E6600 and Abit MAX that was causing similar problems and found it to be the NB temps that went too high after a long time priming.
 
You must log in or register to reply here.
Back
Top Bottom