Problem loading OC settings on startup

A

AmazingKreskin

n00b
Joined
Sep 29, 2006
Messages
17
My system consists of a Biostar 6100-m9 motherboard and a Toledo X2 3800. I have tested and confirmed the CPU and motherboard run stable @ 249 FSB in windows using Clockgen. When I set up the overclock in the bios, I set the HTT link to 3x, the ram divider to 133, and the FSB to 249.. When it boots into windows, I check cpu-z and it says the cpu is running @ 2000 Mhz. So I go to check the bios, and it's set up to run @ 2490 Mhz. :confused:

I've tried setting the fsb to 205 in the bios just to see if its the pci lock or something. I then set Clockgen to set the fsb to 249 on startup. Windows locks up about when clockgen would apply the setting. I've also tried turning off error reporting in the bios. I read that was a problem with my motherboard model. I also read something about the bios having a feature called ONE (Overclocking Navigator Engine), but I cant seem to find it. All I can find is "Performance booster zone", which has the ram and fsb settings.

I'm pretty sure the Pci lock needs a little bump in fsb to engage. When testing the overclock I had to set the fsb to 205 then to 249 just so windows wouldn't lock up. Could that be why the bios wont apply the overclock? If thats so, then why does Clockgen lock up on startup even though I bump the fsb up a little bit?

Just to clarify, I can set up the ram divider and HTT link in the bios, boot to Windows and use Clockgen to set the FSB @ 249 no problem. I just want it to apply during startup so I dont have to fiddle with it every day. Can anyone help me out?
 
Run super pi 1 meg test at 2.0 and 2.49 via bios settings. You should be able to tell if it's a software glitch from the resulting times.
 
Generally CPU-z seems to be correct on the fsb and multiplier settings. But I'm sure it's not 100% accurate.

On my setup, CPU-Z shows correct overclock, but other applications (even windows properties) shows a much higher overclock.

So I agree with learners permit, you should run some tests with both of the settings and see the difference there.
 
Okay, I did the superpi tests. After a lot of restarting due to mistakes on my part, the time for 2000 mhz are 48 seconds. 2500 mhz is 38 seconds. I know I said 2490 in my first post, but when I was setting up the bios I must have accidentally set the FSB to 250. Windows loaded and when I checked cpu-z, it showed the cpu @ 2500mhz.

I guess my problem is solved. Kind of odd 249 wouldn't work but 250 would.:rolleyes: Thanks for the help though.
 
You must log in or register to reply here.
Back
Top