Official Gigabyte X48T-DQ6 Info Thread

[Moose2]

You can run this memory on x48t-dq6 right?
http://www.newegg.com/Product/Produc...82E16820220333

[Ace-a-Rue]

You can run this memory on x48t-dq6 right?
http://www.newegg.com/Product/Produc...82E16820220333

i didn't see that particular memory on gigabyte memory list but they do show one patriot module...take a look: http://www.gigabyte.us/FileList/Memo...a-x48t-dq6.pdf

if you are interested, i am selling my GSkill DDR3 memory used on this board...PM me if you are interested and we can negotiate price.

these are the modules...proven on this board: http://www.newegg.com/Product/Produc...82E16820231167

[Moose2]

i didn't see that particular memory on gigabyte memory list but they do show one patriot module...take a look: http://www.gigabyte.us/FileList/Memo...a-x48t-dq6.pdf

if you are interested, i am selling my GSkill DDR3 memory used on this board...PM me if you are interested and we can negotiate price.

these are the modules...proven on this board: http://www.newegg.com/Product/Produc...82E16820231167

I was looking at it because it was cheap then I saw that sli ready on it and was wondering.

[Ace-a-Rue]

sli ready only applies to nividia chipsets...memory will most likely work on intel chipset boards but not at the specs it says.

[sbenrap]

For those interested, the reply from GIGABYTE came today.

To cut it short, they basically requested to remove battery and short circuit the "clear cmos" pins.
The reason the backup doesn't work, and I quote:
"However, if system boot failed, probably there’s something wrong during BIOS flashing and caused BIOS corrupted that would make secondary BIOS doesn't work either."

There is no mention of the faulty F5 BIOS in the reply despite me specifically mentioning it in the question (as well as the resulting infini-reboot).
To me, this reply is an insult.
They do not take responsibility and are showing disrespect to their customers (and not just any customers, the most high paying ones! I do not believe for a second that they are not aware of the faulty F5 BIOS they released, enough days have passed for everyone to be updated).

I am very happy I managed to unbrick my machine, I installed STEAM on it and ran a game for a few good hours to see that my system is stable.
I wish you all luck with your boards (be it with getting it back quickly from GB or trying the method to "unbrick" it).

[loonym]

LOLoL...this was my response from Gigabyte tech support "We have no known issue with it, we have tested the F5 in our lab without any issue. Please redownload it"

[sbenrap]

LOLoL...this was my response from Gigabyte tech support "We have no known issue with it, we have tested the F5 in our lab without any issue. Please redownload it"

Any luck unbricking your board? Or did you decide to just go ahead and let them handle it?

[Ace-a-Rue]

For those interested, the reply from GIGABYTE came today.

To cut it short, they basically requested to remove battery and short circuit the "clear cmos" pins.
The reason the backup doesn't work, and I quote:
"However, if system boot failed, probably there’s something wrong during BIOS flashing and caused BIOS corrupted that would make secondary BIOS doesn't work either."

There is no mention of the faulty F5 BIOS in the reply despite me specifically mentioning it in the question (as well as the resulting infini-reboot).
To me, this reply is an insult.
They do not take responsibility and are showing disrespect to their customers (and not just any customers, the most high paying ones! I do not believe for a second that they are not aware of the faulty F5 BIOS they released, enough days have passed for everyone to be updated).

I am very happy I managed to unbrick my machine, I installed STEAM on it and ran a game for a few good hours to see that my system is stable.
I wish you all luck with your boards (be it with getting it back quickly from GB or trying the method to "unbrick" it).

me TOOO about unbricking your board!

you have to understand the liability issue with admitting to a huge error like this...once you put it on paper, it opens them up to be sued for negligence and if that negligence caused harm to you or your business, you can see how that would help you to WIN!

the other thing about oriental culture...this is not to be taken in any way of condemming them; it is an explanation...they, not all, most likely the men, have this certain characteristic about acknowledging a mistake has been made....we, some americans, have the same problem...my wife was one..LOL...now she does acknowledge if she is wrong but not back way ago when she was younger; ut-eh!

again, this is not a slam on their culture...i am just trying to show you that a little understanding of why they won't admit to doing anything incorrect or wrong.

[loonym]

Mine couldn't be rescued so it's on it's way to California as I type. I still have an ongoing email dialogue with gigabyte tech support. Some of it is quite humorous. Maybe when they get sick of my baiting and quit responding I'll repost here.

[Supershanks]

Mine couldn't be rescued so it's on it's way to California as I type.

That's tough m8
However if something amusing can ever come out of this I'm sure

I still have an ongoing email dialogue with gigabyte tech support. Some of it is quite humorous. Maybe when they get sick of my baiting and quit responding I'll repost here.

Will be it Look forward to it

[Ace-a-Rue]

Mine couldn't be rescued so it's on it's way to California as I type. I still have an ongoing email dialogue with gigabyte tech support. Some of it is quite humorous. Maybe when they get sick of my baiting and quit responding I'll repost here.

this is a lesson to all of us that having 2 bioses (one as a back up) is not fool-proof unless you can manually select the 2nd bios via jumper method....this "Auto" stuff, in this situation, is for the 'birds!'

[Supershanks]

this is a lesson to all of us that having 2 bioses (one as a back up) is not fool-proof unless you can manually select the 2nd bios via jumper method....this "Auto" stuff, in this situation, is for the 'birds!'

Yes like the old Bios Saviour - proper stuff

[sbenrap]

