• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Gigabyte S3 won't OC at all (even 1mhz) after too high prior OC. FUBAR? Help!

Z

Zinn

Member
I just got this thing, but I had it prime stable for four hours at 475 earlier today (right off the bat).

But I pushed it a little too hard tonight... it just didn't want to do 484 FSB, so I raised the FSB voltage +.1 V and the MCH to +.2V. Still didn't work, but I had a hell of a time getting the thing to post again. Black screen, all that good stuff.

Ended up clearing the CMOS and restarting. Once I got back into the BIOS, I keyed in the values to my proven stable 475 OC. The thing is, when I boot now, the OC doesn't "take" ... The POST screen shows the CPU is at 1860 mhz (267 x 7). No matter how high or low I raise the FSB above 266, it shows 267 on startup. CPU-Z reports that the CPU is running at stock speeds.

I have flashed and reflashed the three latest versions of Gigabyte's BIOS, reset the CMOS, cried, tried using Gigabyte's Windows OC tool (it just gives up and stays at stock speeds when I tell it to apply my settings), and the thing won't go 1mhz overclocked. Also it's acting all weird. My USB mouse cursor was moving itself all over the screen until I unplugged and plugged it back in.

Is the thing burned out? I don't think going from +.1V to +.2V on the MCH should have fried it, considering that I have a 50mm fan glued to the northbridge, but raising the MCH voltage seems to have been the last thing I did between it being stable at 475 and now not OCing at all.

Here's what I conclude from this:
1: I should have spent more than $90 on a motherboard
2: This motherboard is now f*cked
3: I should buy an ASUS P5B-Deluxe with the money I would have spent on Windows Vista
4: Never buying a Gigabyte product again.

Am I off base here? Is there an easy solution for this? Help!
 
NAH, relax - normal probs

I guess you already have F7 bios in?
May have to go back to F6
http://whirlpool.net.au/forum-replies-archive.cfm/652892.html

Basically three things - you gotta "reset" the bios
since you did run 475, we know your ram works
>>>>No usb mouse or USB KB<<<< PS2 only

so - make sure legacy USB is off (you can also turn off all USB roots?)
then you have to either run a $10 PCI VGA card for a boot or 2
and/or run 1 stick of crappiest RAM you can find at SPD, stock voltage
And its normal to auto reboot on changing HW and BIOS/settings

Quote from extremesys

Why can't I overclock at all?
This issue is often mistaken with the issue below. Be sure to read this explanation.
Symptoms of no o/c'ing at all (may be one, may be all):
Cannot change PCIe bus speed, after changing to anything from Auto the system resets in POST before mem testing.
Cannot change fsb because system resets as above.
Changing any V in BIOS doesn't make any difference in o/c.
Changing timing in BIOS doesn't make any difference in o/c

Changing in my mind means ex. 267fsb (stock 266), 265fsb and so on. These are slightly (and more significant) changes which cannot be done. This is not a problem of >450fsb or sth. This is a problem of no o/c at all!
This is not a problem of a fsbwall - this is not for you if you have already overclocked even a 1Mhz!

[A] There are several possible causes of this problem:
ONE = BIOS:
look below at disabling the Legacy USB storage detect option in BIOS and UPGRADE your BIOS.
TWO - VGA:
Your VGA card is probably making MB not to overclock. Try buying some crappy PCI /not PCIe/ VGA 1MB card (or 2, 4 MBs ) and putting it in, booting with only PCI VGA. It worked for me, I could overclock and when I finished I put my 7600GS inside. Everything is working quite ok If not, just try another video card but a different model.
THREE - RAM:
This is the least well known issue today. I guess... replace ram and see if it helps o/c'ing... If so... just buy new sticks = Sorry

What is the problem with memories and DS3?
[A] Some memories require 2.0V to boot. Standard DS3 stock VDimm is 1.8V. Simply after a CMOS reset the system won't boot... If you happened to have such mem, replace them. Or buy some shi++y lowcost mem and put it in to boot, change VDimm and replace with your modules to continue o/c.
Click to expand...
Click to expand...
 
Thanks a lot for your help!

I downgraded the BIOS to F5, cleared the CMOS, took the actual CMOS battery out and cut the power. This combination resolved the problem (although I could have sworn I had done all of this sans removing the battery earlier)

I guess the positive side to all this poking around in my case was that I noticed Zalman 9700 was mounted ass backwards. Remounting it properly brought my load temps down 10C even before the paste cured. Maybe now I can bump this thing up to 476 FSB! 🙄

Seriously though, thanks for the reply! It's awesome to have this thing off the ground again!

BTW, I still can't help being put off by these quirks. This is a bad first impression of a Gigabyte product. I think next time I'll stick with ASUS...
 
I know, but I've had no issues pushing DFI, ASUS and even ECS boards beyond what they're rated. Really, out of five motherboards I've had in the past 2 years, this is the only one that has given me any trouble of this magnitude. Although to go from 266 to 475 FSB is a pretty insanely outrageous increase. So I guess I can cut Gigabyte some slack.

I'm just happy it works again! 🙂
 
Im fed up with the DS3 - the "Gigabyte" (JMicron) 2 purple SATA/IDE ports.
If you use the thing as IDE (for opticals), you have to use SATA in legacy, but if you install JNicron SATA RAID drivers you get no IDE shown or it runs in PIO.

The "second generation" 965P, or ASUS commando is supposed to fix all woes. But then again, I was going to buy the striker until I found out all the bugs IT had.
Even on this one big vdroop
http://www.techenclave.com/forums/new-asus-p965-board-asus-commando-84195.html

Basically, they throw out stuff and use consumers as testers, issue bios advances, then just when its almost working well, they come out with newer model.

BTW - these chipsets have black holes - they go dead for 10 steps then work again, might want to try 490 or 500.
 
He had the wrong side facing the rear of the case, apparently. I quote the FrozenTech review of the Zalman 9700:

"The manufacturer recommends that the warm exhaust from the Zalman CNPS9700 LED be directed towards the rear of the chassis, so make sure to do that."

And, seriously, the above is not Gigabyte's fault at all. Sheesh, a $90 mobo doing 475 prime stable and that wasn't good enough? Glad u didn't kill your board trying to push it further too. That alone should make you praise Gigabyte not condemn them.

Just my first post 2 cents. 🙂



 
wierd haven`t had a singel problem goin to 3.5 ghz with 500x7 on my cellshocks. Only bios i had that gave problems was the F6 that messed with my x-fi soundcard.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top