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 35

post #341 of 810
Quote:
Originally Posted by Snakecharmed View Post
I never found a fix.
I recommend that you get a different motherboard by another manufacturer.
First Let me start by saying someone should sticky my reply, I don't say this lightly, I say it because I have over 300 hours in this problem maybe more.

1. Do NOT recommend people get another brand of motherboard, that is first and foremost because I have used Gigabyte, Asus, Asrock and MSI and they all have this problem.

2. This problem is NOT a manufacturer problem from what I can tell, in my 30 motherboards of testing I have found that only one ( Asus P8Z68 Deluxe and only by sheer luck ) gave me any information and that information was the boot loop into memok reset into Code 78 Indicating what I thought all along was the problem, ACPI. This is a chipset issue, it wasn't right the first time and its not right now, Intel fubar'ed this one.

3. I have NOT found a resolve for this, once it does it the loop will never go away perfectly, I have updated bios', installed 1 - 3 GTX 580's, 1-2 GTX 590's, 1-2 6950's/6970's almost every configuration and brand of memory, SSD, video card and more and nothing makes a difference. I have also changed or ( for the guy mentioning disabling the Marvel chipset ) disabled every and I mean EVERY single type of hardware setting inside the bios' in an attempt to fix this and nothing. The last build the Asus Deluxe all the ACPI options inside the APM section were disabled Fyi so the hardware attempting to use it seems ridiculous in the first place.


Any questions about what all I have or have not tested just ask, but its basically everything, still willing to listen to suggestions for setups/what to check further to find the solution, but I would bet the solution is to tell Intel where to stick this chipset.


As another fyi I should have known months ago when I started this that the fact that I can't put my computer to sleep and have it wake up without a total reboot should have clued me in.


C
post #342 of 810
Quote:
Originally Posted by Nugzo;14552460 
i have a gigabyte z68 that is in an unstoppable loop. I've removed video cards, memory, cleared cmos, removed 24pin, nothing. powers on for 2-3 seconds then off for 8-9 seconds. over and over. nothing i've tried will stop it. it is oc'd and has been running flawless for 4 months. this has happened in the past though. there was some combination of holding power button, pulling power cord then booting into backup bios or something.. I cant find those instructions to save my life, been looking for 2 hours. Can somebody help please? how do you force a backup bios boot? someone said somewhere about shorting pins on the bios chip but i cant find them either.. pics or links to bios chip pics and which pins to short would be awesome if you have it on hand... thnks again..

I have read through this thread, it seems that some have had to actually pull the 24 pin power cable from the board, and clear the CMOS - I think. Best thing to do is start on page 1 and read through unless someone knows for certain, and can advise you what to do.

I'm fairly certain my Z68X-UD4 is going back - What board and bios are you using?? The AMD builds might not be as fast as Intel, but I have never had one that had the issues that I am reading about with the new Intel chipsets. Hopefully BD will even the CPU field a bit.

Trust7 - thanks for the input.
Edited by sequoia464 - 8/11/11 at 10:11pm
System
(14 items)
 
  
CPUMotherboardGraphicsRAM
8320 ASUS Sabertooth 990FX GTS 450 G.Skill 1600 ECO 1.35V 4x4 GB 
Hard DriveOptical DriveCoolingMonitor
SSD's - 2 Crucial M4's - 2 Plextor M3S's - 2 Ki... Samsung Corsair H60 Dell U2711, Dell 2407 
Power
Seasonic 
  hide details  
Reply
System
(14 items)
 
  
CPUMotherboardGraphicsRAM
8320 ASUS Sabertooth 990FX GTS 450 G.Skill 1600 ECO 1.35V 4x4 GB 
Hard DriveOptical DriveCoolingMonitor
SSD's - 2 Crucial M4's - 2 Plextor M3S's - 2 Ki... Samsung Corsair H60 Dell U2711, Dell 2407 
Power
Seasonic 
  hide details  
