Official GIGA P35-S3/DS3/DS3R/DS3P/DS4/DQ6 bios/info thread

[Krohling]

My system won't POST with "Turbo" or "Extreme" options, only "Standard".
And this happens with or without overclocking.
Currently using BIOS F6.

I'm going to test max stable memory frequency with F6 and using stock volts (2.2v)
If it's not satisfactory I'll try F5 or F4.

[zsamz_]

f4i workin niceon p35c

[Bluesign]

Hi! I just want to tell you that I bought the Thermalright Ultra 120 Extreme and I installed it without removing DQ6's backplate. It was no big deal. I just had to buy some nuts and washers to fit the screws. Then I cut four washers from a cardboard and put them under the metal washers. The mobo supports very well the cooler's weight, in fact the cooler is not as heavy as I expected. However, because I heard so many were worried about this aspect, I secured the cooler with a wire so there is no way it will fall. In couple of hours everything was in place and it was worth the effort. With a Scythe S-Flex SFF21E at 1200rpm, this thing keeps my OCed E6750 (3200GHz) around 26-30 degrees while idle and 49-55 under (really) heavy load. And what is incredible about this cooler is that after 2 hours of Orthos and another 2 or 3 programs running at the same time, I saw the temperature dropping(!) from 55 to 49 degrees then rising again slowly then dropping again. This is because of the liquid that flows through those pipes... What can I say... State of the art cooler! With the stock cooler the temperatures were constantly rising and the noise...
I have some new questions for you guys. As I already told tou, I keep my E6750 at 3.2GHz (400x8), the RAM is running at stock timings (4.4.4.12) and frequency (400MHz) and the FSB: DRAM ratio is now 1:1, PCI-E - 100MHz. Is it correct to say that the only part of my system wich is running overclocked is my CPU? I am new at overclocking and I just want to be sure that I didn't overlooked something. Also from these images... can anyone tell me if the voltages are right? And what those temperatures mean? I'm pretty sure that the first is the mobo's temperature. About the second one, I don't know. Temp3 is an error just like the next one. HDD temp is reported correctly. Core0 and Core1 - error, in fact the temps are higher by 15 degrees. Then the core temp at 44 degrees, I don't know what it is... I don't think it is the CPU because normally the cores should always have a higher temp than the case of the CPU.
Edit: Unfortunately I had to remove the crazy backplate in the end because I overlooked a very important aspect which is the mounting pressure on the socket. Sorry about that.

[ceemic]

zsamz_, I'm@f4i for few months and nothing to claim about

[mXpS]

My system won't POST with "Turbo" or "Extreme" options, only "Standard".
And this happens with or without overclocking.
Currently using BIOS F6.

I'm going to test max stable memory frequency with F6 and using stock volts (2.2v)
If it's not satisfactory I'll try F5 or F4.

Someone said there are issues with Turbo\Extreme and F6 BIOS, so I don't think you're alone.

[Tantawi]

Head over to: http://www.station-drivers.com/

New beta BIOSs released today for:

X38-DQ6
P35-DQ6
P35T-DQ6
P35-DS4
P35-DS3P
P35-DS3

[Tantawi]

BIOS F7a beta for P35-DQ6 fixed a major v-drop I had, I set 1.362 in the BIOS and it's 1.328 in Windows, now I set it to 1.34 in BIOS and it's 1.328 in Windows too, I'm happy!

[JoeBar]

Purchased the DS4 Rev 2.0 a couple weeks ago along with 4x1GB of Crucial Ballistix PC2-6400 for my new Q6600 build. Just wanted to report my current settings are running fine, and I haven't had any issues.

Q6600 @ 400x8 w/ 1.325V (BIOS), cooled with Ninja Rev.B
DDR1000 (4:5) 5-5-5-15 T2 w/ 2.0V (BIOS)

Only have run into one issue. Loaded up to get a baseline score with 3DMark06 yesterday and was getting horrible framerates. Never let it finish a run, but was trying to check on stuff while it was running. Hit CTRL-ALT-DEL to start the task manager durning a run and found an error that was hiding. Says D3Derr-devicelost error. Anyhow, I'm not to big on benching, so I let it slide for now, but it will continue to bother me until I figure it out.

Does your pci-e works @ 16X?

[MuffinFlavored]

