*** Official Gigabyte P965-DS3 Thread ***

[tenax]

only problem i had was overclocking capability with the lite-on and my beyond tv pvr front end would not work with it (the dvd burner plugin)

in both the lite-on and pioneer cases, the drives were automatically detected. i use the orange ports for both my sata hard drives and dvd burner. the lite-on was automatically detected as udma 5, the pioneer as udma 4. in both cases, they showed up in system properties as cd/dvd devices..no drivers needed to install with xp, just like a regular ide burner

 

[tenax]

Originally posted by: EXman

Originally posted by: tenax
i assume you have the onboard sound enabled (azalia or whatever it is called) i have read a few threads about sound issues..i'll try to find it and give you a link..but i recall something about getting the latest realtek sound drivers..have you tried the latest on the gigabyte website or just ones on cd? in terms of the dvd drive reading as an scsi, my prior experience says to me that you've put the dvd drive on the jmicron (purple) connector which causes it to be read as a non ide device..whether sata or ide, you can set the drive options as legacy ide so they are seen as ide (see early post from cheeta a few threads back) and use the orange sata ports. the only reason i see to use the purple is if you are going with raid on your hard drives...or your orange sata ports are full up otherwise. you should not have to install any drivers with winxp when using the orange ports. any dvd burner and ide or sata hard drive will be detected and windows native drivers will take care of business and sata drives will simply look like ide devices. (with no performance loss)

I have the drivers from the website yes those are downloaded for everything including the audio. You mean the sound enabled on the BIOS? I'll check that but I think I already did that... Just checked and it is set to AUTO so it is in good shape there.

the DVD drive I am having no problems with the drive is a PATA and not on the sata headers. I just mentioned that because it was the only piece of hardware that turned up as a possible device to add drivers for when trying to add the AUDIO under add hardware.

i've read a thread over at pcper.com talking about an additional device that people couldn't figure out what it was. it's apparently one of the 2 things..either the audio...or sata device on one of the purple ports. and yes, auto should work on the audio..but i'm told don't use the gigabyte drivers..find the realtek page and download the latest drivers for whatever os you are running is the way to go

 

[SchoolBus]

has anyone tried OCZ2P8002GK Platinum XTC Edition memory with this board. As i already have my ram and need to find a board for it.

thanks

 

[tenax]

the only issue i've read about is that "some" people have not been able to get some ocz memory to boot because it is 2.1 volts rated versus 1.9 like corsair..but that's only some people. the recommendation has been if running a higher default voltage memory like that to get a cheap stick of 1.8 or 1.9 rated memory , set your ram voltage to 2.1...where i would be worried about that is what happens if your board gets set back to default settings..kind of a pain..and you definitely would want to own, not borrow a stick in that case

 

[econnelle]

Help!

I had a Foxconn P965 board that I liked but the OC options were nil. I decided to swap out to a DS3 and moved over my hardware. This stuff is less than 2 weeks old so I know none of the carry over equipment is defective.

I had the old system running RAID 0 off of the ICH8R controller. When I pulled the MB out I went into the RAID controller and deleted the array and set both drives back to normal.

Swapped out the board and hooked everything up, created a new array.

I boot off the Vista CD, pick the drivers for the RAID controller and it identified the array. Created a 65gig partition and Vista loaded.

On reboot I get a BSOD, its too fast to catch but in safe mode it locks up on CRCDISK.SYS.

I'm thinking maybe something bad is left over from the previous RAID config. I know in the past with some of the older controllers you needed to zero out the drives completely before moving them to a new controller.

I download Seatools and connect the drivers to the standard controller. During this whole time I find out I need to set the SATA ports to Legacy and figure that is my problem with Vista which I'm sure a few of you will tell me after reading what I wrote.

However being diligent I go ahead and load Seatools and zero out each drive. It fails to write to LBA 0 on one of the drives, the one with the RAID info. So I hook it back up on RAID, go into the controller and remove the array.

Boot into Seatools again and it fails to write out LBA0 on one of the disks again. Fails to do the other erase functions too. I get on the phone with Seagate about how to really zero the drive out. While waiting I reboot again and this time Seatools lets me zero out each drive and everything looks like its good. They both will zero and pass test.