Reply
post #343 of 810
I have two boxes with the GA-Z68MX-UD5-B3 mobo. Both are loaded with 16 GB of Corsair Vengeance RAM. Machine #1 works like a champ. Machine #2 rejects anything over 8MB of RAM. When the additional sticks are in place, it goes into a continuous reboot cycle. It spins up for 5 seconds then reboots ... it repeats this infinitely.

Here are the steps I've taken to fix it ...
  • Moved memory around to see if I had a bad stick. Appeared to be a slot issue. NO JOY.
  • Replaced motherboard (RMA to NewEgg) because I thought it was a bad memory slot. NO JOY.
  • Replaced RAM with new set in new mobo. NO JOY.

At this point, I suspect I have setting wrong in BIOS, but I've looked and don't see anything out of place.

So, I need a sanity check! Anyone else seen this issue? if so, what was the fix?
post #344 of 810
Quote:
Originally Posted by trust7 View Post
First Let me start by saying someone should sticky my reply, I don't say this lightly, I say it because I have over 300 hours in this problem maybe more.

1. Do NOT recommend people get another brand of motherboard, that is first and foremost because I have used Gigabyte, Asus, Asrock and MSI and they all have this problem.

2. This problem is NOT a manufacturer problem from what I can tell, in my 30 motherboards of testing I have found that only one ( Asus P8Z68 Deluxe and only by sheer luck ) gave me any information and that information was the boot loop into memok reset into Code 78 Indicating what I thought all along was the problem, ACPI. This is a chipset issue, it wasn't right the first time and its not right now, Intel fubar'ed this one.

3. I have NOT found a resolve for this, once it does it the loop will never go away perfectly, I have updated bios', installed 1 - 3 GTX 580's, 1-2 GTX 590's, 1-2 6950's/6970's almost every configuration and brand of memory, SSD, video card and more and nothing makes a difference. I have also changed or ( for the guy mentioning disabling the Marvel chipset ) disabled every and I mean EVERY single type of hardware setting inside the bios' in an attempt to fix this and nothing. The last build the Asus Deluxe all the ACPI options inside the APM section were disabled Fyi so the hardware attempting to use it seems ridiculous in the first place.


Any questions about what all I have or have not tested just ask, but its basically everything, still willing to listen to suggestions for setups/what to check further to find the solution, but I would bet the solution is to tell Intel where to stick this chipset.


As another fyi I should have known months ago when I started this that the fact that I can't put my computer to sleep and have it wake up without a total reboot should have clued me in.


C
uhh... Then common sense would dictate that it also involves the motherboard drivers...

What motherboard drivers are you guys using because the ones on the Gigabyte site are OLD. You know you've installed the older screwy drivers because one device doesn't get it's drivers installed properly. It's called "Management Engine Interface".

When I install windows the FIRST THING I INSTALL IS THE CHIPSET DRIVERS!!! If you install other hardware first it might causes major issues. I'm shocked at how many people don't install chipset drivers AT ALL and rely on the windows boxed drivers... DUHH! Then they complain when they have ACPI/power management issues and lockups with PCIE and PCI expansion cards in certain slots, firewire and USB issues... MORONS...

Here is a URL to the LATEST INTEL P67/C200 chipset drivers version 9.2.0.1030 from May 2011 !!!

http://downloadcenter.intel.com/conf...ProductID=3301

Gigabyte's site lists 9.2.0.1021 from January 2011 and the ones on the CD are even OLDER!!!

ALLWAYS INSTALL CHIPSET DRIVERS FIRST!!!

and if you didn't and installed say video or another hardware device driver then chipset you're asking for problems. It's best to uninstall that hardware device FIRST then install the chipset drivers then install the hardware device again.

This has MAJOR affect on how memory address space, DMA, IRQs and so on and so on is assigned to devices on the system. Some of you will require a reinstall of the OS if you've really buggered it... install... uninstall... reinstall then uninstall then reinstall video then reinstall chipset drivers... so on and so on... DUHH!!!