BIOS F7a beta for P35-DQ6 fixed a major v-drop I had, I set 1.362 in the BIOS and it's 1.328 in Windows, now I set it to 1.34 in BIOS and it's 1.328 in Windows too, I'm happy!

My P35-DQ6 no longer holds my FSB setting.
I can set it to 400x9, 400x6, 450x8, anything, it just boots at stock FSB, and my set multiplier.

Let me flash to these beat BIOs and see what if that fixes the problem.

[SaleGseK]

My P35-DQ6 no longer holds my FSB setting.
I can set it to 400x9, 400x6, 450x8, anything, it just boots at stock FSB, and my set multiplier.

Let me flash to these beat BIOs and see what if that fixes the problem.

Yeah, same thing happened to me but with the P35-DS3R, i couldn't make it work with overclock anymore, the solution, flash it back to stock bios (F4)

(Sorry For my english)

[K404]

What Clockgen setup are people using for the DS4 and the DQ6? (ie..what IC)

Thanks,

K

[ceemic]

PLL ending 509. I'm pretty sure all (Gigabyte) P35 can use it...

[rge]

My system won't POST with "Turbo" or "Extreme" options, only "Standard".
And this happens with or without overclocking.
Currently using BIOS F6.

I'm going to test max stable memory frequency with F6 and using stock volts (2.2v)
If it's not satisfactory I'll try F5 or F4.

In BIOS F4, standard, turbo, or extreme settings equates to a "performance" setting on memset of 11, and somewhat loose secondary memory timings. I thinks BIOS F4 all three settings are similar to BIOS F6 standard. (ie I dont think in F4 turbo and extreme changes much of anything).

In BIOS F6, standard gives a "performance" setting on memset of 10 with loose secondary memory timings. Turbo and extreme give a "perfomance" setting of 7 on memset, which equates to about 8% gain on Sandra memory bandwidth scores and tighter secondary timings.

Two possible issues.
If it is the too tight secondary timings on F6 turbo/ext, you can get around this. I am using BIOS F6 OC E6850 to 3.9, in extreme or turbo mode, but I had to manually set all my secondary timings first (trial and error to get tight as possible), then boot to turbo or extreme mode (they are same as far as I can tell after you manually hold timings). That way my secondary timings dont change (beyond the best I could get) and I get the improved 8% memory controller boost measured by sisoft sandra in F6 turbo or extreme.

However, I tried a Eurpean early version of F5? or F6? beta, dont remember, but on it turbo set the "performance" measured by memset to 6, and I could not boot with it. Just for fun, I had memset on 11, and when I changed to 6, my computer shut off. Point is, if "performance" on memset of 7 is problem on your mobo (like 6 was on mine), not the tighter secondary memory timings, then I dont know of a way around that. Then you have to use F6 in standard, or F4 in any mode (same as F6 in standard). You could test this by using memset with F6 standard and then manually changing performance to 7 to see if you can.

Since all mobo are different, and I have different ram, dont know if my settings would help, but will post if you want. I am rock stable on small ffts, blend, and pcie 16x. But if I change one setting, I get either loss pcie 16 to 1x or unstable or reboot issues.

I wish GB would let you manually change the performance in the BIOS, ie like 7, 8 , 9, instead of only two settings, 7 on turbo/extreme and 10/11 on standard.

[Cob]

Hey guys i just flashed F7b for my DS3P and-

- The PC Health menu now lists the actual current voltages for vcore, memory, +3.3v and +12v.



-The memory timings are now split into two sections, one for the main four and one for the sub-timings. I've no issue running the Turbo and Extreme options, tho I didn't try F6 and don't know if I would have had any issues selecting those options in F6.

-Vdroop and vdrop is now less. With 1.5325 set in BIOS I was getting 1.49v at idle and 1.46v under load according to Everest. Now I'm getting 1.50v at idle and 1.49v under load.

-Disabling Hyperthreading also disabled one of my cores. Re-enabling it allowed access to all four cores.

[SaleGseK]

Hey guys i just flashed F7b for my DS3P and-

- The PC Health menu now lists the actual current voltages for vcore, memory, +3.3v and +12v.



-The memory timings are now split into two sections, one for the main four and one for the sub-timings. I've no issue running the Turbo and Extreme options, tho I didn't try F6 and don't know if I would have had any issues selecting those options in F6.

