Jump to content

Archived

This topic is now archived and is closed to further replies.

StewCal

Having OC issues with Replacement Sandy Bridge MB

Recommended Posts

Just installed my replacement Asus Sabertooth P67 and am having trouble overclocking it. Got my original board to 4.8 mhz without any issues at all. Made all of the same adjustments in the Bios but OC doesn't seem to work. The strange thing is that the overclock doesn't fail. The system boots fine, but the CPU speed does not increase. When I reenter the Bios the OC settings are still the same but the speed is still 3.4 mhz. I tried reinstalling the chipset drivers to no avail. Any suggestions would be greatly appreciated.

Share this post


Link to post
Share on other sites
Just installed my replacement Asus Sabertooth P67 and am having trouble overclocking it. Got my original board to 4.8 mhz without any issues at all. Made all of the same adjustments in the Bios but OC doesn't seem to work. The strange thing is that the overclock doesn't fail. The system boots fine, but the CPU speed does not increase. When I reenter the Bios the OC settings are still the same but the speed is still 3.4 mhz. I tried reinstalling the chipset drivers to no avail. Any suggestions would be greatly appreciated.
Try BIOS update.Try complete BIOS reset.Is it EFI or standard?If all fails, I suggest returning it and requesting a replacement.

Share this post


Link to post
Share on other sites
Try BIOS update.Try complete BIOS reset.Is it EFI or standard?If all fails, I suggest returning it and requesting a replacement.
It's EFI. Board came loaded with latest bios update which is newer than what was on old board. I'll try to reflash. Is it possible to go backwards?

Share this post


Link to post
Share on other sites
It's EFI. Board came loaded with latest bios update which is newer than what was on old board. I'll try to reflash. Is it possible to go backwards?
Yes you can always go bachward, newer bios does not always = better perf.There is a new bios for my mobo but I don't need it cause the one I have is 100% stable.

Share this post


Link to post
Share on other sites

It's a long shot but, I've had a similar experience. Try using the 4pin ATX12v cpu connector from the power supply, or the 8 pin if already using the 4pin.I dunno if it's my power supply or the motherboard, but when I experimented with the 8pin connector I got unexpected cpu voltages and the cpu would not turbo.

Share this post


Link to post
Share on other sites
It's a long shot but, I've had a similar experience. Try using the 4pin ATX12v cpu connector from the power supply, or the 8 pin if already using the 4pin.I dunno if it's my power supply or the motherboard, but when I experimented with the 8pin connector I got unexpected cpu voltages and the cpu would not turbo.
Interesting...I think I plugged 2 four pins into the 8 pin socket....don't think i did that last time...I'll give it a try.

Share this post


Link to post
Share on other sites

Tried the bios update....would not allow me to go backward...and checked the power connector. Still won't overclock. I posted on the Asus forum but have had no replies. I guess I'll try to contact Asus support. Bummer, everything was working sooo well before the replacement.

Share this post


Link to post
Share on other sites

Did you try a clear CMOS as Word Not Allowed suggested, Steve?

Share this post


Link to post
Share on other sites
Tried the bios update....would not allow me to go backward...and checked the power connector. Still won't overclock. I posted on the Asus forum but have had no replies. I guess I'll try to contact Asus support. Bummer, everything was working sooo well before the replacement.
This is very unusual behaviour. Going backwards has always been a possibility. That is what BIOS update IS for.Did you successfully flash the current BIOS OVER the current one? Eg. reflash?If it does not work, then the mobo is broken, easy explained.

Share this post


Link to post
Share on other sites

For Asus, it is not possible (without major surgery) to flash back from 1305 bios to an earlier version because the earlier bios(s) do not work with the updated MB's. You can flash the non-updated boards with 1305 and later but then it it also very difficult to go back.

Share this post


Link to post
Share on other sites
For Asus, it is not possible (without major surgery) to flash back from 1305 bios to an earlier version because the earlier bios(s) do not work with the updated MB's. You can flash the non-updated boards with 1305 and later but then it it also very difficult to go back.
Ahh ok, that is a new thing with the B3 mobos. Usually on all other, you could have always switch back to any BIOS you wanted.But seriously, if BIOS is not changing the CPU speed, even after reflash, then it's broken, can't be anything else.

Share this post


Link to post
Share on other sites

Actually, it's a bios thing starting with 1305 on either the B2 or B3. Meaning, if you're still using the B2, like me, and update to 1305 you will not be able to flash back ...without major surgery.

Share this post


Link to post
Share on other sites

Have not tried clearing CMOS yet...will give it a try...Have a tech support email in with Asus. Haven't heard back yet. Thanks for all the suggestions.

Share this post


Link to post
Share on other sites

Doesn't it void your warranty admiting you are OCing to ASUS support?

Share this post


Link to post
Share on other sites

My P8P67 replacement. I thought I had a speed problem when seting up replacement mb but was because using an older version of CPU-Z. Need latest to see new B3 steping. Set your OC using the bios <del> and set ratio to 42 or so.Also make sure the onboard tpu and epu switchesare set to disabled (off).Saved profiles may not work either because of chipset and bios changes, I deleted them but haen't tried yet.ASUS tools work, monitor temp/cpu.Good luck...

Share this post


Link to post
Share on other sites
Doesn't it void your warranty admiting you are OCing to ASUS support?
Why in God's name?Intel actually supports OCing by setting Turbo, so...He didn't say if Turbo is working.Sounds like BIOS is not setting anything.I would suggest using normal BIOS, instead of EFI. Also turn off that stupid Asus logo at boot. And then checking for CPU frequency in the startup sequence. If there it shows no change, then it's sure.

