P35C-DS3R Doesn't hold BIOS OC Settings after shutdown ?

[sourtimes9990]

Hiya,

I have a Gigabyte P35C-DS3R motherboard, with an e6400 core 2 duo and 2gb of crucial ballistix 4-4-4-12. My system is totally stable under orthos at 3.2 Ghz with a FSB of 400 and my memory running at it's rated 4-4-4-12 400MhZ speed.

When I set these settings, I can warm boot or shut down the PC and then restart it (cold boot) and the settings are kept. But, what is weird, if the computer is shut down for a while, a few hours or so and then I turn it on the fans will spin a couple times, then the pc reboots back at the default settings again (2.13 ghz and no OC/voltage settings in place anymore) Any idea why the board is doing this ? I have the F4 BIOS on the board, and when it's OC, I have run all kinds of stress tests for hours and the PC is stable.

Oh, and I do not get any of the error message beep combinations on startup either.

Thanks in advance.

Cheers

 

[boglwe]

I had the same problem with my DS3R. I thought it was one issue and then it popped up again. I currently am at a lost with this problem. There was another thread regarding this somewhere, it was what I was actually looking for. I will keep my eye on this thread.

 

[jto168]

And I thought I was the only one with this problem!

I have found a solution for this problem which I hope will work for anyone else affected.

Remove the battery, clear the CMOS, and replace battery. Configure default settings upon first boot to ensure that your system is fine. Reboot, enter setup and configure your overclock settings.

After saving to the CMOS, the computer beeped, powered down, then powered up to initiate the boot sequence. I booted into Vista x64 without issue, and I inspected the system speed by checking with CPU-Z and CoreTemp.

Both programs correctly displayed by overclock settings (356x9) and I then began to do stress testing.

I've probably restarted 3-5 times each time after saving the initial settings to ensure that they weren't lost on each restart. I went further and changed the settings on a few occassions and tried to restart. No problems (knock on wood).

The only thing I have not tried is having the computer powered off for long periods of time, and then powering it on to see if the settings are still intact.

For reference, my system is as follows:

P35-DS3R Rev 1.0, F6 Bios
Q6600 G0, 356 x 9 (stable 12 hours so far Prime95 v25.4)
SPD 3.00 (effective memory 534)
Crucial Ballistix PC2-8500 4x1GB, 5-5-5-15 @ DDR2-1068

 

[jto168]

Update

I turned off the PC for the day and when I powered it up when I returned home, I experienced the same events as the OP.

The computer powered up momentarily, fans and HDD were moving, then it beeped and then powered off.

It then powered itself on and continued the boot process. Once into the OS, I checked CPU-Z and my settings were back to stock.

I restarted, entered my OC settings, saved and rebooted. Back into the OS again, and I checked CPU-Z; my overclock is in effect.

I'm also at a loss for why this happens and I hope it can be resolved with a BIOS revision.

I'm currently on F6, and I understand a beta F7 has been released.

Please reply to this thread if you experience the same problems or have found a solution!

 

[myocardia]

Your problems (all of you) are happening because you're forgetting one weird little step that's required with all of the Gigabyte P35 motherboards-- after saving the BIOS, re-enter the BIOS and hit F11, then give that overclock setting a name, like 3.2 Ghz or whatever you want to call it. That's all that I've had to do, for my P35C to retain my settings indefinitely.

 

[jto168]

Originally posted by: myocardia
Your problems (all of you) are happening because you're forgetting one weird little step that's required with all of the Gigabyte P35 motherboards-- after saving the BIOS, re-enter the BIOS and hit F11, then give that overclock setting a name, like 3.2 Ghz or whatever you want to call it. That's all that I've had to do, for my P35C to retain my settings indefinitely.

Thank you for your input!
I will try this tonight when I am at home and report back.

I received a reply from another forum which stated it had something to do with the virtual BIOS, and I believe you are referring to the same issue.

 

[jto168]

It looks like the F11 Save-to BIOS profile did not work.

I left the computer off for a couple hours after saving the BIOS settings ot the CMOS via F11 and when I powered up the the CPU Host Control was disabled and the memory timings were all back to default.

I don't know what to do now!

 