-Vdroop and vdrop is now less. With 1.5325 set in BIOS I was getting 1.49v at idle and 1.46v under load according to Everest. Now I'm getting 1.50v at idle and 1.49v under load.

-Disabling Hyperthreading also disabled one of my cores. Re-enabling it allowed access to all four cores.

Whoa! Thats great! I mean, finally they reduce the huge vdrop, i hope it works the same on my P35-DS3R!!

[plguzman]

Good! now let's wait for a DS3R solution... I have to put the BIOS voltage at 1.55V to get 1.48V idle, and 1.44V load @ 3.7 :-O

[AgonxOC]

How is this? Bad Drop?

GIGABYTE GA-P35-DS4 Rev. 2.0

Or is the IP35-Pro is better?


Alex

[JoeBar]

How is this? Bad Drop?

GIGABYTE GA-P35-DS4 Rev. 2.0

Or is the IP35-Pro is better?


Alex

I had both, preferred IP-35 Pro.

[caligula]

No update for DS3R yet. Crossflash does not work from @bios or q-flash

[MuffinFlavored]

My P35-DQ6 no longer holds my FSB setting.
I can set it to 400x9, 400x6, 450x8, anything, it just boots at stock FSB, and my set multiplier.

Let me flash to these beat BIOs and see what if that fixes the problem.

Yeah, same thing happened to me but with the P35-DS3R, i couldn't make it work with overclock anymore, the solution, flash it back to stock bios (F4)

(Sorry For my english)

Thank you for your help.
This was my plan.
To downgrade the BIOS.

Epic fail.

The problem appeared in F6, so I went to F7a, when down to F5, then down to F4. All epic fail.

I will try F7a and clear the BIOs jumper.

EDIT:
Epic fail.
The BIOs cleared.
But any FSB above 267, is 267.

I tried updating, downgrading, "Load optimized fail-safe defaults", no turbo options are enabled, cleared CMOS battery with jumper, I may have, killed the motherboard I guess?

My Windows boots are like, 2 minutes and 50 seconds now.
And sometimes the drive isn't found.
And I am getting random freezes.

The most voltage I ever gave the CPU was 1.475v, and it didn't even POST.
The northbridge, the most whatever +0.2 is.
And, FSB, +0.2.

Well, I guess I'll just buy a Maximus Formula

[Skauneboy]

In BIOS F4, standard, turbo, or extreme settings equates to a "performance" setting on memset of 11, and somewhat loose secondary memory timings. I thinks BIOS F4 all three settings are similar to BIOS F6 standard. (ie I dont think in F4 turbo and extreme changes much of anything).

In BIOS F6, standard gives a "performance" setting on memset of 10 with loose secondary memory timings. Turbo and extreme give a "perfomance" setting of 7 on memset, which equates to about 8% gain on Sandra memory bandwidth scores and tighter secondary timings.

Two possible issues.
If it is the too tight secondary timings on F6 turbo/ext, you can get around this. I am using BIOS F6 OC E6850 to 3.9, in extreme or turbo mode, but I had to manually set all my secondary timings first (trial and error to get tight as possible), then boot to turbo or extreme mode (they are same as far as I can tell after you manually hold timings). That way my secondary timings dont change (beyond the best I could get) and I get the improved 8% memory controller boost measured by sisoft sandra in F6 turbo or extreme.

However, I tried a Eurpean early version of F5? or F6? beta, dont remember, but on it turbo set the "performance" measured by memset to 6, and I could not boot with it. Just for fun, I had memset on 11, and when I changed to 6, my computer shut off. Point is, if "performance" on memset of 7 is problem on your mobo (like 6 was on mine), not the tighter secondary memory timings, then I dont know of a way around that. Then you have to use F6 in standard, or F4 in any mode (same as F6 in standard). You could test this by using memset with F6 standard and then manually changing performance to 7 to see if you can.

Since all mobo are different, and I have different ram, dont know if my settings would help, but will post if you want. I am rock stable on small ffts, blend, and pcie 16x. But if I change one setting, I get either loss pcie 16 to 1x or unstable or reboot issues.

I wish GB would let you manually change the performance in the BIOS, ie like 7, 8 , 9, instead of only two settings, 7 on turbo/extreme and 10/11 on standard.

