i has been oc my rig for past few month ago , i having no prob with 3.6ghz 24 /7 , i use default clock coz no time to ply games
weird prob happening when i notice when i trying oc back my proc to 3.6ghz , seems like i set fsb to 400x9 but it boot up with 333x9
i log into bios again and hav a look on my fsb , the fsb still remain 400 , once again i boot up my pc , it show 333x9 again (keep repeat still the same) bios show 400x9 , in windows cpuz 333x9
wht happening anyway?
the setting is exactly same like wht i set past few month ago but now not working at all
keep booting up with default speed
is my mobo or proc "rosak" liao?

my spec :
e3110
p35 ds3
9600gt
4gb kvr

reli need help i tried google around but i cant find any solution for this weird prob

this really weird.. try to clear cmos see see?

tried tat b4 its not working
flssh bios : not working

degradation? can happen for both proc and mobo?

If you restart during the boot screen, the motherboard automatic put you back to default clock speed. when you enter the bios that time, it will show your last setting.
But looks like you got some experience on OCing, should be no problem bah... you got turn off you speedstep function? make sure its off, try press tab during the bootup screen and see whether its 3.6 or not.

nope
last time my speedstep no disable oso can OC gao gao
plus the when i login back to bios the setting still remain 400x9
it not reset to 333x9
bcoz i know if oc fail my mobo will auto reset the speed back to 333x9
werid

cpuz last time frm the pic u can c the speedstep has been enable



This is my cpuz for now / i set everything auto

---

Added on August 19, 2008, 7:59 pmproblem solved
i oso dunnoe wht happen , problem juz gone after i replug all the hardware LOL

This post has been edited by Irishcoffee: Aug 19 2008, 07:59 PM

have u set ur vMch voltage?

try update ur bios, and refresh back to your old bios again
sometime works if this situation happened

to early for that i think...
maybe bugs kot...

He say solved adi mar. Degradation won't be that quick - prolly some electrical circuit problem.

problem solved oledi after i replug all hardware
~ thread closed ~