DQ6 beta BIOS

Printable View

Show 100 post(s) from this thread on one page

12-13-2006, 02:40 PM
feek

Quote:

Originally Posted by Charloz24

Why in hell are you bashing Dnotis for using a beta BIOS ???? This thread is about beta BIOS and he is sharing his results :nono: :stick: :slapass:

I'm not bashing him? What the :banana::banana::banana::banana:, get a clue. But he said he's leaving the board to go to another because of a problem in a beta bios. At least, that's my understanding of it.
12-13-2006, 02:42 PM
dnottis

Quote:

Originally Posted by feek

I'm not bashing him? What the :banana::banana::banana::banana:, get a clue. But he said he's leaving the board to go to another because of a problem in a beta bios. At least, that's my understanding of it.

From what I've read the only bios that doesnt do this is the F4. I was using a beta bios in the hopes that the board would work correctly.
12-13-2006, 03:33 PM
HeadOn

Well, there's a reason why it's called beta and not final; there will be bugs.
12-13-2006, 03:41 PM
dnottis

Quote:

Originally Posted by HeadOn

Well, there's a reason why it's called beta and not final; there will be bugs.

umm, from what I've read the issue on a cold boot where the DS3 doesnt save the overclock isnt just a bug, it's been an issue with this board from the beginning. I'd call that a nagging flaw - not a 'bug'.

I still have a p5b-e that I had no problems with - other than lack of vdimm (2.1v max) and I wanted to give a DS3 a try and see if it was capable of the same OC. It was an experiment. Overall it did great, in fact I liked it better than the Asus P5B-E, loss vcore droop, more vdimm, mch and FSB voltage adjustments... however something like this, defaulting to stock settings on a cold boot is just downright annoying and Im going to go back to the Asus board for this reason alone. This isnt a new problem with the DS3, it's still not a resolved issue.

Anyways, it has nothing to do with me using a beta BIOS - earlier BIOSes had issues with D9 over 450. I needed 500 - 516 to match the performance of the Asus board so there is no reason to drop to f4 to save my overclock and thus limit the OC to 450 Mhz FSB. Hopefully this clears up what and why I was complaining about it.

Dean
12-13-2006, 03:58 PM
cold_realms

Yea beta, as in the S3, DS3, DS4, and DQ6 boards are Beta products from Gigabyte and we should all expect these kinds of flaws from Beta products :)

My question is: "do we get paid for beta testing their products?"
12-13-2006, 04:42 PM
iceblade

It's a good thing I got my Wii yesterday. It keeps my mind off this damn board!
12-13-2006, 05:23 PM
Tac0

Quote:

Originally Posted by MartianInvader

Keep waiting, it's not what you been waiting for :stick:

ocz titatnium alpha vx2 doesn't even boot at 500x2 4-4-4-15 :fact:

I can POST at 500, and I do not think I have memory issues (if so, I don't give a :banana::banana::banana::banana: because this board is screaming @476 and stable).

I'm just hoping to get a few more mHz maybe. Otherwise, like I said above...:stick:
12-13-2006, 09:00 PM
Richard Dower

Quote:

Originally Posted by cold_realms

Yea beta, as in the S3, DS3, DS4, and DQ6 boards are Beta products from Gigabyte and we should all expect these kinds of flaws from Beta products :)

My question is: "do we get paid for beta testing their products?"

I'm expecting a free 2.0 mobo in the mail :D
12-13-2006, 09:01 PM
Richard Dower

With F7 for the DQ6 i can hit 438-440FSB...but the new betas are pants for overclocking. **i got my OCZ 850W PSU today - woot!**
12-13-2006, 09:09 PM
Rix2357

While trying to hit the magic 3.6ghz overclock with a e6600, I reached a point in my voltage increase where further increases in the setting yielded some strange readings from cpuz.

