Overclock.net › Forums › Intel › Intel Motherboards › P67A-UD7-B3 Killed 2 of my 2600Ks
New Posts  All Forums:Forum Nav:

P67A-UD7-B3 Killed 2 of my 2600Ks - Page 2

post #11 of 22
putting the CPU in, anytime you touch the CPU, in transit from one board to another.

You might want to check your pins in the socket see if they are bent.
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 #12 of 22
Thread Starter 
Yea I destatic'ed myself by touching the case. The board is already on its way to Gigabyte central in the City of Industry, CA, so I can't check for bent pins right now. But I was extremely careful in taking the chip in and out, and looked at the pins after I took it out each time, so I don't think there were bent pins.
Monster
(13 items)
 
  
CPUMotherboardGraphicsRAM
2600K Z77MA-G45 GTX 580 G.Skill Ripjaws 1600 4x4GB 
Hard DriveMonitorKeyboardPower
Vertex 4 ASUS VE276Q CM Storm Quickfire Cherry Red MX AX 860i 
CaseMouse
SG09 Logitech G9X 
  hide details  
Reply
Monster
(13 items)
 
  
CPUMotherboardGraphicsRAM
2600K Z77MA-G45 GTX 580 G.Skill Ripjaws 1600 4x4GB 
Hard DriveMonitorKeyboardPower
Vertex 4 ASUS VE276Q CM Storm Quickfire Cherry Red MX AX 860i 
CaseMouse
SG09 Logitech G9X 
  hide details  
Reply
post #13 of 22
I signed up here just to say that this happened to me as well, because it's the only forum I've seen where someone else had the same problem as I did (I thought I just had a faulty board).

I can't remember all the specifics of everything I did during my install/update process, but I do know that I didn't do everything exactly the same as Sin0822. Also, the Vcore over-voltage was different (1.66V I think, as opposed to 1.78V). The main common thing seems to be bios version F3, so if there's anyone else on F3, I would advise them to go back to F2 or up to F4A (or later) asap.

Here are some notes about what happened with my rig:

1. At some point while installing/updating Windows and upgrading from bios version F2 -> F3 -> F4A, my PC started to become unstable even when not under load (symptom: instant reboot). I went back into bios and noticed that the Vcore had somehow set itself to 1.66V or thereabouts (I forget if I was on F3 or F4A bios version by this stage, definitely not F2). There's no possible way I could have done this by accident. If it was on the maximum voltage I could theorise an accidental keypress and save without noticing, but the fact that it was about 6 steps down from the maximum meant I'd have to make the same retarded typo 6 times in a row, or had the only narcoleptic moment in my life for half a second while my hand was resting on the left or right arrow key.

2. I didn't change the VTT voltage, or indeed any voltage before this happened. Not exited/saved anyway. I scrolled through some settings to see what the low/high values were after I first installed the hardware, but I most definitely didn't save any of those settings and they were all definitely on default auto settings when I exited bios. I didn't even change any clock frequencies because I was still installing Windows and not yet up to my overclocking phase of my build. If the VTT setting is causing it, it seems that you don't have to save the setting for it to change your Vcore. Later when I saw the Vcore had somehow been set to 1.66V, it was the only voltage that wasn't set to Auto so to me that's proof enough that I didn't accidentally change/save my VTT.

3. I noticed that this board would not often not save/load settings on the first attempt, so even if I did load optimal settings (which I usually do as a matter of habit, but I cannot say for 100% certainty that I did this time) it may not have loaded the settings anyway because I'm not in the habit of saving/loading my settings twice. I never saw it fail to load/save on the second attempt though, but sometimes after this happened I started loading/saving 3 times to make DAMN sure the settings carried properly.

4. The CPU deteriorated quite quickly after the first spontaneous reboot, until I worked out what had happened. I'd say less than 10 minutes of running at 1.66V before I noticed it in bios and reset it back to auto/1.2V. It would start to reboot even in bios for no reason, and was still getting worse even after I'd fixed the vcore. This was at 1.66V, if the voltage was 1.78V like catcherintherye's, it's conceivable that the CPU could fry before it finished its first POST.

