Strange thing happened to E8200 OC

sanofi

sanofi

sanofi

Associate
Joined
9 Jul 2006
Posts
1,848
Location
Vienna
So I had my E8200 OC'd to 3.36Ghz@420FSB for months, core at 1.2V and all was fine.

Just today, I noticed that the cpu was back to the stock 2.66Ghz but still at 1.2V. So I checked the BIOS and it seems the manual overide on the FSB had been disabled again and had gone back to 333, but everything else including the core voltage and the mem (that I had increased by 0.2V) was still the same.

Any ideas why this would have happened. EIST and C1E are disabled still.

I've tried to use 420FSB at the current voltage that I had on the OC before, but the machine wouldn't boot past the BIOS splash.

Is there a problem with the cpu? Does the core/mem need more juice? Strange that it would work before at this voltage but not anymore, stranger still that it would reset these settings.

The mem is OCZ 2GB (2x1GB) PC2-6400C4.
 
Last edited:
sanofi said:
So I had my E8200 OC'd to 3.36Ghz@420FSB for months, core at 1.2V and all was fine.

Just today, I noticed that the cpu was back to the stock 2.66Ghz but still at 1.2V. So I checked the BIOS and it seems the manual overide on the FSB had been disabled again and had gone back to 333, but everything else including the core voltage and the mem (that I had increased by 0.2V) was still the same.

Any ideas why this would have happened. EIST and C1E are disabled still.

I've tried to use 420FSB at the current voltage that I had on the OC before, but the machine wouldn't boot past the BIOS splash.

Is there a problem with the cpu? Does the core/mem need more juice? Strange that it would work before at this voltage but not anymore, stranger still that it would reset these settings.

The mem is OCZ 2GB (2x1GB) PC2-6400C4.
Click to expand...

On my old P35-DS4 when it did stuff like this it would also change the memory divider back to something stupid. I suspect that's what has happened here. Check that and see if it's trying to run the RAM at 1400MHz or something.
 
WJA96 said:
On my old P35-DS4 when it did stuff like this it would also change the memory divider back to something stupid. I suspect that's what has happened here. Check that and see if it's trying to run the RAM at 1400MHz or something.
Click to expand...

It's at 5:6 atm. I can't remember if it was like that when it was OC'd or not.

If I push the FSB to 400, should the divider be set to 1:1? Also in terms of voltage, should 1.2V and an extra 0.2V on the mem be sufficient?
 
if it helps, why not try the whole process from scratch. work your way up again slowly from stock.

Before you do though, you havnt installed any new ram have you, or flashed the bios - which sounds like you havnt.
 
toon_mad said:
if it helps, why not try the whole process from scratch. work your way up again slowly from stock.

Before you do though, you havnt installed any new ram have you, or flashed the bios - which sounds like you havnt.
Click to expand...

No and no.

I did try a small jump in FSB, from 333 to 340 at 1.25V, 5:6 still and a +0.2V to the mem (from before) but the machine refused to go past the BIOS splash.
 
My GA-G33-DSR2 does this, so did the G33-S2. I presume you're using a Gigabyte board too OP?

It fires up with all fans at full pelt for 10 seconds, then they drop off their duty cycle then it comes back up. Did it yesterday for 2 minutes after unplugging a USB mouse during sleep, then came back up with default clock speeds.

It's gotta be something to do with a safety feature kicking in and dropping things back to safe limit to allow boot. Royal PITA, I'd rather hit the jumper than have it do it itself randomly!
 
This happens on my board too. OC'd to 3.2, stock volts, memory timings on 4-4-4-12 with +0.1v. Darn gigabyte boards of this era have a habit of resetting the fsb and memory timings for some reason. I stopped the annoying cold boot/full fan thing by slackening the memory timings to 5-5-5-18, and now it boots and holds settings fine. This only happened after I OC'd my CPU, was fine at stock.

Perhaps some more volts to the NB would help me get the timings back, though slacker timings don't seem to make much difference.
 
I'm loathed to dump more volts through the NB if it's only at 400fsb, it gets royally hot as it is right now - any more would fry it fo' sho'.

Worth giving a shot though, if it is that I guess I could redress cooling...
 
randal24 said:
My GA-G33-DSR2 does this, so did the G33-S2. I presume you're using a Gigabyte board too OP?

It fires up with all fans at full pelt for 10 seconds, then they drop off their duty cycle then it comes back up. Did it yesterday for 2 minutes after unplugging a USB mouse during sleep, then came back up with default clock speeds.

It's gotta be something to do with a safety feature kicking in and dropping things back to safe limit to allow boot. Royal PITA, I'd rather hit the jumper than have it do it itself randomly!
Click to expand...

Yes it is and it was doing the full pelt fan thing everytime I restarted after changing anything in the BIOS.
 
not sure it will make a difference or not, but could you write down your overclock settings on some paper, clear the cmos and re-enter them in the bios see if it makes a difference?
 
sanofi said:
No and no.

I did try a small jump in FSB, from 333 to 340 at 1.25V, 5:6 still and a +0.2V to the mem (from before) but the machine refused to go past the BIOS splash.
Click to expand...

Well, at 1:1.2 (5:6) your ram would be running at 400MHz at 333FSB and 408 at 340FSB. My first thought was, it would have to be carp not to overclock past it's rated speed by that little, but if you have manually tightened the RAM timings elsewhere then it might well not boot. Try using the 2:1 or 1:1 dividers and see when it stops booting then.
 
well my gigabyte board in my sig has gone back to the standard clocks and even if i go into the bios and change it it wil stay at 3.16ghz clock speed,you can change the volts to the ram and cpu but even if i change the fsb to 425 which give me 4.0ghz and i save it when it boots its back to 3.16 but in the bios its at 425 fsb,
 
sunderland said:
well my gigabyte board in my sig has gone back to the standard clocks and even if i go into the bios and change it it wil stay at 3.16ghz clock speed,you can change the volts to the ram and cpu but even if i change the fsb to 425 which give me 4.0ghz and i save it when it boots its back to 3.16 but in the bios its at 425 fsb,
Click to expand...

What does CPUz say?
 
WJA96 said:
Well, at 1:1.2 (5:6) your ram would be running at 400MHz at 333FSB and 408 at 340FSB. My first thought was, it would have to be carp not to overclock past it's rated speed by that little, but if you have manually tightened the RAM timings elsewhere then it might well not boot. Try using the 2:1 or 1:1 dividers and see when it stops booting then.
Click to expand...

I haven't touched the timings and the dividers are set to auto.
 
If a board detects a failed boot it will revert to stock fsb. It might be a bug going on with that and its not telling you it has.
 
well i dont know if it was this but i decided to apply some new thermal paste as its been a while and temps dropped a bit so i thought i would try clocking it again,took it upto 3.6 and the clocks are reading 3.6 now,im not saying its that but it seems strange after taking the cpu out all is working again,will knock it back to 4.0ghz tomorrow
 
I'm not sure it's the clocks, mine just threw a wobbler again at stock speeds (albeit hard coded and not on auto). I think this is more to do with memory config than anything, probably the 4x 1gb modules I've got in there. Going to take 2 out tomorrow, and run some tests - will report back with findings.
 
You must log in or register to reply here.
Back
Top Bottom