When I set the cpu vcore voltage to 1.45V or above, cpuz will report back the vcore as 1.212V and occassionally fluctuating to 1.414V. If I set any voltage below 1.45V, the voltage seems to be bumped up in a linear fashion how I expect it to be bumped up. I tried disabling c1 halt, eist, thermal protection, virtualization, and in windows set it to always on, but I still get the voltage drop as soon as I set it to 1.45V. Does everyone else seem to have that problem?

edit: had the problem with cpuz 1.36 and 1.38 and using F7 bios still
12-13-2006, 09:18 PM
Richard Dower

DQ6 2.0 review!

http://www.ocworkbench.com/2006/giga...Q6-REV2/g1.htm
12-13-2006, 10:20 PM
markopoleo

Quote:

Originally Posted by Richard Dower

DQ6 2.0 review!

http://www.ocworkbench.com/2006/giga...Q6-REV2/g1.htm

Thats not a review, thats just pictures of the board..
12-13-2006, 10:25 PM
Richard Dower

Quote:

Originally Posted by markopoleo

Thats not a review, thats just pictures of the board..

Dammit...don't split hairs :stick:
12-13-2006, 10:35 PM
skitlets

Quote:

Originally Posted by Rix2357

While trying to hit the magic 3.6ghz overclock with a e6600, I reached a point in my voltage increase where further increases in the setting yielded some strange readings from cpuz.

When I set the cpu vcore voltage to 1.45V or above, cpuz will report back the vcore as 1.212V and occassionally fluctuating to 1.414V. If I set any voltage below 1.45V, the voltage seems to be bumped up in a linear fashion how I expect it to be bumped up. I tried disabling c1 halt, eist, thermal protection, virtualization, and in windows set it to always on, but I still get the voltage drop as soon as I set it to 1.45V. Does everyone else seem to have that problem?

edit: had the problem with cpuz 1.36 and 1.38 and using F7 bios still

That seems to be a regular problem with CPUZ. It doesn't read voltages past 1.45.
12-13-2006, 11:15 PM
ezechiel1917

hi, i have a strange problem ive never had with any of my previous systems (this is my first intel). When i restart from windows, all of my disks just turn off just a second or two before system actualy restarts and start spinning on again while drives detection screen is up (this doesnt happen with manual press reset button on the case). anyone have any idea whats wrong, ive tested two different PSUs so im suspecting board itself in some way (DQ6 i have tried F6,F7,F8c).

Second question: Is there a way to turn off NCQ in windows, on my old board i could do that in hardware manager, i cant even disable the disk cache as that option is grayed out for me. (also i cant remove safely any hdd as it doesnt appear on the list of usb devices, you should have hot swap option with sata.)

thanks for any ideas.
12-14-2006, 12:47 AM
olhado

Quote:

Originally Posted by olhado

I have problem with my system on Gigabyte DS4 board and Core 2 Duo 6600 - all at stock speed. When turnining on the comp or restarting, system powers off for a moment and then powers on again and then post and go on. Sometimes it goes at once but let say 80% is first power off and then on. System is rock stable. I had no single crash or reboot when working. I noticed it loads different bioses - sometimes it's main bios and sometimes backup. When updating bioses I have to update both of them ;-).

Quote:

Originally Posted by Jimmy007

I think this is normal.. I have the same. All stops for a moment...

Quote:

Originally Posted by ezechiel1917

When i restart from windows, all of my disks just turn off just a second or two before system actualy restarts and start spinning on again while drives detection screen is up (this doesnt happen with manual press reset button on the case).

I know it's quite common as I read about this on other forums too but is it normal? Is there anyone else here who has this issue at stock speed?
I wonder if one shoud leave it as it is and believe that it doesn't harm the system (hdd) and maybe some future BIOS fix it. Or is it reason to RMA the board?

Quote:

Originally Posted by corsair8575

This problems sounds like MB not remembering what kind of hardware is plugged in. Try force setting your ram timings since it thinks its pc4300. find out your ram timings from the stick and put those values in using ctrl+f1 when in bios main screen, then goto mb intelli tweaker.

