Gigabyte P35 Motherboard Thread

[Keystone63]

Kougar, thanks for the help with the power issues. It turned out to be the case must be hooked up the power LED. Guess it is some kind of ground issue......... but seems I am left with the same problem I had for getting the Gigabyte P35C-DS3R.

The reason I am calling this a DMA problem is because I have used different versions of NERO Burning ROM..5,6,and 7 and this prblem has just started up about 3 months ago. I have changed motherboards, burners(HP-Sony-LG interals)all + and (-)R DVD, different media with the same outcome...... have to say up to now it is only internal not with external hardware. Now the PROBLEM........................ I use NERO for burning DVD's of weddings, partys, sporting events etc. ...Mainly because burner Rom has the multiple burners feature so if I have 10 copies of a wedding to do I can get them done with the 2 internal and 2 external burners done faster. I have been doing this for a years and all of a sudden my multiple burn will not work after 12% copies, well it works just takes 4x the time to complete. The burn buffer will LOCK on both burners when working good, then after 12% it wont lock. It keeps switching back and forth between them hence taking for ever to burn. One burner at a time works great, both together not at all.

Same outcome with Three(3) different motherboards and a GIG of memory. Don't know if it is DMA not working write but did in the past. Or Nero software glitch, which Nero WONT comment on this even after writing to tem about it 3 times.

Is there other software out there which will let you use multiple burners?
And like I said, it doesnt affect external if I just run them through USB.
Hope this was enough to give someone a thought on this issue, or how to let Nero know about it.

Thank You All for your time.

 

[Makall]

I've been thinking of building my first PC soon and have decided on the Gigabyte P35-DS3R since it seems pretty good for the price, but upon finding this thread and a few others on google, this motherboard isn't that good is it?

So basically, it just starts up once then once it turns off, you're pretty much out of luck? Rapid powering up and powering down?

Should I get an Asus P5K instead? This is gonna be my first hand built PC, so I'd like as least problems as possible. I don't mind spending a couple more bucks buying a better board if it'll save me some of the grief that many users in this thread seem to have suffered. Is this booting problem only on the first couple batches of this model of motherboard or something, have they fixed it?

Thanks for any help.

 

[MRGOOCH]

Is there any important reason for installing the F5 Bios?

 

[mylittlepony]

Originall posted by: Makall
Should I get an Asus P5K instead? This is gonna be my first hand built PC, so I'd like as least problems as possible. I don't mind spending a couple more bucks buying a better board if it'll save me some of the grief that many users in this thread seem to have suffered. Is this booting problem only on the first couple batches of this model of motherboard or something, have they fixed it?

My system unceremoniously shuts down at least once a day, which is not cool. It's not clear whether it's a motherboard issue or the fact that I'm running Vista x64. The DS3R has received lots of good reviews at various hardware sites, and putting it together and adjusting the BIOS was fairly easy.

Originally posted by: MRGOOCH
Is there any important reason for installing the F5 Bios?

Unfortunately, the only thing listed for the F5 beta and final was "enhance PS2 keyboard," whatever that means. It would be nice if Gigabyte put together a real release note doc. That said, I installed it yesterday, and so far, no random reboots. I'll report back if that changes. (I am using PS2 keyboard and PS2 mouse so that I can avoid having to use a USB hub...so it's possible whatever changed in F5 could help me. We'll see....)

 

[bartmannz]

F6 didn't fix my fan issues so it must be something else. I'm going to try a stock fan.

 

[lightzout]

