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

[Lome]

i guess the 3 boards i bought not good enough proof
you think i cant use a voltmeter
and the last one i got is overvoltin the worst
2.1=2.26
2.2=2.40
what you call that
voltmeter is digital so i can read
i can rewire a house so i know my way around electricity lol

this is on the socket?

[RPGWiZaRD]

I think they are the same in real app performance. From my...er...feeling, i think F3 is just a little faster but F5 gives u better clock.

OK, thanks but I was wondering like memory read/write and latency, if F5 (F5G for DS4) can score same as F3 bios.

[zsamz_]

this is on the socket?

go learn to measure your volts n tell me how much yours is overvolting lol

[MaStA]

Well I'm having some problems. I had a P5B deluxe and it died so I went with the P35-DQ6. Everything is working great and I haven't noticed any problems until now. I was doing some overclocking just trying to get a measily 3.2ghz out of my E6400 which I was able to do on my P5B at like 1.4v. I can get it to boot no problem, but running orthos will freeze the computer within seconds or the highest I've seen is about 6 minutes. I even tried running it at 1.5v vcore, +.40v DDR2, +.20 FSB volt, and +.20 MCH volt with no luck. I am running my memory 1:1 with the clock 400x8 with stocking timings, etc. I even loosened the timings a little. Anyhow overclocking doesn't seem to be the real problem...I can't even run orthos without the computer locking up with everything stock. I do kind of feel stupid to say I killed my P5B with a multi meter lol...I wasn't paying attention and I think I touched two points with one lead. This leads me to ask...could this have harmed any other component or would it have just killed the motherboard as it did? Everything seems to be fine and the +12v, 3.3v, and 5v seem fine. Core temp is reporting in the 30's idle so that isn't an issue either. I was a little pissed about the overclock, but now I'm worried I can't even run orthos stock and not lock up. Any help is appreciated. Thank you in advance.

EDIT - Just to confirm the PSU's volts were fine I used a paperclip to get the PSU running and tested the +12, +5, and +3.3 and they read 12.04-12.05, 5.00-5.01, and 3.29-3.30. So it isn't the PSU I would have to say... I also ran Memtest and did not get any errors.

Jared

[zsamz_]

what voltage were you measuring?
btw my 6400 clocked better on my p5b
i just think we need better bois n board to mature

[MaStA]

what voltage were you measuring?
btw my 6400 clocked better on my p5b
i just think we need better bois n board to mature

On the P5B I was after the vcore and I think I touched two points on a mosfet. Oh well about that...ASUS can go to hell with their rude crappy support. I got a refund on that board through Newegg.

Jared

[MaStA]

Well a couple days ago I put new hard drives in and on an accident put Vista x64 on. Out of curiosity I put my old 80 gig hard drives back in with Vista x86 and orthos is running fine....

So I imagine it was a bad install of 64 bit or something because I know people who have no problems running Orthos on Vista x64. Either way I'm going to format the new drives and put 32 bit on and see if all goes well. Damn I'm pissed...I tore my whole computer apart to find this out... I'll report back after I'm done

Jared

[egraphix]

can anyone recommend a watercooled mosfet for the dq6? im looking at removing the fancy cooling device and place water blocks on hte south/northbridge. along with hte mosfets if available.

[RPGWiZaRD]

So noone knows how F5G / latest F5 BIOS of your motherboard compares to F3 in memory read/write & latency? I would test it out myself but I get the hardware on tuesday perhaps.

[Mysterfix]

Well a couple days ago I put new hard drives in and on an accident put Vista x64 on. Out of curiosity I put my old 80 gig hard drives back in with Vista x86 and orthos is running fine....

So I imagine it was a bad install of 64 bit or something because I know people who have no problems running Orthos on Vista x64. Either way I'm going to format the new drives and put 32 bit on and see if all goes well. Damn I'm pissed...I tore my whole computer apart to find this out... I'll report back after I'm done

Jared

Glad to see you got it figured out.

[MaStA]

Glad to see you got it figured out.

Yeah but Reggie I don't think I found my answer. Anyhow I used a iso file from my school to install x64 this time. A while back I used a downloaded copy of x64 and it worked fine. Of course I'm using a legal key from my school. Anyhow, maybe the iso from my school was corrupt or the install itself was. Anyhow to get to the bottom of it I just installed x64 from the original cd I had from a while back. We shall see...otherwise I will try 32 bit on the new hard drives and if I still have an issue then...I'll worry about that then lol.

