e8400 - Cant OC ot 3.6 but can OC to 4.0?? (Doesnt make sense)

Pyro2008

Junior Member
May 23, 2008
6
0
0
Man, what am I doing wrong here???

I have had this mobo for about a year now and everything has been running fine with my e6600 oc'ed to 3.3ghz.

I just got the e8400 and it is running like junk. At first, it wasnt even being recognized properly, had to reset the cmos using the jumpers. When it booted up, this is the default I get in the bios. (I failed to reset the bios to default settings before adding the new chip)

FSB 1333
CPU 1.17
FSB 1.2
MEM 1.9
SPP 1.25
MCP 1.5
SPP-MCP 1.2

5-5-5-15-2t

48c cpu
34c board
48c mcp

I then tried to overclock to 1600 (3.6ghz) fps with the voltages below, no go wouldnt boot... had to reset the cmos to boot. Tried again but this time with 1780 fsp (yeah I know, 1600 didnt work so let me make things worse .. right?).

Magically, it now boots but gets a startup temp of 59c. Also, I noticed vdroop for the vcore to 1.41 (was set to 1.475) Took it to 1.5 and it vdrooped to 1.45ish.

Anyways, when I boot windows with the following settings it locks after a few min.


(These settings were suggested on another thread)

FSB 1780
CPU 1.475 (actual 1.41)
FSB 1.3
MEM 1.9
SPP 1.45
MCP 1.55
SPP-MCP 1.4

5-5-5-15-2t


I have the latest bios version (which I updated to months ago) 691N0P32.

Here are the specs ...

-MSI NX8800GT 512M OC GeForce 8800 GT 512MB

Intel Core 2 Duo E8400 Wolfdale 3.0GHz LGA 775 65W

-Seagate Barracuda 7200.11 ST3500320AS 500GB 7200 RPM SATA 3.0Gb/s Hard Drive

-G.SKILL 8GB (4 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400)LITE-ON 20X DVD±R DVD Burner with LightScribe Black SATA

-Seagate Barracuda 7200.10 ST3320620AS (Perpendicular Recording Technology) 320GB 7200 RPM SATA 3.0Gb/s Hard Drive

-ZALMAN CNPS 9700 NT 110mm 2 Ball Ultra Quiet CPU Cooler

-EVGA 122-CK-NF68-A1 LGA 775 NVIDIA nForce 680i SLI ATX Intel Motherboard

-CORSAIR CMPSU-520HX 520W ATX12V v2.2 and EPS12V 2.91 Power Supply

-Vista 64bit Ultimate



Why would I be able to hit 4ghz and post but not even be able to boot with 3.6 same voltages??


Thanks ahead of time!
 

Quiksilver

Diamond Member
Jul 3, 2005
4,725
0
71
Sounds like an FSB wall or perhaps something in your settings. Did you turn off C1E and EIST?
Also what is SPP? MCP? SPP-MCP?
 

Pyro2008

Junior Member
May 23, 2008
6
0
0
I was thinking a wall too but then I OC'ed to 4.0 and it booted (wasn't stable but still booted).

3.6=No boot (Tried TONS of different voltage combinations to no avail)

4.0=Booted but locked in Windows

Stock

FSB 1333
CPU 1.17
FSB 1.2
MEM 1.9
SPP 1.25
MCP 1.5
SPP-MCP 1.2

When I attempted to OC to 3.6

FSB 1780
CPU 1.475 (actual 1.41)
FSB 1.3
MEM 1.9
SPP 1.45
MCP 1.55
SPP-MCP 1.4

5-5-5-15-2t


When I OC'ed to 4.0

FSB 1780
CPU 1.475 (actual 1.41)
FSB 1.3
MEM 1.9
SPP 1.45
MCP 1.55
SPP-MCP 1.4

5-5-5-15-2t


Edit: Yeah, turned those off.


These were the exact settings suggested in another thread and a couple users confirmed they worked (no chip is the same so dunno what to expect).

"Link and sync your RAM
Set timings to 4-4-4-12 2T
FSB - 1780Mhz
CPU - 1.475v
FSB - 1.3v
Mem - 2.2v
SPP - 1.45v
MCP - 1.55v
SPP-MCP -1.4v

Disable all of the following: C1E, speedsetep, execute disable bit, spread spestrums, GPUex "
 

JasonandBecky

Senior member
Oct 29, 2001
311
0
0
my guess is when you first started using it, your thermal paste was too thick and was overheating your cpu quickly. After some time the heat and pressure spread out the paste for better contact. Resulting in a much better overclock.
 

Pyro2008

Junior Member
May 23, 2008
6
0
0
I actually thought that too, since I first tried to OC to 3.6. After making it to 4.0 and being able to boot, I tried to scale back down and it stopped booting. :/
 

OCGuy

Lifer
Jul 12, 2000
27,224
37
91
That is alot of Vcore to hit 3.6ghz! (1.275 in BIOS, 1.248 actual was all I needed)
 

Pyro2008

Junior Member
May 23, 2008
6
0
0
Can upping the vcore more than is need for a particular OC actually cause it problems?

I havent really messed with lowering the voltages for 3.6 because I didnt think it would help. Although, I did attempt to load 3.6 with stock settings (auto) and maybe that was too low.

 

aigomorla

CPU, Cases&Cooling Mod PC Gaming Mod Elite Member
Super Moderator
Sep 28, 2005
21,053
3,537
126
Originally posted by: Pyro2008
Can upping the vcore more than is need for a particular OC actually cause it problems?

I havent really messed with lowering the voltages for 3.6 because I didnt think it would help. Although, I did attempt to load 3.6 with stock settings (auto) and maybe that was too low.

1.5 is much too high for a wolfdale.

Try to keep voltage under 1.4V if you want your chip lasting longer then 1 yr.
 

kpo6969

Member
Jul 31, 2007
89
0
0
Originally posted by: Ocguy31
That is alot of Vcore to hit 3.6ghz! (1.275 in BIOS, 1.248 actual was all I needed)
1.262 MIT (P35-DS3L)
1.236 bios
1.216 cpuz
400FSB (1600)
memory 1/1 (2.0)