If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Look in my personal experience updating Bios using FlashSPI I got immediate looper restarts without POST (the system was turning on for 2-3 seconds and then turning off in a loop), and there was no way at all to access Bios to Load as needed Optimized Defaults, so I had to Reset CMos using the jumper on Mobo and all went fine.
Using @Bios I had same issue, but no luck at all clearing CMos, so I had to RMA the Mobo!?
So a suggestment could be to load Bios Optimized Defaults before to update Bios and also after the update as needed, to avoid any kind of issue, but before to do it write down your settings somewhere to not get crazy.
I hope it could help you,
Adriano
Intel Xeon x5650
Gigabyte GA-EX58-UD4 F11T
6Gb Walton Chaintech @ 1600Mhz 7-7-7-18-1T 1.64v
Noctua NH-U12P Push/Pull
Radeon HD4850 512Mb @ 700/1150Mhz MUSASHI cooled
2 Intel X-25V in RAID0
2 Barracuda ST500320AS in RAID1
Spare Maxtor 320GB
Psu Seasonic S12 II 620W
U2-UFO Case cooled by ~750 Cfm!
Win10 64Bit
and Now Comes...(F9I)...
What's new or different to F9
The Link to the Bios Update does not Have any explanations
It would be nice To have the same Information as the "latest overclocking program......Sticky section when a new Version
is available There is a Comprehensive description of the Changes in the new Version......
I am not Complaining......
Just Asking.....
Core 2 Duo E8400 (E0) Gigabyte EP45-UD3P (F9 Bios) Cooler Master V8 Corsair Dominator 1066 PC2 8500 C5 2x 2gb w/cooling fan
(5.5.5.15 at 2.1v) Western Digital 640 blue caviar (2 unit) Palit Hd 4870 sonic dual cooler Cooler Master Silent pro 700w Cooler master RC 690 w/ 6 fan 120mm
Look in my personal experience updating Bios using FlashSPI I got immediate looper restarts without POST (the system was turning on for 2-3 seconds and then turning off in a loop), and there was no way at all to access Bios to Load as needed Optimized Defaults, so I had to Reset CMos using the jumper on Mobo and all went fine.
Using @Bios I had same issue, but no luck at all clearing CMos, so I had to RMA the Mobo!?
So a suggestment could be to load Bios Optimized Defaults before to update Bios and also after the update as needed, to avoid any kind of issue, but before to do it write down your settings somewhere to not get crazy.
I hope it could help you,
Adriano
Thanks for the tips. Previously, I have been using ASUS boards and their BIOS is great. Even after update, all my previous settings are saved and loaded by default. Their BIOS is very stable and fast.
This is my first Gigabyte board. Although the components quality are great, I feel they need to put some more work on refining the BIOS. I was quite shocked to get all kinds of stability problem after updating to the latest BIOS so hopefully future ones will be better. Hope they will fix the SATA AHCI ROM ASAP. I just cant wait 10 secs for it to detect all the SATA devices.
Latest Update : After flashing to F6a, I have no more problems resuming from S3 sleep mode. Good job and hope the slow AHCI ROM will be fixed in the next release.
I wish there was a fix for some psu (TT 1200W) that has problem to start after shutdown from Vista or Windows 7 OS. (GA X58 EXTREME)
I am using that PSU without major problems on the same mobo ( + vista64)...
I know others on this forum have had complaints, but so far so good.
Are you having the cold double boot problem? If so, I don't think that has anything to do with the PSU. Others with different PSU's as well as X58's from other manufacturers are having the same issue...
I also had the double boot "problem" some time ago, but it all of a sudden stopped (After (20th?) BIOS reflash + PSU poweroff/unplug for a couple of minutes). I'm not quite sure what fixed it, but I doubt it was due to cycling power on the PSU. You could still give it a try though ^^
i thought i would just mention that i upgraded to F9a (mobo is GA-EX58-UD4P), and resume from S3 now seems very stable with all voltages set to auto, bclk=166Mhz and multiplier=18 (cpu = 3Ghz). thanks to gigabyte for continuing to refine the bios.
well, unfortunately even though the system wakes very reliably now even when overclocked, i've found that mprime will fail very quickly if it's started after an S3 sleep/resume cycle. yes, i am overclocking and i have most everything set to 'auto'. i know you are not supposed to do this. however, the mprime failure happens even if the system is not overclocked (BCLK=133MHz, cpu=2.66MHz) this is a UD4P with bios F9a. unfortunately i'm not running windows so i cant look at all the clock/voltage parameters after wake, but i assume that the bios must be messing up a clock frequency or a voltage after resuming from S3.
edit: i take it back. it just failed after a cold boot, no sleep. this sucks - maybe something is wrong with my cpu.
edit again: nope, it was the dram - fails memtest86 near the 11GB mark. bumped the voltage a little bit and all seems well. interesting that i never had this problem before bios F9a.
Power Supply: Corsair HX520W
Mainboard : Gigabyte GA-EX58-UD4P rev 1.0
Chipset : Intel X58
Processor : core i7 920 rev C0 CPU HeatSink and Fan (HSF): Cooler Master N520
Physical Memory :Corsair XMS 1333 (6x2GB)
Video Card : Radeon HD2600 256MB
DVD-Rom Drive : LG SATA BD/HD-DVD reader
Operating System : some unix or other
well, unfortunately even though the system wakes very reliably now even when overclocked, i've found that mprime will fail very quickly if it's started after an S3 sleep/resume cycle. yes, i am overclocking and i have most everything set to 'auto'. i know you are not supposed to do this. however, the mprime failure happens even if the system is not overclocked (BCLK=133MHz, cpu=2.66MHz) this is a UD4P with bios F9a. unfortunately i'm not running windows so i cant look at all the clock/voltage parameters after wake, but i assume that the bios must be messing up a clock frequency or a voltage after resuming from S3.
edit: i take it back. it just failed after a cold boot, no sleep. this sucks - maybe something is wrong with my cpu.
F9a on my UD4P was unstable for me and did not reliably wake. While our symptoms sound different, I would suggest going back to F8a if you can and seeing if your reliability improves.
well, unfortunately even though the system wakes very reliably now even when overclocked, i've found that mprime will fail very quickly if it's started after an S3 sleep/resume cycle. yes, i am overclocking and i have most everything set to 'auto'. i know you are not supposed to do this. however, the mprime failure happens even if the system is not overclocked (BCLK=133MHz, cpu=2.66MHz) this is a UD4P with bios F9a. unfortunately i'm not running windows so i cant look at all the clock/voltage parameters after wake, but i assume that the bios must be messing up a clock frequency or a voltage after resuming from S3.
edit: i take it back. it just failed after a cold boot, no sleep. this sucks - maybe something is wrong with my cpu.
Well since you are using Auto when overclocking that is likely the whole issue you are having with resume. They system must be stable to resume properly and Auto often just will not cut it, or gives things to much voltage which can also lead to instability.
But yes, I use UD4P myself so I can assure you that turbo is disabled after a resume which would leave you with a unstable 20 multi and likely also incorrect voltages for the clocks in question. It seems to also change CAS Latency to 4, which is this is a true report to software of this change would also lead to MUCH instability as well all know DDR3 cannot do CAS4. So even if the reported 4 is correct or not, it could be lower then it should be set to and just reporting wrong, but either way I think this also is causing issues.
I have sent in a report about these issues so they are aware of it and I am sure new beta's will soon try to address these issues.
I doubt anything is wrong with your CPU, you just need to setup the BIOS properly. If you need help with that please make a thread and we can help. Even at stock speeds Auto may not properly set things up depending on your ram and ram speed, ect.
I also agree with Anpheus, if you had stability on F8a then I would go back to it as F9a offers no changes/fixes that I have observed
Well since you are using Auto when overclocking that is likely the whole issue you are having with resume. They system must be stable to resume properly and Auto often just will not cut it, or gives things to much voltage which can also lead to instability.
But yes, I use UD4P myself so I can assure you that turbo is disabled after a resume which would leave you with a unstable 20 multi and likely also incorrect voltages for the clocks in question. It seems to also change CAS Latency to 4, which is this is a true report to software of this change would also lead to MUCH instability as well all know DDR3 cannot do CAS4. So even if the reported 4 is correct or not, it could be lower then it should be set to and just reporting wrong, but either way I think this also is causing issues.
I have sent in a report about these issues so they are aware of it and I am sure new beta's will soon try to address these issues.
I doubt anything is wrong with your CPU, you just need to setup the BIOS properly. If you need help with that please make a thread and we can help. Even at stock speeds Auto may not properly set things up depending on your ram and ram speed, ect.
I also agree with Anpheus, if you had stability on F8a then I would go back to it as F9a offers no changes/fixes that I have observed
well i just edited my post - it turns out it was the dram, and was not related to sleep at all. it eventually failed mprime even after a cold boot.
suspecting the memory, i left memtest86 running overnight and found that between 11 and 12GB there were failures. the memory is rated at 9-9-9-24 and 1333MHz, and that's how i have them set in the bios - no overclock for the ram, just the CPU. if i do not tweak the bios settings at all, when bclk=133Mhz and cpu=2.6Ghz, the bios actually pics 8-8-8-19 (IIRC) for the memory, so in fact i had to manually set it to 9-9-9-24 and lower the memory multiplier when setting up the CPU overclock. anyway i increased the Vdimm to 1.580V and memtest86 is happy now, at least for 1.5 iterations.
i actually did not have stability on F8a. the system would die about 1/2 the time resuming from sleep. in fact F9a has been very stable for me resuming from sleep. like 100% stable. i have not repeated my mprime testing yet because i want to let memtest86 run for a few more hours to really prove that the memory is now stable.
sorry for the bad science and the noise. i'm really confused though, since F9a has been very stable from an emprical point of view. like i said i cant see all the multipliers and voltages because i'm not running windows. i actually have turbo mode turned off right now, maybe that's why i don't see any problems?
Power Supply: Corsair HX520W
Mainboard : Gigabyte GA-EX58-UD4P rev 1.0
Chipset : Intel X58
Processor : core i7 920 rev C0 CPU HeatSink and Fan (HSF): Cooler Master N520
Physical Memory :Corsair XMS 1333 (6x2GB)
Video Card : Radeon HD2600 256MB
DVD-Rom Drive : LG SATA BD/HD-DVD reader
Operating System : some unix or other
I am using the modded bios 8b with the new AHCI ROM posted by noangel in post 943. Can someone request that GB put this new AHCI ROM in next beta version of 8 for extreme.
The new AHCI ROM in modded 8b bios cuts 8 seconds off boot time for the extreme. The annoying 8 second delay of dots where the hard drive search occurs on unmodded bios 8b with OLD AHCI ROM is no longer tolerabe, now that I have been spoiled with the better ahci rom......just would like all future bioses to have the new ahci rom...if someone would pass along the request I would appreciate it.
3770K 4.7 - Windows 7 64 - GB UD5h - Dom 2133 - corsair 850 - Intel 520 SSD - 680 GTX - 26 inch Samsung LCD Lian Li G70 WC
Comment