5. The first evidence I noticed that the CPU was dying was the Event log in Windows, which had a bunch of administrator log warnings saying that there were problems with the CPU cache, and that the error messages were generated by the CPU itself and therefore very likely to be a hardware fault in the CPU, rather than a dodgy motherboard or incorrect drivers loaded etc.

6. I sent the CPU back to the shop see if Intel would cover it under warranty. This seemed to be an easier option than convincing Gigabyte that they fried my CPU and making them buy me a new one, even though it is almost certainly their fault. All I could do is sign a stat-dec saying that I had not as yet overclocked anything about the board, but then they might question why I updated the bios if the factory version f2 was working fine, or why I bought a board designed for overclocking and then not overclock it. If I sent the board back after I fixed the bios settings, they'd just say there's nothing wrong with it and therefore it couldn't have killed my CPU. Maybe these forum posts might lend weight to any warranty claims from either Gigabyte or Intel.

7. I've only ever had one other CPU fail in my 18+ years of building PC's and overclocking them, it was a Celeron 300A sometime in the mid 90's and died for no apparent reason (my system froze randomly rather than rebooted, CPU was replaced under warranty by Intel). I'm only mentioning this because of the suggestions that catcherintherye might have fried 2 CPU's in a row with accidental static, which to me doesn't seem very likely for someone skilled enough to build a 5GHz watercooled rig
post #14 of 22
Thread Starter 
Thanks for posting jimx. It would seem the problem so far is only specific to the F4A bios, since you were using this bios as well and experienced a similar problem. I'd hoped that this thread would bring together users who've experienced a similar problem. I'm thinking of just having Gigabyte give me a refund for the board since I got it directly from them rather than giving me a replacement, or just selling the new RMA's board when I get it back, although if the problem is only isolated to F4A rather than say the "official" F3 bios offered on their website, maybe there wouldn't be a problem if I just stuck with F3.
Edited by catcherintherye - 4/29/11 at 10:14am
Monster
(13 items)
 
  
CPUMotherboardGraphicsRAM
2600K Z77MA-G45 GTX 580 G.Skill Ripjaws 1600 4x4GB 
Hard DriveMonitorKeyboardPower
Vertex 4 ASUS VE276Q CM Storm Quickfire Cherry Red MX AX 860i 
CaseMouse
SG09 Logitech G9X 
  hide details  
Reply
Monster
(13 items)
 
  
CPUMotherboardGraphicsRAM
2600K Z77MA-G45 GTX 580 G.Skill Ripjaws 1600 4x4GB 
Hard DriveMonitorKeyboardPower
Vertex 4 ASUS VE276Q CM Storm Quickfire Cherry Red MX AX 860i 
CaseMouse
SG09 Logitech G9X 
  hide details  
Reply
post #15 of 22
That's why I stuck with f3 betas. Zero problems like this (stuff like higher bclk's not working on cold starts at least don't kill chips). I told others that f3 final and f4a are unstable. Some believed me, some didn't. How many more people must have their cpu's fry before others get the point?
SB Rig
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7-2600k Gigabyte P67A-UD5 B3 R9 290X 16GB 
Hard DriveOptical DriveOSMonitor
WD 2 TB, WD 1 TB, 250gb Liteon ihbs212 blu-ray burner/reader XP+W7 Benq XL2720Z 
KeyboardPowerCaseMouse
Ducky Shine 69/Year of the Goat/Shine 5 Seasonic Platinum X1000 Corsair 760T Logitech G502 with r0ach approved ™ sensor 
Mouse Pad
Puretrak Talent 
  hide details  
Reply
SB Rig
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7-2600k Gigabyte P67A-UD5 B3 R9 290X 16GB 
Hard DriveOptical DriveOSMonitor
WD 2 TB, WD 1 TB, 250gb Liteon ihbs212 blu-ray burner/reader XP+W7 Benq XL2720Z 
KeyboardPowerCaseMouse
Ducky Shine 69/Year of the Goat/Shine 5 Seasonic Platinum X1000 Corsair 760T Logitech G502 with r0ach approved ™ sensor 
Mouse Pad
Puretrak Talent 
  hide details  