Sorry to hear it didn't work for you loonym, how long did you try?
It took me about 4 hours in total to revive it (but then again, it would have cost me a lot to ship it to them even if they did admit to an error, which they didn't).

Ace-a-Rue: I understand what you're saying, but something along the line of "it's a known problem with *specific* configurations" would have been better (and doubt it would help with suing). The fact that just getting them to acknowledge the problem would have taken so many mails is what maddens me...
How many mails was I supposed to write until Gigabyte support agrees to RMA? Only God knows probably...
Also, they're lucky it didn't get in any papers (I'm quite surprised actually... maybe it's not that a popular board, or maybe most people don't update BIOS. I only wanted to update mine because I thought maybe it would support my memory DIMMs better...)

And the reason I choose ASUS from now on is simple, they have a method of booting ANY BIOS VERSION from USB in case you brick your machine.
Now THAT I call backup (assuming it works naturally)...

[loonym]

I surely spent considerably less than 4 hours and as to cost, as I already mentioned I had another board going back for an unrelated rma so both shipped in one box. I didn't have to exchange any emails with gigabyte to obtain an rma number, nor did I have to wait. It was simply a matter of filling out a simple online request and I received the rma# about 2 hours later. Not sure how asus got into the topic but I'll add
I've had unrecoverable asus boards, as well as no post doa's. I had the opportunity to try a p5e3-prem-wifi@n a few weeks ago. While it's undeniably a great clocker it's not without flaws. In fact sometimes it's plain buggy. Having tried both, I prefer the x48t hands down.

[Ace-a-Rue]

Ace-a-Rue: I understand what you're saying, but something along the line of "it's a known problem with *specific* configurations" would have been better (and doubt it would help with suing). The fact that just getting them to acknowledge the problem would have taken so many mails is what maddens me...
How many mails was I supposed to write until Gigabyte support agrees to RMA? Only God knows probably...
Also, they're lucky it didn't get in any papers (I'm quite surprised actually... maybe it's not that a popular board, or maybe most people don't update BIOS. I only wanted to update mine because I thought maybe it would support my memory DIMMs better...)

And the reason I choose ASUS from now on is simple, they have a method of booting ANY BIOS VERSION from USB in case you brick your machine.
Now THAT I call backup (assuming it works naturally)...

gigabyte made a huge apology to Asus for fabricating a story of problems for the latest board Asus was releasing...because of that, i doubt they wanted a whole lot of press out of this mess with a bad bios release killing many of their premiere X48T boards.

Asus is good but i heard many user complaints about their tech support being very arrogant with their customers....just be warned...it is usually not greener on the other side of the pasture when it comes to mobo makers.

[loonym]

Since we're critiquing asus I'll add this. Their lineup is so extensive that sometimes I think they have a difficult time providing equal support, bios or otherwise for all their boards.

[Ace-a-Rue]

why not bash asus in a gigabyte thread...LOL

[Supershanks]

The thing that bugs me with Asus is as said their support , also what REALLY ANNOYS, you can't easily flash back to an earlier bios.

Last Asus board I had
Asus P5E3 Deluxe Wifi One solution :-
Offical Thread ASUS P5E3 DELUXE/WiFi-AP Problems, Workarounds, BIOS info. Crazypinoy9 #382

Right in the middle of the writing of the bios shut the power off from the computer. Next turn your computer back on and put in your asus driver cd and let the bios recovery do its magic.

It works , but just to flash back to earlier Bios

P5k was the same you needed a certain version of Afudos to be able to flash back .

So while Gigabyte screwed up royally , as usual the truth is no bugger's perfect

[Ace-a-Rue]

i heard about not being able to flash back to an older bios...could you find the correct afudos program to flash with an older bios?

EDIT...wait a minute...i think i came across that problem on my Asus P5B...same thing; almost positive.

[Supershanks]

i heard about not being able to flash back to an older bios...could you find the correct afudos program to flash with an older bios?

There are always variations as I said the P5K worked with an old Afudos. The P5E3 on the above or as i found later How to Flashback Bios , the main point is why should we need to Who's the Nanny at Asus who decides we can't

[Ace-a-Rue]

yeah, i hear you about Asus into this control about flashing back.

[Ace-a-Rue]

finally sold my board, memory and Q6600...it was not due to the bad bios...i had mine already boxed up to sell before the giga released the official 'dorked' bios

have to say it was a VERY good board...i'm ready for abit's IP45 or IX48 board..bring it!

[Ace-a-Rue]

looks like gigabyte put out an updated "F5" offical bios and they have a special "FLASHSPI.EXE" and Autoexec.bat included...so...no "Qflash" is my impression to get F5 flashed...might be the problem; that is the built-in Qflash program...if they changed the boot block and Qflash doesn't update that area, that would cause your bios to continuously to loop.

[loonym]

looks like gigabyte put out an updated "F5" offical bios and they have a special "FLASHSPI.EXE" and Autoexec.bat included...so...no "Qflash" is my impression to get F5 flashed...might be the problem; that is the built-in Qflash program...if they changed the boot block and Qflash doesn't update that area, that would cause your bios to continuously to loop.

It would be interesting to decompile both those F5 bios and see what the actual difference is. Even opening them with ami tools might show something. Maybe I'll look into that if I get really bored. The way qflash works I think it's really hard to tell if it's flashing the boot block or not.

[Ace-a-Rue]

if you use the "FLASH895.EXE," which is package with F4, that will flash the boot block...but now they have the other flash program...could be the same and they just renamed it.