Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: spurst on January 06, 2012, 07:12:27 pm
-
http://www.overclock.net/t/1034724/gigabyte-p67-z68-boot-cycling-problem/590 (http://www.overclock.net/t/1034724/gigabyte-p67-z68-boot-cycling-problem/590)
This thread is going on 60 pages long now. I have this problem. Numerous other users here, and elsewhere have this problem. Can we at last know what the status on resolution for said problem is? It almost seems related to QPI/VTT/RAM voltages and the way these boards handle them.
I've noticed for the past 6 Gigabyte boards I've used in client builds there is a boot cycling problem one way or another. After shutdown and waiting for approx. 10 seconds booting up again results in boot cycling and results in the board reverting to using the backup BIOS which still boot cycles. Even after copying the new BIOS to the backup BIOS boot cycling still continues. I end up flipping the PSU switch and unplugging the power cable and waiting for a few seconds before the board would boot past POST screen.
Has anyone else encounter this with their new Gigabyte P67/Z68 boards?
I've had 3 builds with other makers, 2x MSI and 1x Asus and those board did not exhibit this problem, both boards are P67 boards.
Facts about Boot Loop:
1) On a cold boot your motherboard will POST up to the "Memory Testing" (which is like the first 3 lines on your POST screen) line and then restarts on it's own. It will continue to do this for a infinite number of times, theoretically. If someone actually wants to sit in front of their computer and start a count on how many times it restarts, be my guest.
2) Restarting will not work, as it continues to boot loop. You'll have to hold down the power button for 5 secs (or whatever amount of time) until your PC manually shuts down. Turning it back on immediately after a shutdown continues the boot loop, you must wait at least 20-30 seconds.
3) In order to get the board to boot properly you'll first have to turn off your power supply (the switch on your PSU if you have one) and pull the power cord. Wait approx. 30 seconds, reinsert the power cord, flip the switch and press the power button. This should get your system to boot normally on 80% occasions according to my experience. Some members have stated that the CMOS must be reset, 24-pin mobo plug needs to be unplugged and CMOS battery has to be removed. You are free to try those methods if the pulling of the power cord method does not work.
There have also been reports of disabling certain options in your BIOS that will remedy the boot loop. First off, those people were not experiencing a boot loop, just a hiccup on a old chipset.
This boot loop problem unique to P67/Z68 chipset and so far most relevant on Gigabyte boards.
At the time of this writing all Gigabyte Z68XP version motherboards only have 1 BIOS update to choose from, which isn't really a update at all.
4) No matter what you do, flashing the backup BIOS with the latest BIOS does not solve the issue. Sadly on some of the newer Z68 boards, THERE'S ONLY 1 BIOS!
Edited by AzO - 7/24/11 at 10:52pm
If you have this problem, please post your system specs, so maybe we can try and figure out some type of resolution.
My specs:
Z68X-UD3H-B3
i5 2500k
Cooler Master Hyper 212
2x 4gb Corsair XMS DDR3 (also tried crucial ballistix)
SATA RAID 0 2x WD raptor 36g
SATA RAID 0 2x Seagate 7200.12 500g
Galaxy GTX 460 SLI 768
Lite-ON DVDRW
Sony Blu Ray
PCP&C 760Watt PSU
I've found that manually setting my memory voltage to 1.65v and QPI/VTT to 1.2v seems to cut down on the boot loop. Doesn't entirely fix it, but does cut down the occurrence.
-
Gigabyte Z68XP-UD3P - Boot Loop / Cold Boot issue
At the end of last year I purchased a Gigabyte Z68XP-UD3P, It was correctly set up for stable usage and overclock usage with 10hrs of prime testing and 5hours of intel burn test at max. I could play BF3 for hours and such. However it wasn't long till I ran into issues whereby, when I started the system up from cold it would just shut off and just do it again and again. Pulling the psu plug, put it back in and the system would boot up fine and be up for hours. However I wasn't sure if this started when I flashed to F6 or Before..
After talking to Support To get this issue fixed I flashed to F7A, but It took awhile to get the system back up at all it would constantly boot loop not giving me much chance to set the bios defaults. When that was done it finally booted and I was up and running for about 8hrs before I went out. Came back started the system up, straight away it shuts off with the cold boot issue.
I've been back and forward with support and they then released a F7B to fix the cold boot issue, again it took some time to get the system back up and running with the annoying boot loop problem. I read a number of forum threads and found that the possible cause was related to the VTT/QPI voltages not being set correctly on AUTO when using XMP PROFILE 1 for memory. It should be setting to 1.2V however the VTT/QPI remains at 1.056V VTT/QPI which is too low, So i set this manually to 1.2V thinking it would finally fix the cold boot issue. But unlike before it lasted 3DAYS and I thought it was fixed :D. Yet the cold boot issue started again :( , this boot loop/cold boot issue can happen at STOCK and Overclocked settings.
Speaking to a number of forum members they told me the correct way to flash, not just flash and be done with it. Support released a F7C bios which every time so far support says " THIS FIXES THE COLD BOOT ISSUE ", Hold on a min support you said F7A / F7B fixes the cold boot, make up your mind.
This was my post using F7C
F7C is the worst bios i've ever used to get it working right with boot loops and a cold boot issue. The Bios still sets the VTT too low when set to AUTO and using xmp Profile 1, the vtt volts don't increase and have to be manually set. But with Bios F7C I had trouble even getting that far!
1. Made sure my bios was set to default settings and used my usb stick to flash to the new F7C.
2. I powered down the system as it told me too, took the psu cable out, pressed the power switch on the psu and system to clear out any left over voltage and also cleared the cmos.
3. Powered up the system and it instantly shut off with a cold boot issue, it did this again after that. So I took out the psu cable put it back in and tried again. I was able to get into Bios.
4. Set to Default settings and rebooted, It hung on the Bios logo so i hit the reset button. Apparently the reset button can cause awful boot loops which it did. It then ended up in a continues boot loop which never happened in any previous bios flash. I was finally able to get back into bios and again set it to default and then it worked.
5. As i was able to set it to default I then proceded to flash the backup bios.
6. Rebooted the system and back in bios it said failed on overclocked settings, even though I had not done any overclocking!. I also noticed again that the VTT voltage as still only at 1.056v when on auto with XMP profile 1.
7. Set my overclocked settings, set the voltages as they should be because VTT and Main memory voltage on Auto doesn't work I was able to get into windows.
I'm using F7C now even though it cold booted last night, It didn't this morning.
Other threads with the issue from other members
http://www.overclock.net/t/1034724/gigabyte-p67-z68-boot-cycling-problem
Other members with the issue Just a few quoted
Originally Posted by MOOGLEYS View Post
Same cold booting issue this morning with either BIOS and stock settings.
Board is going back today and will order a replacement later. Last time I use a gigabyte board. Edit - just rang the retailer for an rma and was told that they have had a lot of these boards returned for this issue?
Originally Posted by nxcess View Post
I get the problem at stock. It seems to make no difference if overclocked or not. It has once again stopped my ssd working and each time I have to put it in an old system to get it going again....
Originally Posted by Jahlord View Post
After experiencing this problem , I googled for solutions.
Seems I'm screwed
However there was this which may help support get this issue fixed!
Mine seems to be resolved after using DVID instead of LLC for overclocking. System booted up on first try.
Come on support get this issue fixed!, it's obviously more of a widespread problem than just me
Intel Core i5-2500K 3.30GHz (Sandybridge) Socket LGA1155 Processor - OEM
OcUK GeForce GTX 560Ti 1024MB GDDR5 PCI-Express Graphics Card
Gigabyte Z68XP-UD3P Intel Z68 (Socket 1155) DDR3 Motherboard
Samsung SpinPoint F4 320GB SATA-II 16MB Cache - OEM (HD322GJ)
60GB SSD used a Cache Drive
Corsair V2 600W Power Supply
Kingston HyperX Genesis Grey 8GB (2x4GB) DDR3 PC3-12800C9 1600MHz Dual Channel Kit (KHX1600C9D3X2K2/8GX)
These are my overclocked settings, THE COLD BOOT ISSUE HAPPENS AT DEFAULT ASWELL
\MB - ( M.I.T )/
\Advanced Frequency Settings/
CPU CLOCK - 33X
BCLK - ( DISABLED ) left at default 100mhz
EXTREME MEMORY PROFILE XMP - ( PROFILE 1 )
SYSTEM MEMORY MULTI - ( AUTO )
\Advanced Cpu Core Features/
CPU CLOCK RATIO [33X]
PWN FREQUENCY CONTROL [ AUTO ]
INTERNAL CPU OVER CURRENT PROTECTION [ AUTO ]
INTERNAL CPU PLL OVERVOLT [ENABLED ]
RATIO CHANGES IN OS [ DISABLED ]
INTEL BOOST TECH [ ENABLED ]
RATIO 1 - 4 [ 47 ]
TURBO POWER LIMIT [ 300 ]
CORE CURRENT [ 300 ]
CPU CORES ENABLED [ ALL ]
CPU ENHANCED HALT C1E [ AUTO ]
C3/C6 STATE SUPPORT [ AUTO ]
CPU THERMAL MONITOR [ DISABLED ]
BI-DIRECTIONAL PROCHOT [ AUTO ]
\Advanced Memory/
EXTREME MEMORY PROFILE X.M.P [ PROFILE 1 ]
SYSTEM MEMORY MULTI SPD [ AUTO ]
PERFORMANCE ENHANCE [ STANDARD ]
DRAM TIMING SELECT SPD [ AUTO ]
CHANNEL A - B [ AUTO ]
\Advanced Voltage Settings/
MULTI-STEPS LOAD-LINE [ LEVEL 6 ]
CPU VCORE [ 1.340V ] ( TEST WITH PRIME 95/INTEL BURN TEST AND THEN LOWER THE VOLTS UNTIL UNSTABLE TO FIND YOUR LOWEST STABLE VOLTAGE )
QPI/VTT VOLTAGE 1.050V [ 1.190v - 1.20v ]
SYSTEM AGENT VOLTAGE 0.920V [ AUTO ]
DYNAMIC VCORE [ AUTO ]
GRAPHICS DVID [ AUTO ]
CPU PLL VOLTAGE 1.800V [ 1.750-1.800V ]
DRAM VOLTAGE 1.500V [ 1.550-1.616V ] ( LOWER OR HIGHER DEPENDING ON MEMORY REQUIREMENTS )
DRAM VREF 0.750V [ AUTO ]
DRAM TERMINATION 0.750V [ AUTO ]
CH-A/B ATA VREF 0.750V [ AUTO ]
CH-A/B ADDRESS VREF [ AUTO ]
\Misc Settings/
ISOCHRONOUS SUPPORT [ ENABLED ]
VIRTUALIZATION TECH [ ENABLED ]
\Power Management/
HPET SUPPORT [ ENABLED ]
HPET MODE [ 64BIT ] - 64bit windows versions
\Pc Health/
CPU SMART FAN CONTROL [ DISABLED ]
-
I too would like to see this issue addressed by gigabyte. This is my first gigabyte board, and will be my last if we do not hear some answers soon.
-
Hi
I am not a Gigabyte official but I agree that there does seem to be plethora of these problem systems at the moment. No official answer has been forthcoming that I am aware of apart from the BIOS updates.
I haven't got access to this board to be able to test out a couple of theories which is always a problem and I have to rely on manuals.
Has anyone tried setting a HDD Delay in the BIOS ? A few seconds should do. Maybe someone could try it and get back to me with the result. ;)
-
DM, are there any gigabyte employees that use this board?
We're looking at over 60 pages of posts over at overclockers, so its seems to be a fairly wide-spread issue that would be in gigabyte's best interest to address, versus users trying to solve this on their own.
There's a pretty significant number of owners with issues, and that's just one enthusiast site! Gigabyte is risking losing all of these users as future customers, not to mention should this potentially turn into a class action lawsuit or massive recall for pushing out a pile of defective boards.
All of my other Gigabyte boards have been great, and I've been buying them for years. However, I built 3 more systems last week, and until Gigabyte at least attempts some type of resolution on this problem, I won't even consider another Gigabyte board.
Now, that my rant is over - I'll try the HDD delay, because I want my system fixed.
Also, If Gigabyte needs a board for testing - I'd be more than happy to SWAP you my board for a known working board of the same model. Z68X-UD3H-B3
-
The only Gigabyte employee to frequent this forum on a regular basis is runn3R the Forum Administrator. You could try talking to him but I don't know if he would be able to help you.
There is of course GGTS also you could try.
Just enter your email address and click on the language of choice. For the UK:
GGTS http://ggts.gigabyte.com/
Please expect several days for a reply.
For other countries:
http://uk.gigabyte.com/support-downloads/support-downloads.aspx
-
The only Gigabyte employee to frequent this forum on a regular basis is runn3R the Forum Administrator. You could try talking to him but I don't know if he would be able to help you.
There is of course GGTS also you could try.
Just enter your email address and click on the language of choice. For the UK:
GGTS http://ggts.gigabyte.com/
Please expect several days for a reply.
For other countries:
http://uk.gigabyte.com/support-downloads/support-downloads.aspx
Done this alot, it's because of my contact with them they they keep releasing more beta bios's
F7B - F7C - F7A, now they mention F7B again :p
-
- MOOGLYS -
Just re-started and it cold booted twice then booted normally. Seems it is not ram related... thought I was on to a winner.
- HORROWOOD -
I have used corsair vengeance low profile (1.35v version), corsair vengeance with the large heatspreaders (1.5v stuff), ballistix tracer, ocz gold and some generic crucial ddr3. All of them do it. All of them pass memtest.
Edit: i doubt it will be fixed, this problem has been on going for months.
What the hell is up with these boards?
-
I think Neil has quoted me from ocuk but I'm also having the cold boot issue with this board and an I5 2500k cpu. I Have just tried some corsair vengeance lp 1.5v ram and thought it was ok but it did it again just now after a re-start.
If this could finally be sorted it would be great as I have always been a gigabyte customer but this is getting a bit silly now with this board.
-
I am sure that Gigabyte is attempting to find the cause of this issue and hopefully they will have a fix soon. I just think they are a bit snowed under with other issues right now and are probably putting all their techs behind them.
-
As mentioned by neil I also have this problem.
Mine actually seems to be worse. It will randomly switch off/freeze whilst in use or even just on the desktop doing nothing. It will then boot loop until it feels like working again.
It is completely random on how to get it working again, clearing the cmos and killing the power a few times tends to do it.
The last time it did it I was playing skyrim, it switched off and the boot loop started again. It then started up and decided to flash itself to the backup bios, this then disabled the SSD caching and lost a load of my data.
I have tried several sets of ram and two power supplies (the 2nd of which is probably the best power supply available and was far from cheap, thanks gigabyte for causing me to waste lots of money trying everything possible). I have also tried two seperate graphics cards.
I have tried memory timing and voltage recommendations from corsair on two sets of ram. I have also tried OCZ gold, crucial ballistix tracer and crucial value ram.
I have tried flashing the latest beta bios that has just been released, that does not even work at all. It will not post and then flashes the backup bios. Great.
The only thing I have noticed is that it seems to be memory related, with the corsair vengeance low profile it seems to do it more often. It will die and boot loop the most when playing football manager 2012 with the corsair LP. With the ballistix tracer when playing football manager the RAM activity LED's do indicate a lot of RAM activity, it however works the best with the ballistix tracer. It still dies eventually.
I really can not be bothered with this board anymore. I will be buying something else so I can actually use my PC.
-
I've sent a message to support and directed them to this thread, doubtful they will reply though :(
-
Hi Neil79,
Well Ultim8 may have just read about this.....you never know.
teknology9
-
Hi, I got a new system about 4 weeks ago with the Z68XP-UD3R mobo. After working fine for 2 weeks, got the reboot loop issue. The mobo was replaced under warranty. The rev 1.3 replacement (same model mobo) ran fine for about 2 weeks, but now it's happened again..! Starts up, stays on for 2 seconds, powers down, repeat until I turn off the power at PSU. No video on startup, no chance to reflash bios, no nothing...
specs are: i5 2500k, Gskill ripjaws 8Gb ddr3, Gainward GTX570, 120Gb OCZ agility 3 SSD, 1Tb seagate and coolermaster hyper 212 CPU cooler.
-
Well Ultim8 may have just read about this.....you never know.
Ultim8 certainly did read this thread earlier but that doesn't mean that he is going to do anything about it necessarilly. The more people who are aware of the problem the better though. ;)
-
Ultim8 certainly did read this thread earlier but that doesn't mean that he is going to do anything about it necessarilly. The more people who are aware of the problem the better though.
Hi DM, yes I know , the point is the post may have come to his/her attention......that is all....no more....no less. :)
Teknology9
-
Oh. Right, I understand then. I thought that you were insinuating that he was going to do something about it. ;)
-
Oh. Right, I understand then. I thought that you were insinuating that he was going to do something about it.
No.....look below...its there in black and white. ::)
"Well Ultim8 may have just read about this.....you never know."
It's clear to most people to read and understand......but thank you for sharing your fascinating interpretation of the above with everyone!!!! :D
Teknology9
-
My problem also has the random freezes, and boot cycling, as noted by horrorwood.
Is anyone who is having these issues NOT using an i5 2500k?
I also have an i3 2100, and I'm going to toss that in there for testing. I actually had to go out and buy parts for a 2nd system because my primary system is so unstable, I cannot trust it for my daily work. I am beyond annoyed at this point. I work full time in IT - I should not be working for free trying to troubleshoot issues for my own PC build. Sorry /endrant.
So thus far I've tried 2 different power supplies. 4 different types of ram (all pass memtest). The system actually passed a prime95 burn in, but then it will sporadically lock up while sitting idle, doing nothing (while I am reading web pages in between scrolling). I've tried 2 different Video cards, and SLI vs Single (although all cards have been Nvidia - 460gtx sli / 8800gt). A different Hard Drive versus 2 SLI SATA setups, different DVD-Rom. Thus far, all things are pointing at the board, the processor, or a combination of how the two play together.
I've reinstalled Vista 64, and Windows 7 x64 so many times now, that Microsoft has to be wondering what's going on with my Keys. I just hope this extra information helps.
Like I said, if Gigabyte wants my system for testing, please send me something comparable that works. I'd be more than happy to submit a sample so they can get to the bottom of the issue. I have a feeling this is a larger issue than we think it is. I'm betting most are just dealing with the "boot cycling" think its user-related - ie I screwed up my windows install or bios settings somehow. However... it cycles with default settings.
-
Hi Neil79 and others
Sorry to hear about your troubles. I will check the status of this issue internally and contact you soon.
-
Hi Neil79 and others
Sorry to hear about your troubles. I will check the status of this issue internally and contact you soon.
Thankyou :)
Please note I don't have any idle issues, my system passes 24hrs of prime and 10hrs of intel burn test, 6hrs of BF3 and even more so of Skyrim.. My issue is that damn cold boot loop. I started it today it started up first time and was fine, yet yesterday Didn't go get so much as a video display and the system shut itself off when booting up then it boot loops. If I take the psu out as many other users have noted then put it back in, the system boots on it's own accord and works perfectly( atleast it does for me).
At one point it lasted 3 days and I thought it was working after i flashed to F7B, it then started cold booting again :(
-
Another person at overclock.net has posted with the same problem as me (sounds like it anyway)
http://www.overclock.net/t/1034724/gigabyte-p67-z68-boot-cycling-problem/590#post_16145740
-
Hello!
I just registered to add that I am having similar problems with my new GigabyteZ68XP-UD3P board. I went for this board because of the good reviews, but frankly it is completely useless when it comes to real overclocking because of the boot loops. It really is a shame because otherwise it's a really good motherboard. My 2500k really wants to go high and loves the voltage as I managed to get it up to 4.85ghz with just over 1.42V, with very reasonable temps. Problem is, I need some voltage to get there, and from the moment I touch the CPU voltage settings, whether it's with LCC or Dynamic settings, I get stuck with a boot loop and need to unplug the power cord, and then start over again from the defaults BIOS values. Not exactly a routine you wanna go through when you get home at 5PM on friday and power up your computer wanting to play you favorite game. So despite my (very small) investment in a "all-in-one" liquid cooling solution and the awesome temps it gets me, I'm stuck running my overclock @4.3ghz using default voltages because that's all that board will let me.
I am very looking forward for an update on that matter, whether it takes the form of a BIOS update or just some tips to get the voltage settings working without a boot loop. I went through the entire thread on overclock.net, trying most of the tips from the users but I haven't had any luck so far.
Thank you very much!
Windows 7 x64 Ultimate
Corsair Carbide 500R
XFX 750W Core Edition Single rail PSU
Cool-IT ECO watercooling
Patriot VIPER XTREME 8GB PC3-15000 @1.65V
Gigabyte Z68XP-UD3P
Gigabyte HD6970
Intel i5 2500k
ADATA 120GB SSD
-
Well it looks as If i got the scripted response again..
Basically
Have you backed up your bios... Like that hasn't been done before and will completely solve this issue :'(
and this was from email
Hi,
After checking with our BIOS engineer, F7a, F7b and F7c also has been implemented the cold boot solution.
We are not able to duplicate this issue on our side. Please provide the steps how to replicate the issue. Alternatively please send the system to GBT UK for further check.
I give up!
-
You're lucky. None of my emails have even been replied to. Then I make this thread, and they reference you, and completely ignore me. At least you've made an impression I guess.
I would attempt to return the board, but its now beyond the initial 30 day return policy. I am still going to see if I can talk to the store manager and see what my options are, as I'm obviously getting nowhere with the manufacturer.
I might expect this with a $50 board, but not one of the higher end models. Frankly, I'm insulted - we should not be chasing down the manufacturer trying to get answers. I'd have expected an official response and a timely reply - even if its just a daily update indicating nothing new has been learned.
I'm sorry if this comes off harsh, but the reality is that I had to build a completely different PC with a non-gigabyte motherboard because I could not count of the reliability of your motherboard. Were I posting from the PC featuring your motherboard it would have boot cycled 8 times (and what is that doing to my SATA hard drive RAID array with it constantly spinning up and shutting down!) and I would have frozen half way through my reply.
-
You're lucky. None of my emails have even been replied to. Then I make this thread, and they reference you, and completely ignore me. At least you've made an impression I guess.
so you asked giga at gts (http://ggts.gigabyte.com)? if they don't reply at gts then call them: G.B.T. INC. Tel: +1-626-854-9338 (http://www.gigabyte.us/about-gigabyte/contact-us.aspx)
as far as i know this forum is mainly for uk users, they can't help all the world. if you are from usa then use official gigabyte usa forum at tweaktown: http://forums.tweaktown.com/gigabyte/ and inform us results and i am curious
-
Hi
Yes you are of course correct that this is a UK Forum and whilst everyone is welcome to participate and even get help on the forum there is a limit to the type and amount of help we can give from here.
TweakTown is the official US forum for Gigabyte. ;)
-
Well it looks as If i got the scripted response again..
Basically
Have you backed up your bios... Like that hasn't been done before and will completely solve this issue :'(
and this was from email
Hi,
After checking with our BIOS engineer, F7a, F7b and F7c also has been implemented the cold boot solution.
We are not able to duplicate this issue on our side. Please provide the steps how to replicate the issue. Alternatively please send the system to GBT UK for further check.
I give up!
if they offered to check your pc in their office then you are the lucky one, not many have this privilege. you should not give up. fight for your right (to party ;))!!!
-
You're lucky. None of my emails have even been replied to. Then I make this thread, and they reference you, and completely ignore me. At least you've made an impression I guess.
so you asked giga at gts (http://ggts.gigabyte.com)? if they don't reply at gts then call them: G.B.T. INC. Tel: +1-626-854-9338 (http://www.gigabyte.us/about-gigabyte/contact-us.aspx)
as far as i know this forum is mainly for uk users, they can't help all the world. if you are from usa then use official gigabyte usa forum at tweaktown: http://forums.tweaktown.com/gigabyte/ and inform us results and i am curious
So this is not an official gigabyte forum? I was not aware tweaktown was the official forum, as its a 3rd party domain. I guess i'll start posting there, too.
-
Hi there,
this is the Official Gigabyte Forum for the UK and Ireland. There are other's in France and other European Countries.
TweakTown is the official place for Gigabyte Technical help in the North America.
Not really sure why Gigabyte decided to use separate Forums for each area rather than one main site but they may have thought that help in the native language was the best way to deal with things.
-
After 3 days of no cold boot issues, today I go out for two hours come back home, turn the system on it doesn't show a boot screen with no video display it shuts itself off . I take out the psu cable, plug it back in the system boots on it's own and again it shuts off >:( >:(
Take out the psu cable again, plug it back in system boots on it's own and it works perfectly back into windows ::)
-
Just as a matter of interest try this. Remove the CMOS battery and then boot up. Obviously you will be in a situation whereby you have no date and time but apart from that it should enable booting without the cycling I think.
-
I've posted this issue at the Tweaktown forums hoping we get it resolved over there.
http://forums.tweaktown.com/gigabyte/47264-can-we-get-official-response-gigabyte-regarding-cold-boot-loop-problem-hitting-p67-z68-boards.html#post413357
-
WOW I am so glad I found this thread I just came home from Comp USA were I was convinced to buy a GA-Z68AP-D3 and when I got home I opened the box and it was not the one I saw in the case it was a (rev. 2.0) and had the mSata on the board which is not going to work for me with the OCZ vertex plus SATAII he sold me. so I started doing a little research and found this thread THANK GOD I have not opened the bag. Its going back tomorrow with 60 pages on the UK site and IDK how many on this one it is obvious I don't want to have the headache at all I do not overclock I bought the heavy board for reliability random reboots is not an option . I am going to go back and buy the Asus I walked in to get the 8 year old one I have is still reliable and I expect the same. and I can still download drivers for it at there site.
Pity I was looking forward to it.
-
appears that Asus has a similar problem http://www.youtube.com/watch?v=OTyyHEldt3o
-
appears that Asus has a similar problem http://www.youtube.com/watch?v=OTyyHEldt3o
That's not a cold boot issue :(
-
Cold boot issue this morning, 4DAYS LATER from the previous one!!. Just don't understand it
These are my settings, happens at default too!. Sometimes within a day it cold boot's, sometimes as above 4days later. Getting annoying now
I5 2500K 4.7GHZ
BIOS VERSION - F7C
\MB - ( M.I.T )/
\Advanced Frequency Settings/
CPU CLOCK - 33X
BCLK - ( DISABLED ) left at default 100mhz
EXTREME MEMORY PROFILE XMP - ( PROFILE 1 )
SYSTEM MEMORY MULTI - ( AUTO )
\Advanced Cpu Core Features/
CPU CLOCK RATIO [33X]
PWN FREQUENCY CONTROL [ AUTO ]
INTERNAL CPU OVER CURRENT PROTECTION [ AUTO ]
INTERNAL CPU PLL OVERVOLT [ENABLED ]
RATIO CHANGES IN OS [ DISABLED ]
INTEL BOOST TECH [ ENABLED ]
RATIO 1 - 4 [ 47 ]
TURBO POWER LIMIT [ 300 ]
CORE CURRENT [ 300 ]
CPU CORES ENABLED [ ALL ]
CPU ENHANCED HALT C1E [ AUTO ]
C3/C6 STATE SUPPORT [ AUTO ]
CPU THERMAL MONITOR [ DISABLED ]
BI-DIRECTIONAL PROCHOT [ AUTO ]
\Advanced Memory/
EXTREME MEMORY PROFILE X.M.P [ PROFILE 1 ]
SYSTEM MEMORY MULTI SPD [ AUTO ]
PERFORMANCE ENHANCE [ STANDARD ]
DRAM TIMING SELECT SPD [ AUTO ]
CHANNEL A - B [ AUTO ]
\Advanced Voltage Settings/
MULTI-STEPS LOAD-LINE [ LEVEL 6 ]
CPU VCORE [ 1.3350V ]
QPI/VTT VOLTAGE 1.050V [ 1.20v ]
SYSTEM AGENT VOLTAGE 0.920V [ AUTO ]
DYNAMIC VCORE [ AUTO ]
GRAPHICS DVID [ AUTO ]
CPU PLL VOLTAGE 1.800V [ 1.800V ]
DRAM VOLTAGE 1.500V [ 1.625v ]
DRAM VREF 0.750V [ AUTO ]
DRAM TERMINATION 0.750V [ AUTO ]
CH-A/B ATA VREF 0.750V [ AUTO ]
CH-A/B ADDRESS VREF [ AUTO ]
\Advanced Bios Settings/
QUICK BOOT - [ DISABLED ]
BOOT LOGO - [ DISABLED ]
\Misc Settings/
ISOCHRONOUS SUPPORT [ ENABLED ]
VIRTUALIZATION TECH [ ENABLED ]
\Power Management/
HPET SUPPORT [ ENABLED ]
HPET MODE [ 64BIT ] - 64bit windows versions
\Pc Health/
CPU SMART FAN CONTROL [ DISABLED ]
-
Hi
From the way things are happening and the timescales involved it sounds more like a software/firmware issue rather than a hardware one. I would have expected a more steady response and the problem showing at regular intervals if it were hardware.
-
There are lots of threads in this forum about this issue, and there are lots of posts all over at other sites about this issue. I think the reason there aren't more, is that its an intermittent problem in the sense that it doesnt always happen. I'm willing to bet that most users ignore it, or simply don't know where to get help about it. Maybe they think its a CPU, RAM, PSU, or Video card issue? We just happened to have extra hardware to plug everything else in and determine that its an issue tied to the motherboard.
-
If, as you say, it is an intermittent problem have you any idea why or what is causing it ? Most problems that are hardware based are replicable and with the right circumstances be made to occur. :-\
-
http://forums.overclockers.co.uk/showthread.php?t=18338090&page=4
See here, currently working with MOOGLY's who also had Cold boot issues who hasn't had any for awhile since either using F6 bios or Certain settings different to mine. The settings are not wildly different so unless he gets any it might be easy enough to find the cause..
I hope :-\
-
Cold boot issue about 5mins ago, so it's NOT EXTREME MEMORY PROFILE X.M.P related. It's heading towards it being the bios itself F7.
-
No problems since swapping to a P8Z68-V PRO/GEN3. I am even using two sets of complete different ram, both of which didnt work on the gigabyte. So you can pretty much rule out the following, CPU, RAM, GPU, PSU, SSD, HDD as being the problem :)
-
UPDATE !!!!!!!!!
No cold boot in two days even when not having the system on for hours and the only thing i've done according to someone elses advice is
PLL OVERVOLTAGE = DISABLED
If this is the cause, why does enabling pll over voltage cause cold boots?
-
I cured my cold boot issues :D :D, it was down to the PLL overvoltage setting, with it ENABLED or even on AUTO it wont be long till I cold booted!, Disabled it and haven't had a cold boot in 5days. Gigabyte needs to look into this, it should NOT be cold booting if the PLL overvoltage is set to enabled :(
This is my final setting :)
I5 2500K 4.7GHZ
BIOS VERSION - F7B
\MB - ( M.I.T )/
\Advanced Frequency Settings/
CPU CLOCK - 33X
BCLK - ( DISABLED ) left at default 100mhz
EXTREME MEMORY PROFILE XMP - ( PROFILE 1 )
SYSTEM MEMORY MULTI - ( AUTO )
\Advanced Cpu Core Features/
CPU CLOCK RATIO [33X]
PWN FREQUENCY CONTROL [ AUTO ]
INTERNAL CPU OVER CURRENT PROTECTION [ AUTO ]
INTERNAL CPU PLL OVERVOLT [ DISABLED ]
RATIO CHANGES IN OS [ DISABLED ]
INTEL BOOST TECH [ ENABLED ]
RATIO 1 - 4 [ 47 ]
TURBO POWER LIMIT [ 300 ]
CORE CURRENT [ 300 ]
CPU CORES ENABLED [ ALL ]
CPU ENHANCED HALT C1E [ AUTO ]
C3/C6 STATE SUPPORT [ AUTO ]
CPU THERMAL MONITOR [ DISABLED ]
BI-DIRECTIONAL PROCHOT [ AUTO ]
\Advanced Memory/
EXTREME MEMORY PROFILE X.M.P [ PROFILE 1 ]
SYSTEM MEMORY MULTI SPD [ AUTO ]
PERFORMANCE ENHANCE [ STANDARD ]
DRAM TIMING SELECT SPD [ AUTO ]
CHANNEL A - B [ AUTO ]
\Advanced Voltage Settings/
MULTI-STEPS LOAD-LINE [ LEVEL 6 ]
CPU VCORE [ 1.340V ]
QPI/VTT VOLTAGE 1.050V [ 1.20v ]
SYSTEM AGENT VOLTAGE 0.920V [ AUTO ]
DYNAMIC VCORE [ AUTO ]
GRAPHICS DVID [ AUTO ]
CPU PLL VOLTAGE 1.800V [ 1.800V ]
DRAM VOLTAGE 1.500V [ 1.625v ]
DRAM VREF 0.750V [ AUTO ]
DRAM TERMINATION 0.750V [ AUTO ]
CH-A/B ATA VREF 0.750V [ AUTO ]
CH-A/B ADDRESS VREF [ AUTO ]
\Advanced Bios Settings/
QUICK BOOT - [ DISABLED ]
BOOT LOGO - [ DISABLED ]
\Misc Settings/
ISOCHRONOUS SUPPORT [ ENABLED ]
VIRTUALIZATION TECH [ ENABLED ]
\Power Management/
HPET SUPPORT [ ENABLED ]
HPET MODE [ 64BIT ] - 64bit windows versions
\Pc Health/
CPU SMART FAN CONTROL [ DISABLED ]
As I said
INTERNAL CPU PLL OVERVOLT - ENABLED = COLD BOOT
INTERNAL CPU PLL OVERVOLT - DISABLED = NO COLD BOOT
-
Nice if that actually works! I have the exact same problem, i have tried to different boards the ga-z68ma-d2h-b3 and the ga-z68mx-ud2h-b3, both have cold boot problems when more than 1 stick of ram is inserted. Have tried for days to get it to work with my corsair vengeance rams.
Only problem is that i can't find "PLL Overvoltage" setting in the bios for these two boards. Where is it? ( please be there, please work :o holding my breath :-X )
Otherwise i will have to return them both (which would be sad as i need them for my hackintosh)!
-
CPU PLL Overvoltage is in the Advanced CPU Core features page. On the advanced frequency settings page, right under the CPU clock ratio = click to enter.
Keep in mind if you are overclocking you will be limited to whatever CPU multiplier your CPU can do without CPU PLL Overvoltage enabled, this is likely less than x47/x48 or so. Otherwise if you try to use too high of a CPU multiplier you will still run into booting issues due to the CPU multi being too high without CPU PLL Overvoltage enabled.
Since those are budget boards, you may not have this option anyway, so it would be disabled. I'll check your BIOSes right now.
*Edit*
Just checked both of those boards latest BIOSes, the option is not present, so it would be disabled by default.
-
Thanks for your time Lsdmeasap! Guess i'm no further a solution then. Both boards have problems booting when i insert more than 1 stick of ram, i don't get it. My intuition tells me it has to do with the pairing of the ram ( but seems unlikely to stem from the rams themselves since i've tested with other rams and the problems persisted ), or some kind of voltage problems because it seems less stable as you add more ram and always becomes unbootable when 4 sticks are inserted. Can't believe i have the same problem on these two boards i just bought!?
-
Have you tried increasing the memory voltage especially when you have filled all the banks. Don't forget to keep an eye on the QPI/Vtt though as you must maintain 0.5v max between that and the memory voltage.
-
You may just need an increased QPI/Vtt voltage, this is often needed when increasing the memory to 4-8GB or above, try rasing this before you insert the second module and see if it helps. Try 1.2-1.35 and see if that helps.
It very well could also be a memory compatibility issue, do you have or can you borrow other memory to test with? If not, maybe think about buying a set of 2x2GB of something else just to test with, DDR3 is dirt cheap these days!
-
It very well could also be a memory compatibility issue, do you have or can you borrow other memory to test with? If not, maybe think about buying a set of 2x2GB of something else just to test with, DDR3 is dirt cheap these days!
If you do follow Lsdmeasap's advice make sure that the new RAM is listed as compatible on the memory manufacturer's website QVL for your motherboard.
-
Is 'cold boot' the same as "The system has experienced boot failures because of overclocking"? I still get this stupid message all the time on my GA-Z68X-UD3R-B3. I had it on early p67 boards and thought they would have fixed it long ago. I'm not overclocking, how how can I experience "boot failures because of overclocking"? My next motherboard will be ASUS.
-
NO, that means your settings are off and are crashing, so BIOS defaults will be used instead of what you see in the BIOS until you correct it with stable settings.
Overclocking or not you still need to setup a few things and test for stability. Did you set XMP or setup your memory manually already? You should do that, and ensure that the memory voltage is set to what is specified for your kit
-
NO, that means your settings are off and are crashing, so BIOS defaults will be used instead of what you see in the BIOS until you correct it with stable settings.
Overclocking or not you still need to setup a few things and test for stability. Did you set XMP or setup your memory manually already? You should do that, and ensure that the memory voltage is set to what is specified for your kit
Yes, I set freq and timings manually. Specified voltage was 1.5v, which is already default, but I also set that manually anyway.
-
If you have 8GB or more you may also need to increase QPI/Vtt voltage, depending on your CPU you might need this anytime with any amount of memory as well because all CPU's are different and not all may be stable with the auto/stock amount.
-
If you have 8GB or more you may also need to increase QPI/Vtt voltage, depending on your CPU you might need this anytime with any amount of memory as well because all CPU's are different and not all may be stable with the auto/stock amount.
Does that count if your using 1333MHz and whatever the default sandy bridge timings are?
-
Oubadah I would suggest that you do as Lsdmeasap advises because he is a wizard at these things and I have learnt much off him before. ;)
-
Thanks DM :)
Yes, if you have 8GB or more you may need to increase QPI/Vtt, I said maybe as it's not a definite. Have you tested your memory at all using your current settings? If not, please do as you may not need to change anything in regards to your memory. Here, use this Memtest86+, run at least 5 full passes or overnight while you sleep.
http://www.memtest.org/#downiso
-
Thanks DM :)
Yes, if you have 8GB or more you may need to increase QPI/Vtt, I said maybe as it's not a definite. Have you tested your memory at all using your current settings? If not, please do as you may not need to change anything in regards to your memory. Here, use this Memtest86+, run at least 5 full passes or overnight while you sleep.
http://www.memtest.org/#downiso
Yes, I've done memtest86+ 24 hours on each stick, then 24 hours with both stick, at rated settings: 1600MHz 8-8-8-24 1.5v 2T. No error, but then sooner or later gigabyte BIOS warning.
I don't want to overclock or change ant QPI/Vtt setting as I don't know what I'm doing and I'll break something. If 1333Mhz 9-9-9-24 could be stable then I'd use that, but I don't know why I should need to mess around with BIOS just to get things stable at stock settings. Gigabyte p67/x68 just seems to be unstable - I don't know anyone with an ASUS board that can't run stock speed reliably without BOIS modification - 8GB or not.
-
I don't know anyone with an ASUS board that can't run stock speed reliably without BOIS modification - 8GB or not.
You do now! I have had problems in the past with Asus motherboards that have been memory related at stock settings. The thing is that board and components vary and especially if you are installing more than the basic amount of memory the settings can require a bit of tweaking.
-
That is one reason I quit buying Asus after 2005 and replaced them with Gigabyte.
What make/model memory?
How many sticks?
Are you only manually setting [XMP] or are you setting other values as well?
What does [XMP] and everything else left on default values report for freq., timings, voltage?
-
Thanks DM :)
Yes, if you have 8GB or more you may need to increase QPI/Vtt, I said maybe as it's not a definite. Have you tested your memory at all using your current settings? If not, please do as you may not need to change anything in regards to your memory. Here, use this Memtest86+, run at least 5 full passes or overnight while you sleep.
http://www.memtest.org/#downiso
Yes, I've done memtest86+ 24 hours on each stick, then 24 hours with both stick, at rated settings: 1600MHz 8-8-8-24 1.5v 2T. No error, but then sooner or later gigabyte BIOS warning.
I don't want to overclock or change ant QPI/Vtt setting as I don't know what I'm doing and I'll break something. If 1333Mhz 9-9-9-24 could be stable then I'd use that, but I don't know why I should need to mess around with BIOS just to get things stable at stock settings. Gigabyte p67/x68 just seems to be unstable - I don't know anyone with an ASUS board that can't run stock speed reliably without BOIS modification - 8GB or not.
Sounds like your memory is fine to me then if you really did all that testing with memtest86+, that's a lot and way more than needed so I don't think it's a memory issue and you don't need to change anything I mentioned since your memory is stable.
-
UPDATE!!
F7E
Beta BIOS
Improve power on issue
Update ME / CPU code
I did say it was a bios/board issue 8)
http://uk.gigabyte.com/products/product-page.aspx?pid=3912&dl=1#bios
-
I asked support what the cause was and I got this
Hi,
Update new ME firmware which fixed cold boot issue.
Which was in the F7e which I already updated too and love , what's ME btw?, could they be talking memory
-
Intel Management Engine
Its remote administration running at the firmware level.
-
So Neil79, have you updated the BIOS to F7E and has it solved the cold boot issue ?
-
So Neil79, have you updated the BIOS to F7E and has it solved the cold boot issue ?
So far yes and was also very easy with no issues to update the bios from the previous one, unlike all the other bloody times lol
-
Well, fingers crossed that it will work better too. ;)
-
Just posting an update on this for anyone following via email updates
Stasio posted a bunch of new BIOS this week and last, they should solve these issues for you guys!
http://forums.tweaktown.com/gigabyte/28441-gigabyte-latest-beta-bios-544.html
-
and again already posted :(
-
I know, just making some rounds for anyone subscribed via email that might have missed it.
-
You may just need an increased QPI/Vtt voltage, this is often needed when increasing the memory to 4-8GB or above, try rasing this before you insert the second module and see if it helps. Try 1.2-1.35 and see if that helps.
It very well could also be a memory compatibility issue...
Hi i tried upping both memory voltage and QPI/Vtt, not helping yet. They were 1.5v and 1.05.
I checked and my ram are listed as being compatible for both the MX and the MA board.
I tried with other rams. But i'm quite sure the issue is with the boards when more than one channel is involved.
When more than one channel is involved the boot cycle happens.
These are the ram's http://www.corsair.com/vengeance-16gb-dual-channel-ddr3-memory-kit-cmz16gx3m4a1600c9b.html
these are their specs:
Performance Profile :: XMP
Memory Configuration :: Dual Channel Memory
Type :: DDR3
Package - Memory Pin :: 240
Package - Memory Format :: DIMM
Tested Voltage ::1.5
SPD Voltage :: 1.5
Speed Rating :: PC3-12800 (1600MHz)
SPD Speed :: 1333Mhz
Tested Speed :: 1600
Mhz Tested Latency :: 9-9-9-24
SPD Latency :: 9-9-9-24
Anything else i can try?
-
It would be worth checking for bent pins on the CPU socket also.
Take all the usual anti-static precautions.
Very carefully remove the heatsink and fan. Probably a slight twisting motion is best to release the two as the thermal paste can act like a glue.
Once off remove the CPU taking extreme care both physically and electrically(static) and place somewhere safe.
Make sure that the lighting is very good and even.
Now scrutinise the socket for any pins that are out of alignment, even slightly. If in any doubt whatsoever take a couple of macro (close up) photos of the socket and post them on here for us to check.
Also look at the bottom of the CPU at the lands (little copper circles) and make sure that there is a mark in each somewhere near the centre. If there are any missing marks or any of the pins are obviously bent then that is your problem.
Before refitting the CPU clean off all residue of the old thermal paste and the same on the heatsink and then apply a small amount (about the size of a grain of rice) to the centre of the CPU once it is inserted in the socket.
-
You said they were 1.5 and 1.05, what is your memory rated at? And up to what did you try increasing the QPI/Vtt?
-
Thanks for your help guys but i think the problem is the gigabyte mobo's themselves...
I have already looked at the CPU thoroughly and am not inclined to take the motherboard out once more.
It is my impression that there is a serious problem with Gigabyte motherboards of this kind since i have been able to find people across the web with the exact same problems, and no resolutions >:(
Look at these threads, we all have the same problems; boot cycle with more than 8gb's of ram:
http://arstechnica.com/civis/viewtopic.php?f=8&t=1162913 (http://arstechnica.com/civis/viewtopic.php?f=8&t=1162913)
http://www.newegg.com/Product/Product.aspx?Item=N82E16813128492 (http://www.newegg.com/Product/Product.aspx?Item=N82E16813128492)
http://www.evga.com/forums/tm.aspx?m=1245497&mpage=1 (http://www.evga.com/forums/tm.aspx?m=1245497&mpage=1)
As far is i can see i have just been unlucky with boards and need too rma both of them if i have the time.
I would like to see an official statement, a bios update, just a clue as to what the culprit of this problem is, since i have already bought one replacement board out of my own pocket.
luckily 8gb ram's are enough for me at the moment, just not very optimal :P
-
The culprit is Intel ME firmware, and BIOS updates have just been posted this week to address the issue, did you try them yet?
-
The culprit is Intel ME firmware, and BIOS updates have just been posted this week to address the issue, did you try them yet?
Interesting...
I already updated the MA board to f10c which didn't seem to resolve the issue.
I haven't updated the MX board though. Is it the F13d update? Under description "improve power on issue" is listed.
Is this the correct update to apply since it wasn't posted this week but rather on the 1/19.
link to bios downloads for GA-Z68MX-UD2H-B3:
http://www.gigabyte.com/products/product-page.aspx?pid=3974&dl=1#bios
crossing fingers :D
-
I think Gigabyte have actually broken things that were working in the first place. I've just been experimenting with a H67MA-UD2H-B3 board, and with it's shipping BIOS (F4 I think it was), I couldn't recreate any boot loop at all - it was perfectly normal. Then I flashed it to F6 (latest), and suddenly every reset makes it shut down/loop and I see this "Waiting for ME ready..." that I never saw before.
I don't get the HT reset issue or "failure due to overclocking" though...
-
The culprit is Intel ME firmware, and BIOS updates have just been posted this week to address the issue, did you try them yet?
Only took a number of my reports and a number of others from other people before they actually fixed it!. All that it's your board RMA it rubbish, glad it's fixed anyway :)
-
From looking around the net it would seem that this has indeed fixed the problem apart from a couple of odd ones that were probably due to some other issue altogether. Let's hope that this has finally been put to bed. ;)
-
It is NOT fixed on my z68x-ud3r.
And I don't suppose it'll ever be fixed on the old H67MA-UD2H-B3.
-
Have you made sure that you have applied the Intel ME update as this is the primary issue ?
-
This issue is not fixed DM, at least not on the Z68X-UD7. It's better than it was with the F10C BIOS admittedly, but I still found that
1) The system is finicky as hell to get set up after a BIOS flash. It will still POST loop after a CMOS reset, and it is still possible to prompt the "Your system has failed because of an overclock..." warning (complete with zilched settings) at completely random moments - even when the darn thing's running at stock speeds. This includes, for example, using ctrl-alt-del to reset the system after running through an Alt-F12 backup BIOS flash!
Despite the fact that the mild overclock I'm running is absolutely rock stable (will survive over 24 hours of stress testing inside Windows, and *never* crashes), the only way to get it set up in BIOS is to make small incremental changes, and continually save settings and restart, putting up with random power cycles as I go. If I try to go from stock speeds to the full whack in one go, the system will start to loop, and eventually throw the "Overclock" warning.
Furthermore, once this warning has started to appear, it is almost impossible to force the system to boot. Go into the BIOS, set up any combination of settings you want (mild overclock, stock or underclock), save and exit, and as soon as it restarts, you'll see the warning again, and, once into the BIOS, you'll see that the settings you made a minute ago have been completely ignored, or replaced by the settings you tried a few minutes earlier.
2) The reset button still doesn't work properly. Sometimes it simply doesn't do anything at all, and other times, using it, even for a perfectly legitimate system reset after booting to a command prompt for some reason, will prompt the "overclock" warning - even if the system's running stock or underclocked! I know there's a known issue with the reset button on the GBT 6-series boards, but that doesn't mean Gigabyte have any excuse not to fix it.
3) If I select "Restart" in the shutdown menu of the OS, the system should, well, restart. However, I'm still finding that, almost at random, mine will suddenly shut down for a few secs and pause before powering up and continuing the restart cycle (with the POST meter reading C0 immediately prior to the power down). This is a minor issue but all those extra power cycles add up to extra wear on hard disks, not to to mention other components, and it's something that isn't an issue on other brands of board.
Oh and before anyone asks, this is all with the ME firmware updated.
Speaking of firmware, not sure whether the "culprit" is the ME, or whethe the problem is in the Award/Gigabyte code failing to program the ME. From what I've observed in testing, it would seem as though the main fault is on the GBT side. Seems like there are ways in which the board's backup BIOS/CMOS can cause more problems than it solves. Whatever the cause, though, it's for the board vendor to fix.
-
Here's another official update guys, I sent in a report on a few users still seeming to have these issues over the past two weeks, so here is there testing results and full reply.
Please pass this info along to your fellow Gigabyte users, thanks!
Test 3 models of Z68 boards with the following BIOS:
1.) Z68X-UD7 with BIOS F10
2.) Z68XP-UD3 with BIOS F9g
3.) Z68AP-DS3 with BIOS FB
Our test results:
1.) Press CTRL + ALT + DEL keys when during boot up or in DOS mode >> Cannot see “continuous reboot loop”, nor “Waiting for ME ready”, nor “system overclocking failure” message. The system just reboot fine.
2.) Press the Reset button
A.) Press the button quickly and release immediately >> Cannot see any issue.
B.) Press the reset button for one second or so (This is not normal behavior.) >> System will shut down, and then power on by itself. Then the “Waiting for ME ready” message appears and then system will shut down and power on by itself again. Sometimes, it will show “System overclock failure” message.
Moreover…
According our testing before,
the issue of “continuous reboot loop” can be fixed by flashing the Backup BIOS with the same version as the main BIOS (latest one).
We Flash the Backup BIOS with the same BIOS version for the main BIOS version before test.
So be careful with that reset button and it should also work properly now too! But I still say avoid if/when possible :D
And always keep backup BIOS up to date matching with the main BIOS.
-
http://uk.gigabyte.com/products/product-page.aspx?pid=3912&dl=1#bios
Support Intel 22nm CPU E1 stepping
Improve power on issue
Update ME / CPU code
F7
-
Hi.
I previously posted in this thread a few weeks ago. Here are my specs, same as before.
Windows 7 x64 Ultimate
Corsair Carbide 500R
XFX 750W Core Edition Single rail PSU
Cool-IT ECO watercooling
Patriot VIPER XTREME 8GB PC3-15000 @1.65V
Gigabyte Z68XP-UD3P
Gigabyte HD6970
Intel i5 2500k
ADATA 120GB SSD
Just wanted to give a quick update on the issue. I am still plagued with cold boot issues, i.e. the computer looping at boot, trying to start but only trying for a few seconds before shutting down again. I just had to clear the battery again to get it up and running.
I installed the latest bios yesterday to see if it was any better. I know the overclock potential of this 2500K and the settings it likes almost by heart now, so yesterday I went into the bios, did my things, and was up and running @4.7ghz like before, 6 hours prime stable, voltages stable as well. I then put the computer to sleep for the night. In the morning I wanted to check out the news, but it never woke up. I pressed enter on the keyboard, fans started spinning, it tried to start up but shut down immediately. It tried and failed again about 7 times before I finally got under my desk to shut down the PSU.
-
Sleep issue is not the same as the issues discussed here really. However, I can try to help you diagnose this.
Do you have the backup BIOS flashed to match the main already? If not, please do that now following this guide, you may need to use PS/2 keyboard or USB to PS/2 adapter
http://gigabytedaily.blogspot.com/2011/02/video-guide-how-to-update-your-backup.html
Do you have other memory to test with? For your memory now, have you ran Memtest86+ and or HCI memtest lately? If not please test now, for at least 5-10 full passes or overnight while you sleep with Memtest86+ latest version.
http://www.memtest.org/#downiso
To test with HCI memtest, you run multiple instances based on the number of CPU cores you have (4), then divide all spare memory in windows (minus a few hundred MB) into those 4 instances
http://hcidesign.com/memtest/
So for example, you have 6GB in windows at idle once windows is done loading, verify unused memory amount in task manager. So let's say you have 6GB left, subtract 200-300 MB from 6GB, you get 5844. Divide that amongst 4 instances of HCI memtest and let it run to around 500% or more, if they all pass without error then your memory settings or voltage are not the cause of your sleep issue.
I recommend extended testing with both programs mentioned above always, but especially now since you are having sleep issues as these are often memory related. Is your 8GB 2x4GB or 4x2GB?
-
Do you have the backup BIOS flashed to match the main already? If not, please do that now following this guide, you may need to use PS/2 keyboard or USB to PS/2 adapter
http://gigabytedaily.blogspot.com/2011/02/video-guide-how-to-update-your-backup.html
This board/bios pisses me off, maybe i shouldn't swear but that's how i feel!. Since the f7e bios i've had what a month without issue apart from this last week when I had two cold boots. It passes prime and intel burn test for many hours so it's not system stability!. A week passes by and i read this post, after another successful boot up I decide to back up the bios just incase I get a cold boot. Thanks to this stupid idea it said that the back up bios was flashed successfully and to reset the system. I press the reset button and what does it do, starts up and shuts down, NICE!
I go into bios and it said it had failed because of overclocking NO IT HASN'T it's because i pressed the damn reset button after a back up bios flash. ok then (I set the defaults in bios), Restart the system and get a nice box of text telling me it had started up but failed due to a failed overclock setting, NO IT BLOODY HADN'T!. Sod this I thought, I booted up the system set my overclock in bios, let the system shut off and pulled the psu cable. Put it back in and it booted it on it's own without me doing anything and wolla it worked fine.Not only did the back up bios idea cause me a great amount of grief but so did hitting that Reset button, Never EVER use the reset button on this board it thinks it's a failed overclock for some stupid reason.
-
Sorry to hear that you are still having problems. You shouldn't use the reset button! ;) Do an extended clear of the CMOS overnight and it should be fine in the morning. I should uncouple the reset button from the motherboard if I were you.
-
Sorry to hear that you are still having problems. You shouldn't use the reset button! ;) Do an extended clear of the CMOS overnight and it should be fine in the morning. I should uncouple the reset button from the motherboard if I were you.
It's fine now, it's still a piece of crap bios and the developers are a bunch of fools
I never use the reset button! only in this instance as it was supposed to be fixed.
-
Sleep issue is not the same as the issues discussed here really. However, I can try to help you diagnose this.
Do you have the backup BIOS flashed to match the main already? If not, please do that now following this guide, you may need to use PS/2 keyboard or USB to PS/2 adapter
http://gigabytedaily.blogspot.com/2011/02/video-guide-how-to-update-your-backup.html
Do you have other memory to test with? For your memory now, have you ran Memtest86+ and or HCI memtest lately? If not please test now, for at least 5-10 full passes or overnight while you sleep with Memtest86+ latest version.
http://www.memtest.org/#downiso
To test with HCI memtest, you run multiple instances based on the number of CPU cores you have (4), then divide all spare memory in windows (minus a few hundred MB) into those 4 instances
http://hcidesign.com/memtest/
So for example, you have 6GB in windows at idle once windows is done loading, verify unused memory amount in task manager. So let's say you have 6GB left, subtract 200-300 MB from 6GB, you get 5844. Divide that amongst 4 instances of HCI memtest and let it run to around 500% or more, if they all pass without error then your memory settings or voltage are not the cause of your sleep issue.
I recommend extended testing with both programs mentioned above always, but especially now since you are having sleep issues as these are often memory related. Is your 8GB 2x4GB or 4x2GB?
Thank you for your time, but I doubt the problem is memory related. I havent had any errors in 4 hours + of HCI, I shut down the testing at +- 600%, and the speed or voltages it runs dont seem to matter either. Those are 2x4gb.
I'll update the backup bios when I get home to see if it changes anything.
As for my issues not being the ones discussed here, would you care pointing me in the right direction then? After all, I first encountered the boot loop problem on a cold boot too. From my perspective, the symptoms are the same, except for the fact that from what I am reading, most people do get to the POST screen before the computer shuts down and tries again. In my case it doesnt even get there, i.e. no text on screen.
-
The problem is often 100% memory related, but not always, if you have done all of the other suggested things to correct this (IE Don't use reset button, backup BIOS matches main, CPU PLL Overvoltage disabled, ect)
The issue is caused when memory errors at bootup cause the ME firmware to mess up, thus a reboot cycle is invoked until it's corrected (IE hard reboot or warm reboot from the BIOS)
How many instances of HCI memtest did you run, with how much memory in each when it reached 600%?
Ahh yes, please do update the backup BIOS, you should have done that first and long ago!
What I meant by not being the same issue as discussed here was your mentioned issue was with sleep, so I just meant you should create a thread and ask for help with sleep issues as these issues mainly deal with cold starts not sleep as that is it's own beast :)
To resume from sleep you have to be 100% tested stable, with several stability testing tools, and still may sometimes need a little bit more memory voltage than you need for stability, in order for S3 sleep to work. Of course it also must be actually working in the BIOS version you are using too, sometimes older BIOSes it is broken until they fix it. I am not sure if it's broke on your model's latest BIOS or not still, I haven't ran into enough users of that board to know for sure.
I see you mention you have the same issue on cold boots, sleep aside, that is relevant to this thread as you mentioned! So for now, do all the things I suggested and don't use sleep for a while, that way you can rule out sleep as part of the issue
-
I had 3 cold boots this morning >:(, system starts shuts off... I pull the psu put it back in, it starts and shuts off. Finally on the third time I pull the psu cable out, put it back in and it starts perfectly.
Backing up the bios is such a placebo but it seems to be the cure all advice on this forum
Why the hell did I get NO cold boots for over a month yet it's happening every so often again, I was on the computer for 8 hrs yesterday thats watching movies-youtube and playing a good three hours of BF3!
-
The problem is often 100% memory related, but not always, if you have done all of the other suggested things to correct this (IE Don't use reset button, backup BIOS matches main, CPU PLL Overvoltage disabled, ect)
The issue is caused when memory errors at bootup cause the ME firmware to mess up, thus a reboot cycle is invoked until it's corrected (IE hard reboot or warm reboot from the BIOS)
How many instances of HCI memtest did you run, with how much memory in each when it reached 600%?
Ahh yes, please do update the backup BIOS, you should have done that first and long ago!
What I meant by not being the same issue as discussed here was your mentioned issue was with sleep, so I just meant you should create a thread and ask for help with sleep issues as these issues mainly deal with cold starts not sleep as that is it's own beast :)
To resume from sleep you have to be 100% tested stable, with several stability testing tools, and still may sometimes need a little bit more memory voltage than you need for stability, in order for S3 sleep to work. Of course it also must be actually working in the BIOS version you are using too, sometimes older BIOSes it is broken until they fix it. I am not sure if it's broke on your model's latest BIOS or not still, I haven't ran into enough users of that board to know for sure.
I see you mention you have the same issue on cold boots, sleep aside, that is relevant to this thread as you mentioned! So for now, do all the things I suggested and don't use sleep for a while, that way you can rule out sleep as part of the issue
I ran 4 instances of HCI as you suggested, separating the unused memory between the four. I let in run the whole day with different settings, varying the amout of memory per instance, setting the affinity of each process to a specific core (or not), etc, and I could never get an error. Prime blend is 20 hours + stable.
I loaded default bios settings, updated the backup bios, shutted down the PSU just like in the video, cleared the CMOS, started the computer and was greeted by a "real" cold boot this time, the system getting to POST but shut down right after. After 6 or 7 loops I decided to do an extended cmos reset. Got it to boot after 15 minutes or so.
I'm just so damn tired of fighting against this board/bios. i'm beginning to think this is just all hardware related and that a few boards are faulty enough to make it a real pita to some overclockers while most will just encounter the problem a few times in its life cycle.
-
It very well could be your board? Have you tried other memory though, just to be sure it's not an issue with your specific memory?
I've never seen it myself, with 2 x P67 (B2), and one Z68, and I'm not just saying that either, and I know plenty who have not as well. But you are right, there are some that just have it no matter what, and without that hardware here in front of me it's hard to say what's going on since I can't replicate the issues myself to try and test things out for users. So there may just be some % of boards that are affected badly for some reason, while others are 100% fine. Have you considered RMA'n the board to try another, maybe you'd have better luck with just another of the same board.
-
I have just joined this forum specifically to find out more about this issue. In my case it struck my GA-Z68XP-UD4, less than a week old. The exact circumstances seem slightly different from the cases already described here. My PC was working normally when it suddenly it blue-screened and tried to restart. At the POST screen, just before the drives should listed, the message "Waiting for ME ready" appeared and after the countdown the system tried to restart. It never broke out of this cycle until I killed the power. When I tried to start up again the same thing happened. I also noted that the BIOS version was indicated as F5, although I had successfully updated to F6 a couple of days earlier.
I notified the board vendor and he suggested resetting the CMOS after removing the battery. I did all this, put it all together again and tried to start up. At first the system hung on the BIOS logo (please get rid of that stupid thing) for over a minute until I switched off. The next time I tried to start it went into the "short cycle" of fans on, then off, then start again, without even getting to the logo. At that stage I gave up and I am waiting for RMA advice.
The RAM was 2x4GB G.Skill F3-12800CLD9-8GBXL - also brand new. These modules were chosen because the G.Skill website shows they are certified for P67 & Z68 boards. I should also say that at no time were any of the voltage or frequency settings in the BIOS changed. All were left in their default Auto settings.
I was amazed to see how much discussion on this problem could be found in different forums. Does Gigabyte take the issue seriously? I have always used Gigabyte boards up to now, but I am starting to feel they can't be trusted. What is going on?
-
Hi and welcome.
I can't help with the actual problem but I can explain why your BIOS has changed from F6 to F5. The Backup BIOS copied it's contents (F5) over the top of the Main BIOS contents (F6) when the system failed to boot properly. This is the Dual BIOS working as it should. In future it is best to upgrade your Main BIOS and then once you are happy with it synchronise the two BIOS chips so that they both hold the same version.
I would suggest trying an extended CMOS clear to see if that helps. Follow these instructions:
Remove the power cable from the mains supply and then press the power switch on the case for a few seconds just to drain any residual energy in the PSU capacitors.
Once done remove the motherboard battery overnight or for at least six hours before replacing it.
Next plug back into the mains supply and boot.
You will now need to enter the BIOS by pressing DEL and load Optimised BIOS Defaults.
Make any other changes to the BIOS settings to suit your self like disabling the floppy drive, disabling the full screen logo and making the HDD the primary boot device and then press F10 to save and exit.
-
Hi and welcome.
I can't help with the actual problem but I can explain why your BIOS has changed from F6 to F5. The Backup BIOS copied it's contents (F5) over the top of the Main BIOS contents (F6) when the system failed to boot properly. This is the Dual BIOS working as it should. In future it is best to upgrade your Main BIOS and then once you are happy with it synchronise the two BIOS chips so that they both hold the same version.
I would suggest trying an extended CMOS clear to see if that helps. Follow these instructions:
Remove the power cable from the mains supply and then press the power switch on the case for a few seconds just to drain any residual energy in the PSU capacitors.
Once done remove the motherboard battery overnight or for at least six hours before replacing it.
Next plug back into the mains supply and boot.
You will now need to enter the BIOS by pressing DEL and load Optimised BIOS Defaults.
Make any other changes to the BIOS settings to suit your self like disabling the floppy drive, disabling the full screen logo and making the HDD the primary boot device and then press F10 to save and exit.
Thanks for that explanation, it means that the change in the BIOS version is irrelevant to the main problem bothering everyone and can be ignored. I actually tried the steps you describe to get things running again, except I didn't wait six hours before replacing the battery. So long? Anyway, it had no effect.
-
It can depend on certain criterior but sometimes a wait of roughly six hours/overnight can be called for it to work properly.
-
Has Gigabyte found a fix for this problem yet? My board is a GA-P43-ES3G and I am soooo tired of this foolishness. If I have to chuck this board in the trash it will be the last Gigabyte purchase for me. What a terrible way to tarnish a name...put defective items on the market and not respond properly to consumer concerns.
Here's what I have inside the box:
GA-P43-ES3G
INTEL Core 2 Duo E8400 3.0GHz FSB1333MHz 6MB LGA775 Dual-Core
2 sticks Crucial Rendition 2GB DDR-2 / 800 / PC6400 /
Corsair XMS2 TWIN2X4096-6400C5C 4GB DDR2 2X2GB PC2-6400
Sapphire ATI Radeon HD4670 512MB 128bit 1DVI/1xVGA Lite
WD Caviar SE-16 / SATA-II 5000AAKS 500GB 7200RPM, 16MB, SATA-
Western Digital WD20EARS Caviar Green 2TB SATA2 3GBPS 64MB Cache 3.5IN Hard Drive
LG GH22NS30 SATA BLACK DVD±RW (22X+/-) DUAL LAYER w/
APEVIA (BK/BK) X-PLORER W/WIN
Coolmax 600 Watt Power Supply
-
Off course you can get an official response from gigabyte regarding z68 boot.
-
Did this ever get solved? I'm *still* getting this issue with the P67 UD7. Random cold boot loops.
£276 worth of motherboard - made all but useless by a bug. :'(
-
I have the same problem and found a solution. In the BIOS settings, after setting the default standard in Fast Boot menu select Ultra fast. Ready! Cold boot will never happen again.
-
Load of garbage from them tbh. My first and last Gigabyte product. >:(
Z68X-UD4-B3 board stuck in boot loop. Sent it back for repair regarding the loop and it comes back with "CPU socket fixed" Well done..
They obviously have issues reading the RMA fault I guess.. Sent it back to me without even testing it & of course same problem..
The funny thing was the guys where I purchased it said some customers are having issues with their Z87 series motherboards (same problem).
-
?
I have this problem with 2 gigabytes mobo, one is brand new, How can this be possible ?
-
?
I have this problem with 2 gigabytes mobo, one is brand new, How can this be possible ?
Don't let this surprise you with Gigabyte.
Picked up the second "repaired" board today with the same issue. NO POST. Waiting 2 months for a fix and sending back and forth.
Went down to the store so they can test it and same problem picked up by the staff.
They are lazy useless "technicians" here in Australia period. Thank god my main PC has an ASUS mobo.
-
I have own a Gigabyte Z68XP-UD4 for almost a year and I'm truly disappointed on the system. Dual Bios should be a great idea, but in practice is a pain in the ass like I never had before with a motherboard.
Problem is: if I use F6 Bios version, everything works as it should, but my OC is not half as good as with UEFI beta BIOS. But when I install UEFI, one of every 5-6 times I cold boot the PC, the system will enter a loop which only can be overrun by unplugging the power cord. I don't even recall how many times I've update to UEFI, and how many more have I downgrade to F6. And the latest UEFI BIOS version listed in the Gigabye official web is listed on March... ¡March! Too bad.
I promise this will be my last experience with Gigabyte in the field of motherboards.
-
I'm also experiencing the cold boot issue among many others problems.
My specs:
GA-Z68X-UD4-B3
Intel i5 2500K CPU / Noctua CPU Cooler
Sandisk Extreme II SSD 240GB
16GB (4x4) Corsair XMS3 1600Mhz CL7
Gigabyte Nvidia GeForce 560 Ti
ThermalTake TR2 700W
Win8 Pro
Running the lastest BIOS
I've already sent it to Gigabyte Australia who seem to have sent it back as it was untouched by the look of the BIOS configuration (I left one setting at a value that would fail booting and it came back with the setting as it was). The reseller Scorptec are not providing any assistance and the board has come back now cold boot looping and double booting basically 2/3 times.
I've changed almost every part in the system to see if there is any chance of it being something other than the motherboard and no luck.
Did anyone solve this?
-
Doesn't look like it. I purchased a budget board (H61M-DS3) as a backup board in 2012, tested once with no issues after delivery then stored. Last year I used it to test some parts then I had the loop issue. Tried several times earlier this year, still the same. 'Was hoping for a solution after 2 years but after 2 hours of web scouring - NIL.
-
The only way this Problem was fix for me was Updating Bios on my GIGABYTE Z68XP-UD3 Motherboard in hopes this gets resolved for ya. I am 100% sure u have tried everything. Shame Giga Motherboards are one of my Fav aside from EVGA Boards. The only way i resolved this was with pulling an all nighter 1/2 gallon of my fav brandy 2 pc's aside on & just kept fighting till i got results. than later i found my dam PSU was working but used my Meter to test Watts Voltages & so on on psu found out it was working but Rail that supplied amp to motherboard itself was faulty.My friend Just try everything at times is something not even related.rinse & repeat till u get results. Sorry i could not be better help.
-
My mobo: GA-Z68XP-UD3P (rev. 1.3; UEFI ver. U1G)
The UEFI U1G was a beta release back in March 2013 and never saw anything else after that.
Boot loop issue is still present, and no new updates have been released.
Having an overclocking motherboard with a bug that absolutely cripples performance by setting a OC cap is horrible.
I'm not sure how Gigabyte boards are nowadays with Z97, but I'm probably never buying another Gigabyte board.
-
I'm not sticking up for them. But the thing is the Z68 board is old technology. The real last official Bios was the F7 02/2012. Most boards that are on the market you really are lucky to see a bios update past two year.
The U1G(UEFI BIOS) was a beta bios and really never was a official bios. The board wasn't really made to support UEFI and that is why it is still a beta bios. It was made so people could try it to see if it work.
Most people that did try it never had really good luck with. I too have one of the Z68 boards that I used for one of my kids and it work great. But I never tried the UEFI bios. I thought about it, but with all I read I wasn't going to waste my time.
-
I'm not sticking up for them. But the thing is the Z68 board is old technology. The real last official Bios was the F7 02/2012. Most boards that are on the market you really are lucky to see a bios update past two year.
The U1G(UEFI BIOS) was a beta bios and really never was a official bios. The board wasn't really made to support UEFI and that is why it is still a beta bios. It was made so people could try it to see if it work.
Most people that did try it never had really good luck with. I too have one of the Z68 boards that I used for one of my kids and it work great. But I never tried the UEFI bios. I thought about it, but with all I read I wasn't going to waste my time.
Very early in the thread, people were reporting cold boot loops under legacy BIOS, and those BIOS were official releases as well!
-
I read this topic from the beginning to the end and I read the topic in the overclock forum too.
I got a GA-Z97-D3H, and I seeing this issue too.
http://forum.giga-byte.co.uk/index.php?topic=16188.0 -> Here's my topic.
So sad. :-\
-
Sorry to come back to this old thread, but I actually have a bit of news regarding this issue.
Since upgrading to Win10, I've tried to get some higher OCs just because I wanna see what the new BSODs look like (not joking).
With my history of cold boot loops when enabling internal CPU PLL overvoltage, I definitely got a BSOD with it disabled.
A special note about this BSOD is that I don't get it when stress testing the CPU. It only BSODs at idle, not load! (This is an entirely separate issue that I've seen on other threads, so I'm not sure how strong the correlation is with cold boot loops.)
I was already OCing anyway, so I figured that I might try to enable it to see if it's any different under Win10.
The OC results were as I expected, stable with higher OC and no BSOD at idles (or light loads).
After shutting down and powering on my system several times, I saw NO COLD BOOT LOOPS.
Even after turning off my system overnight, I saw no boot loops the next morning when I powered it on.
So far, it's only been 24 hours; will report back later if I get a cold boot loop!
-
Sorry to revive an old thread, but I was looking for information about this problem and I'm relieved, I guess, to see I'm not the only one.
Ever since I upgraded my old GA-Z68MX-UD2H-B3 (rev 1.0) from BIOS version F12 to UEFI U1e, booting the computer from power-off makes it turn its power off and on several times until it boots. Usually the screen remains dark while it does this, but occasionally I see "GIGABYTE - UEFI DualBIOS" at the top of the screen before it reboots.
I had this problem long ago when the BIOS and backup BIOS were different versions, and way back then I held down Alt-F12 at boot to copy BIOS to backup and that solved the problem. However, now my backup BIOS is still at F12, and holding down Alt-F12 at boot has no effect.
I'm not overclocking at all. I feel like the solution to my problem would be to copy the UEFI U1e to the backup BIOS, but I have no idea why Alt-F12 no longer works, and there doesn't seem to be any other way to copy it. I even pulled the CMOS battery out for twenty minutes then gave it a new battery - no change.
-
Check this FAQ for BIOS Synchronisation http://forum.giga-byte.co.uk/index.php?topic=10304.0
But, having faced a very similar problem with my own Z68 motherboard and the UEFI BIOS, which I couldn't resolve even after syncing both BIOS chips, I went back to the AMI BIOS which I ran until I upgraded my whole system.
-
THAT WAS IT! Thank you so much for the link to that article! It told me that the keys to hold at boot to copy BIOS to backup were Alt-F10 when I'm running AMI UEFI BIOS! I had never heard that before - all the sources I'd found said that the keys were Alt-F12, but that only works under Award BIOS!
I rebooted, held Alt-F10 - didn't even remove power or wait - and the BIOS copy screen came right up. I copied BIOS to backup, then powered down and cold-booted again.
Unfortunately, the computer turned off/on a few times again before it booted. But then I went into BIOS and changed the XMP profile from "Profile1" to "Disabled". This slows my 1600MHz memory down to 1333MHz, but I've read some reports that the reboot problem could be due to memory, so I'll see whether it helps.