Gigabyte EX58-UD5/Extreme Discussion Thread

Quote:

---

Originally Posted by tipes

Hi all,

Compliments of the season to you all - now for the question.

Just recently put together a system with Gigabyte EX58 UD5+ Corsair dominator 1600 ram And I7 920 chip all runs fine But .....

When I boot up either cold or restart the post screen - ie the first Bios screen never shows up - I have tried the setting in bios for the splash screen on or off plus pressing the Tab key but it refuses to show.

The only way I can get it to show is if I go into bios and load optimized defaults and then it shows splash screen and I can press tab key to see post screen. Anybody else seen this or know the cause of it?

I have loaded the official F4 bios to fix the resume from sleep issue with str, but I had the above problem before this anyway - any ideas anybody?

Would be grateful for input on this one

Ps the problem even happens at stock speeds - only running at 3gig at the mo - with turbo mode ie only 3 gig on 21 multi if that makes sense.

Mark

---

Does this happen all the time or just when you cold boot?

If it happens all the time, are you running SLI or Crossfire? For example, running Crossfire and having your monitor plugged into the wrong card will cause the problem you described: you can't see the POST screen and get no video signal until you boot into Windows. Connecting your monitor to the other video card will resolve this.

If you're NOT using multiple GPU's, then I'm not sure what the problem is and would need more info before trying to determine what it could be.

Quote:

---

Originally Posted by ReverendMaynard

If it does what you need it to do on a daily basis, whether it be folding, rendering, benchmarking, gaming, surfing....putting a system through that much stress to prove stability is for a niche crowd saf; it is far from a standard and never will be.

---

Fully agree

Quote:

---

Originally Posted by yenniedn

Does this happen all the time or just when you cold boot?

If it happens all the time, are you running SLI or Crossfire? For example, running Crossfire and having your monitor plugged into the wrong card will cause the problem you described: you can't see the POST screen and get no video signal until you boot into Windows. Connecting your monitor to the other video card will resolve this.

If you're NOT using multiple GPU's, then I'm not sure what the problem is and would need more info before trying to determine what it could be.

---

Hi

Thanks for your post. I am only using a single 8800gts graphics card, and yes this problem happens all the time. I have also tried both connections to the graphics card with no joy. Hope I can find out what is causing this as it is slightly irritating. If you need more info - let me know.

Mark

So what version of EasyTune 6 really works with X64 Vista?

Quote:

---

Originally Posted by ReverendMaynard

If it does what you need it to do on a daily basis, whether it be folding, rendering, benchmarking, gaming, surfing....putting a system through that much stress to prove stability is for a niche crowd saf; it is far from a standard and never will be.

---

the system doesn't even have to be close to stable for web surfing, or benching. Linpack is made by intel for intel cpus and it will grow over time. I have games that stress the ram more than prime, or OCCT does. Your OC could do what you need it to do for a limited time, but if you start getting data corruption or hardware failures all that work is for nothing. If your OC is not rock solid you could end with data corruption in anything you esp. if you use the onboard controller to control your hard drives. Hey it's your RM data and not mine so it doesn't matter to me if your OC is just prime or OCCT stable.

Quote:

---

Originally Posted by BulldogPO

So what version of EasyTune 6 really works with X64 Vista?

---

the one not released yet ;) :rofl:

Quote:

---

do you guys get higher or most stable overclocks from f3 to f4j on the extremes?

Like any stress testing screenies with difference?

---

I ditched F3 because the F12 boot menu didn't work when OCed.. with F4J it works fine.

Happy new year guys :)

My linX 3hr~ stable settings yesterday failed blend in 9hr 32mins. I guess linX isn't infallible, or you cannot use it as a quick test, certainly not 5 or 10 runs- you need to run it as long as blend.

All we were testing for prime, occt and Linpack in the socket 775 discovered that Linpack quickly discovered the errors in vcc and vdimm, but NO the errors in MCHv. I think things like that happen too in 1366. It is necessary to do tests with everything.
Perhaps one of the most interesting problems that introduces Linpack is the effect of the heat. My hard drive is still dead, but my system is resurrected. Unplugged the hard drive, and left the system at idle for several hours (accidentally), and to my surprise everything is back to being as before:D.
I have made many tests to understand exactly what happened, and I discovered that switching off only one of my three Noctua that blow to the board, i need automatically to increase a notch the IOHv to pass Linpack test. Linpack, because of the enormous stress of heat it produces, and not only because of the electrical stress, has shown me a direct and immediate impact between a couple of degrees plus or minus and the stability of my system as never before saw overclocking socket 775. However, it is very difficult for me to know whether the main reason for this discovery are my OC values, or is the x58 architecture, or is the Gigabyte Extreme ...

Quote:

---

Originally Posted by safan80

