Overclock.net › Forums › Intel › Intel CPUs › Core i7-2600k BSOD
New Posts  All Forums:Forum Nav:

Core i7-2600k BSOD

post #1 of 11
Thread Starter 
Hello fellow computer enthusiasts, my current setup is the following:

CPU: Core i7-2600k (OC 4.5 Ghz)
RAM: Corsair CMX8GX3M2A1600C9 XMS3 8GB DDR3
Motherboard: Gigabyte Z68-UD4-B3
GPU: Sapphire ATI Radeon 5850 HD
HDD: 2x Seagate 1 TB 7200rpm
Cooling: 4x 120mm 1x 200mm
Heatsink: Thermaltake Frio
Case: Thermaltake Armor A90
PSU: Ultra LSP750 750-Watt

That being said all parts except the cpu and motherboard existed in previous build with AMD X6 1055T at the core. Now to the details... I have tested everything and stressed everything to its max pretty much trying to isolate the problem but it never seems to fail under any stress test, quite the opposite. Also the ram passes the latest memtest 100%. But during game play, say battlefield: bad company 2 it will BSOD after about 10-20mins and return 0124 error "Uncorrectable hardware error". Not sure what is causing this, i do not want to have RMA the board or cpu because i believe from stress test alone they are fine. I have read reviews that certain memory speeds/timing are not compatible or finicky with the sandy bridge, i have lowered the timing and speed to suggest by the board manuf for the ram, still no go. Do you suggest purchasing one of the QVL ram setups suggest by Gigabyte? Or what do y'all think the problem could be? On another note it still persists with BSOD even if the cpu isn't overclocked.

If temps are a concern, during stress test the cpu max at about 56 Celsius even lower during game play. Gpu temps under stress max about 70 celcius even lower during game play 38 Celsius. Cooling is not an issue.

Thank you for all your help!
Edited by Rezidude - 5/26/11 at 3:18pm
post #2 of 11
Not trying to be rude or anything but this like the millionth post today about the same exact problem. Same CPU and same mobo lol.

Up your volts, put LLC @ 75% (what ever they call it on your mobo) and if that doesn't work up your VCCIO to 1.075-1.100v
post #3 of 11
Thread Starter 
Okay thank you very much hirolla, my fault for not fully investigating the board throughly.
post #4 of 11
hirolla888

You think it's bad stock BIOS using too low of voltages? Or do you think it's just crappy power components?
Sheep Prodigy
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7-960 4.3 ghz Gigabyte GA-EX58-UD4P AMD HD 6970 2GB GDDR5 2x4GB DDR3 1333 mhz 
Hard DriveOptical DriveOSMonitor
Samsung Spinpoint F3 1TB DVD/DW +- RW/ Bluray W7 64 bit 21.5" e-IPS U2211H 
KeyboardPowerCaseMouse
Dynex cheapie Antec TP-550W Corsair Obsidian 650D Logitech G500 
Mouse Pad
google o.o 
  hide details  
Reply
Sheep Prodigy
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7-960 4.3 ghz Gigabyte GA-EX58-UD4P AMD HD 6970 2GB GDDR5 2x4GB DDR3 1333 mhz 
Hard DriveOptical DriveOSMonitor
Samsung Spinpoint F3 1TB DVD/DW +- RW/ Bluray W7 64 bit 21.5" e-IPS U2211H 
KeyboardPowerCaseMouse
Dynex cheapie Antec TP-550W Corsair Obsidian 650D Logitech G500 
Mouse Pad
google o.o 
  hide details  
Reply
post #5 of 11
Quote:
Originally Posted by AsAnAtheist View Post
hirolla888

You think it's bad stock BIOS using too low of voltages? Or do you think it's just crappy power components?
Honestly I don't know why this is such a common problem

Gigabyte make really good boards so I doubt it's crappy components. The problem seems to only occur with the 2600k, so maybe hyper threading has something to do with it.
post #6 of 11
0x124 is usually a problem with the CPU->IMC transactions, rather than the cpu cores themselves freezing up (core crashes are 0x101). Can also be caused by the IMC. 0x1E's can happen from that too. This can be caused by multiple things.

He can't use LLC 75% because that is ONLY on the Asus M4E. Gigabyte doesn't have %'s.

Set the BIOS to 1.25v and turn on LLC.
If you still get 124's, then the problem is strictly the RAM. You either need proper RAM (Gskill Ripjaws PC3 12800's 1.5v are a good start), or you need to manually change the RAM settings with your non certified RAM. What to change? I don't know. You can start by raising VTT to 1.2v, changing command rate to 2T, forcing the RAM down to 1333 mhz...bumping VCCSA up to 1.0v...I honestly don't know...
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 #7 of 11
Thread Starter 
Well after trying all the above, i think combination of the suggested tweaked it to the perfect setting, have not BSOD at all during any stress test (never did before) and it is now no longer BSOD during any gameplay. Thank you all for your help!
post #8 of 11
Thread Starter 
So as problem persisted a day later, i tried everything from stock settings with no hyper threading to the unthinkable. Then with a little more research on different forum board, came to found that it was dealing with big conflict between a recent punk buster update the gigabyte utilities! Who would have thought. Ever since i have removed the gigabytes utilities have zero crashes.
post #9 of 11
Quote:
Originally Posted by Rezidude View Post
So as problem persisted a day later, i tried everything from stock settings with no hyper threading to the unthinkable. Then with a little more research on different forum board, came to found that it was dealing with big conflict between a recent punk buster update the gigabyte utilities! Who would have thought. Ever since i have removed the gigabytes utilities have zero crashes.
This might have worked for me just now. Spend about 3 days loading and unloading drivers, swapping out hardware, tweaking things, and nothing would get me past 10-15 minutes in a game. Just did this and played about 2 hours straight on 100% default bios settings *knock on wood*.

Thanks :0
post #10 of 11
Do you have EasyTune installed? I had this exact same problem until I uninstalled it, haven't had the problem again since.

Edit: Oh, wait, someone already said that.
Edited by SafeKlok - 7/4/11 at 7:31am
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › Core i7-2600k BSOD