[SerpentRoyal]

This has always been a nagging issue with some Gigabyte boards.

Still don't understand why they are resistant to povide actual voltage set in BIOS instead of +.xxxV.

 

[hemmy]

This happens sometimes (randomly I think) on my 965P DS3 if I have the comp off for days at a time.

Luckily I almost never turn it off But it sounds like an exclusive Gigabyte problem

 

[SerpentRoyal]

Neighbor has the exact same issue with his Gigabyte 965 so I converted him to a $70 Abit IP35-E in August. Deep CMOS clearing didn't help. Perhaps this is a Gigabyte-specific hardware defect since we're seeing similar behaviour with the P35 boards.

 

[jto168]

It seems like this issue is hit or miss depending on the individual board.

Some users have not reported this problem at all, while others have experienced this problem one way or another.

I'm wondering if this is an undiscovered issue with most users because the BIOS settings are reset only when the computer has been off for more than a period of time. I'm assuming many users keep their computers on a lot, so this might be an issue that has not come up for those that do.

I've also come across owners of the P35 based Gigabyte boards reporting problems with booting and an endless loop of booting, powering down, and then the BIOS values resetting to normal/default values.

In my particular case I do not believe the battery is the culprit. The only two items that are reset to default values is the CPU Host Control (enabled/disabled) which in turn allows you to adjust the FSB, and Memory settings which allows you to set a memory divider (SPD) and the timings for the memory.

If the battery was faulty, I would expect to see all my configured BIOS values and settings to return to default values, but that has not happened.

Another user reported that it might be due to incompatibilities with certain memory, and with memory running above DDR2-1066. It appears GA officially supports memory speeds up to and including DDR2-1066, which may indicate that anything higher would result in unstable operation.

I've tried to reset the CMOS by shorting the CLR_CMOS pins, and I've also removed the battery for a long enough time for the CMOS to clear itself. Unfortunately my system still loses its OC settings when powering up from an OFF state.

It's a minor annoyance, but I can live with loading up my CMOS profile upon each power up. Thankfully this problem doesn't reset all the CMOS settings.

 

[egrimisu]

Hi i have P35C-DS3 and a friend of mine has a P35C-DS3R. We both encounter this error: every night i turn off my pc, in the morning when i power up my pc i got this BOOT BLOCK and it writes to me after a few restarts that the checsum is not corect or something.We run the PC a stock settings only the ramd is set to +0.2v
Is tehre a solutions or the mobo is defect and i shall change it?


Thanks

 

[VirtualLarry]

Is this only the P35C-xxx models, or does it affect the P35-DS3R model as well?

 

[supaboi]

Hate to bump a really outdated thread but i am exhibiting the same issues as the OP.

My overclocks are fine and temps are fine

Q6600 G0 @ 3.2GHz (8x400) @ 1.3V bios, 1.26V actual
2x2GB Crucial Ballistix 800 @ 4-4-4-12 2.0V
Thermalright Ultra 120 w/ push-pull fan config @ 48degrees load prime95

So i stress test the above config in prime 95 overnight with no errors and decent temps. Restarting the PC will retain the config. Its only when i cold boot it, the settings will be erase. FSB will go back to stock and RAM timing but the multiplier and CPU voltage stays modified...

The computer does struggle when cold booted. Fans would spin up but shuts down briefly before repeating itself again. Once it boots up correctly, the OC would reset.

BIOS is currently F10

Hopefully in the 3 yrs since this thread was created, theres a solution but google doesn't seem to agree

 

[kiriakos]

I have also the EP35C-DS3R Ver 2.1 Bios F4 ..

I got the same story too, and even worst , it booted up , and showed an recovery screen due Bios corruption .

The Q6600 was oced to 3G .
I use CPU voltage Auto ... C1 enabled ... Speed-step enabled.

What I will try to find out are until what FSB, the CPU have cold boot, with no issues.
Currently I have step back to 323X9 = 2.9G ( and testing )

 

[kiriakos]

In order to not cause confusion ... I have the EP35C-DS3R Bios:F4

I have to admit that this its my first PCI-E + Core Quad Duo setup.
( I came from the old school I875 + P4 + AGP )


