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

[ThePiston]

can someone tell me what voltages to start out with on my CPU and ram to start a decent OC? Also, which place to I change for the system bus? Is it the CPU host controller?

 

[redhawk56]

Originally posted by: vailr

Originally posted by: redhawk56

Originally posted by: jimbofoxman

Originally posted by: redhawk56
Does your northbridge heatsink say Gigabyte on it in big letters?

Yes it does....

Ok.....good..........then we have verified that some people are getting the real rev 2 boards. I just hope I get one when my replacement comes from newegg. What bios came on it? Was it F7?

redhawk:
Did you get an answer from Gigabyte tech support, as to why the "GIGABYTE Virtual Dual BIOS Technology" wasn't able to recover your board to a bootable condition?

Safe
Safe is the key feature of GIGABYTE S-series motherboards with the following elements: Excellent hardware design reinforced BIOS protection through GIGABYTE Virtual Dual BIOS Technology and GIGABYTE BIOS Setting Recovery Technology. Unique system software such as Xpress Recovery 2, PC Health Monitor, HDD S.M.A.R.T., and C.O.M. further strengthen the stability and reliability of your PC!..
Text

I'm sorry, but I am laughing when I remember the various times that I communicated wtih GB tech support. They simply issued an rma and told me if they found anything wrong with the board they would repair/replace it within 6 weeks. So i chose to rma it to newegg iinstead.

Concerning the virtual bios, it tried to recover itself but turned itself off in the middle of the recovery. That was the end of everything.

 

[levimax]

 

[levimax]

If someone can confirm it'll resolve the SB X-Fi issue I may just give it a try. As it is with the F6, windows will detect my X-Fi most of the time and on rare occasion it does not show up.


F8i (and I would assume F8 final) completely resolved the SB X-Fi random driver loading issue for me. For anyone with SB X-Fi I would recommend F8 for that reason alone

 

[Ricochet]

Thanks, levimax. I will give F8 a run as soon as it's convenient. Hopefully it doesn't ruin my current overclock.


Off topic: Welcome to the forum! This is the 2nd time in the same day that a lurker signed up to answer my question. (REF)

 

[AdamK47]

I finally have no need for a floppy drive. I made a cheap USB Flash Drive bootable and put the BIOS files on it. The DS3 saw it as a standard hard disk and I was able to boot from it just like a floppy, although much much faster. I'm using the F8 final BIOS and took the floppy drive out of my computer for good.

 

[ThePiston]

i have a bunch of thumb drives alying around and I've been meaning to do that - care to link me to the place where you learned that? thanks

 

[AdamK47]

Originally posted by: ThePiston
i have a bunch of thumb drives alying around and I've been meaning to do that - care to link me to the place where you learned that? thanks

Here you go. I downloaded the HP Drive Key Boot Utility that's linked on that page. It requires boot files. I used the files from my floppy disk before I removed the drive.

 

[redhawk56]

I would strongly suggest against flashing the F8 bios. I've seen 2 boards DOA since last night. One on XS and one on another forum. I would not risk it.

 

[amenx]

To those with X-fi issues, it appears its not just with the DS3, but with other non-Gigabyte mobos as well. There are a couple of threads with a few hundred posts on this issue at the Creative forums dated from before the DS3 went to market which involved the X-fi not being recognized when booting into Windows.

I have this issue as well but found it 'manageable' as long as I didnt fiddle around with the bios, esp the voltages.

 

[amenx]

Originally posted by: Gary Key

Originally posted by: amenx
This F8 is a step backwards for me. After loading optimized defaults, then re-entering my OC settings, it wont post. Went back to F7 which was working OK.

Did you clear the CMOS after loading the F8 also? I have found this to be an issue when using @BIOS. Usually, I shutdown the system after flashing, clear CMOS, boot, load defaults, reboot, load my settings, and all is well.

Thanks, I'll give that a try, and yes its with @bios due to no floppy.

 

[Ricochet]

Originally posted by: redhawk56
I would strongly suggest against flashing the F8 bios. I've seen 2 boards DOA since last night. One on XS and one on another forum. I would not risk it.

That scares me.

 

[yellowflash]

I just gave the final F8 bios a try, and it didnt help much with my overclock. I'm still stuck at 460fsb x 6 on my 6300. Maybe its my ram? I had my crucial 10th anniversary set to 5-5-5-23 at 2.3v. Anyone have their D9 issue fixed with the F8 bios?

 

[little legionaire]

Hi,

I'm a new member of this forum, frankly because of my beloved DS3 and SataII raid0 problems. I had no problems with my optic drives before when i decided to upgrade my HDD's to raid0 mode. They were working fine without any issue.

First failure was "PIO mode stuck" but with this forums wise guidance ( bios update to F7 and Raid/Ide fix ) i've solved this trouble ( They all at UDMA 2 ) but second probably the worst.