Device Manager-->System devices is the area and devices that get installed screwy that cause these issues when the chipset drivers (and latest bug free) are NOT installed OR installed AFTER any other device, soundcard, NIC, Video Adapter and so on... not to mention ACPI issues!

PS Disable "CPU PLL Overvoltage" don't use auto BS as you can't trust it, Turn off Turbo Core unless you set it to higher than your overclock. A lot of dorks have turbo core set to auto or enabled and have it set to factory defaults which is clock speeds on each core SLOWER than your overclock. This can cause issues... Also make sure "Performance Enhance" is set to normal.
Edited by HiroPro - 8/12/11 at 8:59pm
Hal9000
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500K @ 4.2Ghz 1.325v in BIOS but 1.278 DMM Gigabyte P67A-UD5-B3 BIOS F5 HD 4890 Mushkin Blackline 996744 PC3-12800 8-8-8-24@1.58v 
Hard DriveOptical DriveOSMonitor
WD Caviar Black 1TB SH-203N Win 7 Ultimate X64 and Linux Mint LG 24" 16:10 
PowerCase
Corsair HX650 Lian Li PC-8FI 
  hide details  
Reply
Hal9000
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500K @ 4.2Ghz 1.325v in BIOS but 1.278 DMM Gigabyte P67A-UD5-B3 BIOS F5 HD 4890 Mushkin Blackline 996744 PC3-12800 8-8-8-24@1.58v 
Hard DriveOptical DriveOSMonitor
WD Caviar Black 1TB SH-203N Win 7 Ultimate X64 and Linux Mint LG 24" 16:10 
PowerCase
Corsair HX650 Lian Li PC-8FI 
  hide details  
Reply
post #345 of 810
Quote:
Originally Posted by HiroPro View Post
uhh... Then common sense would dictate that it also involves the motherboard drivers...

What motherboard drivers are you guys using because the ones on the Gigabyte site are OLD. You know you've installed the older screwy drivers because one device doesn't get it's drivers installed properly. It's called "Management Engine Interface".

When I install windows the FIRST THING I INSTALL IS THE CHIPSET DRIVERS!!! If you install other hardware first it might causes major issues. I'm shocked at how many people don't install chipset drivers AT ALL and rely on the windows boxed drivers... DUHH! Then they complain when they have ACPI/power management issues and lockups with PCIE and PCI expansion cards in certain slots, firewire and USB issues... MORONS...

Here is a URL to the LATEST INTEL P67/C200 chipset drivers version 9.2.0.1030 from May 2011 !!!

http://downloadcenter.intel.com/conf...ProductID=3301

Gigabyte's site lists 9.2.0.1021 from January 2011 and the ones on the CD are even OLDER!!!

ALLWAYS INSTALL CHIPSET DRIVERS FIRST!!!

and if you didn't and installed say video or another hardware device driver then chipset you're asking for problems. It's best to uninstall that hardware device FIRST then install the chipset drivers then install the hardware device again.

This has MAJOR affect on how memory address space, DMA, IRQs and so on and so on is assigned to devices on the system. Some of you will require a reinstall of the OS if you've really buggered it... install... uninstall... reinstall then uninstall then reinstall video then reinstall chipset drivers... so on and so on... DUHH!!!

Device Manager-->System devices is the area and devices that get installed screwy that cause these issues when the chipset drivers (and latest bug free) are NOT installed OR installed AFTER any other device, soundcard, NIC, Video Adapter and so on... not to mention ACPI issues!

