if anyone in this forum has UAC enabled...I'll laugh.Quote:
Originally Posted by Lukee
Printable View
if anyone in this forum has UAC enabled...I'll laugh.Quote:
Originally Posted by Lukee
Same thing :p
UAC is good for normal PC users, but not for us.
Hmm seems like this isn't the problem though.Quote:
Originally Posted by Hornet331
Am i the only one that everything works ok for :D
Sleep mode fine (rare in my experience - a huge plus, i'll be using it often when my OC is nailed down), dynamic energy saver thing fine (though i haven't started using it - does it do something similar to EIST?), Easytune fine...
I'm on a fresh vista x64 HP install right now after my raid array was buggered over the weekend so there is no trick to getting them to work :shrug:
Only thing so far to annoy me with this system is vista hangs on the 'welcome' for a good 10-15 seconds every boot, even after my fresh install. This points to one of the Gigabyte programs/utilities, though i tried disabling all my startup programs and it still happened, which points to perhaps a process. The boot log in event manager wasn't helpful, so i'll investigate further when my OC is finished. Minor annoyance i know but when you shell out the money for two of these velociraptors a faster boot is one of the things you're looking for in return!
I have everything disabled with vlite, security center, uac, system restore, firewall etc..... i mean everything is disabled. Vista 64 runs smooth as butter with all that disabled.
and ive disabled everything et6 still doesnt work for me :down:, might have to load up vista 64 bit see if that does anything
these were the settings for whats in my sig, but like i said after i flashed bios i needed more vcoreQuote:
Originally Posted by speckled10
voltages for 4.2ghz 8 hours 38 mins of prime
200 x 19 + turbo, HT on
cpu vcore 1.55v
qpi/vtt 1.535v
cpu pll 1.88v
qpipll 1.18v
ioh core 1.24v
ich i/o 1.58v
ich core 1.22v
vdimm 1.66v
qpi link was x36
and uncore was running at 3400mhz
____________________________________
voltages for 4.137ghz stopped after 14 hours of prime
197 x 19 + turbo, HT on
qpi link x 36
uncore frequency x17
vcore 1.49375v
qpi/vtt 1.495v
cpu/pll 1.88v
qpi/pll 1.18v
ioh core 1.14v
ich i/o 1.58v
ich core 1.16v
vdimm 1.66v
_________________________________________
voltages for 4.1ghz 14 hours prime
195 x 19 + turbo HT on
qpi link x36
uncore frequency x18
cpu vcore 1.45v
qpi/vtt 1.435v
vdimm 1.64v
everything else auto
_________________________________________
voltages for 4ghz 13 hours prime
191 x 19 + turbo , HT on
qpi link x36
uncore frequency x18
vcore 1.375v
qpi/vtt 1.315v
vdimm 1.64v
rest auto
edit... im trying out f4r now
at first EasyTune 6 wasn't working for me either. I had been using a hard drive off my X38 board and plugged it into this board and it took. I had SP2 installed on my Vista Ult. x64 and EasyTune 6 would give an AppCrash error and then when I clicked continue it would give me a windows sockets initialization error. Not sure if you all got that same error or not.
I thought maybe it was SP2, so I reinstalled Vista Ult x64 and loaded EasyTune 6 just after my lan drivers and it worked fine. I then installed SP2 then my drivers and it still worked.
Hope this helps someone.
-=Mark=-
Here are some tips for installing EasyTune:
1. Dont install it from an USB-Drive or Network-Share, always copy the Installer-File to a local Driver.
2. Always install it as Administrator (right click on the Installer-File and chose Run as Administrator), even you have UAC disabled.
3. Before install a new Version of ET6 uninstall any Version first witch already is Installed, and check for leftover chunk.
I have Vista x64 and Catalyst 8.12 and ET6 works great.
Hope this helps anyone
here's one of my first actual 3D bench since setting up this i7 deal.
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
http://img211.imageshack.us/img211/856/gigabyteje9.jpg
http://img211.imageshack.us/img211/g...jpg/1/w750.png
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 :(
88 has always been an open, un-allocated error code from experience dealing with manufacturers. RMA time.Quote:
Originally Posted by kayl
kayl
i got your email
i have never seen that code come up
try to loosen your mount a little
also clean and reseat the CPU
what bios are you on
I like this :up:Quote:
Originally Posted by ReverendMaynard
Seems it is 8BhQuote:
Originally Posted by kayl
Attachment 91346
Manual:
http://download.gigabyte.ru/manual/m...8-ud5(p)_e.pdf
not sure exactly what bios version i was running. I have been trying to get system to run today on air with no luck :(Quote:
Originally Posted by dinos22
I go into bios and let it sit, around 1min later system crashes and I get that error. Leave it for a few hours and try again, same issue. Looks like its either the cpu or the motherboard damit
Quote:
Originally Posted by Hornet331
thanxs for that link Hornet331, had a quick flick and found what you said on page 120 but not much other info in relation to my problem, so what does that mean??
1) Invoke all ISA adaptors ROM’s
2) Invoke all PCI ROM’s (except VGA)
I know the graphics card runs fine in my other 775 system?
Ya think it’s the mobo that playing up??
kayl, not sure thats the real problem, cause code 69 says its "turn l2 cache on" which many users its the triple channel mem in the wrong slots
I am not sure, do you have any PCI card in you system? (Sound card etc).
i always have User accounts disabled ! (easytune doesnt work)Quote:
Originally Posted by Lukee
Quote:
Originally Posted by MarkJohnson
yep , thats the Error !
Kayl are you using the the white Ram slots?? (3x Ram sticks @ Triple channel are always in White slots )
regards
You're chasing your tail with that code. Your LED post says 88, and by everything that I've been told it is an open code, meaning the board has more than one issue so by default it spits out a "blank" code.Quote:
Originally Posted by kayl
word :) Not bad for a first run on a single card. Looking for 20k tonight.Quote:
Originally Posted by Bobbylite
Quote:
Originally Posted by ReverendMaynard
Yep much better than me on 1 card, the best I can do is 18,175, and that is with my i940 at 4.4ghz, ultra 735 core, 1688 shader, 1181 mem, going up 1 notch on any ultra settings and get freezes. I guess that difference is because my ultra is at pcie 1 instead of 2, and any other tech enhancements from G90 series.
http://service.futuremark.com/compare?3dm06=9347092
That is still a sick score for an 8 series. Have you ran with HT on? I found in gave me 1100 cpu points, which might be irrelevant to the overall score, but interesting none-the-less. All I heard before the i7 released what that HT was going to cripple 3D perf....bull :banana::banana::banana::banana: lol.Quote:
Originally Posted by rge
Going for 700/1500/1050 tonight for a run at 20k.
Here's my compare. You have me creamed in cpu score.
http://service.futuremark.com/compare?3dm06=9341263
I think my next move is 64b Vista. 32b can't be helping.
Yep, that is with HT on. Good luck with 20k. I cant decide on when to upgrade mine, waiting at least month or two to see what comes out.Quote:
Originally Posted by ReverendMaynard
thanks :up:Quote:
Originally Posted by rge
The next couple of months we're going to see die shrinks, process shrinks...yadda yadda. Not really anything worth waiting for unless you're into a hot box like the proposed GTX295 GX2.
I think 2 or 3 260 216's are the seet spot right now for i7 3D bench madness :)
Count me in! And you're right about GTX260 x2/3, especially if the 55nm are selling now.Quote:
Originally Posted by ReverendMaynard
I have found the LED post codes to be not that useful also, i've never had big problems where i was stuck and couldn't post but i've had the floppy related error code 6F when it was definitely a memory problem. It's like the LED display isn't quite keeping up with the data being processed so it crashes out before it's on the right code or something.
I get that same error as well, but it is when I push the Bclk and I don't have enough qpi/vtt voltage.Quote:
Originally Posted by Xello
Never been a fan of two cards sandwiched together. AMD approach to multi gpu, single slot cards is much more desirable. The 55nm thing is understandable but the way that nVidia is sneaking them in under the same product name is bull:banana::banana::banana::banana:. I love nVidia's cards, but the way they do business is evil.Quote:
Originally Posted by Xello
As for the LED posts...I think they are extremely useful, except when you get an empty block lik 88. I've had two boards that gave that error, both times it resulted in a board RMA, which fixed the issue.
After experiencing the software nightmare that was quad-crossfire 4870x2 i have to disagree, they can keep their 80c idle temps! The design has its merits but the gpu furthest from the fan gets very toasty. That wasn't the reason i decided to ditch the cards, but NV's temps are just sensible with their cooler's design. @ 100% fan speed on both 4870x2's they would not go below 51c, no joke! And it sounded like a jet engine taking off.Quote:
Originally Posted by ReverendMaynard
Anyway going OT a bit...
Yeah LED posts are very useful i was just saying on this board it doesn't seem to work out, for example displaying the floppy error when it's memory / QPI related :shrug:
I have seen better temps from 4870x2's at half the fan speed. No joke.Quote:
Originally Posted by Xello
BOT...
If you find an error code that is false, report it to Gigabyte. Chances are, they had no clue about quite a few possible errors and yeah it ended up giving you the wrong one. That would piss me off lol. They may be able to fix that if there is enough input from end users....who knows. This is the first Gig board that I've ever owned and it's pretty decent. Haven't had a failed overclock attempt with it yet.
I WCed the dual 4870x2s and they are at 38C and 28C with no noise. Those fans were terrible at 50%
I know, you need to keep these at 45% or higher to keep them stable, especially mine since i have the TOP overclocked version. I wish an aftermarket cooler would be released already, air cooling tho, i dont do water.Quote:
Originally Posted by Lukee
New BIOS:
GA-EX58-Extreme-BIOS F5a
GA-EX58-Extreme-BIOS F4
GA-EX58-UD5-BIOS F4
GA-EX58-DS4-BIOS F4
http://forums.tweaktown.com/f69/giga...st-bios-28441/
Merry Christmas !!! :toast:
thanks stasio,Quote:
Originally Posted by stasio
whats changed from f4r to f4 ?
anyone tried the vdroop pencil mod on ud5 yet ?
merry christmas guys :up:
New BIOS added:
GA-EX58-UD5 - F5a
GA-EX58-UD4P - F4c
GA-EX58-UD4 - F3f
Link above
Just trying F4 now.
Bios F4 (Extreme and UD5)
- Fix S3 resume turbo mode issue
- Fix DualBIOS recovery issue
- improve System Stability
If updating from F4j Extreme or F4n UD5, will also get
-Fixed VT function, multi reset XMP
-pink/red warning voltages
-enter without scrolling CAS
you need waterQuote:
Originally Posted by GAR
Did they put in a 40X for QPI multi? That would be a nice Christmas present!!
With F4 i got probs get in windows at 190 bclk, more vcore also no change it.
Maybe it's my 12 Gb dont know, for now i stay with F3 200x21 all enabled, memory 8-8-8-20 T1 :D
Holy crap, F4 ?final was the buggiest bios I ever tested, that includes every F4beta and every single ?20+ beta bioses on my old P35 DQ6.
Every time I reboot, blank monitor screen, could not hear windows load either, just freeze on blank screen but with computer running. Each time I rebooted, had to turn off short time (hard restart) +/- clear cmos. I downloaded again, flashed again (thinking bad flash even though no error message), but same thing. Then panicked that my mobo crapped out. But reflashed all way back to F4j, working fine again now. F4 would not even reboot correctly with all stock/auto.
Anyone else tries let me know what happens...but if you get a blank screen with rebooting and cant get out of it, clear cmos works. I am thinking whatever "fix" they did to the dual bios or S3, my computer did not like.
If anyoen tried F5a for the extreme, please share your experiences.
Bios F5a for GA-EX58-UD5
http://www.fileden.com/files/2008/7/...82/EX58UD5.F5A
http://www.abload.de/img/unbenannt62je.png
Tried 5a and 4 both give hardware errors in windows,back to the f4r.
well that explains why they released f5a 7 hours after f4 :eek:Quote:
Originally Posted by rge
im on f4r at the moment
i have no problems with F5a (UD5), can run same settings as on F4r.Quote:
Originally Posted by mearle73
Just tried F5a Extreme, I am still getting problems with reboot. Hard reboots, ie shut completely down, restarts ok. But reboots, upon restarting, system does not turn on keyboard (no green light) and does not turn on monitor (no green light and blank screen), even waiting 2-3 minutes and can not hear windows load. Also if enter bios, hit save and exit, again blank screen, and no green light on keyboard. Going from f4m to F4/F5a some serious bugs...but like freshy said, with very quick release after looks like they are trying to fix.
thanks for testing these out guys....I sure as hell ain't doing it ;) F4j is a keeper for my particular set up.
Happy Holidays :)
damn I just installed my ex58-ud5. it came with the F3 bios should I upgrade?
Already give my link above.Quote:
Originally Posted by Chri$ch
How can F4j be so stable and the more recent bios's lose that stability? I don't know much about bios programming but surely you want to leave the bits that are ok :D
Think i'll be on f4j forever, no complaints though i wouldn't know it was a beta bios.
Sry, didnīt see it :(Quote:
Originally Posted by stasio
I think they need to go back to f4j, and start reprogramming from there. Or make one change, get rid of CAS scrolling, and then call F4j, F4 final.Quote:
Originally Posted by Xello
Safan80, I think most on UD5 are using F4r or F4n beta bioses, though some with UD5 can correct me if I am wrong. I would not use F4 final, it is still to early in beta stage:p:
F3 is stable, but you dont get the permanent turbo multi, which is especially useful for i920 to have 21 multi, as 19 and 21 multi's seem to work better on i920, just like 21 and 23 multi works better on i940, ie can use much less vcore for same mhz.
does gigabyte still have the beta bioses up?Quote:
Originally Posted by rge
All the beta bioses just disappeared from everywhere since this am. Station drivers you can thank for being slow:p:.. still has f4r for UD5, may want to download before it disappears from there as well.Quote:
Originally Posted by safan80
http://www.station-drivers.com/page/...a-ex58-ud5.htm
ive still got f3, f4e, f4k, f4l,f4n,f4r,f4 and f5a for ud5
if ya's cant find em anywhere pm me and i'll email em to ya's
best ones for me so far f4k and f4r
just got F4r thanks. I think I'm going to bed now :lol:
freshy: don't delete them I want those lol
official F4 bios now on Gigabyte's page.
http://www.giga-byte.com/Support/Mot...ProductID=2958
You know since you said that, I had to try F4 again. And you are right. F4 works fine on auto settings, rebooted 3x without issue. I need to actually boot up at everything auto before complaining about stock:D.Quote:
Originally Posted by Ghigo
I made changes 1 at a time. It is bclk that causes problem. At 170 bclk reboots fine into windows. 180 bclk, will not reboot, have to do a hard restart. Also at 180 cant save bios and get into windows until doing a hard restart. 180 bclk would work providing you are always willing to shut computer completely off everytime you need to reboot, ie only hard reboots. Back to 170 bclk, and reboots without issue, no need to do hard restart. This is similar problem that occurred on my P35 DQ6 that was solved by messing around with pcie volts/clock. Have locked 100, but no help.
Just could not imagine a bios being released where stock did not work, but apparently just any bclk ~180 and above that does not work correctly.
EDIT: the only fix for bclk of 180 and above on F4 final bios seems to be upgrading to F4j bios. I tried altering cpu/pcie clock drive, pcie mhz up and down, pcie volts, all other voltages including vcore/qpi/vtt/mem, and mem and uncore down to r/o mem, but F4 and 180+ bclk just can not get to reboot, hard boot to windows only, and if go to bios then save, have to shutdown pc manually or occasionally do clear cmos to get back.
Just played Crysis Warhead for an hour...smooth as butter, but I noticed a flashing led at the left of the chipset(almost under the block).
Anyone know what this little guy is for and what it represent when it's flashing?
Thanks for being the guinea again RGE, let us know if you resolve that issue.
thanks man, mine got tossed :(Quote:
Originally Posted by Xello
Flashing what colour? Page 26 of manual has info on the NB led's, one is overvoltage the other is temp. Overvoltage has off = normal condition, green = slight, yellow = moderate, and red = high. Temp is off = below 60c, green = 61-80c, red = over 80c.
Doesn't mention that they can be flashing :shrug:
Interesting to read that for me also, i didn't have a program to give me a NB temp reading, someone recommended Speedfan and said that 'temp 3' was NB, which for me was 61c, but with no light on that can't be my NB temp.
green iirc. It stopped maybe 30 seconds after I stopped Crysis so it would lead me to believe it's temperature. I have everest and it shows me idling at 35C MB. Might not be the right temp though. Checking for newer version.Quote:
Originally Posted by Xello
Thanks for checking that out Xello :up:
Hey Rev, take a look at your Max NB temps under load. I think it is a new function of the F4 bios(es). I looked in the manual as well and nothing is clearly documented. Nice clocks BTW. :up:Quote:
Originally Posted by ReverendMaynard
Thanks :)Quote:
Originally Posted by ShoNuff
lol just did that. 55C max running prime blend. I should note that this did not happen with the 8800GT installed, and I've been pounding the absolute :banana::banana::banana::banana: out of this rig the last few days after getting the gtx260.
http://www.lavalys.com/forum/index.p...05&#entry19805
I think that everest beta version in post 12 will read NB correctly and mobo sensor (different). Speedfan version 4.37 temp 3 on mine corresponds to NB reading on everest in linked version, and both of those NB temps go up in accordance with IR reading on base NB sink, so I think they are reading correctly on mine. prior to putting a fan on mine NB temp loaded 55C, I put spot fan on, now NB max 47C.
I just use spot fans, silent on medium setting and put out lot air, 1 mem and 1 on nb. I tried small nb fan, but didnt do squat for temps, still loaded 54C
Hi
New oficial/final F4 bios for Extreme/UD5 & DS4 released!!
Quote:
F4 Bios Oficial (Extreme/UD5 & DS4)
1. Fix S3 resume turbo mode issue
2. Fix DualBIOS recovery issue
3. Improve System Stability
Also new F5a Beta Bios for Extreme/UD5 and other bios for a lot of X58 Giga Models
Quote:
GA-EX58
GA-EX58-Extreme - F5a
GA-EX58-Extreme - F4
GA-EX58-UD5 - F5a
GA-EX58-UD5 - F4
GA-EX58-UD4P - F4c
GA-EX58-UD4P - F3
GA-EX58-UD4 - F3f
GA-EX58-UD4 - F2
GA-EX58-UD3R - F2
GA-EX58-DS4 - F4
>> http://forums.tweaktown.com/f69/giga...st-bios-28441/
regards
It is fan time perhaps. Thanks for the link :)Quote:
Originally Posted by rge
Official F4 BIOS didn't do anything to resolve my S3 resume issue - with or without Turbo on.
All the new F4 did was prevent me from booting at my previous 200x19 settings so I had to go to 190x20 instead for 3.8GHz. Vcore went up from 1.2875v to 1.3v in order to boot.
Well that is 3 people in this thread that tried bios F4, and 3 people that had same bug with high bclk. F5a same issue, hope GB is not going to build all new bioses around this bugged one.Quote:
Originally Posted by yenniedn
Official F4 BIOS actually hung a couple of times on POST and I had to reset before even being able to get into the BIOS setup screens. Entered my previous 3.8GHz settings and F10'ed. Vista would not boot up and would BSOD each time. Changed my multiplier and added voltage just to get Vista to boot.Quote:
Originally Posted by rge
Going to try F5a and see if it's any good . . . if not, then it's back to F4m for me.
Overclocking guide for Gigabyte X58 for I7 920 to 4 Ghz
http://lakesidepc.com/Core.i7.920.oc....12.12_ENG.pdf (Thanks to Guru3d Member Lahomer for posting it)
OK, so F4 didn't solve anything for me so I went to try F5a on my Extreme - now I've got the exact same problem you described in your previous post. Clearing CMOS (which I've done 3x or 4x now) does NOT fix it for me and I simply cannot boot into Windows now. I even went and reflashed my BIOS back to the last good one for me (F4m) and now my computer is completely useless!
Can someone either post a link for F4j or email it to me?
This really, really, really sucks. This board has been a really big headache for me ever since I got it!!!
Quote:
Originally Posted by rge
http://www.station-drivers.com/page/...x58-extrem.htm
F4j extreme here
As last resort, unplug, take the cmos battery out for few minutes, that has worked for me when clear cmos doesnt. Also make sure right after flashing bios to f4j, you load optimum settings then save before rebooting to clear out all buggy crap from F4/F5a.
This is unbelieveable. Absolutely NOTHING will allow my computer to boot again right now.
Clearing CMOS = nope.
Unplugging everything including the CMOS battery = nope.
Flashing to previously working BIOS'es = nope.
Loading optimized defaults = nope.
Loading fail safe settings = nope.
Repairing Windows via the Vista installation DVD = nope.
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.
This is the most problematic (yet most expensive) motherboard I've ever had!
EDIT; these boards seem to be shaping up as somewhat problematic if nothing more than a simple bios flash is causing so many problems. Never owend a Gigabyte board before but I have a X58-UD5 Extreme and an Asus P6T-Deluxe sitting before me atm and am just waiting for my wb to arrive before trying them both out. By the looks of things if this Gigabyte causes half the problems I'm seeing here it won't last long in my house, shame because I was looking foward to a new experience but a new experience filled with headaches isn't what I had in mind.....time will tell but I now have some reservations about the UD5-EXT after reading all the goings on in this and other threads.
This is the price you pay for being an early adopter - which I never mind doing. However, I got the 680i and 780i boards when they first came out and they too had their growing pains. The difference was that EVGA was much more proactive, knowledgeable and helpful that Giga Tech Support has been. I've called them four times now and they've yet to ask my once about what my BIOS settings are, what other hardware I use or anything. They just ask me what the problem is - and after I tell them, their only answer is to wait for a new BIOS that "might" fix the problem. Well, neither beta nor "official" BIOS updates have done anything to fix my S3 resume problem. In fact, they've only caused me more problems and set me back.Quote:
Originally Posted by lowdog
Anyways, my system is back up after a fresh OS install. In the process of reconfiguring and re-installing everything. I swear, it seems just like the other day I was doing all of this . . . oh wait, it WAS just the other when I did do this!!! :down:
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.
Hey guys im having trouble overclocking my ud5, and also trouble with ggb's apps!
When i OC my system, 2.6 > 4.0, or even the teeniest amount, 2.66 > 2.7 for example, my com boots up like normal! I can get into bios, the raid shows up fine and all..
but it cant reach my windows loading screen (the one with microsoft Corp, and the loading bar), it just wont get there! What could be the problem? I think its my windows, not my rig right?
Tried following EXACTLY like in the 'how to overclock ur ud5' guide, and still no avail
And im also having the, Easytune6 crash on startup and Energysaver 'your bios does not support bla bla'
Using Vista SP1 64-bit
Hope u guys can shed some light on this! Thanks in adv
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.
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!
damn the F3 bios is unstable at stock. running F4r now.
:ROTF: 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) ? :p:Quote:
Originally Posted by yenniedn
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. :cool:
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. :p:
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
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
What software you recommend? I was planning to use my beloved Ghost 2003 in DOS mode...Quote:
I suggest you to invest in a decent backup program if you plan on using a raid 0.
Lol seriously?Quote:
Originally Posted by Hornet331
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.
Does anyone know if the software DES is fully compatible with the board overclocked?Quote:
Heres what i did incase anyone else is having my problem..
Uninstalled Easytune6 & EnergySaver
Disabled CIA
I never uses third party raid onboard adapters for harddrives...Quote:
Originally Posted by jcool
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. :p:
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.Quote:
Originally Posted by yenniedn
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)Quote:
Originally Posted by jcool
It is for me, though i'm not really using it yet.Quote:
Originally Posted by vega22
yeah same here, F4j S3 works without a problem. :yepp:Quote:
Originally Posted by Xello
Thx. I want to use this thing but in my xp x64 the DES freeze all the OS when i push "on"Quote:
It is for me, though i'm not really using it yet.
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 :)Quote:
Originally Posted by rge
yeah some people are just to careless and then get angry when they have to reinstall everything. :p:Quote:
Originally Posted by rge
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 :D
Look, buddy, you got a problem with my post, report me. Don't flame. :down:Quote:
Originally Posted by lowdog
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.
Quote:
Originally Posted by yenniedn
I'm having the same issue here.Quote:
Originally Posted by vega22
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???
Quote:
Originally Posted by kayl
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:mad:
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.Quote:
Originally Posted by Hornet331
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.
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.
Quote:
Originally Posted by 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?
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.
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:Quote:
Originally Posted by ReverendMaynard
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!"
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.
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.Quote:
Originally Posted by yenniedn
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!