Gigabyte EX58-UD5/Extreme Discussion Thread

[SteveRo]

ymir, can you boot into windows if you set bios to default?
If not, try F8 and safe mode - if this works you probably have a scrogged driver, if this does not work try to repair windows.

[Zmir]

if i change it back to the regular clocks, voltages it has no problem going back in even after the failure. If i adjust the clock but leave the voltages alone, same thing happens! it seems if i adjust the clock the slightest bit it wont get in windows, will try to underclock it and see if it still has this problem, if its still there then its definately my windows!
and no i havent tried going into safe mode/repairing after overclocking, will try that now!

[safan80]

damn the F3 bios is unstable at stock. running F4r now.

[Hornet331]

So I'm having to reformat my RAID O OS partition and do a fresh OS install!!! This is the FOURTH time I've had to do so since I bought this board about a month ago. I've been having so many problems with this board since I upgraded from my Q6600 system that I held off on validating the Vista install until things were stable. Just YESTERDAY I went through the whole call Microsoft and jump through their hoops routine to activate my Vista install. Finished installing ALL of my apps just this afternoon. And now, it's ALL gone and I get to do it all over again.

sorry but that just made me laught.... you have a raid 0 (suicide raid) and run the OS on it and you have no mirror backup... are you a masochist (J/K) ?

I had my share of experience with onboard raid 0/10 and the one thing i learned from it, was that raid zero has earned its nick "suicide raid" for real.

First thing i have done when i still had my raid, was a mirror backup of my system partition. Sometimes a failed oc could rendered the whole os unusable... well no big deal with a mirror -> 30min and system was back to where i started.

I suggest you to invest in a decent backup program if you plan on using a raid 0.

Its funny to see people blame the board, when the actual cause is something elese.

[Zmir]

Okay im not sure which solved it, but its totally solved, system runs smoothly at 4.2Ghz! Its faster than i could have ever imagined O.o
http://valid.canardpc.com/show_oc.php?id=469817
DONT laugh at my graphic card please!!!

Heres what i did incase anyone else is having my problem..
Uninstalled Easytune6 & EnergySaver
Disabled CIA

[vega22]

Big problems with F4 here too. System unstable. The worst thing is return to f4j failed to recover the stability that had been achieved in this bios before. Now I'm doing the second deep clear cmos. Battery off, etc

I suggest you to invest in a decent backup program if you plan on using a raid 0.

What software you recommend? I was planning to use my beloved Ghost 2003 in DOS mode...

[jcool]

sorry but that just made me laught.... you have a raid 0 (suicide raid) and run the OS on it and you have no mirror backup... are you a masochist (J/K) ?

I had my share of experience with onboard raid 0/10 and the one thing i learned from it, was that raid zero has earned its nick "suicide raid" for real.

First thing i have done when i still had my raid, was a mirror backup of my system partition. Sometimes a failed oc could rendered the whole os unusable... well no big deal with a mirror -> 30min and system was back to where i started.

I suggest you to invest in a decent backup program if you plan on using a raid 0.

Its funny to see people blame the board, when the actual cause is something elese.

Lol seriously?
I've ran a non-backuped raid 0 for OS and all my Data for years now, since 2001 actually. Different arrays of course, but I never had one fail on me on an Intel controller. And I usually get like 100+ crashes due to unstable OC before I find my max stble setting.. maybe something else is defectve m8?
Did you usethose 4 differently coloured Gigabyte SATAs to do your raid? Don't. Use the normal ICH10R ports. I ran a testsetup with SSD raid from the mobo and it crashed like 40 times during testing.. no problems at all.

[vega22]

Heres what i did incase anyone else is having my problem..
Uninstalled Easytune6 & EnergySaver
Disabled CIA

Does anyone know if the software DES is fully compatible with the board overclocked?

[Hornet331]

Lol seriously?
I've ran a non-backuped raid 0 for OS and all my Data for years now, since 2001 actually. Different arrays of course, but I never had one fail on me on an Intel controller. And I usually get like 100+ crashes due to unstable OC before I find my max stble setting.. maybe something else is defectve m8?
Did you usethose 4 differently coloured Gigabyte SATAs to do your raid? Don't. Use the normal ICH10R ports. I ran a testsetup with SSD raid from the mobo and it crashed like 40 times during testing.. no problems at all.

I never uses third party raid onboard adapters for harddrives...

Anyway count yourself lucky that you have gone this far wihout an incident, just search the web.