put in your timings so the mb doesnt need to power on momentarily and remember and detect what ram you have.

I tried to enter timings manually but it didn't help.

Vista is near and I was looking for excuse to try different RAM. So yesterday I moved from 1GB PATRIOT 5300 to 2GB GEIL ULTRA 5300 and still no improvement. I entered timings in BIOS, set voltage as stated on sticks and computer still cycling before post - maybe even more than eariler - now 2, 3 or 4 cycles before post.

There's one more thing I noticed yesterday. I set timings to 3 4 4 8 (DS4@F7E) and when I check them in CPU-Z or Everest it shows they are 3 4 4 9... Maybe BIOS and mobo try to set optimal timings on their own and cycles when doing it...
12-14-2006, 02:24 AM
Marvin_The_Martian

Quote:

Originally Posted by Tac0

I can POST at 500, and I do not think I have memory issues (if so, I don't give a :banana::banana::banana::banana: because this board is screaming @476 and stable).

I'm just hoping to get a few more mHz maybe. Otherwise, like I said above...:stick:

I can post at 520 with my 120E geil kit.... :slap: and it's sp1m stable to 522 ;)

The issue is I got a €500 ocz kit, which doesn't even come close. Don't tell me because you think you got no issues because you're running 476 fsb, think ur on x2 ram multi which is below spec for my ram, that the board doesn't still have the same issues.
12-14-2006, 02:44 AM
Jimmy007

Quote:

Originally Posted by DStealth

Don't worry, flash it! The boards are same I have them both and have tested all DQ bioses on my DS4 ;) That's why I told you which one is the best :) Till now, f7c i very poor performer and clocker.

How did You do that? I've tried flash my DS4 with DQ6 F7 bios, from QFlash, but I've got error checksum or something like this. I can't flash it.
12-14-2006, 03:12 AM
laziepig

Quote:

Originally Posted by Jimmy007

How did You do that? I've tried flash my DS4 with DQ6 F7 bios, from QFlash, but I've got error checksum or something like this. I can't flash it.

use @bios =.=" there's only 2 ways to flash your bios unless u got some 3rd party stuff...
12-14-2006, 07:10 AM
ScythedBlade

QFlash is better than @BIOS ... it's the floppy thing
12-14-2006, 07:30 AM
dnottis

Quote:

Originally Posted by ScythedBlade

...it's the floppy thing

They make pills for that now.

:p:

Sorry - back on topic.
12-14-2006, 07:49 AM
bingo13

Update- It appears Gigabyte figured out the disappearing OC settings on some of the boards. I will have more information tomorrow.
12-14-2006, 08:05 AM
DStealth

Quote:

Originally Posted by bingo13

Update- It appears Gigabyte figured out the disappearing OC settings on some of the boards. I will have more information tomorrow.

Alle- luia :eek:

So much hating the damn thing, with each power ON.
12-14-2006, 08:11 AM
laziepig

Quote:

Originally Posted by ScythedBlade

QFlash is better than @BIOS ... it's the floppy thing

QFlash doesn't let you flash ur DS4 with DQ6 bios... I'm not an @bios fan tho... only used it once to flash my DS4 with DQ6 F7
12-14-2006, 09:06 AM
dnottis

Quote:

Originally Posted by bingo13

Update- It appears Gigabyte figured out the disappearing OC settings on some of the boards. I will have more information tomorrow.

Dammit. ..and I'm about ready to RMA this thing too.

I went back to F8I just to give it the benefit of the doubt. Worked great all night. This morning I had about 10 boots in a row, warm and cold that it wouldnt hold the OC. Finally it started working again. I even decided to give F7 a shot but it couldnt OC over 470 for me. Tomorrow I've got an Asus P5B Deluxe coming its too bad I really liked this motherboard.

Show 100 post(s) from this thread on one page