Wow temperatures are rising in here! :p: :D
I am sure there was just a language/translation problem, no need to take it personally guys, we are all here doing the same thing. :toast:
Printable View
Wow temperatures are rising in here! :p: :D
I am sure there was just a language/translation problem, no need to take it personally guys, we are all here doing the same thing. :toast:
Merc/09.891s/P5K Deluxe/Core 2 e8400 @ 4682MHz/5-5-5-11 2T (624MHz)/Water/02-03-08
http://img216.imageshack.us/img216/3...9891he5.th.jpg
WOOT!! In the 9 second bracket.
1.60 set in BIOS
nice going it seems the e8400/8500 likes the p5k motherboard as cordovader who posted earlier also had good results , whats the fpo/batch code of your chip
Well, I went back to the store and exchanged my CPU for another one, Q746A503 is my # and it seems to be much better...
4014mhz @ 1.27v VS 4014mhz @ 1.44v running orthos on it now and it has made it past the 10 minute mark. I'll be curious to see where I can get with this chip.
I want to run it around the 4ghz mark 24/7 so this seems to be much more suitable.
My 8400 is:
Q746A377
1.225v
Pack date 1/4/08
I couldn't get her to 560. Maybe 540. I'll post some settings later have to watch the ball game.
fRzzy/09.578s/Gigabyte P35-DS3P/Intel Core 2 Duo E8400 @ 4860MHz/Crucial Ballistix Tracer 667 @ 540MHz 4-4-4-12 2T/AirCooled by TR IFX-14/02-04-08
http://img517.imageshack.us/img517/3...sultmz1.th.png
People are saying ignore coretemps and look at CPU temp, what program can be used? (Most accurate?)
Here is my 1meg Pi at 4860mhz.:D
@ flesheatinvirus
Nice clocks there. Your RAM is doing some pretty good clocks there,congrats !
@frzzy and flesheatinvirus
I don't understand how I could get a 09.891s time at 4682MHz and you guys are getting just 09.578s at an incredible 4860MHz. You both should be in the 8 second bracket i would think. What version of Spi are you running? I have noticed that I have to run Pi twice to get a good number. The first is always higher. I have no idea why. Incredible clocks BTW guys, very well done.
It's just normal on intels. :)
A quick test with my E8400:
http://www.abload.de/img/1mfzjs.jpg
I guess I have to up my volts. :shrug: Great job guys. :up: I can't believe we can get in the 9 seconds on water. Never thought i'd see it from an X86. An amazing chip for sure.
Maxwolfie: CPUID Hardware Monitor and SpeedFan are two free programs which show the cpu temp in Windows, although SpeedFan seems a bit buggy with the Wolfdales.
I was wondering why I can't break the 10 sec. barrier in SuperPi1M. I have the same or better settings that some of the others, but 10.2 sec is the best I can do? More FSB?? Some have broke 10 sec. with 502FSB with the same ram timings as mine? Is it my crummy DDR2-667 ram or do I need water cooling??
wow, a lot of 1.6v out here lol... :( i hope our suicide runs dont massacre our procs, mobos and mems lol. The max I did was 1.55v (1.536v vdroop) for my 4.5ghz run.
So just so we are all on the same page. It is confirmed that the core temps are not working... Mine is idling at 34 C and core 1 says 60C and core 2 says 43. Also the two cores dont flucuate much. Ive tried reseating my water block 4 times. Changed thermal paste twice. And even flipped the water block around. Made no differnece at all and did not help lower the gap between the two core temps. So I am pretty sure that these are not worth looking at, which it seems the rest of this thread is in agreement with. I just wanted to make sure.
I've started trying to overclock this with the 680i and am having a hell of a time. It seems I have a fsb hole. At 1800 it wont post no matter the multiplier. At 1900 I can run orthos, but seems to be freezing after 2-8 minutes. I am going to do more tests, but this is as far as I got with day 1. Anyone else have any luck with the 680i.
For those concerned with high voltages and degredation here is a link to the E8000 series data sheet. Section 2 covers electrical specifications. ftp://download.intel.com/design/proc...s/31873201.pdf
There's also a supplementary document / spec update with a list of errata.
Many of the errors mention workarounds that can be addressed in updates to bioses. Others will be addressed in a new stepping.
Pain in the butt for board and bios engineers, but would be very grateful if they did the fixes that they can.
Well the microcode update would have to be added into the bios and new bios prepared and released no? I do remember there being a bunch of issues with 65nm C2D and I think there was a microcode update for those.
If you look at the list of errata there are a lot of "bios workaround" mentions. For example the most recent addition - AW51 from 02/01/2008.