the system doesn't even have to be close to stable for web surfing, or benching. Linpack is made by intel for intel cpus and it will grow over time. I have games that stress the ram more than prime, or OCCT does. Your OC could do what you need it to do for a limited time, but if you start getting data corruption or hardware failures all that work is for nothing. If your OC is not rock solid you could end with data corruption in anything you esp. if you use the onboard controller to control your hard drives. Hey it's your RM data and not mine so it doesn't matter to me if your OC is just prime or OCCT stable.

---

You reply too me like I don't know wtf I'm doing when oc'ing lol. I don't give a rats ass about corrupt data, I've been overclocking for 10 years, I've learned how to effectively back up my data. I'm just glad that I'm not an OCD stability guy. Life it too short for that bs.

Quote:

---

Originally Posted by Xello

Happy new year guys :)

My linX 3hr~ stable settings yesterday failed blend in 9hr 32mins. I guess linX isn't infallible, or you cannot use it as a quick test, certainly not 5 or 10 runs- you need to run it as long as blend.

---

who said its a quicktest anyway. :p:

Quote:

---

Originally Posted by Xello

Happy new year guys :)

My linX 3hr~ stable settings yesterday failed blend in 9hr 32mins. I guess linX isn't infallible, or you cannot use it as a quick test, certainly not 5 or 10 runs- you need to run it as long as blend.

---

QFT

Linpack is awesome for speed at quickly pinpointing OC points that are a notch or so from stable, much quicker than prime, but if going to equate to prime 12 hrs, it has to run for many hours as well.

I have yet to see a 12 hour prime blend or small ffts oc on mine fail linpack, even overnight linpack runs, though others claim to. Also on my rigs, have not seen a 100-200 pass linpack run AT MAX MEM setting fail prime yet, though others have, and no doubt possible. A 200 run linpack on max mem takes about 6 hrs. On core i7 need to run two version to get near max mem though, one at near max, other on "infinite" run of 256 or 512. The newest version use two at half max...havent played with it enough to know how it compares to max mem.

I have never had a crash from bad OC after being 12 hrs prime stable, so I will continue to use that as my gold standard, though that may change as i use linx more. Though it is not a bad idea to run at least short runs of both, after being stable in one, as they test in different ways and one or the other may pinpoint a weakness better in your particular rig.

Quote:

---

Originally Posted by vega22

All we were testing for prime, occt and Linpack in the socket 775 discovered that Linpack quickly discovered the errors in vcc and vdimm, but NO the errors in MCHv. I think things like that happen too in 1366. It is necessary to do tests with everything.

---

Prime stressed the MCH even less then linx, the only test program that i know that stressed the MCH to some point was memtest.

Thats why i still keep memtest in my test setup. I tested my setup for 7h linx stable and have no problem so far.


Sure there are people out there that run 12h+ prime linx etc. but what they get from that i dont know. :p:

My system runs 12-14h a day when im home but far away from the stress levles linx puts on the system.

For myself i consider a system stable after 6h+ of linx, everything else is a waste of time in my eyes, cause it adds nothing to stability at my usage behaviour. :yepp:

But the discussion about stability is as old as ocing itself.

I´m not the only one who has seen fail OCCT and Prime in 5 minutes, while Linpack was over 50 runs, everything because of the MCHv. But Memtest can be as effective as Prime or OCCT for MCHv. I have not tested that.
It´s impossible to reach an agreement between a game system and a workstation talking about stability. Everyone do what the peace of their minds need.

Quote:

---

Originally Posted by Hornet331

Prime stressed the MCH even less then linx, the only test program that i know that stressed the MCH to some point was memtest.

Thats why i still keep memtest in my test setup. I tested my setup for 7h linx stable and have no problem so far.


Sure there are people out there that run 12h+ prime linx etc. but what they get from that i dont know. :p:

My system runs 12-14h a day when im home but far away from the stress levles linx puts on the system.

For myself i consider a system stable after 6h+ of linx, everything else is a waste of time in my eyes, cause it adds nothing to stability at my usage behaviour. :yepp:

But the discussion about stability is as old as ocing itself.

---

What vega22 said is perfectly true.
Prime blend --> custom --> check box "run FFT inplace" is the quickest and most reliable way to determine a mobo problem. Linpack won't detect these unless they are severe, as for memtest.. well, if memtest freezes due to a failing MCH, your rig is unstable to the extent that Windows won't even start to boot 99% of the time. :rolleyes:

HI GUY ,F5A BUG BIOS ,CAN'T 2000CL7 F4J F4M PASS OK

http://pic.kaixin001.com/pic/photo/4...4_38474280.jpg

2000 CL7 PASS CL7-7-7-21 1T D9JNL

http://pic.kaixin001.com/pic/photo/4...4_38474999.jpg

the problem is, theres no MCH voltage any more. :p

It was true for the C2, and for C2 is till would use Prime as my main stability testing tool but not for Ci7.

MCH voltage is gone now and instaed it is linked to QPI/VTT (Vdimm for L3 cache).

I booted windows several times and linx crashed after several minutes, and all i had to do was increasing QPI/VTT, so its not ture anymore that you can't boot windows with to low qpi voltage...

