Printable View
:banana: F3C BIOS for Giga 965P-S3
http://rapidshare.de/files/27991966/965PS3.F3C.html
:toast: F4C BIOS for Giga 965P-DS3
http://rapidshare.de/files/27992161/965PDS3.F4C.html
:woot: F3B BIOS for Giga 965P-DS4
http://rapidshare.de/files/27992357/965PDS4.F3B.html
:cool: F3E BIOS for Giga 965P-DQ6
http://rapidshare.de/files/27992450/965PDQ6.F3E.html
Thanks is there a change log?
Gigabyte didn't send me that.Quote:
Originally Posted by BottomsUp
yay i hope we can OC higher with this one..
Ya, they were officially sent to me from Gigabyte, but use them at your own risk.:D
thanks for hosting it. Just got email from gigabyte about this BIOS too
Ill Mirror These...
Haltech's Gigabyte Mirror
cool lets see some results with F4c bios
was FSB for the DS3 600? if not it is now! To bad i'm stuck on 443 though!
glad to see the BIOS keep coming. I hope that the 2.3vdimm limit will be fixed. Flashing now, brb
i just noticed everytime i put my vdimm over .3 i get 'FAIL' for DDR18v in the PCH health menu of the bios. What's that all about?Quote:
Originally Posted by irev210
official? didn't see on their web site tho...
official but not yet released on site.Quote:
Originally Posted by Juunishinshou
I dont know, I have the DQ6.Quote:
Originally Posted by BottomsUp
AND! I am glad to report that it is finally FIXED!
F3E FINALLY allows you to boot with above 2.30Vdimm THANK GOODNESS!
Things seem to be really improving for gigabyte. I am glad they are actually supporting their products, and FIXING things. Turning out to be a decent investment after all!
480Mhz+ FSB, VDIMM in BIOS actually working, fixed RAID issue....
Things still left to test- Vcore, will it be able to boot above 1.600?
I got more memory testing to do. Both Micron D9 and Elpedia E6-E seem to work well with the board.
anyway, Im excited. THANKS GIGABYTE!
GIGABYTE, give us 3.0VDIMM!!!!!!
SOUNDS GREAT!;)Quote:
Originally Posted by irev210
Last time I looked, Lestat was wondering if any version of the Gigabyte 965 mobos were seeing much over 400fsb when using a multi of 9 or better. Show me the magical 9x445 dual prime stable and you can be a hero to many people at XS and start a stampede on top of the first stampede for these mobos.
any luck boot 500+ for DS3 with this new BIOS?
it seems that I can't go beyond 495 to pass the windows loading screen (with F3 BIOS).
Good to see Gigabyte doing so well. Companies that support their products deserve good reviews!
To be fair though, the memory problem a LOT of people have been having should never have happened! How much testing must they have done on this board?????? :rolleyes:
Got the DS4 myself, OCZ 6400 Special-Ops RAM 2x1GB. Won't bloody post so have to try the beta bios tonight and prey it works!
Quote:
Originally Posted by gundamit
there is no problem with 445+, i havent tested booting in BIOS over 400 yet, but using Easy Tune 5... I can crank the FSB on E6600. I havent had much time to play with it, but the highest i've reached so far is 475*9 on conroe with NO mobo chipset fans.
anyway, i need more time to reset up phase, and I will continue to go up.
Here's a clue about the changes:Quote:
Originally Posted by BottomsUp
"The E6600s and up are different animals on this board. I will post some E6600 results in a couple of days. Due to the 4MB cache and hitting the 1066 memory strap earlier, these CPUs have not been clocking as high on the P965 boards (9x410 or so) unless you drop the mulitplier which defeats the purpose of buying one. The bios revisions are coming in hot and heavy right now. I already had three from Gigabyte today, one from Biostar, two from Asus and Foxconn."
http://forums.anandtech.com/messagev...&enterthread=y
Looks like E6600/DS3 owners will be happy soon!
Oohhhhhhhhh!!!!!!!!
:o
using Easy tune is impossible for me and several others as the minute you touch the bios to overclock easy tune will no longer start up properly.
you will either see ther program flash on screen like it doesnormally, and the taskbar icon is dead. OR you wont see anything at all. and easy tune wont run.
i also do not have any options for memory divider, pci-e voltage and pci-e freq.
not sure exactly what the program is doing or why it doesnt like when you OC with the bios but when I, thats ME, overclock with the bios easytune wont work.
not only that but i cant overclock at all with easy tune. i cant get maybe oh i dont know 100mhz on the fsb then the program just bails.
the system wont boot any longer.
are you guys installing easy tune from the cdrom or the website ?
if gigabyte has taken further steps.... then rock on!! kick arse!
i think we need to get some screen shots of this.
p.s.
how do you have the bios setup. ? do you have everything in the bios as defualts ? or are you overclocking as far as you can with the bios then switch to easy tune.?
im asking becuase when i overclock, as i said. with the bios easy tune will no longer turn on.
God willing, this will solve some of the issues people have been having the E6600 and the 1.8V issue. Can anyone confirm that this Bios is the magic bullet?
Anyone hit 9 x 400 with an E6600 on air yet with the new bios on bootup? Stable?
Great news guys, please keep posting the betas as they come in, my cheap ass Celeron never arrived :-(
So no build today, maybe tomorrow and i'll reprt back with my DQ6 and F3e beta.
Yeah, I figured you'd be happy Lestat :)
I have the ds4 with a celeron 331 for testing. I measure the vdimm just like this guy on the ds3 http://www.xtremesystems.org/forums/...d.php?t=107692 , i can read it throught two mosfet under the right dimm sockets and it seems that default is 2 Volt not 1.8V. I also have a big problem setting the cas latency (CL). I have kingston value 2x1giga with elpida 6e-e rated cl5 and when i put in bios the CL 5 or auto is gives me 3, so i can play only with CL4 for overclocking!!!! I hope gigabyte fix this CL bug in the next bios update. I believe thats the problem when some rams doesn't work on ds3/ds4/ds6 especially if are rated @ 800 it will try with CL3, very difficult to boot for the majority of ddr2 sticks. :)
Even if the BIOSs linked here don't fix the problem, it is great news that Gigabyte is actually aware of the E6600 problem and has figured out why it's happening.Quote:
Originally Posted by Alphy
i gotta do more testing but i am booting from the bios at 420!!
im outa time for now gotta get to work!
god why cant it be saturday!
Woot! for Lestat.
:-)
doh!
i jumped the gun on 420.
rebooted again just to see if it would hold and it bailed. back to the system going on and off on and off.
they have changed something.
the F3 bios would reset the bios and let you boot into the bios if you overclocked too far. the F4 bios isnt letting you do that. you have to reset the bios. i dont care for that but hey they are making progress and its a beta so...
Quote:
Originally Posted by aldamon
the 1.8v issue do you mean the ram , most GOOD ram not being able to boot cuz the bios uses 1.8v as default ?
thats a mixed bag. the ram has to be programmed to run at low voltages. but also the bios has to be programmed to kick the voltage up if higher ram is installed.
usually its the rams responsibility to be able to run at a lower voltage.
i'll try my gskill(as i havent returned it yet cuz im lazy) and report back but i doubt it will work.
I know what you mean. :(Quote:
Originally Posted by Lestat
Just tested F3e on my DQ6.
You can now boot over 1.6vcore and you can boot at +0.3vmch, but not over.
It's getting better at least, before I got no boot at over 1.6vcore and over +0.25vmch.
Yeah, it looks like I was wrong about that.Quote:
Originally Posted by Lestat
Real quick, what does mcvh stand for?
wow thats definately wierd.Quote:
Originally Posted by Kesnel
wow i just realised 1.6vcore holy smokes dude what are you doing. LN2 i hope
any gskill rams support improvment with these bios or not ?
I've not got my e6600 yet, still using a Celeron 326 as a stopgap, cooling is modded Mach II GT. :)Quote:
Originally Posted by Lestat
Wow, Mach II on a Celery? :sofa:Quote:
Originally Posted by Kesnel
(just kidding BTW)
E6300/E6600 owners, report your findings! If this Bios does fix the undervoltage RAM problems, I might pick one up today.
Good luck with your E6600.Quote:
Originally Posted by Kesnel
I am stuck at 312FSB 2.8GHZ. Anything higher and it won't boot to windows. I've tried everything that I know of. :mad:
I have not tried anything other than F3 though.
i wouldnt look for gigabyte to fix the gskill issue, honestly i wouldnt.
if they are able to super! if not, the true problem lies in gskills ram not bumping down to a lower speed/voltage in order to boot. ie having a boot up profile.
but gigabyte could also program the bios to use a higher vdimm if it doesnt boot.
also remember the majority of the ram and specifically the ones they have in the ram compliant list are all 1.8-1.9v ram. not 2.0-2.2v ram.
i saw one guy using some of the HZ's and he said he can actually boot with them but he didnt say if its the 5400 or 6400. if its the 5400 so what the 6400's are the killers.
Quote:
Originally Posted by Brahmzy
312 holy poo!
ok lets start
whats your cpu, your ram your psu, etc etc. we'll get you going to 400!!
Please help Lestat - my problem lives in here (specs are towards the end of page 2:
http://www.xtremesystems.org/forums/...=109706&page=2
I am able to boot my DS3 with HZ 6400, but i BSOD trying to install windows unless i up the voltage .2 or .3.... .4 or higher gives me a 'FAIL' message for DDR in the PCHealth screen. This RAM is also failing memtest as low as DDR886 even with a few extra volts. I spend $240 on this stuff expecting it to run faster and i think it's the cause for my llimited overclock at 430fsb. I'm thinking of buying some DDR1000 to see if it helpsQuote:
Originally Posted by Lestat
I tried the new f3b bios for ds4. It overclocks my rams way better than before, generally an improvement to the previous bios. Also I measure the vdimm and default is 2.13V on ds4!!!! I know that is correct because it runs my elpida 6e-e @ 800 4-4-4, cannot do that with 1.8-1.9 right? ;)
Another major bug!!!!! WHEN YOU UP THE VCORE YOU LOSE IN MEMORY PERFORMANCE!!!! WTF? I am now @ 1.525Vcore memtest unbuffered 2952, i set it to 1,535 -> unbufferered ~2800 and so on.... when i set 1,6+ vcore i have almost 1300 mb/s in memtest!!! what a difference! I believe the guy who made a comparison 965 vs 975 must do it in default speeds not overclocked, because there is a big BUG when you up the vcore, you lose way to much in performance!
Gigabyte please fix it!
So far not seeing any improvent in eith the F4A or the F4C bios over the F3. Could really use a RAM multiplier of less than 2 though, something along the lines of 1.77 would be fantastic please gigabyte
please say more, then I'll pass them to GBT.
Here is one for you. Anything over .3vdimm give a DDR18V Fail in PChealth screen. This is with G.Skill HZ ram regardless of memory multiplier or FSB speed.Quote:
Originally Posted by kenofstephen
Gskill still doesnt boot with the latest beta bios.
and it still doesnt boot until you manually set 2.2v which falls out of the ram's specified voltages. (manually setting by swapping ram)
its required to use more than the ram is even spec'd for.
this is the GSkill 6400 ZX
the motherboard needs to auto adjust its voltage to allow for higher quality ram.
right now the system is defulating to 1.8v no matter what ram you use and thats, frankly unacceptable to be honest. the baord some how needs to adjust itself.
now also gskill needs to make the ram bootable at lower voltages.
im running 32m Pi at 415 bootable so ill have a screenshot here shortly.
i was going to try for higher but wanna do it in stages.
Kenofstephen
IDE devices ARE STILL USING PIO MODE when you have RAID enabled.
this ABSOLUTELY! needs to be addressed!
peoples drives are going to be damaged if this isnt fixed.
when RAID is DISABLED and you install the gigabyte SATA drivers the cdroms are then recognised as a SCSI device. you do NOT need to install the gigabyte SATA drivers for everything to work fine. but if you do NOT the ide devices are using PIO mode.
this is causing incredibly painstaking slow down when running programs like power dvd or Windvd and other DVD programs as the system has to search for IDE devices and it cant find any and then see's scsi drives.
the entire interface of the IDE ports if totally screwed up. Gigabyte needs to work with JMicron to get this issue resolved quickly whether it be a bios update or a driver update.
the latest drivers off of the website now install the Secondary IDE Controller as a SCSI device. it doesnt call it the gigabyte controller it calls it Standard Secondary IDE Controller. this again is WRONG!!!!!
a standard IDE controller is NOT a SCSI device.
i dont know who's programming these drivers but wow..
420 bootable and stable!
425 instantly bombs!
Kenofstephen.
the bios no longer resets itself when there is a fialed overclock PLEASE PLEASE tell gigabyte to put thise feature back!!
having to reset the bios is retarded. its so 5 years ago! lol.
yeah im hitting a wall at 420fsb
and letast has spoken
Where did you get this info from that drives can be damaged using PIO mode?
I second that suggestion.Quote:
Originally Posted by BottomsUp
[QUOTE=Lestat]
when RAID is DISABLED and you install the gigabyte SATA drivers the cdroms are then recognised as a SCSI device. you do NOT need to install the gigabyte SATA drivers for everything to work fine. but if you do NOT the ide devices are using PIO mode.
this is causing incredibly painstaking slow down when running programs like power dvd or Windvd and other DVD programs as the system has to search for IDE devices and it cant find any and then see's scsi drives.
QUOTE]
Whoa wait a minute. Are you saying that the drives are going in to pio mode if you DISABLE RAID too? I thought this was only happening if you have raid configured?
If I have raid disabled do I run any risk of having my sata devices go in to pio mode?
No, only when raid is enabled
Quote:
Originally Posted by kiwi
Ok good. Thats not what lestat just said. I was hoping it was a typo...
it can affect me at the moment of to install components if change the bios or is equal
It came to him in a dream...Quote:
Originally Posted by kiwi
Quote:
Originally Posted by kiwi
Actually it mostly affects DVD/DVDR drives. CD drives can operate in PIO so can hard drives. Its the optical dvd drives and writers that will actually break running under PIO. They were never made to run under this old standard.
Any cases of broken DVD drives in PIO mode? Link?
I wasn't even able to normally use it in PIO mode since my DVD was so slow and lagged all system that one would be too pissed using it :p: Though I've never seen broken drive because of that.
OK, I flashed my DS3 with the F4c using @BIOS.
It has done absolutely nothing to help my 2.8GHz / 312x9 wall I'm hitting.
Prime bombs instantly.
[QUOTE=HeadShotWI]Quote:
Originally Posted by Lestat
sorry gentlemen that is a type-o i meant when raid is ENABLED
when raid is DISABLED they are seen as SCSI devices which is causing issues with certain DVD viewing programs and also other dvd related programs.
basically the program is slow as mollassis and doesnt hardly function.
it takes nearly, and i timed it, 10 minutes for Windvd to work. and several minutes for it to even play a dvd movie.
Quote:
Originally Posted by Brahmzy
Brahmzy
did i miss your reply to me question ?
what cpu, what ram what psu and what video.
also what usb devices are you using ?
thats an absolutely horrible issue i would consider calling gigabyte about an rma and see if ther eis anything that can possibly be done. i know it runs at stock. but see what they say maybe they would be willing to do an rma.
also guys i am able to do 420 bootable with AUTO (g)mch, fsb, and pci-e
i do not need to raise them in order to do 420 bootable.
aside from the boards IDE issues i absolutely love this board. best money i have spent since i got my Ultra-D.
Quote:
Originally Posted by aldamon
sorry for tripple posting.
that is nothing more than most other boards that would have the vdimm in RED.
its not an issue so much as a warning saying hey, you got your vdimm kinda high for normal ddr II.
dont worry about it. it doesnt effect anything that i am aware of.
ok i thought it would be causing a problem. Thanks for confirming.Quote:
Originally Posted by Lestat
Quote:
Originally Posted by Lestat
Lestat, here my dedicated thread - it shows all of my progress thus far and all of my system specs...thanks for the help.
http://www.xtremesystems.org/forums/...d.php?t=109706
If I knew it was the DS3, I'd send away for another one - I cannot afford the downtime to RMA this board. I've been without a decent PC for 3 months and don't want to go into withdrawls again. :)
Could I have jacked something up by swapping out the NB cooler? I mean the NB stays VERY cool - software temp readings say the copper cooler's doing it's job well. Ugh.
Quote:
Originally Posted by BottomsUp
np but dont hold me to that, i dont know for 100% certain i can only comment on my experiences. but i have yet to see anything bad.
its the "PC Health" so .. its just warning page.
just wanna say that the PIO MODE problem is fixed with F4 bios
http://www.alojarfotos.com/images/kanza/dma.jpg
i´m still having problems with the board but dont know where the problems come, i decided to buy a P5WDH and tomorrow the memories e cpu will join her.
byes
Quote:
Originally Posted by pcdoc1
if you people knew even 1/10th of what you kids wish you knew you would know that beyond any reasonable doubt that PIO mode will KILL a dvd rom or burner.
please for your own safety do your fvking research before you go trying to flame me.
do you even know what PIO mode is without going to wikapedia ?
i tell you what.. you go ahead and switch your drives to friggin PIO mode and see how long it takes before you cant burn disks anymore.
PIO mode is the slowest and most legacy way a device can run. and YES pio mode can harm a hard drive too. but ive never actually... no i take that back i HAVE seen hard drives in PIO mode but its short lived with a driver update.
thats why i have repeated harped that gigabyte needs to sit down with jmicron and fix it with drivers or a bios/sata-rom update.
Quote:
Originally Posted by jpcastro
JP i need to know EXACTLY what drivers your using and link me to them.
i still have the PIO mode issue
1)
are you even installing the Gigabyte sATA drivers ?
2)
are those DVD/CDROM's or hard drives ?
3)
did you simply install the bios and reboot and now they are PIO mode ?
i have done this and they are still PIO mode.
i may reload my machine tonight and see what happens.
4)
can you also tell me what the make and model of those drives are that are showing as DMA mode.
the Primary IDE device to be looking at is the THIRD in that list you see in device manager. Prim IDE 1 and 2 are sata. the third is the IDE port.
oh yeah baby DMA mode is back!!!
if you dont use raid and you installed the Gigabyte Sata drivers UNINSTALL THEM!!
DMA mode is now fully working!!
if you have raid they should be working also
god dang its about time. i knew they ould fix it with a bios update!!
you wanna say im wrong now ? be my guest.
dvd program such as windvd and power dvd and nero dvd tools are now 100% working at full speed.
no more HUGE delays or lockups of those programs.
they working.
man keep it coming gigabyte keep it coming!!
thanks for the info, lestat. Now I'll know I can flip the raid mode to "on" when I get my e6400 in the mail tomorrow. :)
bad about this bios, that you have to clear CMOS manually
well now comes the real test.
im reloading with a raid stripe.
so lets keep our fingers crossed!
Mine is still in PIO mode as I using Raid-0. How do I correct this?Quote:
Originally Posted by Lestat
damn it now im getting that stupid.
cant find XXX driver, if your using a cdrom make sure the cdrom is in the drive.
this is because i am using the F6 option to laod the RAID drivers.
damn it i hate this type of error because there s no fix. XP just does this whenever it wants to for no reason.
i tried skipping them since they are already loaded into ram. but when it rebooted i got a Stop 0x07B error which is inaccessible boot device. which is funny cuz i got the windows XP loading screen.
ggrr. must have been referring to the cdroms.
oh well back to the grind stone to see whatn i can find out.
bad boy.... hhmm.....
right click the 3rd Primary ide device in device manager and chose to uninstall,
then reboot. see if it changes.
ok. you did install this F4c bios right,, just making sure.
So Lestat,
does this mean I can RAID0 my Raptors AND run my 2 IDE DVD burners in UDMA??
I'm on F4c right now...
nice so almost all problems have been fixed with this bios, that's awesome, just give us the higher fsb for a 9x multi and I'm a happy camper:):p:
to ensure that i am giving you gentlemen the most accurate information that i can possibly give you, unlike some people who seem to think i blow smoke out my arse, even after i can back up every statement i make. i am double and triple checking everything.
my earlier statement was made NOT using raid. now the thing is, if you didnt use raid, your devices still had trouble using DMA mode, infact they actually would be a SCSI device because of the way the gigabyte controller drivers treated that IDE device.
i uninstalled those drivers because you dont need the gigabyte drivers to run standard raid. infac ti would advice against using them. the gigabyte sata controller is a legacy device you dont need sata drivers. i installed them during my late nights of testing.
i currently have destroyed my perfectly running windows install to test the raid function for everyone.
but currently for some reason am having some issue with the F6 install drivers from the gigabyte website. incase some of you didnt know they just released new gigabyte raid drivers yesterday, funny they release a new beta bios and new raid drivers at the same time. hhmm and they had the balls to tell me they couldnt duplicate the issue ? pfpfpf..
anyways. im trying to help everyone here not just myself.
i want everyone to know beyond a doubt that this is gunna work or not under raid and non raid.
so say what you will about me but dont ever doubt my dedication to helping those of us with issues and standing behind my statements with pure evidence when i make such statements.
i will have more results for you all in a while.
right now i need to figure out why the NEW f6 drivers are having issues during the XP install.
please bear with me everyone.
They are still PIO mode.:(Quote:
Originally Posted by Lestat
ok download and install the new raid drivers from the gigabyte site. see if those help you.
i cant think of anything else...
but i will look into it.
you can also try going back to the old drivers off the cd if you ARE using the new raid ones.
i still cant get the new F6 drivers to work it keeps telling me it cant find the jraid even though it looks right at the floppy and reads it it says it cant find it,
im sure many of you guys have seen this.
not sure why it does it.. so i reformatted the floppy and am using the drivers off the CD
the manual reset issue has been reported ~ :)
thanks Ken!!!
ok well i have no idea wth is going on but the only way i could get XP to load was the slipstream the raid drivers into the isntall using NLite.
so xp is loading right now on a raid stripe.
Thanks! It surely is a pain in the arse to have to do!Quote:
Originally Posted by kenofstephen
hey lestat,Quote:
Originally Posted by Lestat
i am sure a lot of ppl are holding on to their breaths waiting for your raid results. I hope it works out.
:toast:
regards,
karan
Doesn't do anything at all. What is the date for these drivers? I got the one off of their site. They are dated 6/16/06.Quote:
Originally Posted by Lestat
the ones on their site right now are 8/x/2006
Quote:
SATA RAID
Download Date Description Version Size
Download 2006/08/02 GIGABYTE SATA2 RAID Driver (Preinstall driver, press F6 during Windows* setup to read from floppy)
O.S. : Windows XP 64Bit 1.12.01.00 0.08 MB
Download 2006/08/02 GIGABYTE SATA2 RAID Driver (Preinstall driver, press F6 during Windows* setup to read from floppy)
O.S. : Windows 2000,Windows XP,Windows Sever 2003 1.12.01.00 0.08 MB
Download 2006/08/01 GIGABYTE SATA2 RAID Driver
O.S. : Windows 2000,Windows XP,Windows XP 64Bit 1.12.01.00 2.28 MB
Aug 1st 2006
make sure your looking at the DS3 and not the S3 or the 4 model or the DQ6 model.
good to see new bios updates
any overclock updates?
lestat what was your previous OC compared to 420MHz stable and bootable now
This is the ones I am using. How come CPU-Z still reads my bios as F1?Quote:
Originally Posted by Lestat
http://www.gigabyte.com.tw/Support/M...ProductID=2314
guys what is the max vdimm of DS4 mobo?
Yesterday, I was able to setup a raid1 with fc4 bios and newer sata raid drivers. The installation went off with little trouble. For some reason... the message about not verified for windows and usb keyboard not working to continue is annoying!!! Plugged in a ps2 keyboard and installed successfully even after second attempt. My DVD drive was set to DMA mode with these new drivers and raid activated.
Thanks lestat for the suggestions! Time to overclock this d805 while I wait to order e6600.
DMA mode is fully working.
so as of now no more worries.
this was fixed with the bios not the drivers, incase anyone was wondering.
didnt get to do any testing last night as i was already up late trying to get windows updated and drivers installed.
i will finish all that up and do more tonight.
as of now im at a wall at 420mhz. its kinda flakey though but 415 100% perfect.
before 410 was flakey and sometimes didnt even boot.
so not a huge improvement but its a step forward on the FSB limits of the 9x or higher cpu's.
we need some people with 6700's and 6800's to report in.
some ES models and retail models.
Sweet. Maybe we can end this "965 is no good for 4MB cache chips" garbage soon.Quote:
Originally Posted by Lestat
I'm feeling better and better about my DS3 purchase.
Will the updated BIOS allow my DVD-RW drive to be recognized as an IDE device instead of SCSI?Quote:
Originally Posted by Lestat
Sorry for the noobish question. But I am getting a DS3 today. How can I verify that it is in DMA mode?
Go to device manager from system. Under IDE ATA/Atapi controller, right click on primary ide channel (maybe multiple) for properties. Should be under advanced settings tab =>transfer mode.