then i think both of us were unluckyQuote:
Originally Posted by Hughyhunter
Printable View
then i think both of us were unluckyQuote:
Originally Posted by Hughyhunter
Q750A219, very good batch but need a bit too much voltage for 24/7 above 4ghz.
500*8, 1.28V load / 1.31V idle:
Windows and orthos is showing 4500mhz, it think it is 9 multiplier...
http://img170.imageshack.us/img170/1...4gighe1.th.jpg
4.1ghz, 1.35V load / 1.39V idle:
http://img170.imageshack.us/img170/6...idlepn6.th.jpg
rofl. you think thats alot of voltage? hahaha
Im running 4.1GHz on my Q746A333 (i think, cant remember the last 3 digits off the top of my head) and im using 1.46825 in bios, 1.42-1.43 on idle, 1.41 underload. Now thats too much voltage, 1.39 is fine.
How long have you been running at that vcore. Some have had issues running a high vcore for long periods. NOT ALL, but some.Quote:
Originally Posted by Furiøùs
Wow... that is a bit much. I had an issue with mine. I had it at 450x9 1.375 in bios (prime95 stable for a few hours) for a few months. Then one day decided to do a few high voltage benches and when I went back down to 450mhz with 1.375 it wouldnt even pass orthos 15mins (granted I had never used orthos before) and now I'm not even stable at that frequ with even 1.38 (45mins produced an error) so I'm sticking with 3.6ghz 1.225 in bios 1.20 cpu-z. For the games I play I cant notice a diff with .4ghz, so dont see a reason for 4.05ghz and above. At least until BF3 comes out!:ROTF:Quote:
Originally Posted by Furiøùs
@natech
What are the other settings did you use for your OC? like NB volts, vdimm, divider, etc.? :D
@mrcape
The first E8400 is really a nasty performer. It needs around 1.39v to be stable at 3.8ghz. Batch/FPO Q746A466.
Mine is currently Q746A512. I guess this chip is great for 24/7 but the voltage scales quite high with higher clocks.
I just notice (thanks for the tip) its much easier to work with lower multis with the E8400. i tried 9x467 and 8.5x495 the latter is much easier to work with.
nah, still runs fine at 4GHz at 1.36v underload. good chip.. somewhat.
Yes 8.5x495 is a sweet spot for me as well.Quote:
Originally Posted by fireice2
Really because no e8400 I know can do 3600 with default voltage. Look in the p5n32-e sli plus thread and you will find at least two e8400s, including mine, that need more than 1.300V to get this speed.Quote:
Originally Posted by Ovidiu
This is a rarity though. I would say a majority of E8400s will be stable at 3.6ghz. I do however think it all has to do with the motherboard as far as default voltages go. My mobo cpu voltage in auto is like 1.325 if not higher. I was talking to another guy on here and his mobo default or auto was 1.25, some of the batches cant run 3.6ghz with that low volts. Mine however can run 3.6ghz without error with 1.225v, and I like that spot.Quote:
Originally Posted by panfist
Wondering but not tried whether putting lower multi does require different vcore for same frequencies but with higher multi .Quote:
Originally Posted by fireice2
anyone knows?
from what I've seen around , and surely true for xeons E3110 they can do 3.6 ghz mostly at stock vcore .Quote:
Originally Posted by panfist
my Q746 runs stable orthos at that o/c with even 1.15v load ( although auto settings does put +1.23v for safety I think ... )
I saw benches on reviews with E8400 at stock vcore for such overclock 3.6 ( 400 x 9 )
I think it depends on your luck. I had an E8200 and E8400 which needs around 1.4Vcore to get stable @ 4Ghz (500FSB)
:D Germany, sold by a member of another forum, was untested !!! :p:Quote:
Originally Posted by Dragon heart
lol seems you got some luck of the newbie :ROTF: ;)Quote:
Originally Posted by camouflage
still on air and 23C room temp...seems good to me...:D
5040mhz 1.65vcore 560x9 on water, too bad my mobo is so unstable above 520fsb. :rolleyes:
http://www.hwbot.org/result.do?resultId=702353
Hughy, didnt i say that those high voltage tests would :banana::banana::banana::banana: up the chip? Damn man, really sorry to hear that though.. i said that it would screw the chip up :( Not saying i told you so, but damnit. lol nah, might put her down to 4.0Ghz, now that i hear everyone telling me its too much. still runs great though i give it that..
Another vote for the 8.5 multiplier. Mine is ridiculously better there, requiring significantly less voltage for the same clocks at 8x or 9x.
Yeah... I know! I got greedy and wanted to bench.Quote:
Originally Posted by Furiøùs
I'm going to try the 8.5 multi next... I just think though that the higher bandwidth on the mobo will just be more unstable and stressful on the chipset. :shrug:
I know your pain, i backed it down to 4GHz and now i needed to bump Vcore from 1.425 to like 1.43 something, its the one 1 bump up after 1.425, leaving the chip there from now on. not worth it
Hey guys, first post.. Ive been following this thread along with others, waiting for my account to be processed. Anyhow, I've got an Abit iP35 Pro and E8400 Batch Q750, G.Skill PC2-8500 1066 DDR @ 1080. I've had mixed results with this chip, but I'm having a bit of an issue the last few weeks. I can run orthos for 48+ hrs straight, prime, superpi, everything.. nothing crashes, nothing gives errors, however.. the computer locks up completely (must be reset) when the computer is idle, seems like anywhere between 10mins - 1 1/2hrs. I'm currently running the official v16 bios on this board, my CPUz load vcore is 1.32 at the moment, I've had it all the way up to 1.39 and i still get the same issue with the idle locking, its weird.. stays stable no matter what WHILE its under load.. but once you stop/pause orthos, and leave the computer, or leave it idling all night while not under load, it'll be locked up in the morning.
My temps are ~50c under load or less at 1.32 vCore, ive tried everything, reinstalling xp, my MCH, VTT, ICH all have been bumped up a notch or two, my DDR @ 2.100. (VTT = 1.21, MCH 1.44, ICH 1.32, GTLREF's @ 61% at the mo.), my ram timings are stock (5-5-5-15) for this ram.. now, i did get the computer all the way thru the night idling and several hours the next day when i didn't have everest running in the background (with sensor icons in the systray) and no orthos, realtemp, or cpuz running.. coincidence? or has anyone else had this problem? phew, sorry.. im long winded.. thanks guys, hope im not in the wrong place here :p love your forums
BTW, I'm at 450 x 9. I've tried higher FSB's, and they'd probably be fine, but the idle problem still occurs.. I'm going to run orthos for a few hours now, and stop it before i goto bed with no everest/cpuz/realtemp running and see if it is still live and kicking in the morning..
Mobo : Abit iP35 Pro
GFx : MSI NX8800GTS OC'd Edition
Proc : Intel e8400 Wolfdale 3.0GHz @ 4.050
Mem : G.Skill 4GB (2 x 2GB) PC2-8500 1066
Cooler : Ultra Chilltec Thermoelectric Peltier
PSU : Antec NeoPower Blue 650w
:welcome:Quote:
Originally Posted by resyn
Good to have ya here... :yepp:
First off... Good choice in hardware. The Abit is a great o'cer! Hope it doesn't crash tonight without those things running. If it does forget about what I am going to say first. First I would suggest setting all to stock/default (make sure it's prime stable even with stock voltages) and seeing if it crashes with those programs running or not. If it does than it's not your overclock... if it doesnt there is something about your overclock and those programs running.
Second thing is (if comp crashes tonight or if it crashes when you set all to stock/default) it may be a PSU. I have found in the past that no matter how much you spend on a PSU that sometimes you get a bad one that does some funky stuff. I have changed every part in my rig before with similar problems only to find out that the last component left was the PSU and sure enough that was it. Electricity does funny things sometimes. However I would try all other things before you exchange a PSU. I would even run memtest for hours on you current rig to just make sure you memory is stable. It sounds like it is though with prime/orthos.
:welcome:
Pretty much what Hughyhunter suggested, it sounds like unstable ram to me. Try memtest86 as he said, make it a bootable disk and let it run for a few hours. (i still need to run memtest myself :p:)
Here is all the info I could think of.Quote:
Originally Posted by natech
So all voltages except cpu core voltages are default. I have only rised core voltage. Should I rise something other too?
e8400 batch is Q805A. I really don't remember what the divider is for mem but I had it so that memorys are about 800MHz even under. I really think that memory (yes, my memory sucks, but still) isn't the limiting factor here.
And I use 9x multiplier.
I will do more testing when I get home from work.
Thanks :)
Thank you, I do appreciate it :DQuote:
Originally Posted by Hughyhunter
Well, here we are next morning, I left the system running all night with no programs open (just some firefox windows, which loves to suck down the ram) and it didn't hard lock. So it seems the second time this thing has stayed up through the night is when everest and cpuz werent running (i actually had left realtemp running). I'll do this a few more times, as I'm starting to believe everest has something to do with it. Also, I have booted into memtest and let it run all night with no issues in the last few days. This ram doesn't seem to like the timings tightened, but I haven't messed with em too much in order to eliminate having any further issues.
Also, I have set it back to stock a few times (within the last couple weeks), and the idle hardlock problem continues there as well.
There were a couple of times I noticed when this thing idle-hardlocked, I looked down into the systray at the everest temp icons and noticed the "PWM" temps (according to the little temp icons) got stuck at 172c, and the cpu case temps also stuck at some weirdly high number *but numbers were normal before it locked up. So maybe everest/everest driver glitched, and then hung windows out to dry?