OK I wanted to chime in with my latest success of stable gaming at 3108MHz (7x444) after lots of reading and sporadic tweaking without much luck. I would try something new and then play for a few days before making any changes but couldnt seem to get very far beyond 2.6g until I stumbled across 444x7 while running the memory at different ratios and speeds. I honestly still dont get how it works other than that I may have been better off with the 800dDr2 @4-4-4-12 timings. I cant afford to buy more memory so just decided to experiment with what i have. I was getting BSoDs when idle so i thought it may be memory related and also changed the optimized default of turbo back to standard which may have stopped the BSoDs if it wasnt lowering the ddr fsb. So now my mem. freq. is 444/ FSBRAM 1:1/5-6-6-17 (set to auto) but its only getting 1.8volts. Speedfan released a new beta today which shows my temp1 as 43c and temp at 32c idling. i still need to check in at the bleeding edge to see what else i can to do get best results with the current ram but since i rarely to get play as it is I havent had a ton of motivation to start pushing upward yet. That said I would like to get closer to Kougar's 100% OC as long as its going to improve in-game performance.

 

[bartmannz]

Just incase anybody has fan issues, I found that the problem with my Fan not working was probably caused by the fan drawing too much current on startup. If I fit a standard type 1500 rpm fan everything works fine, if I fit the 2200rpm speed one it doesn't. Since my system is all overclocked I want to keep it cool so using an aftermarket fan controller. I'm never been a big fan of running fans off the motherboard connectors anyway

 

[Acanthus]

This is a great overclocking board (rig in sig) however, for some reason if i go over about 440fsb, windows only sees 2 of the 4 cores.

Orthos only sees 2 cores, and windows still calls it a core 2 quad, but the performance tab of the task manager only shows 2 cores...

Increasing vfsb, vcore doesnt help

Increasing PCI-E doesnt help

Memory is set to 1:1 and works fine at 335x3

 

[Maxtr0sity]

Long post, big problem. I'm praying someone can help me on this.

My setup:
E6750 on Tuniq, GA P35-DS3R, 2GB Ballistix, Corsair 520HX, 1950Pro

I built this rig about 2 weeks ago, no major problems until now. It will not POST.

I've stripped the rig of all its peripherals, all that's connected is RAM, heatsink/fan, CPU, and the 2 power cables (2x12 and 2x2). I'm currently powering on the system by shorting the two connectors on the mobo (red colored).

When I power on, the computer powers on for 3 seconds, shuts off. Pause 3 seconds, it'll power on again and repeat process.

I have done zero overclocking. Last thing I remember doing is upgrading the BIOS from the @BIOS utility from F4 to F5e, then I tried to update again, got an error. This last statement being the only possible reason for failure.

I've changed the CMOS battery, cleared CMOS, no avail, powers on...then power off.

If I take out the CPU, the mobo remains powered on however.

I can't RMA this because stupid me, I've thrown away the box that came in it.

 

[de8212]

WHich board would be best for me? System in sig. i am getting rid of the 680i but will reuse the rest.

Looking at GA-P35C-DS3R
and
GA-P35-DS3P


Will the tuniq have a problem fitting on either board? I seem to remeber reading a review that it could touch some of the caps. Anyone confirm or deny this???


EDIT - I also read somewhere (maybe even in this thread) that there was going to be a revision 2 of these boards. Has this been confirmed and are these available yet? Any links to find out waht the differences are in Rev 2???

 

[SerpentRoyal]

Originally posted by: Maxtr0sity
Long post, big problem. I'm praying someone can help me on this.

My setup:
E6750 on Tuniq, GA P35-DS3R, 2GB Ballistix, Corsair 520HX, 1950Pro

I built this rig about 2 weeks ago, no major problems until now. It will not POST.

I've stripped the rig of all its peripherals, all that's connected is RAM, heatsink/fan, CPU, and the 2 power cables (2x12 and 2x2). I'm currently powering on the system by shorting the two connectors on the mobo (red colored).

When I power on, the computer powers on for 3 seconds, shuts off. Pause 3 seconds, it'll power on again and repeat process.

I have done zero overclocking. Last thing I remember doing is upgrading the BIOS from the @BIOS utility from F4 to F5e, then I tried to update again, got an error. This last statement being the only possible reason for failure.

I've changed the CMOS battery, cleared CMOS, no avail, powers on...then power off.

If I take out the CPU, the mobo remains powered on however.

I can't RMA this because stupid me, I've thrown away the box that came in it.