Jared

[Mysterfix]

Well how long did orthos run on the old drives? It may just be down to a voltage issue now, unless your running with everything @ stock settings. Either way you should start out with a fresh install windows and see how far you get.

[MaStA]

Well how long did orthos run on the old drives? It may just be down to a voltage issue now, unless your running with everything @ stock settings. Either way you should start out with a fresh install windows and see how far you get.

Well with everything aside and a fresh install of Vista x64 from a different cd...over an hour running orthos and still running great. Looks like either the cd was corrupt or the install didn't go well. Either way I'm a happy camper. So all along I thought my cpu was crap and it was a corrupted install.

Jared

[Lome]

go learn to measure your volts n tell me how much yours is overvolting lol

BIOS 2.2
SOCKET 2.18 at load
go away


measure the socket then i will belive your overvolt story

[zsamz_]

BIOS 2.2
SOCKET 2.18 at load
go away


measure the socket then i will belive your overvolt story

btw the measure point is not a socket

[berdde]

Does any one have problem about power/standby on DS3R? My board keeps giving me issues related to it. Gigabyte support is not very helpful and keeps talk about overheat or power supply issue, kept talking about putting PCIE_12V power although I have told him twice my video card does not have PCIE_12V connector. (low end 2400PRO card) But my e6600 is hardly overheat, core temp 45C idle/65C load, and my Seasonic S12 500W has been awesome in doing it's job on the other board.

Problems on this system let me think it's DS3R related:
1) resume from standby doesn't work for USB mouse/keyboard. Unfortunately I do not have PS/2 keyboard/mouse. It's kind of ridiculous that this is not supported.
2) When hit power button, first LED will come up, just a flash then go down. And go up after 5 seconds. It does this every time.
3) Occasionally the system will shutdown/restart out of no reason at all - not running heavy apps, no gaming on this system.
4) Happen once, hang during Windows trying to go to standby mode.

I really doubt that this board has some design problem about ACPI/standby, etc. Any one has similar problem?

Is there a way to isolate the problem beside getting another motherboard?

[NJDevilsFan21]

I have a P35-DQ6 on the way. Can anyone who has this board recommend good FSB/MCH voltages for 400FSB?

Also, hows the PWM area in terms of temps with quads? I don't care about dual cores because those don't raise the PWM temps nearly as much as a quad will. Will I need a fans over the giant array of heatsinks?

[slayer_warrior]

Does any one have problem about power/standby on DS3R? My board keeps giving me issues related to it. Gigabyte support is not very helpful and keeps talk about overheat or power supply issue, kept talking about putting PCIE_12V power although I have told him twice my video card does not have PCIE_12V connector. (low end 2400PRO card) But my e6600 is hardly overheat, core temp 45C idle/65C load, and my Seasonic S12 500W has been awesome in doing it's job on the other board.

Problems on this system let me think it's DS3R related:
1) resume from standby doesn't work for USB mouse/keyboard. Unfortunately I do not have PS/2 keyboard/mouse. It's kind of ridiculous that this is not supported.
2) When hit power button, first LED will come up, just a flash then go down. And go up after 5 seconds. It does this every time.
3) Occasionally the system will shutdown/restart out of no reason at all - not running heavy apps, no gaming on this system.
4) Happen once, hang during Windows trying to go to standby mode.

I really doubt that this board has some design problem about ACPI/standby, etc. Any one has similar problem?

Is there a way to isolate the problem beside getting another motherboard?

in bios in power management setup can u give list on how u have it setup or pic of that bio screen.
add: and what os u are useing.

[zsamz_]

I have a P35-DQ6 on the way. Can anyone who has this board recommend good FSB/MCH voltages for 400FSB?

Also, hows the PWM area in terms of temps with quads? I don't care about dual cores because those don't raise the PWM temps nearly as much as a quad will. Will I need a fans over the giant array of heatsinks?

i'm @ 525 +3 n +3

[MaStA]

