it is called a nforce chipset, lol
Weird E8400+790i overclocking stuff...
Ok so I'm new to this forum and wondering if you veterans might have some insight into this confusion...
So I've been messing with my E8400 overclock in my EVGA 790i board. I had it running at 4.05Ghz with a 2Gb Patriot Viper DDR3 EPP RAM kit that was *supposed* to run at 2000Mhz but never could. The best I could do was get it to 1700, and I tried everything I could fathom, from switching to the "black" RAM slots to disabling EPP. So, I finally went out and got some Corsair Dominator DDR3, rated for 1600 Mhz with 8-8-8-24 timings. It's actually 2 sticks from an i7 6Gb kit, which I found out from Corsair would run fine in my Core 2 Duo system. So effectively I'm running 4Gb at 1600 Mhz with stock timings, and stock 1.65v.
Anyway, I installed it and went back to all stock settings and decided to see what my overclock headroom would be with the new RAM. I brought my FSB overclock to 1600 Mhz with no problems, with my FSB/Memory unlinked. as soon as I would bring the FSB past 1600 though, it would automatically drop my RAM clock to 1518 or some strange number, despite it being manually set to 1600. If I tried to boot with the FSB anywhere past the 1600, I'd get a BSOD. I tried to slightly overclock the RAM along with the FSB, and even tried linked/synced up to 1620, but couldn't get it stable. I found it particularly strange because I'd had my FSB way past 1700 with my Patriot RAM, and I would think the new Dominator stuff, with 2 extra gigs and lighter timings, wouldn't stand in the way of getting back to where I was.
Finally, I started tinkering with my FSB speed and noticed that every setting between 1600 and 1739 would automatically slow down my RAM clock, but as soon as the FSB was at 1740 my RAM went back to it's 1600 Mhz setting. Is this some math equation I don't get? Does the RAM clock normally get changed when the FSB is operating within a certain range?
So... onto the weirdness with the voltage settings... everything had been on stock voltage up to the 1740 Mhz (that's 3.91 Ghz for the E8400). I booted fine but was failing some Prime95 tests on Core 0, so I upped the voltage settings one click and went back to Prime95, and it was fine for over 12 tests. I continued this up to my current 1780 Mhz (4.0 Ghz) But, I've been noticing that for some reason, this BIOS doesn't actually set the voltage where you tell it to. I currently have the voltage setting in the BIOS at 1.412v, it shows an actual 1.36v being used in the BIOS system monitor, and CPU-Z in windows has it totally different- 1.38v during idle, and for some reason it drops to 1.35v during stress testing with Prime 95... ??? Oh, and idle temps are 53c in BIOS, 67c during Prime95 (via Real Temp in Windows).
I understand that the max recommended voltage for the E8400 is 1.4v, so I'm a bit reserved about cranking it up any further because I'm not sure which monitor I should trust in what it's actually pulling. By all accounts, I'm thinking I'm lucky to have gotten so close to 4.0 Ghz on stock voltages so far, and my overclock feels somewhat safe up to this point... I haven't really been pushing too hard yet. If I'm still below 70c under load, will I be safe in pushing on with the voltages and speeds?
Ok sorry for the longwinded first post... dam noobs...
So I've been messing with my E8400 overclock in my EVGA 790i board. I had it running at 4.05Ghz with a 2Gb Patriot Viper DDR3 EPP RAM kit that was *supposed* to run at 2000Mhz but never could. The best I could do was get it to 1700, and I tried everything I could fathom, from switching to the "black" RAM slots to disabling EPP. So, I finally went out and got some Corsair Dominator DDR3, rated for 1600 Mhz with 8-8-8-24 timings. It's actually 2 sticks from an i7 6Gb kit, which I found out from Corsair would run fine in my Core 2 Duo system. So effectively I'm running 4Gb at 1600 Mhz with stock timings, and stock 1.65v.
Anyway, I installed it and went back to all stock settings and decided to see what my overclock headroom would be with the new RAM. I brought my FSB overclock to 1600 Mhz with no problems, with my FSB/Memory unlinked. as soon as I would bring the FSB past 1600 though, it would automatically drop my RAM clock to 1518 or some strange number, despite it being manually set to 1600. If I tried to boot with the FSB anywhere past the 1600, I'd get a BSOD. I tried to slightly overclock the RAM along with the FSB, and even tried linked/synced up to 1620, but couldn't get it stable. I found it particularly strange because I'd had my FSB way past 1700 with my Patriot RAM, and I would think the new Dominator stuff, with 2 extra gigs and lighter timings, wouldn't stand in the way of getting back to where I was.
Finally, I started tinkering with my FSB speed and noticed that every setting between 1600 and 1739 would automatically slow down my RAM clock, but as soon as the FSB was at 1740 my RAM went back to it's 1600 Mhz setting. Is this some math equation I don't get? Does the RAM clock normally get changed when the FSB is operating within a certain range?
So... onto the weirdness with the voltage settings... everything had been on stock voltage up to the 1740 Mhz (that's 3.91 Ghz for the E8400). I booted fine but was failing some Prime95 tests on Core 0, so I upped the voltage settings one click and went back to Prime95, and it was fine for over 12 tests. I continued this up to my current 1780 Mhz (4.0 Ghz) But, I've been noticing that for some reason, this BIOS doesn't actually set the voltage where you tell it to. I currently have the voltage setting in the BIOS at 1.412v, it shows an actual 1.36v being used in the BIOS system monitor, and CPU-Z in windows has it totally different- 1.38v during idle, and for some reason it drops to 1.35v during stress testing with Prime 95... ??? Oh, and idle temps are 53c in BIOS, 67c during Prime95 (via Real Temp in Windows).
I understand that the max recommended voltage for the E8400 is 1.4v, so I'm a bit reserved about cranking it up any further because I'm not sure which monitor I should trust in what it's actually pulling. By all accounts, I'm thinking I'm lucky to have gotten so close to 4.0 Ghz on stock voltages so far, and my overclock feels somewhat safe up to this point... I haven't really been pushing too hard yet. If I'm still below 70c under load, will I be safe in pushing on with the voltages and speeds?
Ok sorry for the longwinded first post... dam noobs...
1 - 11 of 11 Posts
same set up same problems but its not a problem the ram will auto adjust to your cpu fsb mine is 1778 @ 1.3v 4ghz stable can get 4.5 stable but to hot. my ram is 1600 comes up as 1333 manuel fix set timing and volts from manufature specs and boom rock solid you got to increase alot of thinks hit me up ill help you also if you can get your hands on a stock pentium D cooler with the copper core helps temp alot
nothing to do with the n force chip so the intel pxx is better for overclocking mad style. Mine still runs with the best of the best
look at my sig rig.
running 3 years strong.
running 3 years strong.
and fyi my cpu has been running 4ghz 24/7 for as long as i built it in 2006 i did upgrade to the e8400 and the 790i board with the 2 260s and ram lol when it all came out that mb was almost 300 bucks. the nb and sb voltage is a world of help
Dude, I've tried to run Patriot 2000mhz on that same setup. I had my 8400 at 4.5ghz 24/7 also. Getting the ram to work at 2000mhz was impossible. It kept corrupting my system files and I would have to reload windows. I tried everything and no go.
It's really not that much faster anyways. 1600mhz is plenty, and runs better with lower timings. Try to tighten up the timings at 1600mhz and you'll be good.
I went to the e8600 and was hoping to run 500x10 for 5ghz with 2000mhz ram. I got the 5ghz no prob, but couldn't get the ram.
It's really not that much faster anyways. 1600mhz is plenty, and runs better with lower timings. Try to tighten up the timings at 1600mhz and you'll be good.
I went to the e8600 and was hoping to run 500x10 for 5ghz with 2000mhz ram. I got the 5ghz no prob, but couldn't get the ram.
its the ram this board only supports certain 2000mhz ram 1800 is best with no issues but 1600 seems fine to me i write at 9877mb a sec cas lat is 50.9 so not bad at all
my ram is 1600 but comes up 1333 with wrong timings on auto
Quote:
Ram always seems to do that. Usually defaults way slower than it is. All the 1366 builds always are set at 1066mhz 9-9-9-24. Even with 2000mhz ram. You have to set the ram your self.Originally Posted by berretta42;12519366
my ram is 1600 but comes up 1333 with wrong timings on auto
Quote:
Ram always seems to do that. Usually defaults way slower than it is. All the 1366 builds always are set at 1066mhz 9-9-9-24. Even with 2000mhz ram. You have to set the ram your self.Originally Posted by berretta42;12519366
my ram is 1600 but comes up 1333 with wrong timings on auto
1 - 11 of 11 Posts
- This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Overclock.net
A forum community dedicated to overclocking enthusiasts and testing the limits of computing. Come join the discussion about computing, builds, collections, displays, models, styles, scales, specifications, reviews, accessories, classifieds, and more!
Full Forum Listing
Explore Our Forums
Top Contributors this Month
View All
HappySheep
329 Replies
Ichirou
265 Replies
GRABibus
226 Replies
Recommended Communities