Who said you cannot RMA the board without the box? Send it back to the factory. If you cannot flash back to the F4 BIOS, then you'll probably need to replace the BIOS chip. I would also try to reboot with a known good PSU (probably the same problem).

 

[Maxtr0sity]

I've tested my PSU with a multimeter, everything checks out according to specs.

Since I bought it at newegg, I've read their policy and it states they need everything for a RMA (including the box), so should I RMA to Gigabyte?

Are there any other ways to flash the BIOS without booting? The closest thing I can think of is clearing CMOS, but that didn't work.

 

[davidwiz]

I had a similar problem with a GA-P35C-DS3R. Ran for 1 day without problems then wouldnt boot, fans started for a few seconds, but then shut down. The power supply was a brand new Antec 430 but I checked the PSU with another motherboard and checked the PSU with an Antec powersupply tester, everything checked out. RMA'd the mother board and got a new motherboard and it wouldnt boot but the fans stayed running this time. I ended up pulling a power supply from another comp and it booted the new motherboard fine. The new Antec works in other comp and worked for this motherboard for 1 day but wouldnt boot up the GA-P35C-DS3R anymore for some reason.

 

[Maxtr0sity]

I don't think it's the power supply's problem though, I've tested the power supply by shorting the green and black, all the leads have correct and stable voltages.

 

[lightzout]

I am curious about Maxs problem. This sounds like its cycling but unable to load the bios. Have you tried holding the DEL key during the entire reboot to get into the bios? Also, have you tried booting from a floppy into the bios flash application? Maybe someone can answer this- why not look at whether its a failure with the cpu or ram? I would try using one stick of ram, different ram slots, different vid card (do you have an old pci card?) Did you double check to make sure you are using right power connects from your psu? I have the 24-pin main hookup and the 8-pin connected with modular cables from the corsair 520 myself. I was unsure at first since the mobo shipped with a plug covering 4 of the pins. the fact it is booting at all makes me think you are clser to finding a simple error somewhere in the bios or hardware setup but if not Gigabyte will probably be happy to rma it. If you haven't done an RMA its usually a hassle free process since companies want to keep customers. I have only had one bad RMA experience and that was with GEIL sending me back bad ram. i haven't had to rma to gigabyte yet but two emails i sent to support went unansered and they dont have much in the way of support on their site so i guess they depend on the strength of their hardware and the endusers ability to go elsewhere for help.

 

[mylittlepony]

F6a BIOS just released today, though the note is very similar to the F5e: "Fix PS2 keyboard compatibility issues"

I'm using a PS2 keyboard (and a PS2 mouse). How about everyone else? I still get blue screens once or twice a day (very randomly, doesn't appear to be load-related). It's still very possible it's more of a Vista x64 issue, though.

 

[lightzout]

I am using the v5 BIOS from Gigabytes support page and if i have had any BSODs since it may only be once or twice and it seems like its always when idle with no programs running. I also selected minimal power management under power options but i may use always on as well since i suspect the idle driver issues may have come from hardware powering down but thats a guess. i still havent had time to see what i can do with my memory voltage and pci-e to boost game performance and maybe get the fsb over 444x7

 

[Drexl]

The problem Maxtr0sity has which may be related to the BIOS update is the reason I decided to get the DS3P, which has dual bios that overwrites a bad flash with a backup. I've also heard that using the @BIOS utility is not as safe as flashing from the non-Windows utility. I used a flash drive and it couldn't be easier.

To address a comment made a few pages ago about the dual bios feature: it doesn't just give you a chip to mess up and a spare. The backup chip will overwrite the bad flash with its BIOS while leaving the backup intact, and the backup can't be accessed by the user. So, you could have many bad flashes since the backup would be there to overwrite again and again.

 

[Rebel50]

I was wondering if anyone using the new 1333fsb C2D's E6750/6850 still has the double post/boot issue when overclocking using the P35 motherboards.

