fatal1ty fp-in9 sli

[Nickg]

i would keep the cpu the same and go for 375fsb and then try 400! if it doesnt work, try 1.45 on the cpu. 1.5 should be safe ish providing you have decen cooling? (i have arctic freezer pro 7 on mine atm). what cpu btw?

id be interested to see how you get on.

[Moonwizard]

I got a e6600 and I gave up at 350... I tried to go unlinked and have my ram at 800 but that gave me errors in super-pi. I get the feeling that I've stumbled onto a bad cpu. So now I am back at stock. Or might just be the mobo and I've not gotten the hung of overclooking with C2D.

I just redid some of my hose for my watercooling. I had kinks in it and it seems to have done about 1 degree for the cpu in idle. strange thing I noticed is that my system temp are higher then my cpu temp atleast with Abit EQ. Can it be true? Hm, one more thing. I've disabled all in the CPU feature stuff. Except thermal control. Is there something else I should disable and then have a go?

Oh, it did some wonder to have a 80mm fan on the NB sink and it is hanging off to one side so it actually cools down the PWM as well.

I can get a pic for you guys as soon as my camera batt are charged.

[BUFF]

I get the feeling that I've stumbled onto a bad cpu. :

the guys on XS reckon that the latest batches of C2D aren't great overclockers.
They surmise that either all the best process is being used for quads or that Intel have tweaked the process for yield & lost some of the headroom.

[Moonwizard]

Here is how I solved the warm NB sink.



It might be so. That is my usual luck. Oh well.

After my p42.4bghz that did 3,24ghz@stock voltage I've had bad clockers. Oh well. I'll wait and see what this bios solution can do and I am probably going to get better w/c too before I start playing more. I'm happy with it as it's. Not that you notice those 2 fps more if you got a highend gfx.

[danroyle]

put on bios 11 havent done much with it yet but i keep getting some warning beep before it starts upits 3 lots of 2 beeps in a siren style if you get what i mean


anyone

[Nickg]

yea i get the same every time i softrestart the machine. its just the CPU siren fan i think which goes OFF/ON while the power is still on hence the siren?

but i now have a new stable overclock! 387.5Mhz FSB!

only problem is the voltages i have to give it!

vcore 1.4
VTT 1.5
NB 1.5

i went into the bios and dropped each voltage by a single increment - rebooted and tested to see which would be stable.. answer i cant drop any one of those voltages @ 387.5fsb otherwise superpi fails within 2 1m tests.

with them as per above i can dual orthos and superpi stable, so im not @ 3.1Ghz (8x 387.5mhz) with a superpi time of 18.45 seconds!

can anyone else get a stable fsb any higher than this?

[danroyle]

yea i get the same every time i softrestart the machine. its just the CPU siren fan i think which goes OFF/ON while the power is still on hence the siren?

but i now have a new stable overclock! 387.5Mhz FSB!

only problem is the voltages i have to give it!

vcore 1.4
VTT 1.5
NB 1.5

i went into the bios and dropped each voltage by a single increment - rebooted and tested to see which would be stable.. answer i cant drop any one of those voltages @ 387.5fsb otherwise superpi fails within 2 1m tests.

with them as per above i can dual orthos and superpi stable, so im not @ 3.1Ghz (8x 387.5mhz) with a superpi time of 18.45 seconds!

can anyone else get a stable fsb any higher than this?

that a lot of increase to get more fsb out of it at
vcore 1.3
and all other voltrs stock i get 350 fsb easy and am currently trying to increase it

seems alot of extra volt to put through for little increase mate

[Nickg]

yea at 2.92 ghz (365 fsb) i can run @ stock or undervolt the vcore and run the nb @ 1.39

19.5seconds SuperPi 1M

3.0Ghz
8x 375
Vcore 1.375
vtt 1.39
nb 1.45

18.9 SUperPi 1M

3.1ghz
8x387.5mhz
vcore 1.40
vtt 1.5
nb 1.5

18.5 SuperPi 1M


my ram is @ 833mhz 4-3-3-12 t2 @ 2.1v (ballistix 5300 2gb kit) this is 100% comfortable and will do higher/tighter

edit: i have lowered the LDT tried SYNC and UNSYNc modes,

Vdroop;