PS Disable "CPU PLL Overvoltage" don't use auto BS as you can't trust it, Turn off Turbo Core unless you set it to higher than your overclock. A lot of dorks have turbo core set to auto or enabled and have it set to factory defaults which is clock speeds on each core SLOWER than your overclock. This can cause issues... Also make sure "Performance Enhance" is set to normal.
dude it cant be the drivers..this happens before drivers are loaded, before windows is loaded.. Try again man, no way its drivers... have you even read this thread?
post #346 of 810
Yes I read the entire thread... and I don't have the issue... but hey I'm a 38 year old veteran that built his first PC at the age of 9 in the MID EIGHTIES!!!

I can't see how the issues you are describing and others regarding shutting down could even be replicated BEFORE an OS is installed as you assert as there is no software to send the ACPI shutdown signal/state/command.

"No way it's not drivers" well brother... it's almost ALWAYS drivers if not RAM or Power that cause 95% of issues. Do you even understand that shutdown process as it related to BIOS/ACPI/IMEI on Win 7 !?! well I do and it involves DRIVERS DUH!!!

PS if you install Linux you might have hope of understanding the ACPI shutdown process and how it works. With M$ you'll never learn and your knowledge will remain stagnant

PSS Make sure high precision event timer is set to 64bit if your OS as it defaults to 32bit in BIOS. Also disable the EUFI boot CD/DVD support as some optical firmware won't like it(more like the BIOS won't like the CD/DVD firmware)... and don't mess with that 100meg partition M$ creates!!!
Edited by HiroPro - 8/14/11 at 12:56am
Hal9000
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500K @ 4.2Ghz 1.325v in BIOS but 1.278 DMM Gigabyte P67A-UD5-B3 BIOS F5 HD 4890 Mushkin Blackline 996744 PC3-12800 8-8-8-24@1.58v 
Hard DriveOptical DriveOSMonitor
WD Caviar Black 1TB SH-203N Win 7 Ultimate X64 and Linux Mint LG 24" 16:10 
PowerCase
Corsair HX650 Lian Li PC-8FI 
  hide details  
Reply
Hal9000
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500K @ 4.2Ghz 1.325v in BIOS but 1.278 DMM Gigabyte P67A-UD5-B3 BIOS F5 HD 4890 Mushkin Blackline 996744 PC3-12800 8-8-8-24@1.58v 
Hard DriveOptical DriveOSMonitor
WD Caviar Black 1TB SH-203N Win 7 Ultimate X64 and Linux Mint LG 24" 16:10 
PowerCase
Corsair HX650 Lian Li PC-8FI 
  hide details  
Reply
post #347 of 810
Quote:
Originally Posted by Nugzo View Post
dude it cant be the drivers..this happens before drivers are loaded, before windows is loaded.. Try again man, no way its drivers... have you even read this thread?

You didn't answer my query regarding installing the chipset drivers... Do you even install them? And if so what version do you install? The really old ones on the motherboard CD, the old ones on Gigabytes site, or the latest from Intel?

And if you install them do you install them BEFORE you install your video/audio/nic drivers?

PS how do you explain the fact I don't have this issue what so ever as many other don't have it either!?! uhhh we know how to install a custom PC and we don't have ID-10T errors.
Edited by HiroPro - 8/12/11 at 9:45pm
Hal9000
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500K @ 4.2Ghz 1.325v in BIOS but 1.278 DMM Gigabyte P67A-UD5-B3 BIOS F5 HD 4890 Mushkin Blackline 996744 PC3-12800 8-8-8-24@1.58v 
Hard DriveOptical DriveOSMonitor
WD Caviar Black 1TB SH-203N Win 7 Ultimate X64 and Linux Mint LG 24" 16:10 
PowerCase
Corsair HX650 Lian Li PC-8FI 
  hide details  
Reply
Hal9000
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500K @ 4.2Ghz 1.325v in BIOS but 1.278 DMM Gigabyte P67A-UD5-B3 BIOS F5 HD 4890 Mushkin Blackline 996744 PC3-12800 8-8-8-24@1.58v 
Hard DriveOptical DriveOSMonitor
WD Caviar Black 1TB SH-203N Win 7 Ultimate X64 and Linux Mint LG 24" 16:10 
PowerCase
Corsair HX650 Lian Li PC-8FI 
  hide details  