I don't know if it works with DQ6 but I know for a fact that the F3 BIOS for DS4 allows you to manually adjust the performance level. In that vesrion the tRD value corresponds to Memsets performance level. So I actually had to downgrade the stock BIOS to get the performance I wanted. Hope this helps.

[miahallen]

Does your pci-e works @ 16X?

That was the problem! I had also been having an issue with my music & videos (only the audio) not playing smoothly when doing ANY activity (even scrolling in a web page). After I found out about the x16 -> x1 issue, I investigated, and sure enough, I was running at x1.

I solved the problem based on reccommendations earlier in this thread. I manually set my PCIe clock to 110MHz in the BIOS, and raised my PCIe & MCH voltages slightly. Now I'm at x16 and posted a 3DMark06 score of 13,260

How is this? Bad Drop?

GIGABYTE GA-P35-DS4 Rev. 2.0

Or is the IP35-Pro is better?

Alex

I have the DS4 Rev2.0 and have found the Vdroop isn't too bad (F7 BIOS). My BIOS setting is 1.325V, CPU-Z shows 1.296V at idle and at load it flucuates between 1.264V & 1.280V.

[SySTaXer]

Thank you all guys for the responses and sorry for my late reply.

That was the main reason i ditched this board within a week...

PCI-E 1x prob appears when u're using MCH voltage over +0.2v. Try to lower that and see what happens. If the high vmch is required for your oc, then either lower your oc or get another m/b...

Yesss!! Thank you! the MCH Voltage over +0.2v is causing the problem. Anything higher than +0.2v on MCH and it will cause the PCIEX1 issue.

It works fine with MCH Voltage +0.2v .I am currently testing the stability of my overclock with MCH on +0.2v .I used to set it on +0.3v .

But certainly it shouldn't be like this cause some people may need to have more than +0.2 MCH Voltage to reach stability with their overclock.

I am not giving my P35-DS3P enough voltage to have the problem, but my old P5BDlx did the same thing, one trick i had with it and it usualy worked is when the x1 appears, shut it down, unplug the power cord and press the power button on the case a few times, then replug the cord and at least on the P5B dlx it was back at x16 after that

Thanks. That trick doesnt work in my case. The only way to get it back up to PCIEX16 for me is to pull out the graphics card completely waiting for 20 seconds then reseating the graphics card back into mobo. It will boot with correct PCIEX16 into windows but falls back to PCIEX1 again after a reboot unless I set the MCH Voltage to +0.2 or lower.

According to another forum
Set your PCIE freq. to 101 mhz. That will correct the 1x PCIe link width.

It appears this problem is caused if you alter the vcore voltage.. I'm still waiting for the board, but starting to get worried as I read more and more problems

Thanks. Yea I have tried increasing the PCIE Freq from 100 to 120 it didn't help and I am setting my Vcore on 1.5875 that is something I cannot change cause I need that much for a stable OC.


Thank you again JoeBear.


EDIT: Hmmm it actually seems that the combination of having the MCH voltage set to no higher than +0.2 / PCIE Voltage set to +0.2 and raising the PCIE Freq to 105 is fixing the problem in my case. I am so glad that I can keep my P35-DQ6.

[r4st4m4n]

I don't know if it works with DQ6 but I know for a fact that the F3 BIOS for DS4 allows you to manually adjust the performance level. In that vesrion the tRD value corresponds to Memsets performance level. So I actually had to downgrade the stock BIOS to get the performance I wanted. Hope this helps.

In my case too, on all the BIOSes I've tried (from F4 to F6), the tRD = performance level in memset.

On my system, I've manually entered all the memory timings and subtiming (except the last one which is on Auto since it seems to be the only value where I can boot). When I change the memory performance setting, it doesn't change anything (at least from the results I get from Everest).
Bu If I only select the 4 first memory subtiming, I did see it changed the memset performance level.

Then I've concluded that the memory performance setting is only useful if you don't manually enter all the memory subtimings. However I left it to Extreme just in case ...

[plguzman]

BTW, I have found that the PC won't resume from hibernation if the OC is too high. I am stable @ 3.7 for everything (even prime) but not for hibernation resuming.

I do a lot of hibernation and is kinda annoying to let the PC powered when nothing is being done (and also consumes a lot of power) or to being restarting a lot during the day, so I scaled back to 3.6 and even lowered my volts, and now hibernation works.

Anybody else had this situation? oh, this is Vista 64 btw...