Yea...sux u had to be the guinea pig...but someone had to try it
Doesn't look like anything spectacular...lets hope Abit's NF2 is
Yea...sux u had to be the guinea pig...but someone had to try it
Doesn't look like anything spectacular...lets hope Abit's NF2 is
E8600. EP45-UD3P. 500FSB 24/7. Still WinXP. Heatware
lol, that's why I'm not moanin and groanin too much, picked the board 'cuz it was new and untried.
ABIT listens to the peeps, looking forward to hearing good stuffs about the NF2
The plural of "anecdote" is not "data."
I just got my KD7E today and so far it takes my 1700+Tbred to 9x205fsb @ 2.0v with fastest ram settings.
How high is it safe to take the vcore on air with the Tbreds?
As high as your cooling can keep up with. Hows your temps @ 2v and what cooling are you using on the CPU?
E8600. EP45-UD3P. 500FSB 24/7. Still WinXP. Heatware
I'm using a Volcano9, was too lazy to put my Alpha8045 back on.
It was at 59c at 2.0v and 59c at 2.2v (doors open heat off) and it didn't help.
If going from 2v to 2.2v doesn't help your OC, then there's no point in going higher. 2v is prolly the highest that your cooling will keep it cool enough & allow any more OC headroom. Good luck
E8600. EP45-UD3P. 500FSB 24/7. Still WinXP. Heatware
Thanks N8!
I figured i hit the limit when 2.2 did no good.My Tbred is kinda a junker too, can't get it over 1900mhz no matter what i try.
Just wanted to report that I've had the board for a while and it has data corruption issues above 200 FSB.
3dmark will eventually abort with corrupted textures at as low as 203 FSB and at as low as 204 I've lost the O/S.
Overall mine's a fine board, kicked right up to 208 FSB without blinking, but not an xtreme board
The plural of "anecdote" is not "data."
I did a few runs of 3DMark at 211fsb@2.0v no HDD corruption yet. But at 211fsb@2.025v or 212fsb@2.0v it gives me reg errors that are fixed on reboot.
Last edited by SlimHitman; 12-06-2002 at 01:15 PM.
*sniff* - Even after some heavy burnin at 208, booting at 209 FSB still gives me the dreaded HD recal click at or shortly after the Win2k login screen. Disk corrupt at reboot every time.
Jealous of that 211 FSB SlimHitman? You bet I am
The plural of "anecdote" is not "data."
My first Tbred RIRGA 0233 would only do 206fsb.My AUIGA 0245 does the 211fsb.From what i've read the newer the better on the Tbreds.
Progress here - small, but progress.
After a 12 hour memtest86 continous burnin at 211, I can now boot without apparent corruption at 209.
Maybe this samsung 256 ctl stick just needs some conditioning.
Guess it's not time to pass this one on to the kids, not yet!
The plural of "anecdote" is not "data."
I lowered my multi to 9 and relaxed most of the mem timings and was able to finish a couple 3DMark runs at 215.Then it got late and i got greedy and went straight to 220fsb...lol.So i ended up going to bed with a corrupted HDD that wouldn't boot.With the lowered timings and multi i lost about 500pts too.
Got my KD7-E yesterday, and my Win2k "got lost" at 1943 mhz (185x10.5), didnt burn in anything. My win2k installation was kinda FUBAR anyways. 1.95v on the CPU, 2.95 on the RAM. Gonna burn her in today. Temps are great, like 11-16c on CPU and about the same on the mobo. Its like -10 celsius here now gotta love that for aircooling. But i dont like sitting in the cold tweaking it though, as ill catch a cold soon :P
Intel i7 3930K C2 @ 4700 mhz (100 x 47) 1.4v
EK Supremacy/EK XTC 420+280/EK DCP4.0/PrimoChill 1/2 ID 3/4 OD
Asus Rampage IV EXTREME
16 GB G.Skill RipjawsZ @ 2400 CL10-12-11-1T
Zotac GTX670
Antec Quattro 850W
Intel 330 180 GB + Micron C400 128 GB
LD Cooling PC-V7 B/R
Bookmarks