Last week a friend of mine had to reinstall his os on a PT6, cause his raid 0 failed. (and his system was't even oced).

Running os, and even saving data on none backuped raid 0 is careless. But im not the person whos gona tell you what you should do with your data.

[Xello]

P.S. add BIOS F4j to the list of BIOS'es that does not solve my S3 issue. So (in order) F3, F4m, F4 (official), F5a and F4j don't do anything for S3 resume.

The board is not your problem, then, i'm the proof, i can resume without issue on f4j. Unless you have a different revision of the board, if one even exists yet.

Did you usethose 4 differently coloured Gigabyte SATAs to do your raid? Don't. Use the normal ICH10R ports. I ran a testsetup with SSD raid from the mobo and it crashed like 40 times during testing.. no problems at all.

I recommend the opposite, my ICH10 raid 0 was corrupted over the weekend after simply trying to stress test 4ghz QPI. I've been using the hardware raid since then and no problems (actually speeds up the post process, too)

Does anyone know if the software DES is fully compatible with the board overclocked?

It is for me, though i'm not really using it yet.

[Hornet331]

The board is not your problem, then, i'm the proof, i can resume without issue on f4j. Unless you have a different revision of the board, if one even exists yet.

yeah same here, F4j S3 works without a problem.

[vega22]

It is for me, though i'm not really using it yet.

Thx. I want to use this thing but in my xp x64 the DES freeze all the OS when i push "on"

[rge]

To me the most important component when OCing is backup image software. Back to normal in 7 minutes whenever a software issue arises that I think will take longer than a few minutes to fix. Not to mention, I am using an old XP license, forget calling microsoft with reactivation each time I have to reinstall. I am not even using raid (1 intel SSD was expensive enough), and I would not dream of running without imaging software, already used it twice since I7 build, once was corrupted OS from bad stick ram...not dealing with driver error messages every time reboot.

[ReverendMaynard]

To me the most important component when OCing is backup image software. Back to normal in 7 minutes whenever a software issue arises that I think will take longer than a few minutes to fix. Not to mention, I am using an old XP license, forget calling microsoft with reactivation each time I have to reinstall. I am not even using raid (1 intel SSD was expensive enough), and I would not dream of running without imaging software, already used it twice since I7 build, once was corrupted OS from bad stick ram...not dealing with driver error messages every time reboot.

Word. Why just yesterday I lost my large RAID0 array. No worries with a 2tb NAS and Acronis TI

[Hornet331]

To me the most important component when OCing is backup image software. Back to normal in 7 minutes whenever a software issue arises that I think will take longer than a few minutes to fix. Not to mention, I am using an old XP license, forget calling microsoft with reactivation each time I have to reinstall. I am not even using raid (1 intel SSD was expensive enough), and I would not dream of running without imaging software, already used it twice since I7 build, once was corrupted OS from bad stick ram...not dealing with driver error messages every time reboot.

yeah some people are just to careless and then get angry when they have to reinstall everything.

[Xello]

Indeed. I was too, years ago, but after it happens a certain number of times you realize all by yourself that keeping important stuff on a seperate drive is wise

[zlojack]

Honestly mate if that sort of comment is the culmination of your thought processing abilities toward delivering helpful advice pertaining to the poster's mentioned problems then suck it back up your anus because that's where this sort of drivelly diahorea comes from.

Look, buddy, you got a problem with my post, report me. Don't flame.

It's called a joke. After all the stuff he tried and he's still having trouble, I was trying to inject a bit of humour. If you look at his response, you can see he took it properly.
Merry Christmas.

No, unfortunately, I could not . . . because the mighty e-peen that I once had when I bought what was supposed to be the top-of-the-line Gigabyte X58 motherboard is all shriveled up now.

[yenniedn]

Big problems with F4 here too. System unstable. The worst thing is return to f4j failed to recover the stability that had been achieved in this bios before. Now I'm doing the second deep clear cmos. Battery off, etc

I'm having the same issue here.

F4m was working well for me (minus the S3 resume issue). F4 FUBAR'ed everything up and now, no matter what BIOS I use, I cannot get the same performance/stability back like it was on F4m. Even applying more voltage doesn't help.

What can I do just to get back to where I was before on F4m before the "official" F4 BIOS screwed everything up???

[hiwa]

can anyone tell me what the 8.8. error code means on the GIG X58 -UD5, i dont have the manual with me so cant look it up
Pics not the best, but this is what im refering to




if i leave the board for 6 hrs and then try it again it boots fine, then i clear bios and restart and it happens again. So not sure if its the cpu or the mobo

got it on my board yesterday,what did u do? is your board dead ?
after 15h i power on my pc and no way to start

[yenniedn]

sorry but that just made me laught.... you have a raid 0 (suicide raid) and run the OS on it and you have no mirror backup... are you a masochist (J/K) ?

I had my share of experience with onboard raid 0/10 and the one thing i learned from it, was that raid zero has earned its nick "suicide raid" for real.

First thing i have done when i still had my raid, was a mirror backup of my system partition. Sometimes a failed oc could rendered the whole os unusable... well no big deal with a mirror -> 30min and system was back to where i started.

I suggest you to invest in a decent backup program if you plan on using a raid 0.

Its funny to see people blame the board, when the actual cause is something elese.

Hey, I DO blame this board because I've been building my own systems for 7-8 years and (since motherboard prices keep going up) this is the most expensive motherboard I've ever purchased and it's also the buggiest. The issues I've describe didn't just start with flashing to F4. In fact, flashing to F4 was an attempt to fix problems that have persisted ever since I got the board. I've had slow boots, S3 problems and board SATA ports since the beginning. I've resolve the slow boots but not the S3.

F4, as you can see from the other posters above, really f@cked up some people's setups. In my case, it made a finicky board even worse.

As for my RAID and restoring stuff, I keep all my important data on my two non-RAID'ed 1TB drives and also have them backed up on externals. My raptor RAID is just for OS and apps - which, under normal circumstances, I don't mind re-installing because it's not that hard to do. If that was the only problem then no big deal. But you add in all the other problems I've had with this board (which has been TWO Extremes now due to one RMA) - then, yeah, I have every right to be pissed at this board.

[ReverendMaynard]

everytime I've fooked my RAID it was my fault. Might want to re-think your last 7-8 years of building pc's and throw what you know out the window.

[yenniedn]

The board is not your problem, then, i'm the proof, i can resume without issue on f4j. Unless you have a different revision of the board, if one even exists yet.

Then what do you suggest is the problem? My specs are in my sig.

Are you saying that you originally had an S3 resume issue that was later resolved on F4j?

I received the board with F3 and had the S3 issue from the get go. Only discovered this forum at the time F4m was released so used F4m - which helped my stability but did not resolve S3. Went to "official" F4 - which really screwed everything up. Then F5a - then reformat then finally to F4j . . . but it seems that ever since "official" F4, nothing has been the same since I cannot get back to my previously stable 3.8GHz OC no matter what I do.

So even though I'm on F4j, I don't think I'm really on F4j because I think something F4 crap is still lingering and messing with everything. So even if F4j "would have" resolved my S3 issues under "normal" circumstances, I think I have to clean up the previous F4 fiasco before things "might" work properly.

[yenniedn]

everytime I've fooked my RAID it was my fault. Might want to re-think your last 7-8 years of building pc's and throw what you know out the window.

I've very seldomly fooked up my RAID. And as I said, it's not that big a deal to re-do the stuff. The previous times I've installed the OS are:

1) initial build
2) upon receipt of my 2nd board due to bad SATA ports (I know it wasn't necessary but I did it anyways)
3) wanted to test (by process of elimination) what was the cause of the 3 to 4 minute slow boot issue I previously had
4) the last one was the F4 BIOS fiasco (this was the only one that HAD to be done)

