Did you try the most obvious thing - raising vcore?
If your temperatures are fine, do it.
If your temperatures are fine, do it.
Suggestions to OC e8400 to 4.0ghz
Sup everyone. Hoping someone can give me some suggestions to get my e8400 to 4.0ghz. At the moment I am able to get into windows at 3.8 and run orthos for a short time (~10min) without errors. However when i try going to 4.0ghz i either get an error in orthos after the first minute or i get a blue screen of death before getting into windows. When i've been able to get into windows @ 4.0 ghz the FSB
![]()
RAM ratio is wierd, like 13:11 i believe. I was getting the same error in orthos @ 3.8 so i set my dram to 850 to get it to 1:1.
Here's the settings i have for 3.8ghz:
425 FSB x 9 multiplier @ 1.32 vcore
850 Freq on memory (425mhz) @ 5-5-5-15 with 2.1 vcore
everything else is set to auto and of course the features required to be disabled are.
I have tried playing with the memory timings however i'm getting the blue screen before i load into windows. This is what i've tried so far on the memory:
4-4-4-12, 5-5-5-15, 6-6-6-18 and all with 2.1-2.2 vcore.
At the moment i am taking off to class so i plan on leaving orthos running (roughly will be 2hours).
Here's the settings i have for 3.8ghz:
425 FSB x 9 multiplier @ 1.32 vcore
850 Freq on memory (425mhz) @ 5-5-5-15 with 2.1 vcore
everything else is set to auto and of course the features required to be disabled are.
I have tried playing with the memory timings however i'm getting the blue screen before i load into windows. This is what i've tried so far on the memory:
4-4-4-12, 5-5-5-15, 6-6-6-18 and all with 2.1-2.2 vcore.
At the moment i am taking off to class so i plan on leaving orthos running (roughly will be 2hours).
1 - 17 of 17 Posts
Quote:
You certainly have a good chip there. But we are only talking 5 hundredths of a volt here. May be enough to get him stable. If he is getting to windows some of the time all he needs is a little more. Still can't rule out the NB but he is 1:1 right now so I don't think that's it.
Originally Posted by darklink You guys have some seemingly high vcores for your OC's. My E8500 hits 4.365GHz at just 1.34375 in the bios (1.336 under load in windows). At most set ur vcore to 1.34 and see if you get stable. If the only thing you have changed is the vcore and mem timings and voltage, I would try raising some other voltages such as your NB voltage. I am not too familiar with nvidia boards but you might want to try bumping the NB voltage in small increments and then boot and check for stability. With your memory, start with the 6-6-6-18 settings at 2.1v while raising the FSB to increase your CPU OC. Once you get your CPU stable, start tightening the timings on your RAM and see where you end up. |
Quote:
I tried that but wouldnt boot into windows. Changed the memory timings to 6-6-6-18 and it booted. However after a few seconds inside windows it crashes. I tried loosening the memory timings but i get the same issue and blue screens.
Originally Posted by zomgiwin kay, so you need to unlink your RAM from CPU (best thing about nvidia chipsets) then, you raise your fsb to 1778 (1777 is 3999mhz if your ok with it) and next, you set your cpu Vcore to something like 1.35 should do it (if its stable, lower it as much as you can while staying stable, if its not, raise it a bit. to be super safe, don't pass 1.3625, if you want to, you can go a bit higher tho) |
2
Quote:
Crap
![]()
I could have sworn the MCP was the NB but then again, I don't own an nVidia chipset.
As far as going for 4.0GHz, maybe try bumping the FSB MHz just a few at a time (try 5 MHz) and see if settings still remain stable. See just how far you can get before it's no longer stable then bump the cpu and ssp/nb voltage a notch and see if it becomes stable. The fsb voltage at 1.4 might be a bit too high. Once again, I am not familiar with nVidia boards but on my Intel board, that voltage is referred to as VTT and you usually dont need more than 1.3. Setting it too high can actually decrease stability.
Originally Posted by Sivsta Found it =) SPP (northbridge), MCP = southbridge. From what i found |
As far as going for 4.0GHz, maybe try bumping the FSB MHz just a few at a time (try 5 MHz) and see if settings still remain stable. See just how far you can get before it's no longer stable then bump the cpu and ssp/nb voltage a notch and see if it becomes stable. The fsb voltage at 1.4 might be a bit too high. Once again, I am not familiar with nVidia boards but on my Intel board, that voltage is referred to as VTT and you usually dont need more than 1.3. Setting it too high can actually decrease stability.
Quote:
I've got E8400 easily up to 4.00GHz.
445MHz x 9 (FSB x multiplier)
Vcore = ~ 1.30V (after vdroop 1.28V)
NB voltage = 1.20V
DRAM voltage = 1.90V
DRAM timings = 5-5-5-10 2T @ 850MHz
All special options disabled (C1E, speedstep, etc.)
Originally Posted by Sivsta Ah, didnt know that. I'll actually set it back to 1.3 and see if my 3.8 is still stable. Once i feel it is i'll start bumping the FSB. |
445MHz x 9 (FSB x multiplier)
Vcore = ~ 1.30V (after vdroop 1.28V)
NB voltage = 1.20V
DRAM voltage = 1.90V
DRAM timings = 5-5-5-10 2T @ 850MHz
All special options disabled (C1E, speedstep, etc.)
Quote:
I'll try that when i get home from work. However i might need to leave the vcore where it is now since last time i couldn't get it to load into windows @ 1.32. Thanks
Originally Posted by Biatch I've got E8400 easily up to 4.00GHz. 445MHz x 9 (FSB x multiplier) Vcore = ~ 1.30V (after vdroop 1.28V) NB voltage = 1.20V DRAM voltage = 1.90V DRAM timings = 5-5-5-10 2T @ 850MHz All special options disabled (C1E, speedstep, etc.) |
1 - 17 of 17 Posts