Share this post


Link to post
Share on other sites
Why in God's name?Intel actually supports OCing by setting Turbo, so...He didn't say if Turbo is working.Sounds like BIOS is not setting anything.I would suggest using normal BIOS, instead of EFI. Also turn off that stupid Asus logo at boot. And then checking for CPU frequency in the startup sequence. If there it shows no change, then it's sure.
Reason I asked is because I always heard OCing voids your warranty, and also because I've been wanting to post in the Asus forums about my issue with this system's LLC + OC: it will overvolt after restarts. In other words, I get more Vcore in Windows (less Vdroop) after restarts than after cold boots And at least my board seems to have the post screen bugged in regards to CPU freq: it shows 3443MHz all the time or something like that, even OCed to 4.8GHz

Share this post


Link to post
Share on other sites
Guest firehawk44
Just installed my replacement Asus Sabertooth P67 and am having trouble overclocking it. Got my original board to 4.8 mhz without any issues at all. Made all of the same adjustments in the Bios but OC doesn't seem to work. The strange thing is that the overclock doesn't fail. The system boots fine, but the CPU speed does not increase. When I reenter the Bios the OC settings are still the same but the speed is still 3.4 mhz. I tried reinstalling the chipset drivers to no avail. Any suggestions would be greatly appreciated.
What are you looking at that states your settings are at 3.4 GHz? Because that's what it will normally show at idle until you open up a program. If you have the ASUS monitoring program running when opening up a program, it will show you whether you are overclocked or not. In the system settings page of Windows it will always show 3.4GHz. Mine is definitely o/c'd to 4.8GHz but everything shows 3.4GHz when idle. When I open FSX or Internet Explorer, it will show the o/c'd speed. I haven't checked but believe it shows 3.4GHz in the bios too even when you have changed all your settings to o/c to 4.8GHz. You should also let the system bios automatically o/c your system and/or go into the ASUS auto tuning program in Windows and try to o/c that way by simply clicking on the Extreme button. The latter will tell you exactly how much they were able to overclock your system. The fact you are able to boot into Windows w/o an issue indicates to me there is nothing wrong with your board.Best regards,Jim

Share this post


Link to post
Share on other sites
What are you looking at that states your settings are at 3.4 GHz? Because that's what it will normally show at idle until you open up a program. If you have the ASUS monitoring program running when opening up a program, it will show you whether you are overclocked or not. In the system settings page of Windows it will always show 3.4GHz. Mine is definitely o/c'd to 4.8GHz but everything shows 3.4GHz when idle. When I open FSX or Internet Explorer, it will show the o/c'd speed. I haven't checked but believe it shows 3.4GHz in the bios too even when you have changed all your settings to o/c to 4.8GHz. You should also let the system bios automatically o/c your system and/or go into the ASUS auto tuning program in Windows and try to o/c that way by simply clicking on the Extreme button. The latter will tell you exactly how much they were able to overclock your system. The fact you are able to boot into Windows w/o an issue indicates to me there is nothing wrong with your board.Best regards,Jim
The first time I noticed a problem was when I tried to use FSX. Was not performing nearly as well as with original board. Another key thing is that the fans don't rev up which they always start to do when Fsx is loading the scenery. No Turbo, Definately an issue.
Why in God's name?Intel actually supports OCing by setting Turbo, so...He didn't say if Turbo is working.Sounds like BIOS is not setting anything.I would suggest using normal BIOS, instead of EFI. Also turn off that stupid Asus logo at boot. And then checking for CPU frequency in the startup sequence. If there it shows no change, then it's sure.
Ai Suite is showing 1599.3 mhz at idle...Hmmmmm. That doesn't seem correct....
My P8P67 replacement. I thought I had a speed problem when seting up replacement mb but was because using an older version of CPU-Z. Need latest to see new B3 steping. Set your OC using the bios <del> and set ratio to 42 or so.Also make sure the onboard tpu and epu switchesare set to disabled (off).Saved profiles may not work either because of chipset and bios changes, I deleted them but haen't tried yet.ASUS tools work, monitor temp/cpu.Good luck...
What is CPU-Z? Didn't come with my Sabertooth P67....

Share this post


Link to post
Share on other sites
Guest firehawk44
The first time I noticed a problem was when I tried to use FSX. Was not performing nearly as well as with original board. Another key thing is that the fans don't rev up which they always start to do when Fsx is loading the scenery. No Turbo, Definately an issue.Ai Suite is showing 1599.3 mhz at idle...Hmmmmm. That doesn't seem correct....What is CPU-Z? Didn't come with my Sabertooth P67....
You should Google CPU-Z and you will find where you can download it. CPU-Z gives you valuable info about your system components. But CPU-Z will still read 1599.3 MHz until you open up a program then it will start showing 4788 4800 etc. As I stated before, I am o/c'd to 4.8GHz and the ASUS AI Suite Monitor states 1599.3 MHz at idle too. You appear to be o/c'd okay, you just have a slow running FSX. In that case it could be system drivers. Make sure you have the latest drivers installed that are recommended for the 1305 bios - http://www.xtremesystems.org/forums/showthread.php?t=265477 . It does not hurt to reinstall a driver. If FSX is still slow, then you might simply rename the FSX.cfg and let it rebuild and see if the default settings work better and go from there with any tweaks.Best regards,Jim

Share this post


Link to post
Share on other sites

×
×
  • Create New...