Reply
post #16 of 22
I have the same board as you and i didn't get that 1.7 @ boot bug. I do have my chip at 1.5v though and i haven't had any troubles so far not even heat. The board is awesome and the chip is even better so don't give up hope you most have just been real unlucky to get that bad board sorry man. I've actually made it to windows at 1.68v on accident of course when i was fooling with llc which i immediately changed back down to 1.5v. Then i had to read up on LLC because i was overly uncautious trying to make it to 5ghz stable. Hopefully you get it all situated good luck man.
post #17 of 22
Thread Starter 
Getting the board back from Gigabyte tomorrow. Will install on Saturday and hopefully Gigabyte didn't give me back the same board without fixing it and I fry a third, then I can probably apply to Guinness for a world record.
Monster
(13 items)
 
  
CPUMotherboardGraphicsRAM
2600K Z77MA-G45 GTX 580 G.Skill Ripjaws 1600 4x4GB 
Hard DriveMonitorKeyboardPower
Vertex 4 ASUS VE276Q CM Storm Quickfire Cherry Red MX AX 860i 
CaseMouse
SG09 Logitech G9X 
  hide details  
Reply
Monster
(13 items)
 
  
CPUMotherboardGraphicsRAM
2600K Z77MA-G45 GTX 580 G.Skill Ripjaws 1600 4x4GB 
Hard DriveMonitorKeyboardPower
Vertex 4 ASUS VE276Q CM Storm Quickfire Cherry Red MX AX 860i 
CaseMouse
SG09 Logitech G9X 
  hide details  
Reply
post #18 of 22
Thread Starter 
Update: Got the board back and it's the exact same board. They didn't even give me back the original outer box for the UD7. Even though there's a sticker on it that says its been looked at I don't dare to put another chip in. I did some Googling on Gigabyte RMA's and it seems like there have been several instances where they just sent back the same thing unfixed. I'm not going to take that chance with this one. I shot them this email:

"The board that was returned to me was the same board I sent in, and I specifically requested a new board. I am uncomfortable putting another CPU into this board because it managed to kill the last two CPUs I put into it. Even if it has been inspected I don't want to take the chance that it will happen again. If I put a third CPU into this board and it dies again, will Gigabyte pay for it? I would now just like to send this board back in for a full refund, since I got it from you guys. Please send me a pre-paid shipping label, thanks."

Will update with a response when I get it.
Monster
(13 items)
 
  
CPUMotherboardGraphicsRAM
2600K Z77MA-G45 GTX 580 G.Skill Ripjaws 1600 4x4GB 
Hard DriveMonitorKeyboardPower
Vertex 4 ASUS VE276Q CM Storm Quickfire Cherry Red MX AX 860i 
CaseMouse
SG09 Logitech G9X 
  hide details  
Reply
Monster
(13 items)
 
  
CPUMotherboardGraphicsRAM
2600K Z77MA-G45 GTX 580 G.Skill Ripjaws 1600 4x4GB 
Hard DriveMonitorKeyboardPower
Vertex 4 ASUS VE276Q CM Storm Quickfire Cherry Red MX AX 860i 
CaseMouse
SG09 Logitech G9X 
  hide details  
Reply
post #19 of 22
Quote:
Originally Posted by catcherintherye View Post
Update: Got the board back and it's the exact same board. They didn't even give me back the original outer box for the UD7. Even though there's a sticker on it that says its been looked at I don't dare to put another chip in. I did some Googling on Gigabyte RMA's and it seems like there have been several instances where they just sent back the same thing unfixed. I'm not going to take that chance with this one. I shot them this email:

"The board that was returned to me was the same board I sent in, and I specifically requested a new board. I am uncomfortable putting another CPU into this board because it managed to kill the last two CPUs I put into it. Even if it has been inspected I don't want to take the chance that it will happen again. If I put a third CPU into this board and it dies again, will Gigabyte pay for it? I would now just like to send this board back in for a full refund, since I got it from you guys. Please send me a pre-paid shipping label, thanks."