Many seem to forget that everything that was ok C2D is not valid for Ci7.

Anyway as i said befor how to test stability and even the basic definition "what is stable" is not defind by anyone, its rather a thing of personal reception.

I have my own guidelines and standards what i consider stable and how i test it, and i never had problems since 8 years now, so for my needs my methods are the correct way. :p:

Anyone can do as they please i dont stop anyone form doing things how they want, i just that for me some things that got mentined here are a waste of time in my eyes.

Quote:

---

Originally Posted by BulldogPO

So what version of EasyTune 6 really works with X64 Vista?

---

The one that came in CD of Gigabyte works fine for me in Vista Bsns 64Bit SP1 version.

Only problem is BCLK in QuickBoost looks funny ... 560Mhz, 600 Mhz and 640Mhz(It is probably showing Bclk x 4)

Love to know how you got that to work, tried every version and it still crashes on Vista64 SP1&2

Quote:

---

Originally Posted by BulldogPO

So what version of EasyTune 6 really works with X64 Vista?

---

I got the newest version working with a fresh install. Mine was corrupted somehow. All I did was install Vista Ult x64 sp1, then install easytune first off and it was fine. I even installed sp2 and it still worked.

-=Mark=-

Quote:

---

MCH voltage is gone now and instaed it is linked to QPI/VTT (Vdimm for L3 cache).

---

Hehe...IOH is the x58 northbridge voltage...

Quote:

---

Originally Posted by vega22

Hehe...IOH is the x58 northbridge voltage...

---

Yeah but the MCH (memory controller) is now on the CPU not the NB.

Quote:

---

Originally Posted by vega22

Linpack, because of the enormous stress of heat it produces, and not only because of the electrical stress, has shown me a direct and immediate impact between a couple of degrees plus or minus and the stability of my system as never before saw overclocking socket 775

---

It's also difficult for me to believe my temps are holding me back, which are topping 55-60c, when i see people here topping 70-80c regularly, and 90c+ without fatal issues.

Quote:

---

Originally Posted by Hornet331

who said its a quicktest anyway. :p:

---

Compared to prime, pretty much everyone, on the posts i was reading, on this forum and others. If you google you'll find many posts stating between 5 and 20 runs as commonly used to verify complete stability. Like i said yesterday (or the day before maybe) the reason i switched to it was because prime started causing crashes after huge periods of time, and i was after a quicker way to test. Linpack was a much quicker way to test, by popular opinion anyway. If i'm going to have to run even that for 6-8hr+ to get reliable results, i'll stick to what i know (prime) :up:

ok I think I might still be drunk from last night but dont most mother boards for sli/quad sli need the cards to be on the top pcie lane and the bottom lane? I am trying to change some things on mine :) but the sli connector is short and it looks like both cards will have to go into the top and the middle lane. From reading the manual it seems like that is the way to do it. :confused:

I think I might leave it for another day cause the beers is not helping :ROTF:


gigabyte x58 extreme motherboard

Quote:

---

Originally Posted by bench2die

ok I think I might still be drunk from last night but dont most mother boards for sli/quad sli need the cards to be on the top pcie lane and the bottom lane? I am trying to change some things on mine :) but the sli connector is short and it looks like both cards will have to go into the top and the middle lane. From reading the manual it seems like that is the way to do it. :confused:

I think I might leave it for another day cause the beers is not helping :ROTF:


gigabyte x58 extreme motherboard

---

You wouldn't want a card in the bottom slot anyway, if you can help it, it runs at half the bandwidth of the top + middle slot (x8 compared to x16+x16)

Quote:

---

It's also difficult for me to believe my temps are holding me back, which are topping 55-60c, when i see people here topping 70-80c regularly, and 90c+ without fatal issues.

---

It´s important to note that i have spoken of thermal issues only in relation to use of a very strong test as Linpack. My cpu and mobo temperatures are good, even by air. But, as i´m experiencing, the key is the union of heat stress plus electrical stress. I think that is not important 10 degrees at 3.8Ghz, 180 bclk, full load Prime, but maybe only 3 degrees at 4.0Ghz, 211 bclk (my settings), full load Linpack. Comes to my mind the word "electric fatigue" or, better, "PCB fatigue".

Quote:

---

Compared to prime, pretty much everyone, on the posts i was reading, on this forum and others. If you google you'll find many posts stating between 5 and 20 runs as commonly used to verify complete stability. Like i said yesterday (or the day before maybe) the reason i switched to it was because prime started causing crashes after huge periods of time, and i was after a quicker way to test. Linpack was a much quicker way to test, by popular opinion anyway. If i'm going to have to run even that for 6-8hr+ to get reliable results, i'll stick to what i know (prime) :up:

---

The key is that with Linpack we can achieve very quickly (generally) a system full Prime95 stable. But is not so fast to reach a system Linpack stable (although this is faster than achieving a stable prime95 system using only prime95). The problem is compounded if Linpack from a certain OC level begins to introduce abnormal errors due to its enormous and abnormal power.