I have find and sort out the hiccup issue on my MB , all that was needed , even for stable cold boot at default speeds , was to adjust manually the CPU core voltage ,
even at the default CPU core voltage of the Q6600 1,23750 ..

After this , my system boots nicely , at every cold boot.
Conclusion the EP35C-DS3R Bios:F4 ( has an Bug at the CPU voltage detection : Setting Auto )



I started to overclock my system,
and found that if I follow, the suggested core voltage , from know CPU's that are the same type with my .. example :
Core™ 2
Quad
Q6600
2.40GHz 8MB Kentsfield 65nm G0 95W 1066

And

Core™ 2
Extreme
QX6850
3.00GHz 8MB Kentsfield 65nm G0 130W

By adding in bios the proper core voltage for the 3.00GHz 8MB Kentsfield = 1.28800 FSB=334

The motherboard will run perfectly with no issues what so ever.

( Some people they must understand, the relation between the core voltage and FSB )

If you select to run your current CPU at the speed of the above example .... the core voltage are known , in other words its documented !!

Another very significant factor , are the motherboard it self ,
and how the electronics of it responds in any CPU that needs more that 130W , that is the official up to point , described clearly at the supported CPU's list for an 8MB Kentsfield .

The 3.00GHz 8MB Kentsfield 65nm G0 130W , its the official last step ,
as properly supported CPU on those boards.

Above 3.00GHz the 8MB Kentsfield , will have some difficulties to stay sharp .

On a second note :
The Intel Core™ 2 Extreme QX9770
3.20GHz 12MB Yorkfield 45nm C1 135W 1600FSB

Its also supported , but its 135W ... Yes that the true max wattage, that those board can handle nicely...
And so the 3.00GHz 8MB Kentsfield haves one small room to be overclocked until to draw 135W from the 130W ( at the default FSB ) .

And the conclusion are , that the 3.2G mark with an 8MB Kentsfield to be an true long shot .


WHY ? Because those Watts , are calculated at the default core voltage.
By bumping up your core voltage , you consume sooner , all the available energy that the electronics can supply .

Example :
1.20V X 115 Ampere = 138W
1.50V X 115 Ampere = 172W

If you was not aware that those CPU's have on their specs an max Amperes draw as 115 Amperes .
Then you are justified to get mad about failed overclocks.

And no , the most powerful PSU , its not the solution so to overpass those limits ...

Our subject remains and is the motherboard, and what it can handle in Watts , with all the parts around the socked just air cooled.

Good luck to all.

PS: Personally I am back to stock speeds,
It saves energy , plus cooler running system ,
and its more worthy to me , than bumping anything up,
for just 2-3 fps gain, in benchmarks.

Plus , the D.E.S. EnergySaver, its an amazing technology,
lowers the V-core by it self , and the CPU runs frozen .
10C above the ambient temperature .
( Install the software , its not a bloat , its an true worthy application )

 

[anarchoi]

Ok so 3-4 years later: did anybody find a solution? Im having the excact same problem with bios resetting and its driving me nuts.

If the answer is in the above post: my apologies but I simply dont understand it then.

My CPU is a Q6600.

 

[kiriakos]

I have trash this board, I am using an ASUS P5QC that is fantastic, and I wish you doing the same.

 

[ndrw833]

Hello All,
im still interested in any solution. I also using a p35c-ds3r F12 mobo with q6600 GO cpu with Elixir (Nyanya) 8GB DDR3-1600MHz. I can use the cpu on 3.0GHz abolutely perfectly stable, but if i power off the PC for a long time after turn on, the Bios resets the OC CPU Mhz settings to stock.
What i tried before without success so far:
-Adjust voltages manually
-Save/load BIOS presets (F11)
-Replaced the the PSU from 550W to 700W
-Adjusted manually memory timings
-Adjusted PCI Express Frequency
-Removed almost every HW component from the mobo slots (HDD`s, Optical drive, PCI devices)

Usually after a very cold boot i have to set the CPU OC Frequency settings and reboot several times before the system able to accept and not restores it to stock for Unkown Reason.
Thanks

 

[kiriakos]

Hello All,
im still interested in any solution.

Neither God can help you, trash this garbage, or use default settings.