• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

P35 DS3R Issue

R

Riznarf

n00b
Joined
Sep 10, 2007
Messages
8
So I just installed the F11 version of the BIOS which GEATLY helped with stability. (my system wouldnt boot with F8 installed.) However, now for some reason I cant OC. I'd go into the BIOS, (EIST is off) set the fsb to 400, save, and reboot, everything seemed fine.

I got into windows, looked in CPUZ and it still showed stock speeds (2.66ghz) which I confirmed with several other programs. So I thought maybe I hadn't saved the BIOS, so I rebooted and was surprised to see the 400fsb setting still there, but no apparent overclock. Any ideas?

Here's my rig:

P35-DS3R
e6750
2x 1gb Crucial Ballistix
eVGA 8800gts 320mb
Corsair 520hx

Please help, thanks.
 
I had the Gigabyte GA-P35-DS3R and same thing happened to me with the F11 bios. I updated the bios and poof. I couldn't overclock the FSB by 1 MHz!!!

I could get into windows and OC my E8400 all the way to 4.05GHz using the Gigabyte EZ-tune software. I ended up RMA'ing my board and getting something else.

Everytime I tried to OC within the bios I got a cold reboot and the bios wouldn't save my OC settings. The bios would however save any other setting I changed without a cold reboot. Really weird, I don't think I had a bad board. Just funny bios and behavior with the E8400.
 
Any USB drives attached to the computer? Sometimes they can cause gigabyte boards to not hold their overclock. Go over your BIOS settings again, all of them. Make sure that they are all correct. When I first got my P35-DS3R I couldn't overclock either until I went over all the BIOS settings to make sure they were correct.
 
thanks for all the help. Yes, I have my wireless keyboard/mouse and printer hooked up via USB. I also disabled the legacy USB in the BIOS, however, the problem remains. ALL my settings in the BIOS were saved and correct however, but with no overclock. Any other ideas? Thanks.
 
I've read on the German Gigabyte forum that when the OC doesn't stick you must:
1. unplug the power cord from the PSU, then replug and see if it works.
2. unplug the power cord, clear CMOS (taking out the battery too), make again the changes in BIOS then test it.
Usually the first method works. ;)
If after a long time the board doesn't remember the OC settings, then you must "Load optimized defaults" and reset everything like it was before.
 
I haven't had this problem with my DS3R after flashing to F11 bios. I will note that it does do a cold boot after changing anything FSB related in the bios, which I thought to be weird. Thought my board was defective until I found out that's normal.

turn off EIST and CIA2 in the bios. That'll stop the factory SpeedStep. Do a "Ctrl-F1" from the main bios screen to turn on advanced settings. Double and triple check everything.
 
I had this board with an E8400. Rev 2.1 and tried F9, F10 and F11 bioses. Cleared Cmos and all. Still didn't keep my OC settings. I could OC in windows though. Happy your issues are resolved though.
 
I tried clearing the CMOS, reseting the optimized defaults, and then tried to OC again all with no luck. Here are my BIOS settings, because I have no clue what could be the issue. Please take a careful look and let me know if you notice anything please: (Flexion, just in case, what program did you use to overclock in windows?)

dsc01279ai8.jpg


dsc01280zf6.jpg


dsc01281sz8.jpg


dsc01282wn4.jpg


As you can see there SHOULD be a modest overclock on my CPU (2.66 to 2.8) but in windows, according to CPUZ, Everest, Orthos, CoreTemp, etc, it's still running at 2.66ghz

Thanks as always.
 
Disable virtualization, unless your running VMWare, and disable that full screen logo. At lease you'll be able to see what your proc is running at before getting into Windows. Set your PCI-e frequency to 100. Some people play with that, but I've found to make more of a mess when you're trying to get stable.

Other than that everything looks good. If it's still a no-go try unplugging the 24pin power connector on the mobo, remove the cmos battery and let it sit for 5 mins. That should clear everything out pretty good. Put it back together and put all your settings back in the bios. If it still doesn't work I'd RMA the board.
 
Riznarf,

Wow, I thought this was and e8400 problem and not a P35-DS3R problem. Have you used Gigabyte's easytune inside windows to OC? You can pretty much adjust vcore and FSB with that software, so you'd get an idea of what your CPU is capable of. I used this when I had my P35-DS3R, just to make sure that it wasn't my CPU that was the problem.

You can verify your OC using CPUz and also check 3Dmark CPU scores to see if it is performing normally. If you can OC within windows, but can't OC within the bios, I'd say get another board. Because then it's probably not any of your other components causing the issues.

Also is your board saving all of the other settings (such as raid, voltages, etc.) and not FSB and Multi settings? If so, this is exactly the same problem that I had.
 
Same problem here now on my DS3R r2.0. When I went to f11 bios I am back at stock settings on my q6600 no matter what I do. Of course, before even searching here had went thru all of the steps suggested above with the same problem. I guess I will have to be happy with EZ-Tune since I dont feel like pulling my board out of my case and be without BF2 and COD4 for more than a day.

Anyone found a solution to this besides to RMA the board?
 
bink said:
Same problem here now on my DS3R r2.0. When I went to f11 bios I am back at stock settings on my q6600 no matter what I do. Of course, before even searching here had went thru all of the steps suggested above with the same problem. I guess I will have to be happy with EZ-Tune since I dont feel like pulling my board out of my case and be without BF2 and COD4 for more than a day.

Anyone found a solution to this besides to RMA the board?
Click to expand...

Only thing I've heard of working for people is clearing the CMOS and starting over. Unplug the 24pin connector, pull the CMOS battery and let it sit for a few mins. Plug it all back in and try your overclock again. Only adjust what you need to adjust, don't go crazy changing everything at first.
 
wow this seems like a big problem :|
I'm still using a pretty old bios...F4 or the one after it.
have you tried contacting gigabyte support? maybe if enough people email them they should find a way to fix this oc problem
 
HydroBudz said:
Only thing I've heard of working for people is clearing the CMOS and starting over. Unplug the 24pin connector, pull the CMOS battery and let it sit for a few mins. Plug it all back in and try your overclock again. Only adjust what you need to adjust, don't go crazy changing everything at first.
Click to expand...

Dang, just tried that as well...again, with no luck. I actually had an ok chip that ran around 3.43( dont remember exactly) with a thermalright 120 extreme...of course I keep the house at 58-60 in the winter time. I may go back to the F4 bios, but i was enjoying at least looking at the extra memory timing settings (placebo effect I guess)..

BF2 and COD4 all play nice at stock speeds anyways...thats all that matters.

:(:(:(
 
I had major issues after flashing to F11 also, however ...... I fixed my problem by clearing the cmos then everything started working as it should. Try that. Doh nm I did that and it worked for me.
 
You must log in or register to reply here.
Back
Top