The only 'error' I get is booting Seatools it tells me Invalid Partition table on Drive 0 and Drive 1 which I assume is correct since I totally wiped the drives.

So back onto the RAID controller. Create the array, boot Vista DVD, load the drivers.

Finds the array, create a partition. The SATA drives are set to Legacy in the BIOS...I hit next and get:

[/b]Windows Cannot determine if the computer contains a valid system volume[/b]

Run Seatools again and both drives check out....

Any idea's?

I'm assuming my BSOD was from not having the SATA drives set to Legacy but now I can't even get the system to load period.

I can't imagine I FUBAR'd the drives.

Thanks!

 

[Glenn]

You might check out my posts above because I had very similar problems and finally ironed them out with different drivers.

Originally posted by: econnelle
Help!

I had a Foxconn P965 board that I liked but the OC options were nil. I decided to swap out to a DS3 and moved over my hardware. This stuff is less than 2 weeks old so I know none of the carry over equipment is defective.

I had the old system running RAID 0 off of the ICH8R controller. When I pulled the MB out I went into the RAID controller and deleted the array and set both drives back to normal.

Swapped out the board and hooked everything up, created a new array.

I boot off the Vista CD, pick the drivers for the RAID controller and it identified the array. Created a 65gig partition and Vista loaded.

On reboot I get a BSOD, its too fast to catch but in safe mode it locks up on CRCDISK.SYS.

I'm thinking maybe something bad is left over from the previous RAID config. I know in the past with some of the older controllers you needed to zero out the drives completely before moving them to a new controller.

I download Seatools and connect the drivers to the standard controller. During this whole time I find out I need to set the SATA ports to Legacy and figure that is my problem with Vista which I'm sure a few of you will tell me after reading what I wrote.

However being diligent I go ahead and load Seatools and zero out each drive. It fails to write to LBA 0 on one of the drives, the one with the RAID info. So I hook it back up on RAID, go into the controller and remove the array.

Boot into Seatools again and it fails to write out LBA0 on one of the disks again. Fails to do the other erase functions too. I get on the phone with Seagate about how to really zero the drive out. While waiting I reboot again and this time Seatools lets me zero out each drive and everything looks like its good. They both will zero and pass test.

The only 'error' I get is booting Seatools it tells me Invalid Partition table on Drive 0 and Drive 1 which I assume is correct since I totally wiped the drives.

So back onto the RAID controller. Create the array, boot Vista DVD, load the drivers.

Finds the array, create a partition. The SATA drives are set to Legacy in the BIOS...I hit next and get:

[/b]Windows Cannot determine if the computer contains a valid system volume[/b]

Run Seatools again and both drives check out....

Any idea's?

I'm assuming my BSOD was from not having the SATA drives set to Legacy but now I can't even get the system to load period.

I can't imagine I FUBAR'd the drives.

Thanks!

 

[Cheex]

Originally posted by: tenax
only problem i had was overclocking capability with the lite-on and my beyond tv pvr front end would not work with it (the dvd burner plugin)

in both the lite-on and pioneer cases, the drives were automatically detected. i use the orange ports for both my sata hard drives and dvd burner. the lite-on was automatically detected as udma 5, the pioneer as udma 4. in both cases, they showed up in system properties as cd/dvd devices..no drivers needed to install with xp, just like a regular ide burner

Good because I don't want to buy any trouble on myself.
I'll probably get the Samsung SATA DVD-RW in about 2 weeks.
I'll let you know how it goes then but in the mean time, please check out my other thread:
E6300/DS3/G.SKILL/Tuniq


Thanx guys.
:beer::beer:

 

[econnelle]

Glenn,

Thanks I'll be searching.

I fixed the drive issue...don't know how exactly, just went back through the entire procedure again. I'm back to the BSOD and lock up on CRCDISK.SYS.

 

[Madmanxer]

Another success story.

I replaced an MSI 965 Platinum due to poor overclocking ability with a DS3 rev 3.3 last night.

System booted perfect, I went right to bios and got 8 * 400 on my 6400 with absolutely no other changes. Tonight I'm going to clean install XP and do some benchmarking.

Another happy Gigabyte owner!

 

[econnelle]

Glenn,

Thanks for the link. That fixed it right up!

