Overclock.net › Forums › Intel › Intel Motherboards › Gigabyte P67/Z68 boot cycling problem
New Posts  All Forums:Forum Nav:

Gigabyte P67/Z68 boot cycling problem - Page 15

post #141 of 810
Quote:
Originally Posted by Villosa View Post
Let me get this straight, we're talking about when the PC turns on with fans spinning etc and shuts off in 5 sec or so and then does it over and over again right? Never reaching bios or show any indication of life on the screen?? Cause I haven't experienced that, my Z68XP has been good to me.
This is what I was referring too also. So that youtube video I linked to was not excactly the same.
    
CPUMotherboardGraphicsRAM
Core i7 2600K@4.5GHz Asus P8P67 Pro 3.0 (B3) EVGA GTX 1070 SC Black Edition 4x4GB Corsair Vengeance 1600-9-9-9-24-2t-1.5v 
Hard DriveOptical DriveOSMonitor
M500 240GB SSD for OS, 2x256GB M4's Raid0 for ... Generic Windows 10 Pro 64 Bit Asus VK266H 
PowerCase
Corsair RM 750x Cooler Master Storm Scout 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Core i7 2600K@4.5GHz Asus P8P67 Pro 3.0 (B3) EVGA GTX 1070 SC Black Edition 4x4GB Corsair Vengeance 1600-9-9-9-24-2t-1.5v 
Hard DriveOptical DriveOSMonitor
M500 240GB SSD for OS, 2x256GB M4's Raid0 for ... Generic Windows 10 Pro 64 Bit Asus VK266H 
PowerCase
Corsair RM 750x Cooler Master Storm Scout 
  hide details  
Reply
post #142 of 810
I somehow managed to fix it on my board. It has been six days without it happening since I flashed back to F6 from F7d. Keep in mind though F6 originally caused it but somehow this latest flash fixed it. While it's been only six days, it should have shown by now. Also, I've done a ton with this board now and it hasn't even looped once. I've switched on/off my system dozens of times, I've upgraded a video card, I've re-organized my cables, I've messed with the BIOS a ton, etc. The only thing that changed with my latest flash is I used a known stable overclock of 24hr Prime95 and 50 Linx runs. All the other times I was still working to find a stable OC so all the other BIOS flashes experienced unstable overclocks at one point.

