Odd overclocking within the Gigabyte DS3L

[Glavinsolo]

I recently built up a e3110 on a gigabyte ds3l.

I updated to the recent bios F8b before I overclocked.

I had my pc overclocked to 430x9=3870mhz

PCI Express was locked at 100mhz

Memory can handle 2.1 volts which is set

CPU is set to 1.3v

All memory timings are accurate and capable.

------------------------------

Last night I ran OCCT for 12 hours stable.

-----------------------------

Today I rebooted my PC and all of my overclock settings are still there.

What is extremely odd is that the Overclock is not showing.

My PC is showing 3.00ghz and ram is slightly overclocked to 800mhz.

This is with FSB set to 430 and multiplier set to 9!

Ram is set to 5:6 ratio

Any ideas or previous experiences with this in overclocking?

 

[Tempered81]

post a cpuz screenshot of all 5 tabs during load & idle, did you save your oc profile into the bios?

is that the most up to date bios?

 

[Glavinsolo]

Originally posted by: jaredpace
post a cpuz screenshot of all 5 tabs during load & idle, did you save your oc profile into the bios?

is that the most up to date bios?

sure,

I saved my oc profile to the bios and it is loaded, when I go to the bios all overclocking settings are set and it shows what my overclock should be 3870mhz

It is also the most up to date bios.

It is just really weird,

let me get those screenies and maybe load up this easy tune thing gigabyte has

 

[Idontcare]

On DS3L's you can save your BIOS settings like usual with most motherboards by pressing F10, etc. But you can also save your settings to a profile, there are 10 slots for doing such, it is a red screen when you get there.

Be sure and save your overclock to the profile as well as the F10 usual way. Not sure why but for me I stopped getting funny business when I started saving my settings to profiles and with F10 to exit after saving to a profile.

One other thing, DS3L's are hyper-sensistive to thinking you had a failed overclock and then resetting your clocks to "safe settings". The bios values won't change when this happens, but the computer will be forced to run the safe settings until you go into the BIOS and resave the settings.

The most common way I have found to falsly convince the DS3L you had a failed overclock is to simply reboot your system after saving any changes in the BIOS. Say you save your settings, system boots again, you get into windows and all is happy. Then you do an update, or something that requires a reboot so you let windows reboot the system.

Since the computer is rebooting, for any reason and after any length of time, since you made the BIOS changes and you haven't done at least one cold boot since the changes the BIOS interprets the reboot as a failed overclock.

So...on DS3L anytime you tinker with the BIOS you must to a hard shutdown, at least once, before allowing the computer to reboot (other than that initial reboot the BIOS does when you exit the BIOS).

 

[Glavinsolo]

CPUZ Screenshot of what I have

Note my bios reads 430fsb and 3870 however it doesn't acknowledge the overclock

Its as if somewhere Gigabyte said hey you can't overclock anymore.

I even tried flashing the bios over

 

[Glavinsolo]

Originally posted by: Idontcare
On DS3L's you can save your BIOS settings like usual with most motherboards by pressing F10, etc. But you can also save your settings to a profile, there are 10 slots for doing such, it is a red screen when you get there.

Be sure and save your overclock to the profile as well as the F10 usual way. Not sure why but for me I stopped getting funny business when I started saving my settings to profiles and with F10 to exit after saving to a profile.

One other thing, DS3L's are hyper-sensistive to thinking you had a failed overclock and then resetting your clocks to "safe settings". The bios values won't change when this happens, but the computer will be forced to run the safe settings until you go into the BIOS and resave the settings.

The most common way I have found to falsly convince the DS3L you had a failed overclock is to simply reboot your system after saving any changes in the BIOS. Say you save your settings, system boots again, you get into windows and all is happy. Then you do an update, or something that requires a reboot so you let windows reboot the system.

Since the computer is rebooting, for any reason and after any length of time, since you made the BIOS changes and you haven't done at least one cold boot since the changes the BIOS interprets the reboot as a failed overclock.

So...on DS3L anytime you tinker with the BIOS you must to a hard shutdown, at least once, before allowing the computer to reboot (other than that initial reboot the BIOS does when you exit the BIOS).

Great explanation and I am 90% with you let me apply your theory and get back to this thread

 

[badlogic]

Im using Bios F8A and have had np getting to 4ghz stable 24/7. Anything higher and I dont like the voltage I have to put in and the heat.

 

[Glavinsolo]

Ok I'm about to pull my hair out on this one now.

I just did the jumper trick on the motherboard ... that didn't work

I just removed the battery and put it back in ... that didn't work