I'm not saying I'm the best system builder or that I know everything and that's the reason I'm on here - is to seek advice on how to fix these annoying issues. But when I've been on the phone with Gigabyte Tech Support four times and the best (and ONLY) answer they can give me each time is: "wait for the next BIOS release" . . . it's bull-crap. If that's their only answer and F4 BIOS caused me and others the same issues - I don't have a right to be frustrated with this board?

In fact, if I called Giga Tech right now to ask how to "recover" from the BS that was the F4 BIOS, I'm positive that they'll say: "Just wait for F5!"

[vega22]

I think, only think, that i start to understand exactly what problem have entered the "infamous" F4 Bios. Seems to be the voltage adjust in IOH Core. Before, i just had to set this setting in Auto (1.1000v in ET6), @ 19x211, F4j, for thousands of Linpack x64 pass. Now, i begin to achieve stability by raising the voltage to 1.2000v, in F4j. Anyway, it´s early to be sure.

[Xello]

Then what do you suggest is the problem? My specs are in my sig.

Are you saying that you originally had an S3 resume issue that was later resolved on F4j?

It suggests that there is a component in your rig that does not like sleep mode, my first suspect would be your 4870x2. I had two of them in my old blackops and sleep mode resume gave me BSOD every time. One thing is for sure, sleep mode is finicky with hardware, that's why i was delighted to find out it worked with this board properly.

The board had F2 i think when i received it, and i flashed to latest (F4j at the time) within an hour of getting it so i have no idea if it was buggy with the retail bios, i suspect it wasn't but not sure. If not your video card i think the only other culprit could be one of your drives. Haven't much experience in trouble shooting this, it's simply been my experience that certain combinations or certain components themselves may be to blame for the sleep mode trouble alot of people suffer.

I'm not sure if it's possible for parts of an old bios code to 'linger', unless the bios flash was incomplete (which should instead brick your board), if you're on F4j but can't achieve the same overclock as you had on F3 i'd return to F3 for now.




On another note, it occurred to me that the reason i can't achieve cas 8 on my memory is pretty obvious - the fact that the more expensive Dominator 1600mhz cas 8 kit exists means corsair are binning chips at that level, so i probably won't get to cas 8 on the normal XMS3 kit. Not too bothered though, with 9-8-8-20 and 18,000mb/s read on Everest it's more than i'll ever need!