Runs great so far. Running a E4300 at 2.4ghz right now and will go farther once I play around with it a bit more.

Only 2 minor problems. When swapping to the admin permission screen it gets jumbled instead of going dark. Also the performance thing won't update. It reads 1.0 for the 8800 until you install the drivers. I installed the drivers and it runs through the update but never refreshes the numbers.

 

[EXman]

Driver for realtek Audio. this is what you need for the DS3 Audio!

Thanks Tenax for getting me in the right direction!

 

[econnelle]

Short lived excitement

Booted up, loaded the Nvidia drivers, all was well. The video issues went away but it still insists on being at a 1.0 for video performance.

Downloaded the Adrianne demo, so slow and sound break up constantly. I had this on the Foxconn board and then it went away on its own. Downloaded all the demo's for the 8800 and all the same issue.

Run Supreme Command and initially its ok but you get crackling from the audio, heavier you get into the game the more performance issues pop up because of sound.

Ran 3DMark 06, starts out ok but when you run the demo once the ships start flying out of the big carrier its jumpy and with a lot of static.

Even with the sound disabled it does it...using the latest Nvidia Vista driver for the 8800.

Checked all my settings but it does it at stock 1.8ghz, 2.4ghz, and 3.0ghz.

If I can get this fixed I'll be very happy. I put it to 333mhz bus speed, voltage to Auto and it's been running perfect all night.

Any clues on the sound issue? I am running the 1.6 driver.

 

[DemiAjax]

hey all, first time builder here, any help would be appreciated.

Building my new DS3/e6300 rig. Bench testing my 1900gt, 2 gb, ds3, e6300 with Arctic cooling freezer 7 outside of my p180. Antec trio 650 PSU.

Plug in necessary cables, hit power switch on front of case. Rig powers up. Hadn't plugged it into my CRT yet. Turn rig off, plug into CRT. Rig powers on, CPU cooler and graphics card spin regularly, no POST visual on CRT. Turn rig off, resecure connection to monitor. Hit power button on rig, no power, no nothing.
What gives?
Any suggestions?
I don't know if it's the PSU or the mobo, or if i'm screwing something up basic.
12 V and 24 pin are connected. GPU is connected to PSU.
I'm confused.

Edit: Bought thermaltake PSU tester, seems my PSU is in order. Does this mean my mobo is a lemon? Guess I have to RMA it back to Ewiz unless anyone comes up with any other ideas.

edit: resolved, man i'm dumb, haha

 

[JJordan]

Will this MB have any trouble with 4 Gig of memory (4 x 1gig sticks)?. I have 2 gigs now. Ad-Dta at new egg is $120. Thinking about adding 2 gig. Not overclkocking memory so I think the memory woudl work but not if MB has trouble with all 4 slots full.

 

[vailr]

Originally posted by: JJordan
Will this MB have any trouble with 4 Gig of memory (4 x 1gig sticks)?. I have 2 gigs now. Ad-Dta at new egg is $120. Thinking about adding 2 gig. Not overclkocking memory so I think the memory woudl work but not if MB has trouble with all 4 slots full.

Requires a 64 bit O.S. to fully utilize all 4 GB of memory.
A 32 bit O.S. can only access about 3.2 GB out of the 4 GB.

 

[Bozo Galora]

@DemiAjax

Care to let everyone else in on what silly thing you did?

 

[DemiAjax]

Was benching it outside of case, and it was grounded by my anti-static wrist band that I took off and forgot to remove the copper from mobo =P

Another few questions though:
According to TAT/Core Temp my cores are at about 63 C each while running dual Prime95, on a 6300 @ 2.1 ghz, should I reseat my HS (Arctic COoling Freezer 7) and reapply some Arctic Cooling MX-1?

If so, what's the best way to apply it? One even line down the center of the chip? Or should I try to spread it around?

Also, I think there's already MX-1 on the chip from the Freezer 7, do I have to isopropyl it off before reapplying or is it fine because i'm reapplying the same compound?
Thanks,
Alex

 

[PFCWintergreen]

I'm not sure whether to be excited about my new computer (DS3, E6400, 1GB Patriot DDR2 800) or not after reading this thread. I think mostly I just hope everything works...

Anyone want to reassure me that it'll be okay?

 

[amenx]

Beta BIOS out, F11a:

http://www.station-drivers.com/telechar...nt/gigabyte/beta-bios/965pds3_f11a.exe

 

[econnelle]

Some info that might help with the crackling sound along with more information on my problem above.

I had problems with crackling sound at stock speeds(1.8ghz e4300), 2.4ghz, and 3.06ghz.

The video performance problem I had above, according to a poster over at TG say my MCH voltage might be to blame or I needed to set my PCI-X to 102mhz to force it to not drop down to 1X from 16X.

Using a HDR demo I found out that the video ram slower at any OC'd speed than at stock. I confirmed the CPU was running faster with Sandra but the video kept falling. Also my Windows Performance score would always be 1.0 on video.

Here were the numbers from before the fix:

1.8Ghz
16551 MIPS
11563 MFLOPS

200fps avg 640x480
88fps avg 1660x965
47fps avg 1680x980

2.4Ghz
21935 MIPS
15321 MLOPS

106fps avg 640x480
64fps avg 1660x962
10fps avg 1680x980

3Ghz
27393 MIPS
19109 MLOPS

112fps avg 640x480
67fps avg 1660x965
10fps avg 1680x980

I noticed Supreme Command ran well and I thought it had to do with going full screen. Going full screen dropped performance to slide show rates. Since SC doesn't really run in full screen rendering I thought that was the issue.

After the fix I noticed that I could run SC at 4X AA and it ran great where as before at 2X it would start to get a bit choppy.

I upped the MCH .1v first and it totally fixed my problems. Adrianne and Froggy ran great. For some odd reason Cascades still doesn't run right but everything else does so I'm not complaining.

Here are my numbers at 3.06ghz on the HDR demo:

640x480 242fps avg
1680x960 48fps avg

A 40fps improvement over 1.8ghz and a 130fps improvement over the unfixed 3ghz speeds.

The byproduct is my sound issues went away also. Sounds plays perfect with no static. I had tried the 1.61 drivers and that did not help the sound issue.

Only fixing the video issue helped me.

I'm reading a lot of people who are having issues like this, not as severe but someplace in between running at full speed and the slideshow rates where I was.

I wonder how many might be having similar problems and don't even know it. Playing Supreme Commander you wouldn't have guessed the performance was not upto where it should be if you had no comparison.

Some people thought the card was clocking down but I confirmed this with Rivatuner it was always at 576mhz.

Great board and worth the 3 days of frustration to figure it out. I was just suprised to see how scattered the information on the video problem was so hopefully this will be helpful to someone else.

 

[tenax]

Originally posted by: EXman
Driver for realtek Audio. this is what you need for the DS3 Audio!

Thanks Tenax for getting me in the right direction!

exman, am i to assume it fixed the song up for you? if so, good to hear, glad to help.

 

[tenax]

Originally posted by: econnelle
Some info that might help with the crackling sound along with more information on my problem above.

I had problems with crackling sound at stock speeds(1.8ghz e4300), 2.4ghz, and 3.06ghz.

The video performance problem I had above, according to a poster over at TG say my MCH voltage might be to blame or I needed to set my PCI-X to 102mhz to force it to not drop down to 1X from 16X.

Using a HDR demo I found out that the video ram slower at any OC'd speed than at stock. I confirmed the CPU was running faster with Sandra but the video kept falling. Also my Windows Performance score would always be 1.0 on video.

Here were the numbers from before the fix:

1.8Ghz
16551 MIPS
11563 MFLOPS

200fps avg 640x480
88fps avg 1660x965
47fps avg 1680x980

2.4Ghz
21935 MIPS
15321 MLOPS

106fps avg 640x480
64fps avg 1660x962
10fps avg 1680x980

3Ghz
27393 MIPS
19109 MLOPS

112fps avg 640x480
67fps avg 1660x965
10fps avg 1680x980

I noticed Supreme Command ran well and I thought it had to do with going full screen. Going full screen dropped performance to slide show rates. Since SC doesn't really run in full screen rendering I thought that was the issue.

After the fix I noticed that I could run SC at 4X AA and it ran great where as before at 2X it would start to get a bit choppy.

I upped the MCH .1v first and it totally fixed my problems. Adrianne and Froggy ran great. For some odd reason Cascades still doesn't run right but everything else does so I'm not complaining.

