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

post #1 of 22
Thread Starter 
I just want to share my recent experience and see if anyone has had anything similar, namely their motherboard killing their CPUs. I've been out of commission and on my laptop the last few days because my UD7 killed 2 2600Ks. A few days ago my computer suddenly shut off and wouldn't turn back on again, the PSU just made click when I tried to start it up. Thinking it was anything but the CPU I tried replacing all the other parts to no avail. I finally took the 2600k back to where I bought it and when they diagnosed it they confirmed it was dead, and gave me a new one. I brought the new 2600K back and tested it on the MSI P67A-C43 that I had lying around due to my part-swapping tests. It worked fine. I then put it into my UD7 and when I pressed power there was just a click from the PSU, it wouldn't start up. I put the 2600K back into the MSI board and it wouldn't work anymore. I then took it back to the place I purchased it and it was confirmed dead.

So today, I RMA'ed the UD7 and brought the chip back and got another 2600K, which is working fine in the P67A-C43 for now. All other parts are the same, PSU, GPU, drives, etc..I think it may have to do with the voltages on the F4A bios I was using on the UD7, Sin0882 and others said it was unstable and I had the LLC at level 9. Maybe this killed my CPUs? I hope Gigabyte doesn't send me back the exact same board and end up with me killing a 3rd 2600K. Has this happened to anyone else as well? I Googled but didn't come up with anything, maybe because this is a relatively new board.
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 #2 of 22
If I remember correctly, I read in xtremesystems there's a buggy bios that pushes the vcore to 1.7++ on boot. Let me find that post and if I'm right, that's the one that killed your 2600K.
Red-rolock
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 4770K Asus Sabertooth Z87 POV GTX 670 8gb (2x4gb) G.Skills RipjawsX 1866 CL9 
Hard DriveHard DriveHard DriveOptical Drive
Samsung Evo Pro 120gb 1TB Western Digital Caviar Black 500GB Seagate Barracuda SATA DVDRW 20x 
CoolingCoolingOSMonitor
Corsair H100i 3 x Phobya Nano LED red fans, 2 x Scythe Kama fans Windows 8.1  LG IPS234V 23' 1920x1080 
MonitorKeyboardPowerCase
AOC LED 1920x1080 Razer BlackWidow XFX PRO 850W XXX edition Corsair Carbide 500R 
MouseMouse PadAudioAudio
Logitech MX518 Steelseries Diablo 3 edition Logitech z323 Logitech G35 
  hide details  
Reply
Red-rolock
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 4770K Asus Sabertooth Z87 POV GTX 670 8gb (2x4gb) G.Skills RipjawsX 1866 CL9 
Hard DriveHard DriveHard DriveOptical Drive
Samsung Evo Pro 120gb 1TB Western Digital Caviar Black 500GB Seagate Barracuda SATA DVDRW 20x 
CoolingCoolingOSMonitor
Corsair H100i 3 x Phobya Nano LED red fans, 2 x Scythe Kama fans Windows 8.1  LG IPS234V 23' 1920x1080 
MonitorKeyboardPowerCase
AOC LED 1920x1080 Razer BlackWidow XFX PRO 850W XXX edition Corsair Carbide 500R 
MouseMouse PadAudioAudio
Logitech MX518 Steelseries Diablo 3 edition Logitech z323 Logitech G35 
  hide details  
Reply
post #3 of 22
Yep, sin0882 is the same guy in xtremesys that mentioned that bug.
Red-rolock
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 4770K Asus Sabertooth Z87 POV GTX 670 8gb (2x4gb) G.Skills RipjawsX 1866 CL9 
Hard DriveHard DriveHard DriveOptical Drive
Samsung Evo Pro 120gb 1TB Western Digital Caviar Black 500GB Seagate Barracuda SATA DVDRW 20x 
CoolingCoolingOSMonitor
Corsair H100i 3 x Phobya Nano LED red fans, 2 x Scythe Kama fans Windows 8.1  LG IPS234V 23' 1920x1080 
MonitorKeyboardPowerCase
AOC LED 1920x1080 Razer BlackWidow XFX PRO 850W XXX edition Corsair Carbide 500R 
MouseMouse PadAudioAudio
Logitech MX518 Steelseries Diablo 3 edition Logitech z323 Logitech G35 
  hide details  
Reply
Red-rolock
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 4770K Asus Sabertooth Z87 POV GTX 670 8gb (2x4gb) G.Skills RipjawsX 1866 CL9 
Hard DriveHard DriveHard DriveOptical Drive
Samsung Evo Pro 120gb 1TB Western Digital Caviar Black 500GB Seagate Barracuda SATA DVDRW 20x 
CoolingCoolingOSMonitor
Corsair H100i 3 x Phobya Nano LED red fans, 2 x Scythe Kama fans Windows 8.1  LG IPS234V 23' 1920x1080 
MonitorKeyboardPowerCase
AOC LED 1920x1080 Razer BlackWidow XFX PRO 850W XXX edition Corsair Carbide 500R 
MouseMouse PadAudioAudio
Logitech MX518 Steelseries Diablo 3 edition Logitech z323 Logitech G35 
  hide details  