It's strange behavior that i could not understand the real reason. I had two optic and properly they are setted as master&slave but always if i use one of them the second one is shuts itself does not recognize any dvd or cd anymore when i tried to play it.

Mates if you have any idea about my eternal torture with raid0, please help me.

 

[tastyratz]

little: as far as weird optical issues update to the latest jmicron (read: latest... not latest by gigabyte. use the link i posted a few back, gigabyte is a few revisions behind.) driver, I had some before and it patched it up for me, maybe the same for you.

redhawk: ive seen failures on the betas of F8, But I havent seen any that are directly related to using f8 final. hutch on xs was crying before the needle hit the skin - false alarm. Wheres the other failure you heard about?


anyone else able to successfully slipstream the raid drivers into their xp cd yet where it wont cause a bsod at partition promp? been a big issue and I havent found a fix yet, im trying to install windows on my raptorx2 raid0 without a stupid floppy drive.


also side question, I cant find anything about the "turbo" etc memory options you get after ctrl f1? not talking about the generic timings control, but when you go into the advanced menu and change your timings theres an additional option under it all for memory to function a other modes like normal, turbo, etc. what exactly is that and what does it do?

 

[Undersea]

Well any more feedback on f8 yet? I'll load it tonight.

This bios thing reminds me of chaintech woes using winflash. With a dual core and version f5 chaintech bios would flash bad. Many, many people had problems with flashing.

Use the built in flash utility and a floppy.

BTW I used the new jmicron drivers. I tried them out last night and am using the 1.17.08.1 drivers for XP. Raid.

I did not use the drivers in windows yet. The utility they give when loaded is about usless.

Seen here:

http://www.station-drivers.com/page/jmicron.htm

Get to flashing everyone!

Gary does this version bios fix the D9 bug? What are the stated fixes?

Never had optical problems but the newest jmicron drivers work fine on the board. I run a raid 0 with 1 optical drive. I'm holding off flashing at this point. I'm pretty sure version 2 DS3 won't have the D9 problems.

I wrote gigabyte about the windows drivers which load the raid utility in the task bar and you do not need to load them. The utility is all they do.

 

[ThePiston]

like i said guys, i used the Windows @bios tool (do'nt use internet option because it still downloads F7) and F8 works fine, i'll let you know how my OC goes tonight - I've got a 6 pack waiting for me at home.

 

[redhawk56]

In my opinion, I don't see any benefit to warrant the risk of flashing this bios. Nobody is having better overclock results or benchmark results. After waiting 2 months, the only thing that GB can put in the comments on the bios is that is updates a cpu id. That is complete b---s---. When I get mine back on RMA I'm selling it just because of the way this was handled.

The other person I saw was also on XS. They commented about their first DS3 refusing to post shortly after flashing f8i. Mine died on f8J and hutch on XS, although you say he was overreacting, had to go through things you should never have to do after flashing, just to get the machine to post.

So you guys can do what you want, I'm not really trying to debate this. I just have a bad taste in my mouth after this experience. Have fun!

 

[dnottis]

I wanna know if this solves the cold boot issue - where the OC is lost on a cold start.

 

[redhawk56]

Originally posted by: dnottis
I wanna know if this solves the cold boot issue - where the OC is lost on a cold start.

I have looked high and low for an answer to that and I can't find anyone/anywhere reporting that issue is fixed. I had that same exact issue on mine with my 920, so it isn't unique to the C2D. It is either the board or the bios.

 

[ThePiston]

hey guys, I put my multiplier at 8X and the CPU controller at 350 and when I boot it says I'm getting 3150mhz, shouldn't it be 8x350=2800? Now I nkow why it wouldn't post at 400mhz on CPU host controller. Someone helpe me out and tell me what I'm doing wrong.

 

[amenx]

Originally posted by: ThePiston
hey guys, I put my multiplier at 8X and the CPU controller at 350 and when I boot it says I'm getting 3150mhz, shouldn't it be 8x350=2800? Now I nkow why it wouldn't post at 400mhz on CPU host controller. Someone helpe me out and tell me what I'm doing wrong.

The e6600 multiplier is 9 not 8, so 350 x 9 = 3150.

 

[ThePiston]

Originally posted by: amenx

Originally posted by: ThePiston
hey guys, I put my multiplier at 8X and the CPU controller at 350 and when I boot it says I'm getting 3150mhz, shouldn't it be 8x350=2800? Now I nkow why it wouldn't post at 400mhz on CPU host controller. Someone helpe me out and tell me what I'm doing wrong.

The e6600 multiplier is 9 not 8, so 350 x 9 = 3150.

so it's locked at 9?

 

[tastyratz]

no the highest multiplier you can use is 9. You can use 6,7, and 8 as well

 

[ThePiston]

Originally posted by: tastyratz
no the highest multiplier you can use is 9. You can use 6,7, and 8 as well

mine's set at 8 under CPU rate, but it's posting at 9... am I missing something