I'm curious, perhaps it's possible unstable overclocks can corrupt the BIOS and cause the boot loop? This would explain why it happens even when you go back to stock. I don't think this idea is too farfetched either. Gigabyte uses a hybrid UEFI BIOS that lets you modify BIOS settings in Windows via TouchBIOS. Couldn't it be possible an unstable overclock, which results in Windows crashing, could somehow cause BIOS corruption? It's just a thought and could very well prove to be wrong but some of you suffering from it may want to try one of the following:
  • Flashing to F6 at STOCK settings. Remaining at STOCK settings after the flash and see if the boot loop reappears
  • Flashing to F6 at known stable overclock settings and then resetting these known stable overclocks afterwards. (NOTE: You must be absolutely positive your overclock is stable. I'd strongly suggest nothing less than 24hr Prime95 and 50Linx runs. Otherwise, it may very well be an unstable OC.)

Edited by sgr215 - 6/18/11 at 2:06pm
5820k
(15 items)
 
  
CPUMotherboardGraphicsRAM
5820k @ 4.5Ghz Gigabyte GA-X99-SLI EVGA GTX 980 Ti 32GB G.SKILL DDR4 2400 
Hard DriveCoolingOSMonitor
2x Samsung 256GB 850 Pro SSD's Corsair H110i GTX Windows 10 Pro 64Bit Dell U2311H (IPS Panel) 
PowerCaseAudio
Seasonic X-1250 Obsidian 900D HT Omega eClaro PCIe 
  hide details  
Reply
5820k
(15 items)
 
  
CPUMotherboardGraphicsRAM
5820k @ 4.5Ghz Gigabyte GA-X99-SLI EVGA GTX 980 Ti 32GB G.SKILL DDR4 2400 
Hard DriveCoolingOSMonitor
2x Samsung 256GB 850 Pro SSD's Corsair H110i GTX Windows 10 Pro 64Bit Dell U2311H (IPS Panel) 
PowerCaseAudio
Seasonic X-1250 Obsidian 900D HT Omega eClaro PCIe 
  hide details  
Reply
post #143 of 810
Quote:
Originally Posted by sgr215 View Post
I somehow managed to fix it on my board. It has been six days without it happening since I flashed back to F6 from F7d. Keep in mind though F6 originally caused it but somehow this latest flash fixed it. While it's been only six days, it should have shown by now. Also, I've done a ton with this board now and it hasn't even looped once. I've switched on/off my system dozens of times, I've upgraded a video card, I've re-organized my cables, I've messed with the BIOS a ton, etc.

I'm curious, perhaps it's possible unstable overclocks can corrupt the BIOS and cause the boot loop? This would explain why it happens even when you go back to stock. I don't think this idea is too farfetched either. Gigabyte uses a hybrid UEFI BIOS that lets you modify BIOS settings in Windows via TouchBIOS. Couldn't it be possible an unstable overclock, which results in Windows crashing, could somehow cause BIOS corruption? It's just a thought and could very well prove to be wrong but some of you suffering from it may want to try one of the following:
  • Flashing to F6 at STOCK settings. Remaining at STOCK settings after the flash and see if the boot loop reappears
  • Flashing to F6 at known stable overclock settings and then resetting these known stable overclocks afterwards. (NOTE: You must be absolutely positive your overclock is stable. I'd strongly suggest nothing less than 24hr Prime95 and 50Linx runs. Otherwise, it may very well be an unstable OC.)
Yes that could be the problem, the bigger problem is that its hard to reproduce so its even harder to fix. If something is easily reproducible then you can pin point the problem, if its not acting the way it should. What was linked in that UD3R video was acting like it should b/c the settings the guy had were unstable, or its a bug, with the exact settings he put in who knows if his RAm timings are correct? There are many ways to fight each argument, i just have no clue why you asus guys would even be in this thread? Bashing for no apparent reason on a product you dont even own?
X99 Main Rig
(10 items)
 
  
CPUMotherboardGraphicsRAM
Intel 5960X Extreme Edition @ 4.5GHz Always Changing VisonTek R9 290 G.Skill Ripjaws 4 16GB (4x4GB) DDR4 @ 3200MHz 
Hard DriveHard DriveHard DriveCooling
Samsung 128GB M.2 PCI-E 4x SSD Apotop 256GB SSD 1.82TB NAS Noctua NH-D15 with both fans 
OSPower
Win7 Pro Enermax 1000W 
  hide details  
Reply
X99 Main Rig
(10 items)
 
  
CPUMotherboardGraphicsRAM
Intel 5960X Extreme Edition @ 4.5GHz Always Changing VisonTek R9 290 G.Skill Ripjaws 4 16GB (4x4GB) DDR4 @ 3200MHz 
Hard DriveHard DriveHard DriveCooling
Samsung 128GB M.2 PCI-E 4x SSD Apotop 256GB SSD 1.82TB NAS Noctua NH-D15 with both fans 
OSPower
Win7 Pro Enermax 1000W 
  hide details  
Reply
post #144 of 810
Quote:
Originally Posted by Sin0822 View Post
What was linked in that UD3R video was acting like it should b/c the settings the guy had were unstable, or its a bug, with the exact settings he put in who knows if his RAm timings are correct? There are many ways to fight each argument, i just have no clue why you asus guys would even be in this thread? Bashing for no apparent reason on a product you dont even own?
No one is bashing anything. I'm no fanboy or trying to be rude in any way.

I'm just stating the fact that Gigabyte has had these loop-cycle-problems for years.
    
CPUMotherboardGraphicsRAM
Core i7 2600K@4.5GHz Asus P8P67 Pro 3.0 (B3) EVGA GTX 1070 SC Black Edition 4x4GB Corsair Vengeance 1600-9-9-9-24-2t-1.5v 
Hard DriveOptical DriveOSMonitor
M500 240GB SSD for OS, 2x256GB M4's Raid0 for ... Generic Windows 10 Pro 64 Bit Asus VK266H 
PowerCase
Corsair RM 750x Cooler Master Storm Scout 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Core i7 2600K@4.5GHz Asus P8P67 Pro 3.0 (B3) EVGA GTX 1070 SC Black Edition 4x4GB Corsair Vengeance 1600-9-9-9-24-2t-1.5v 
Hard DriveOptical DriveOSMonitor
M500 240GB SSD for OS, 2x256GB M4's Raid0 for ... Generic Windows 10 Pro 64 Bit Asus VK266H 
PowerCase
Corsair RM 750x Cooler Master Storm Scout 
  hide details  
Reply
post #145 of 810
Quote:
Originally Posted by turrican9 View Post
Motherboard reboots several times and go back to stock settings. This is the typical loop boot issue. This can also get worse and worse, until the computer go in an eternal loop and won't boot up at all.
Which has just happened to me. Though to clarify, only my CPU multiplier got reset when the loop occurred. Didn't matter if it was set below or above default. Been using the board since the 7th with the cold boot loop and now today, suddenly, without changing anything, it's just an eternal loop that absolutely refuses to post. Unplugging the 24-pin power connector didn't work either. Put my trusty UD3R back in which I"m typing from now. *sigh*
Edited by Patrick Wolf - 6/18/11 at 5:55pm
post #146 of 810
Quote:
Originally Posted by turrican9 View Post
No one is bashing anything. I'm no fanboy or trying to be rude in any way.

I'm just stating the fact that Gigabyte has had these loop-cycle-problems for years.

Turrican is right. I experienced this exact issue with 2 GA P965 boards. I finally realized that it was a RAM compatibility issue. I suspect that a lot of these boot loop issues are RAM related.
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel E6600 (LL629A) DFI BLOOD IRON P35-T2RL Diamond HD3870 GSkill ( 2x1G) DDR2-800 HZ's 
OSMonitorKeyboardCase
Windows XP Home (OEM) Sceptre 22" + Sceptre 20" Logitech G15 XG VIPER ( hey, it was free.) 
Mouse
LOGITECH MX518 
  hide details  
Reply
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel E6600 (LL629A) DFI BLOOD IRON P35-T2RL Diamond HD3870 GSkill ( 2x1G) DDR2-800 HZ's 
OSMonitorKeyboardCase
Windows XP Home (OEM) Sceptre 22" + Sceptre 20" Logitech G15 XG VIPER ( hey, it was free.) 
Mouse
LOGITECH MX518 
  hide details  
Reply
post #147 of 810
I'm starting to think we're all talking about different bugs here in regards to older boards experiencing it. That video looks nothing like the boot loop I experience. In fact, that video looks like the board is doing exactly what it's supposed to do; recovering from incorrect settings and then properly posting.

Here is what happens on Z68 boards:
  1. End-user presses the power button
  2. The system powers on, fans spin up, system LED's light up, and board LED's light up. There is no video.
  3. After a second or two the system suddenly shuts back off. Fans and LED's turn off and the system is effectively in an off state.
  4. A couple seconds later, without any user intervention, the system turns back on. Fans spin up, leds turn on, and no video is displayed. Once again, after a couple seconds the system suddenly shuts back off.
  5. This process repeats indefinitely until the PSU is switched off and/or power is physically pulled from the PC. The system will almost NEVER recover on it's on.
  6. Once you pull the power the board will post. However, the user may, or may not, experience several oddities such as incorrect time and/or a message complaining the BIOS recovered from an unstable overclock. (Which often happens even with the system at stock)

Edited by sgr215 - 6/18/11 at 6:34pm
5820k
(15 items)
 
  
CPUMotherboardGraphicsRAM
5820k @ 4.5Ghz Gigabyte GA-X99-SLI EVGA GTX 980 Ti 32GB G.SKILL DDR4 2400 
Hard DriveCoolingOSMonitor
2x Samsung 256GB 850 Pro SSD's Corsair H110i GTX Windows 10 Pro 64Bit Dell U2311H (IPS Panel) 
PowerCaseAudio
Seasonic X-1250 Obsidian 900D HT Omega eClaro PCIe 
  hide details  
Reply
5820k
(15 items)
 
  
CPUMotherboardGraphicsRAM
5820k @ 4.5Ghz Gigabyte GA-X99-SLI EVGA GTX 980 Ti 32GB G.SKILL DDR4 2400 
Hard DriveCoolingOSMonitor
2x Samsung 256GB 850 Pro SSD's Corsair H110i GTX Windows 10 Pro 64Bit Dell U2311H (IPS Panel) 
PowerCaseAudio
Seasonic X-1250 Obsidian 900D HT Omega eClaro PCIe 
  hide details  
Reply
post #148 of 810
^ That sums up my board almost exactly. Except my system usually did recover after 3-4 cycles, but now it's just an endless loop with no fix. Have to RMA.
Edited by Patrick Wolf - 6/18/11 at 8:03pm
post #149 of 810
Thread Starter 
Quote:
Originally Posted by chroniX View Post
AzO, unless I'm mistaken, I believe Gigabyte has UEFI as well, it's just not GUI driven.
Yes, hybrid UEFI with traditional GUI.

Quote:
Originally Posted by drBlahMan View Post
I understand that. ASUS has always been quick to fix there boot-loop situations. I give them high respect for that. Gigabyte on the other hand, has been going through this for ages. Gigabyte does need to be more consistent in releasing their fix for these problems. I just do not like the fact that people get up here and start making it sound like you're doomed whenever you buy a Gigabyte mobo. Yeah, I got alittle sensitive about it (shame on me) but at least individuals should be a bit more factual when talking about these occurences.
2 points, 1) People don't want to deal with this problem, even if there is a small chance. 2) Gigabyte is not swift in dealing with this problem.

turrican9 is blowing this way out of proportion.

That is NOT and I repeat NOT the boot loop problem exhibited on the P67/Z68 boards.

With the boot loop, you can't even enter the BIOS, it gets stuck at Memory Testing and then reboots, infinitely, IDE channels 0-X will not detect/show up.

Quote:
Originally Posted by turrican9 View Post
Yes it is the boot loop issues. Motherboard reboots several times and go back to stock settings. This is the typical loop boot issue. This can also get worse and worse, until the computer go in an eternal loop and won't boot up at all.
No, that is not a boot loop, sorry.

Quote:
Originally Posted by rottenotto View Post
Turrican is right. I experienced this exact issue with 2 GA P965 boards. I finally realized that it was a RAM compatibility issue. I suspect that a lot of these boot loop issues are RAM related.
No, it's not RAM related. I tired using two different manufacturers on Gigabyte's QVL and nothing worked. Still boot looping.

Quote:
Originally Posted by sgr215 View Post
I'm starting to think we're all talking about different bugs here in regards to older boards experiencing it. That video looks nothing like the boot loop I experience. In fact, that video looks like the board is doing exactly what it's supposed to do; recovering from incorrect settings and then properly posting.

Here is what happens on Z68 boards:
  1. End-user presses the power button
  2. The system powers on, fans spin up, system LED's light up, and board LED's light up. There is no video.
  3. After a second or two the system suddenly shuts back off. Fans and LED's turn off and the system is effectively in an off state.
  4. A couple seconds later, without any user intervention, the system turns back on. Fans spin up, leds turn on, and no video is displayed. Once again, after a couple seconds the system suddenly shuts back off.
  5. This process repeats indefinitely until the PSU is switched off and/or power is physically pulled from the PC. The system will almost NEVER recover on it's on.
  6. Once you pull the power the board will post. However, the user may, or may not, experience several oddities such as incorrect time and/or a message complaining the BIOS recovered from an unstable overclock. (Which often happens even with the system at stock)
Bingo!

Quote:
Originally Posted by turrican9 View Post
No one is bashing anything. I'm no fanboy or trying to be rude in any way.

I'm just stating the fact that Gigabyte has had these loop-cycle-problems for years.
No, but you're wrong. Only for P67/Z68 chipset. I've been a loyal Gigabyte user before the P35 days, I'm sure much longer than you. Me switching my clients to Asus says A LOT about the P67/Z68 chipset.
Edited by AzO - 6/18/11 at 8:13pm
Shhhhh!
(13 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 930 Gigabyte GA-X58A-UD3R XFX 5870 1GB 6GB G.SKILL PI 1600MHz 
Hard DriveOptical DriveOSMonitor
120GB OCZ Vertex 2, 2x Hitachi 2TB (7K2000) Pioneer Blu-ray BDR-205BKS, Samsung SH-S243N Windows 7 Ultimate x64/WinXP Pro SP3 Samsung P2570 
KeyboardPowerCaseMouse
Logitech Elite Keyboard Corsair 850HX Lian-Li PC-B70 Logitech MX510 
Mouse Pad
Gel 
  hide details  
Reply
Shhhhh!
(13 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 930 Gigabyte GA-X58A-UD3R XFX 5870 1GB 6GB G.SKILL PI 1600MHz 
Hard DriveOptical DriveOSMonitor
120GB OCZ Vertex 2, 2x Hitachi 2TB (7K2000) Pioneer Blu-ray BDR-205BKS, Samsung SH-S243N Windows 7 Ultimate x64/WinXP Pro SP3 Samsung P2570 
KeyboardPowerCaseMouse
Logitech Elite Keyboard Corsair 850HX Lian-Li PC-B70 Logitech MX510 
Mouse Pad
Gel 
  hide details  
Reply
post #150 of 810
< Boot loop here. That is why I am going to ASUS.
First of all, the boot loop.
What sgr215 describes is exactly what I am having. And I do get "System has recovered from an unstable overclock" and my BIOS is returned to the ORIGINAL BIOS that was delivered with the mobo.
This happens every time I start to overclock. Currently I am overclocked at 4.1GHz, and after that Mr Bootloop strikes me all the time. That's pissing me off.
Never have got any issue's with ASUS/MSI and this is my first Gigabyte and it's disappointing me.
My New build <3
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 2600K @ 4.5 Gigabyte GA-P67-UD4 EVGA GTX 570 Kingston HyperX 1600Mhz 
Hard DriveOptical DriveOSKeyboard
Samsung 1TB Sony-Nec Windows 7 Pro Razer Lycosa 
PowerCaseMouse
XFX Pro 750W NZXT Phantom Razer Deathadder 
  hide details  
Reply
My New build <3
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 2600K @ 4.5 Gigabyte GA-P67-UD4 EVGA GTX 570 Kingston HyperX 1600Mhz 
Hard DriveOptical DriveOSKeyboard
Samsung 1TB Sony-Nec Windows 7 Pro Razer Lycosa 
PowerCaseMouse
XFX Pro 750W NZXT Phantom Razer Deathadder 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel Motherboards
Overclock.net › Forums › Intel › Intel Motherboards › Gigabyte P67/Z68 boot cycling problem