Reply
post #4 of 22
Thread Starter 
Quote:
Originally Posted by Retrolock View Post
Yep, sin0882 is the same guy in xtremesys that mentioned that bug.
Yea he said it was unstable but I didn't think it'd be THAT unstable to be instantly killing my chips on startup. The F4A bios for P67A-UD7 should be called the Chipkiller Bios.
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 #5 of 22
no it has to do when you flash a BIOS incorrectly, and only occurs after a bad flash. You also have to do certain things for it to occur and it only occured from flashing from BIOS F whatever to BIOS F3. If you flash to BIOS F3 and you don't load optimized defaults and you set qpi/vtt over 1.2v then the vcore will shoot to 1.78v. It hasn't killed anyones chips, and you have to do exactly what i say, you have to set qpi/vtt over 1.2v and you have to not load optimized defaults, and there were only accounts of it with BIOS F3 flash, not F4A. F4A actually fixed that bug.

It only occurs with a bad BIOS flash, and the thing is all you have to do is reset BIOS and load optimized defaults and reboot.

it wont automatically just set your VCore for 1.78v lol.

If you are on BIOS F4A then that isn't the problem. I also told GB and they weren't able to reproduce it, and i only was able to produce it one time on purpose.

I bet something is wrong with your PSu or your setup like a short or somthing, i haven't heard of the board killing CPUs, even with 1.78v.
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 #6 of 22
Thread Starter 
Quote:
Originally Posted by Sin0822 View Post
no it has to do when you flash a BIOS incorrectly, and only occurs after a bad flash. You also have to do certain things for it to occur and it only occured from flashing from BIOS F whatever to BIOS F3. If you flash to BIOS F3 and you don't load optimized defaults and you set qpi/vtt over 1.2v then the vcore will shoot to 1.78v. It hasn't killed anyones chips, and you have to do exactly what i say, you have to set qpi/vtt over 1.2v and you have to not load optimized defaults, and there were only accounts of it with BIOS F3 flash, not F4A. F4A actually fixed that bug.

It only occurs with a bad BIOS flash, and the thing is all you have to do is reset BIOS and load optimized defaults and reboot.

it wont automatically just set your VCore for 1.78v lol.

If you are on BIOS F4A then that isn't the problem. I also told GB and they weren't able to reproduce it, and i only was able to produce it one time on purpose.

I bet something is wrong with your PSu or your setup like a short or somthing, i haven't heard of the board killing CPUs, even with 1.78v.
Thanks for replying. I flashed with Q-Flash in the Gigabyte bios. I replaced the PSU already btw in between killing the two chips, one AX850 for another. I also thought it might have been watercooling problems so I took out all the watercooling before I put in the 2nd chip, and it still died.
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 #7 of 22
then something is wrong with your board, because that is very odd. CPus also easily die from static so that is always a possibility. Other than that there is no issue with teh P67A-UD7 killing CPUs other than yours is the first i have heard. Sorry about it, i am sure if it kills GBs CPUs they will replace it.
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 #8 of 22
Make sure that you discharge ALL static from your body before touching the chip....or wear an anti-static wrist strap, the technically correct way

Although...it sounds like a faulty mobo to me. Maybe somewhere along the PCB, voltages were crossed??? I dunno...just brainstorming here! Hopefully, you'll get a new board back and it'll fire right up and run just as fast as the Road Runner does when he sticks his tongue out at Wylee Coyote and yells "Beep-Beep"............
post #9 of 22
Pity those 2600K's though, killed before they were abused.
Red-rolock
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 4770K Asus Sabertooth Z87 POV GTX 670 8gb (2x4gb) G.Skills RipjawsX 1866 CL9 
Hard DriveHard DriveHard DriveOptical Drive
Samsung Evo Pro 120gb 1TB Western Digital Caviar Black 500GB Seagate Barracuda SATA DVDRW 20x 
CoolingCoolingOSMonitor
Corsair H100i 3 x Phobya Nano LED red fans, 2 x Scythe Kama fans Windows 8.1  LG IPS234V 23' 1920x1080 
MonitorKeyboardPowerCase
AOC LED 1920x1080 Razer BlackWidow XFX PRO 850W XXX edition Corsair Carbide 500R 
MouseMouse PadAudioAudio
Logitech MX518 Steelseries Diablo 3 edition Logitech z323 Logitech G35 
  hide details  
Reply
Red-rolock
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 4770K Asus Sabertooth Z87 POV GTX 670 8gb (2x4gb) G.Skills RipjawsX 1866 CL9 
Hard DriveHard DriveHard DriveOptical Drive
Samsung Evo Pro 120gb 1TB Western Digital Caviar Black 500GB Seagate Barracuda SATA DVDRW 20x 
CoolingCoolingOSMonitor
Corsair H100i 3 x Phobya Nano LED red fans, 2 x Scythe Kama fans Windows 8.1  LG IPS234V 23' 1920x1080 
MonitorKeyboardPowerCase
AOC LED 1920x1080 Razer BlackWidow XFX PRO 850W XXX edition Corsair Carbide 500R 
MouseMouse PadAudioAudio
Logitech MX518 Steelseries Diablo 3 edition Logitech z323 Logitech G35 
  hide details  
Reply
post #10 of 22
How would static have gotten to the chip if it was already seated on the mobo and being used previously? Seriously, this is not a challenge question but a 'is that possible?' question.
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