Will update with a response when I get it.
Sad to hear, thankfully distro in my country for Gigabyte offers 1to1 exchange for such instances.
Core i7
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel I7 2600K Gigabyte P67A-UD7-B3 MSI 580GTX Lightning GSkill Trident 2 x 4 GB CL 7 
Hard DriveOSMonitorKeyboard
Intel 510 120GB SSD + Samsung F3 1TB + WD Blue 1TB Windows 7 64Bit Dell Ultrasharp U2311H + Dell Ultrasharp U2311H Ducky 9008 G2 Cherry MX Brown 
PowerCaseMouseMouse Pad
Seasonic X 850W 80+Gold HAFX Razer DeathAdder Black edition Razer eXactmat 
  hide details  
Reply
Core i7
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel I7 2600K Gigabyte P67A-UD7-B3 MSI 580GTX Lightning GSkill Trident 2 x 4 GB CL 7 
Hard DriveOSMonitorKeyboard
Intel 510 120GB SSD + Samsung F3 1TB + WD Blue 1TB Windows 7 64Bit Dell Ultrasharp U2311H + Dell Ultrasharp U2311H Ducky 9008 G2 Cherry MX Brown 
PowerCaseMouseMouse Pad
Seasonic X 850W 80+Gold HAFX Razer DeathAdder Black edition Razer eXactmat 
  hide details  
Reply
post #20 of 22
Quote:
Originally Posted by catcherintherye View Post
Update: Got the board back and it's the exact same board. They didn't even give me back the original outer box for the UD7. Even though there's a sticker on it that says its been looked at I don't dare to put another chip in. I did some Googling on Gigabyte RMA's and it seems like there have been several instances where they just sent back the same thing unfixed. I'm not going to take that chance with this one. I shot them this email:

"The board that was returned to me was the same board I sent in, and I specifically requested a new board. I am uncomfortable putting another CPU into this board because it managed to kill the last two CPUs I put into it. Even if it has been inspected I don't want to take the chance that it will happen again. If I put a third CPU into this board and it dies again, will Gigabyte pay for it? I would now just like to send this board back in for a full refund, since I got it from you guys. Please send me a pre-paid shipping label, thanks."

Will update with a response when I get it.
Why don't you just use f3g (or f3h I think for the ud7) and not even worry about the F4 bioses (or F3 final?). All you need are LLC1 and LLC2 anyway, and they work fine. Heck, on my UD5, LLC2 ->BIOS 1.400v, gives 1.428v load in Battlefield BC2, which is nowhere near as bad as I thought LLC2 would be. In Prime, about 1.440v max.

Use F3H and you won't kill any of your cpu's anymore.
SB Rig
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7-2600k Gigabyte P67A-UD5 B3 R9 290X 16GB 
Hard DriveOptical DriveOSMonitor
WD 2 TB, WD 1 TB, 250gb Liteon ihbs212 blu-ray burner/reader XP+W7 Benq XL2720Z 
KeyboardPowerCaseMouse
Ducky Shine 69/Year of the Goat/Shine 5 Seasonic Platinum X1000 Corsair 760T Logitech G502 with r0ach approved ™ sensor 
Mouse Pad
Puretrak Talent 
  hide details  
Reply
SB Rig
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7-2600k Gigabyte P67A-UD5 B3 R9 290X 16GB 
Hard DriveOptical DriveOSMonitor
WD 2 TB, WD 1 TB, 250gb Liteon ihbs212 blu-ray burner/reader XP+W7 Benq XL2720Z 
KeyboardPowerCaseMouse
Ducky Shine 69/Year of the Goat/Shine 5 Seasonic Platinum X1000 Corsair 760T Logitech G502 with r0ach approved ™ sensor 
Mouse Pad
Puretrak Talent 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel Motherboards
Overclock.net › Forums › Intel › Intel Motherboards › P67A-UD7-B3 Killed 2 of my 2600Ks