Here are my numbers at 3.06ghz on the HDR demo:

640x480 242fps avg
1680x960 48fps avg

A 40fps improvement over 1.8ghz and a 130fps improvement over the unfixed 3ghz speeds.

The byproduct is my sound issues went away also. Sounds plays perfect with no static. I had tried the 1.61 drivers and that did not help the sound issue.

Only fixing the video issue helped me.

I'm reading a lot of people who are having issues like this, not as severe but someplace in between running at full speed and the slideshow rates where I was.

I wonder how many might be having similar problems and don't even know it. Playing Supreme Commander you wouldn't have guessed the performance was not upto where it should be if you had no comparison.

Some people thought the card was clocking down but I confirmed this with Rivatuner it was always at 576mhz.

Great board and worth the 3 days of frustration to figure it out. I was just suprised to see how scattered the information on the video problem was so hopefully this will be helpful to someone else.

i have had the problem with 16x pci-e dropping down to 1x and didn't have a clue why. the only suggestion i ran across is to shut down..turn power off so things go to default and that should get it back up. i did that, then loaded my saved overclock bios for 390 fsb and it retained the 16x..i believe that bios version has the MCH voltage raised when i created it..and it was by .1..my pcie frequency is always left at stock which most seem to advise. i did try raising pci-e in increments from 100 to 104 when i had this problem..that didn't do anything fix it. so maybe the mch voltage fix is logical

 

[Cheex]

I'm currently rock stable (13 hours Orthos) at 3.150GHz (450x7) but I'm having cold boot issues. How can I fix that? Do I increase the MCH voltage? Do I increase CPU or RAM voltage? I don't know. I just hope someone can help.

Cold boot issues are nothing short of ANNOYING!!!

:|:|

 

[tenax]

unfortunately, i think this issue goes beyond this mobo and impacts on more mobos with the p965 chipset. i've had cold boot issues with the biostar version to the point it just would not boot period..i've read recently many a thread that the asus board can have this issue..same with the gbyte..no one appears to have made a correlation beside me to the chipset being the common factor..maybe because almost everyone seems to get their boards running, they say good enough (like me..i run mine 24/7 cause it's a pvr system as well so i rarely need to reboot unless software installation requires it so while it has happened for me..i always get it going again quickly with a shutdown of my power switch, boot to default, boot to saved profile and i'm back in action) if i had to turn it on off everyday, i'd probably share your frustration. i've tried all kinds of different settings and sometimes a restart requires the tricks be employed, sometimes not and i can't say definitively "this is how you can avoid cold boots with this mobo"..fyi, i have my mch and fsb voltage boosted by .1, cpu voltage stock (cause i have no reason to raise and raising it seems to have done nothing to resolve this issue anyway) and my ddr voltage .2..so , i don't think raising the voltage is the trick..i'm feeling there are no fixes, only workarounds on this issue.

 

[Cheex]

Originally posted by: tenax
unfortunately, i think this issue goes beyond this mobo and impacts on more mobos with the p965 chipset. i've had cold boot issues with the biostar version to the point it just would not boot period..i've read recently many a thread that the asus board can have this issue..same with the gbyte..no one appears to have made a correlation beside me to the chipset being the common factor..maybe because almost everyone seems to get their boards running, they say good enough (like me..i run mine 24/7 cause it's a pvr system as well so i rarely need to reboot unless software installation requires it so while it has happened for me..i always get it going again quickly with a shutdown of my power switch, boot to default, boot to saved profile and i'm back in action) if i had to turn it on off everyday, i'd probably share your frustration. i've tried all kinds of different settings and sometimes a restart requires the tricks be employed, sometimes not and i can't say definitively "this is how you can avoid cold boots with this mobo"..fyi, i have my mch and fsb voltage boosted by .1, cpu voltage stock (cause i have no reason to raise and raising it seems to have done nothing to resolve this issue anyway) and my ddr voltage .2..so , i don't think raising the voltage is the trick..i'm feeling there are no fixes, only workarounds on this issue.

Thanks for your input. I appreciate it. I guess I'll just have to live with it then.

But...

What are these and what is the purpose and/or benefits of raising the following voltages:
1) PCIe
2) FSB
3) MCH