1.4 in bios = 1.368 in CPUz idle, underload drops to 1.352 and to 1.344 flickering occasionally.

the above scores are orthos dual core stable for 1hour +, with SuperPi32m winamp, and various other processes running.

[Azurael]

Sorry; did somebody say there was something wrong with this board?

www . ndt-uk . net / misc / images / computer / hundredpercent.jpg

(You'll have to remove the spaces since this forum won't allow me to post an image until I've got 5 posts, apparently. Bit stupid but oh well.)

Orthos small FFT priority 9 stable for several hours, but a bit hot with the boxed cooler and a desk fan pointed at the side of the machine for my liking - maybe after my waterblock turns up. Memory is PC6400 at cas4-4-4-10 1T. 2MB C2Ds suck for SuperPi 1M A 4MB part could probably get that time at 5-600MHz less. Lucky real world performance gaps aren't half as bad

This is with V11. V12 wouldn't even boot at my day to day running speed (350x9) after playing with any clock speed settings beyond the initial setup.
I didn't have the problems many were experiencing with the shipping V10 though, so YMMV.

My board runs at 350 just fine with stock NB voltage too. Just thought I'd post here because I was fed up with people slagging off Abit and threatening to RMA just because they haven't quite perfected the BIOS on this board yet. I've had far less stable boards out of the box from much larger manufacturers like EPoX, DFI and Asus (Including 1 EPoX 754 board, an 8KDA3J that never ran stable because of it's awful VRM, a DFI Infinity nF2 which blew huge traces on the board running toward the back panel and killed poor old PS2 keyboard.) It's not like any manufacturer is immune to these problems.

One thing I would like in the BIOS on this board is user selectable FSB strap, since I really can't be bothered to take the CPU out of my system AGAIN to do a BSEL mod on it - I'd like to see where I can go with a different strap and multi.

[Nickg]

hmm yes but can you get above 350 and can you get over 400FSB?

the thing is it may not specifically be an OC board, but it shouldnt perform so far under the level the competition is obtaining. the Asus P5N-E is getting a lot higher FSb with no worries...

[Azurael]

The P5N-E also has inadequate stock cooling, bad VRM circuitry by comparison and atrocious Vdroop (a related problem, I should imagine) and thus probably wouldn't run my E4300 at that speed without >1.6v, which I wouldn't be willing to do.

It's early days yet. Wait before complaining. These new BIOSses are already a huge improvement on the shipping release.

[jimborae]

Just flashed to bios 11 and there's definitely a slight improvement, 450 fsb is now bootable & stable for me. Previously the highest I could boot stable was 438fsb . Still a long way off 500fsb stable which is what I'm hoping for from this board but at least it's a step in the right direction.

Keep going Abit

[Azurael]

hmm yes but can you get above 350 and can you get over 400FSB?

That doesn't make sense... Isn't 400 over 350?

Anyway, I've never tried dropping the multi on my 4300 and over 3.6GHz isn't likely to happen when I've got heat problems at that speed so I'll see what I can get out of it now. Remember than non BSEL modded E4300s run into an FSB wall at around 400 anyway on a lot of boards though!

[BUFF]

the thing is it may not specifically be an OC board, but it shouldnt perform so far under the level the competition is obtaining. the Asus P5N-E is getting a lot higher FSb with no worries...

Having spent some time on the MSI forum their boards have pretty much similar problems overall.
& the Asus definitely isn't perfect & most people running 500fsb are feeding the nb 1.596V (the BIOS jumps from 1.39 to that - weird figures)

Not to mention that there is a definite suspicion that recent C2Ds aren't clocking as well as earlier ones.

[gilgamesh]

Having spent some time on the MSI forum their boards have pretty much similar problems overall.
& the Asus definitely isn't perfect & most people running 500fsb are feeding the nb 1.596V (the BIOS jumps from 1.39 to that - weird figures)

Not to mention that there is a definite suspicion that recent C2Ds aren't clocking as well as earlier ones.

They arent m8
week 33 is utter pants, i have a week 33 6400 and it doesn ot clock as well as my week 24 6600 (and week 24 is a really rubbish week at that)

THe best weeks are weeks 27 to 31

gilgamesh

[jimborae]

Has anybody noticed an increase in temps with bios 11? Both Core Temp and Abit's monitering tool are showing an increase of around 10c on my board using the new bios.