Well I'm having some problems. I had a P5B deluxe and it died so I went with the P35-DQ6. Everything is working great and I haven't noticed any problems until now. I was doing some overclocking just trying to get a measily 3.2ghz out of my E6400 which I was able to do on my P5B at like 1.4v. I can get it to boot no problem, but running orthos will freeze the computer within seconds or the highest I've seen is about 6 minutes. I even tried running it at 1.5v vcore, +.40v DDR2, +.20 FSB volt, and +.20 MCH volt with no luck. I am running my memory 1:1 with the clock 400x8 with stocking timings, etc. I even loosened the timings a little. Anyhow overclocking doesn't seem to be the real problem...I can't even run orthos without the computer locking up with everything stock. I do kind of feel stupid to say I killed my P5B with a multi meter lol...I wasn't paying attention and I think I touched two points with one lead. This leads me to ask...could this have harmed any other component or would it have just killed the motherboard as it did? Everything seems to be fine and the +12v, 3.3v, and 5v seem fine. Core temp is reporting in the 30's idle so that isn't an issue either. I was a little pissed about the overclock, but now I'm worried I can't even run orthos stock and not lock up. Any help is appreciated. Thank you in advance.

EDIT - Just to confirm the PSU's volts were fine I used a paperclip to get the PSU running and tested the +12, +5, and +3.3 and they read 12.04-12.05, 5.00-5.01, and 3.29-3.30. So it isn't the PSU I would have to say... I also ran Memtest and did not get any errors.

Jared

Well after lots of testing and going through stuff to try finding out what the issue was I have come down to this...

I believe Kaspersky 7.0 is the problem. Seeing that a clean install of Vista x64 ran orthos fine until I put Kaspersky 7.0 on it. After uninstalling Kaspersky 7.0 orthos runs fine again. Whether Kaspersky in general won't work well with Vista x64 or if it is just 7.0. I know 6.0 works fine with Vista x86.

So my question is...

Does anyone run Vista x64 and Kaspersky 7.0? If so, do you have any problems with running orthos?

Thank you,
Jared

[berdde]

in bios in power management setup can u give list on how u have it setup or pic of that bio screen.
add: and what os u are useing.

I used to enable Power On By Mouse and Power On By Keyboard, found they did not work so restore BIOS to factory default. Now it is as follow.


It might be my illusion but after restoring BIOS to default, the random shutdown/restart (item 3) no longer happens. (Used to be once or twice each day in the first two days.)

OS is Windows XP Pro SP2
All drivers appear to be loaded okay. No unknown device in Device Manager.

[slayer_warrior]

Power On By Mouse and Power On By Keyboard leave that disable. u should be able to awake from standby with them disable at least i can useing usb mouse.

i had same problem as u did but i change few setting in xp pro sp2 and in bios u can try this.

acpi susepend s1 (pos)
soft-offbypower-bttn (delay4sec)
leave the rest in default

add: in windows i change some setting in screen saver then click power make sure ((standby, turn monitor off,turn off hdd))i have them set to never. i don't have that problem any more.

[lukeo]

Anyone know what Gigabyte broke in F11b and F12 bios? F10 and F11a work great on my board I run 3.6ghz stable (515FSB) around the clock folding.

Flashing to F11b or F12 and I cannot boot over 400FSB, no matter voltages or timings.

The one problem I have is sometimes the PC doesn't startup after I reboot and I have to reset it (with the button) and then it's away again. This is noted as fixed in F12 which is why I was interested in flashing to that bios revision.

I don't want to lose 115mhz of FSB headroom just to have my computer reboot successfully 100% of the time. Any thoughts?

[r4st4m4n]

Anyone know what Gigabyte broke in F11b and F12 bios? F10 and F11a work great on my board I run 3.6ghz stable (515FSB) around the clock folding.

Flashing to F11b or F12 and I cannot boot over 400FSB, no matter voltages or timings.

The one problem I have is sometimes the PC doesn't startup after I reboot and I have to reset it (with the button) and then it's away again. This is noted as fixed in F12 which is why I was interested in flashing to that bios revision.

I don't want to lose 115mhz of FSB headroom just to have my computer reboot successfully 100% of the time. Any thoughts?

Wrong thread. Here is is for the P35-DS*/DQ6

[jacek]

I have a P35-DQ6 on the way. Can anyone who has this board recommend good FSB/MCH voltages for 400FSB?

Also, hows the PWM area in terms of temps with quads? I don't care about dual cores because those don't raise the PWM temps nearly as much as a quad will. Will I need a fans over the giant array of heatsinks?

Your system should be stable with default voltages.
I'm at 490 without increasing voltages on the mainboard.