Overclockers said to remove any usb storage device ... done ... still not working

eh

 

[Glavinsolo]

It seems that none of my FSB settings are sticking but every other change I do within the bios sticks.

This is really odd, I can overclock the ram but it seems the mb is locking the FSB on the proc to 333.

 

[Xpoc]

Do you have cpu host control enabled?

 

[Glavinsolo]

Originally posted by: Xpoc
Do you have cpu host control enabled?

Yeah

 

[Idontcare]

Do you have another LGA775 CPU you can stick in the board to confirm it is the mobo having issues and not the CPU?

If you stick everything back to stock (as in "Auto", not manual voltage inputs to stock values) across the board, from PCIe to ram to CPU settings, everything...and then fire up CPU-Z at idle and watch what changes when you load prime95.

Did all the speedstep features work as expected when you do this? (clock multi should be 6x at idle, jumps to 9x at load, and voltage should be lower at idle than your VID reported in Coretemp)

Something is definitely wrong, all you can do at this point is partition the problem down to a mobo or cpu issue and limit the number of RMA's you might be doing (if you are inclined to RMA stuff for not overclocking to your expectations).

And sorry to hear of your aggravation and experience, not fun when stuff doesn't work like it should.

 

[Xpoc]

Maybe bad bios. Try clearing cmos or reflash.

 

[j0j081]

is it a good idea to update to this bios for overclocking? I am still running F6 the version mine came with.

 

[Glavinsolo]

Originally posted by: Idontcare
Do you have another LGA775 CPU you can stick in the board to confirm it is the mobo having issues and not the CPU?

If you stick everything back to stock (as in "Auto", not manual voltage inputs to stock values) across the board, from PCIe to ram to CPU settings, everything...and then fire up CPU-Z at idle and watch what changes when you load prime95.

Did all the speedstep features work as expected when you do this? (clock multi should be 6x at idle, jumps to 9x at load, and voltage should be lower at idle than your VID reported in Coretemp)

Something is definitely wrong, all you can do at this point is partition the problem down to a mobo or cpu issue and limit the number of RMA's you might be doing (if you are inclined to RMA stuff for not overclocking to your expectations).

And sorry to hear of your aggravation and experience, not fun when stuff doesn't work like it should.

Yeah, speed step works fine

seems this is a common problem in p35s

same thing mentioned in this thread I'm reading through it now,

Text

Thanks everyone for the replies

 

[andrei3333]

i think you cant RMA for failure to OC i have the same board and there is a note somewhere in the manula or the box that reads something like they do not guarantee any overclocks which makes sense since user A may get to 4GHz while user B with the same settings may get to 3.6 or 3.8 i duno just my 2 cents

 

[Glavinsolo]

Ok, it works now.

Steps to take if you have this problem

Bios vrs doesn't matter get the latest one.
CMos clear doesn't matter
battery clear doesn't matter

If you encounter this problem do the following

1. Put your settings in
2. it will post at stock settings
3. allow it to go to windows
4. shut down once in windows (no restart or suspend)
5. unplug the power cable
6. count to 10
7. reinsert your power cable
8. If it does a double boot then your overclock failed
9. If it does not do a double boot you will see on the post screen your overclock
10. profit

This board is finicky end of story, what seems to be the limiting factor is that it has a running history of all your posts and wants at least one good post to fall back on.

Disable everything you won't be using, legacy drive support, serial, parallel etc etc

 

[superstition]

This board is gay end of story

I guess that's why I like it. The "gay" board keeps me warm at night.

 

[Glavinsolo]

New CPU-Z Screenie

I'm sure I could lower the voltage but screw it at this point

 

[Idontcare]

Glad you fixed it.

I remember trying to assist someone about a month ago and I insisted they remove the power cord from the PSU in order to get the BIOS to set correctly and all I got in return was a shitload of threadcrappers telling me I was full of BS.

Thanks for reconfirming my sanity, and congrats on getting your rig back.

 

[Glavinsolo]

Originally posted by: Idontcare
Glad you fixed it.

I remember trying to assist someone about a month ago and I insisted they remove the power cord from the PSU in order to get the BIOS to set correctly and all I got in return was a shitload of threadcrappers telling me I was full of BS.

Thanks for reconfirming my sanity, and congrats on getting your rig back.

Yeah the unplugging of the power cord simulates a long shutdown period.

If you shutdown and press the power button again without the removal of the power cord the mobo thinks you had a crash. I'm sure you could get away with waiting 2mins or so but the removal of the power cable for 5 secs usually does the job.

Thanks Idontcare