I currently have an E4400 with a P35 DS3 and the only way around the double post/boot issue I have found is to use either the 3.33 or 4 ram multiplier. The only problem with using these multipliers is that when you start raising the FSB, I start to run into problems overclocking my RAM

Current settings are FSB = 285 X 10 (2850 mhz) RAM @ 3.33 = 475 mhz @ 5,5,5,18 / 2.0 volts.

The chip is capable of more than 3.2 ghz, but my RAM is unstable over 500 mhz - which is not surprising since they are only Corsair PC6400 DDR2 - using ProMos chips.

Obviously I would not be able to overclock a 1333 FSB CPU very far using such a high RAM multiplyer, if I run into double post/boot problems.

Any feedback would be appreciated.

Thanks

 

[EdibleTarget]

Well, I ended up RMAing my old board with the core problems AND cold boot problems, and the board I have now only has the cold boot problem minus the clicking noise. It seems to forever start and hang, then reboot itself until I turn the PSU on and off on the back of the case. My specs can be found in the middle of this thread on page 10.

I tried increasing the voltage to my RAM, I tried Option 2. Is there anything I can do before I just return this mobo for an eVGA?

 

[Rebel50]

Originally posted by: Rebel50
I was wondering if anyone using the new 1333fsb C2D's E6750/6850 still has the double post/boot issue when overclocking using the P35 motherboards.

Well in reply to my own post - I picked up an E6750 to replace my E4400 and am happy to say that the double post/boot issue is gone at last

Would this be due to the new chip having a different "strap" than the old 800 FSB chip ?

Anyway I am very happy with the replacement - currently running at 3.4ghz @ 1.38 volts, CPU temps at 50 deg when running Orthos - this is almost 10 deg lower than the E4400.

 

[PAPADOC]

Yup, I got the P35-DS3R and the Q6600.

And I am very pleased with the results.

To give you an idea on how far you can push FSB with the 9x multi, I can go to 430 mhz and it will boot into windows and not crash unless i run orthos or play a game (for a while).

I usually will keep it at 420 FSB for more stable performance.

I haven't yet searched for the FSB that will be stable with Orthos, although I did bench orthos for 30min. at 400FSB and it did not crash, hence that's 3.6 Ghz and I am happy with that.

So I think this board has a FSB limit at 430 mhz with 9x, I lowered the multi to 7x but that only got me to 450 FSB.

I am running bios version F6a

Also I noticed, that in the bios the cpu voltage 1.7v & 1.9v are missing.
Hence after 1.6v you can only select 1.8 (which fails to boot) and i didn't try 2.0v.

This is bad cause if i could choose 1.7 I will bet I can hit 4 Ghz for sure.

So yes this board is great for the Q6600.

 

[PAPADOC]

Hey Maxtr0sity,

the exact same thing hapenned to me after i set the cpu voltage to 1.8v.

Same stupid loop.

but 1 of the following 2 things fixed it (I can't remember which one) :


I cleared the bios for about 1-2 min. then rebooted.

or

I cleared the bios for about 1-2 min. then powered on the pc by pushing and holding-in
the power button for maybe 20 seconds, then the pc rebooted again.


Hope this helps.

 

[speckedhoncho]

I have seen that most P35 boards' memory bus speed is listed as 1066. Can DDR2-800 work on most boards? Is it a sketchy situation?

I want to use OCZ's DDR2-800 modules which have a CAS of 3, and the board I am considering is the MSI P35 Platinum. Knowing that the board's BIOS releases have brought wrath upon people, should I attempt this combo?

 

[kallekill]

I got a Gigabyte P35-DS3 and when I go into BIOS and PC health monitor I get pass on everything except "DDR 18v" which gets fail. I have used over voltage to run my ram at 2.2V (It is designed for 2.3V). Is this the reason? Also when the system boots I get the thing were it starts to boot, then shuts down and boot like normal which I have heard is pretty common. I read that it could be because some memory settings and that the system is unstable after this, but I have had no problem. This booting thing doesn't happen every time either. About 50 % of the time or more.