Reply
post #348 of 810
I also have to point out TENS OF THOUSANDS of prefab computers have been shipped and will be shipped with the P67 chipset from prefab vendors like HP, Dell, Sony et al.

If what you guys are suggesting is true it would make the news like the B1/2 stepping SATA issues as thousands and thousands of users would be affected...

Think about it and use some common sense and follow my posts and you won't have this issue with one exception... BIOS/RAM compatibility issues... mostly caused by using AUTO to set your memory because the user is to stupid to understand how to set it manually.

Newegg et all just LOVE YOU GUYS with your CONSTANT RMAs and returns!!!

Guys... BUY A BOOK... perhaps the 20th version of Scott Mueller's defacto/Tome book "Upgrading and Repairing PCs". Any PC tech worth his weight has owned this book as it's been around for 20 years!
Edited by HiroPro - 8/12/11 at 10:38pm
Hal9000
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500K @ 4.2Ghz 1.325v in BIOS but 1.278 DMM Gigabyte P67A-UD5-B3 BIOS F5 HD 4890 Mushkin Blackline 996744 PC3-12800 8-8-8-24@1.58v 
Hard DriveOptical DriveOSMonitor
WD Caviar Black 1TB SH-203N Win 7 Ultimate X64 and Linux Mint LG 24" 16:10 
PowerCase
Corsair HX650 Lian Li PC-8FI 
  hide details  
Reply
Hal9000
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500K @ 4.2Ghz 1.325v in BIOS but 1.278 DMM Gigabyte P67A-UD5-B3 BIOS F5 HD 4890 Mushkin Blackline 996744 PC3-12800 8-8-8-24@1.58v 
Hard DriveOptical DriveOSMonitor
WD Caviar Black 1TB SH-203N Win 7 Ultimate X64 and Linux Mint LG 24" 16:10 
PowerCase
Corsair HX650 Lian Li PC-8FI 
  hide details  
Reply
post #349 of 810
Quote:
Originally Posted by HiroPro View Post
You didn't answer my query regarding installing the chipset drivers... Do you even install them? And if so what version do you install? The really old ones on the motherboard CD, the old ones on Gigabytes site, or the latest from Intel?

And if you install them do you install them BEFORE you install your video/audio/nic drivers?

PS how do you explain the fact I don't have this issue what so ever as many other don't have it either!?! uhhh we know how to install a custom PC and we don't have ID-10T errors.
i havent had the issue for over 4 months til now. I have a folder with all the updated drivers as of my last windows install which was about 4 months ago. It has worked flawles Oc'd to 4.8, 100% stable using any stability or burn in test. My first install when the board came out was using the drivers from CD. i always install chipset drivers first. I own a PC repair store and have done this daily for 10 years. But like i said, it doesnt mattter in my case. I never get to a point where drivers are loaded, only powers up for a few seconds.
post #350 of 810
Quote:
Originally Posted by HiroPro View Post
]
PS how do you explain the fact I don't have this issue what so ever as many other don't have it either!?! uhhh we know how to install a custom PC and we don't have ID-10T errors.
luck you ID-10T, that explains it. Some peoples bad luck lol. It doesnt happen to everyone. It hasnt happened to any of the many customer builds i've done ( all gigabyte or ASUS boards)with this chipset family, only my personal system. I dont know if i agree with the previous poster either who said it was the chipset, not the motherboard, as i havent seen/read anything near as widespread as the gigabyte issues. I also dont know if i agree that you know how to install a custom PC.... If you did you should know that drivers, whether new, old, or windows installed, Do not load before POST lol. How could they? HDD's havent even been initialized yet.....My board still does it now on the bench with nothing installed but memory and video card.
Edited by Nugzo - 8/12/11 at 11:00pm
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