Overclock.net › Forums › Intel › Intel CPUs › Damn it's this situation again... CPU is stable with 12 hours of Prime95 but sometimes crashes when gaming @_@
New Posts  All Forums:Forum Nav:

Damn it's this situation again... CPU is stable with 12 hours of Prime95 but sometimes crashes when gaming @_@

post #1 of 15
Thread Starter 
Hey I'm just wondering if anyone can help me with something about my overclock that's got me a bit confused... My CPU can pass 12 hour blend tests on Prime95 and has been running fine for weeks. I had one occasion though a few weeks back where Portal 2 made the computer lockup and I got a blue screen saying something about a clock interrupt not being recieved or something like that. It's the same blue screen I kept seeing during the process of getting my overclock stable, or at least what I thought was stable... So i bumped up the Vcore one increment on the offset voltage and have been usng the computer without any apparent problems since. Today I was playing BF3 for about 45 minutes and then suddenly the computer just locked up and I got that blue screen with the clock interrupt message again. I don't get it, I can pass 12 hours on Prime95 and use the computer for all sorts of things (including playing games) without seeing any problems, but on rare occasions playing a game can cause this... I am using offset voltage with C1E enabled and with C3 & C6 disabled btw, as recommended in overclocking guides. Anyone got any ideas what it could be? It seems like it's hard for me to try different things and test to see if it's fixed as it only happens on rare occasions when playing a game. Thanks for any help thumb.gif

Edits:

Up until now I had only been running stress tests in Prime95 without changing the amount RAM that was used. I tried a 1792 FFT test with 90% RAM usage and it fails within seconds. I also got a 0x00000101 blue screen which apparently means more Vcore is needed.
Edited by ET900 - 4/25/12 at 1:30pm
post #2 of 15
What BSOD code(s) are you recieving when it crashes?

Also are you using any load line calibration (LLC)? If you are then lowering this and upping your vcore a bit may help. Hard to say though without a BSOD code.
Tevatron K
(15 items)
 
 
CPUMotherboardGraphicsRAM
2600K @ 4.8ghz Z77 Sabertooth R9 290 8GB Samsung 30nm @ 1866mhz 
Hard DriveHard DriveOptical DriveCooling
M500 240GB SSD 3x 3TB HDD's Sony DRU-V200S Custom water cooling 
OSMonitorKeyboardPower
Windows 7 64bit QNIX 27" 1440p @ 96Hz Ducky 1008 BeQuiet 1200w 
CaseMouseMouse Pad
HAF 932 Logitec G5 Table top 
  hide details  
Reply
Tevatron K
(15 items)
 
 
CPUMotherboardGraphicsRAM
2600K @ 4.8ghz Z77 Sabertooth R9 290 8GB Samsung 30nm @ 1866mhz 
Hard DriveHard DriveOptical DriveCooling
M500 240GB SSD 3x 3TB HDD's Sony DRU-V200S Custom water cooling 
OSMonitorKeyboardPower
Windows 7 64bit QNIX 27" 1440p @ 96Hz Ducky 1008 BeQuiet 1200w 
CaseMouseMouse Pad
HAF 932 Logitec G5 Table top 
  hide details  
Reply
post #3 of 15
Increase CPU voltage to 1.35v use it for a few days and see if it still happens. That is still a very safe voltage, no need to worry. I ran mine at 1.46v-1/47v for over a year with no problems.
    
CPUMotherboardGraphicsRAM
3930k 4.7 1.368v RIVE BIOS 2105 680L 1330/7011 16GB Samsung 2133Mhz  
Hard DriveCoolingOSMonitor
Crucial M4 240GB  H110 after 4x H220 RMA Win 8.1 64bit XL2420T Lightboost  
KeyboardPowerCaseMouse
SS 6Gv2  EVGA 1300G2  Arc Midi R2 Zowie AM, many opticals 
Mouse PadAudioAudioAudio
SS QCK+ Xonar Essence STX AK100 MKII Shure SE846  
AudioAudioOther
Ultrasone Pro 900 Sennheiser HD700 Intel EXPI9301CT NIC 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
3930k 4.7 1.368v RIVE BIOS 2105 680L 1330/7011 16GB Samsung 2133Mhz  
Hard DriveCoolingOSMonitor
Crucial M4 240GB  H110 after 4x H220 RMA Win 8.1 64bit XL2420T Lightboost  
KeyboardPowerCaseMouse
SS 6Gv2  EVGA 1300G2  Arc Midi R2 Zowie AM, many opticals 
Mouse PadAudioAudioAudio
SS QCK+ Xonar Essence STX AK100 MKII Shure SE846  
AudioAudioOther
Ultrasone Pro 900 Sennheiser HD700 Intel EXPI9301CT NIC 
  hide details  
Reply
post #4 of 15
I'm completely stable for 24/7 F@H or Rendering, however very, very, occasionally I'll get a BSOD with a code of 124, indicating more Vcore.
Swag box m8
(13 items)
 
7 x BL460c
(6 items)
 
 
CPUMotherboardGraphicsRAM
2500K Asus P8P67 Sapphire HD 5770 2x8GB Corsair 1333MHz 
Hard DriveMonitorMonitorPower
Corsair Force 3 120GB Aoc F22S+ Aoc F22S+ Powercool 850W 80+ 
Case
NZXT Phantom 
CPUCPUMotherboardRAM
Xeon E5520  Xeon E5520  BL460c G6 12GB ECC DDR3 
Hard DriveOS
1TB of SAN Server 2008 R2 
  hide details  
Reply
Swag box m8
(13 items)
 
7 x BL460c
(6 items)
 
 
CPUMotherboardGraphicsRAM
2500K Asus P8P67 Sapphire HD 5770 2x8GB Corsair 1333MHz 
Hard DriveMonitorMonitorPower
Corsair Force 3 120GB Aoc F22S+ Aoc F22S+ Powercool 850W 80+ 
Case
NZXT Phantom 
CPUCPUMotherboardRAM
Xeon E5520  Xeon E5520  BL460c G6 12GB ECC DDR3 
Hard DriveOS
1TB of SAN Server 2008 R2 
  hide details  
Reply
post #5 of 15
Try custom FFTs of 1344 and 1792, lots of sandy bridges have the most trouble with those.

I would also do 20 passes of IntelBurnTest. It WILL get hot, keep it below 85C and you'll be fine. 20 passes is like 1 1/2 hours or so. If it passes all this then the next think would be 5-10 passes of memtest.

If all that passes, then it could be the GPU that's the problem... or something else. I would see if it still happens at stock.
The Leviathan
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 6700k @ 4.7GHz MSI Z170A Gaming M7 12GB NVIDIA Titan X (Pascal) 32GB G.Skill Ripjaws V (DDR4 3200) 
Hard DriveHard DriveCoolingCooling
2x 1TB Samsung 960 PRO 193TB unRAID Server 3x 140mm Noctua NF-A14 Noctua NH-D15 
OSMonitorKeyboardPower
Windows 10 Pro x64 65" LG 65E6P (4K OLED) Ducky DK9008 Shine 3  Corsair AX860 
CaseMouseAudioAudio
Corsair Obsidian 750D Logitech G502 Proteus Sprectrum Denon X7200WA (Receiver) 2x Klipsch RF-7 (Front Speakers) 
AudioAudioAudioAudio
4x Klipsch RS-62 (Surround Speakers) Klipsch RC-64 (Center Speaker) 4x Klipsch CDT-5800-C II (Atmos Speakers) 2x SVS PB16-Ultra (Subwoofers) 
  hide details  
Reply
The Leviathan
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 6700k @ 4.7GHz MSI Z170A Gaming M7 12GB NVIDIA Titan X (Pascal) 32GB G.Skill Ripjaws V (DDR4 3200) 
Hard DriveHard DriveCoolingCooling
2x 1TB Samsung 960 PRO 193TB unRAID Server 3x 140mm Noctua NF-A14 Noctua NH-D15 
OSMonitorKeyboardPower
Windows 10 Pro x64 65" LG 65E6P (4K OLED) Ducky DK9008 Shine 3  Corsair AX860 
CaseMouseAudioAudio
Corsair Obsidian 750D Logitech G502 Proteus Sprectrum Denon X7200WA (Receiver) 2x Klipsch RF-7 (Front Speakers) 
AudioAudioAudioAudio
4x Klipsch RS-62 (Surround Speakers) Klipsch RC-64 (Center Speaker) 4x Klipsch CDT-5800-C II (Atmos Speakers) 2x SVS PB16-Ultra (Subwoofers) 
  hide details  
Reply
post #6 of 15
Thread Starter 
Quote:
Originally Posted by Jokah View Post

What BSOD code(s) are you recieving when it crashes?
Also are you using any load line calibration (LLC)? If you are then lowering this and upping your vcore a bit may help. Hard to say though without a BSOD code.

I don't know what the code is but I will take note next time! I've had this overclock for a couple months at least and I've only had these 2 blue screens in that time so it may be a while until I get another! I am using LLC on High with offset voltage -0.035. Idle is a little under 1v. Also I have just tried enabling Spread Spectrum as I've heard it can sometimes stablize overclocks. It doesn't seem to really mess with the Bclk for me so I thought it was worth a go. Also I have noticed that it's stopped the Vcore fluctuating so much under load.
Quote:
Originally Posted by Scorpion667 View Post

Increase CPU voltage to 1.35v use it for a few days and see if it still happens. That is still a very safe voltage, no need to worry. I ran mine at 1.46v-1/47v for over a year with no problems.

That wouldn't be such a bad idea to try but unfortunately a few days of testing just isn't going to be enough. I think I'd have to test for a few months because these blue screens are rare. It is still possible though that it could be because the Vcore is to low so I will keep this in mind and maybe try upping the Vcore a little each time it happens and see if it eventually goes away...
Quote:
Originally Posted by overclocker23578 View Post

I'm completely stable for 24/7 F@H or Rendering, however very, very, occasionally I'll get a BSOD with a code of 124, indicating more Vcore.

I really need to see if that's the code I'm getting. All I know is it said something about a clock interrupt not being recieved from a secondary processor or something along those lines. It could just be that more Vcore is needed though. Hopefully it's that simple!
Quote:
Originally Posted by Murlocke View Post

Try custom FFTs of 1344 and 1792, lots of sandy bridges have the most trouble with those.
I would also do 20 passes of IntelBurnTest. It WILL get hot, keep it below 85C and you'll be fine. 20 passes is like 1 1/2 hours or so. If it passes all this then the next think would be 5-10 passes of memtest.
If all that passes, then it could be the GPU that's the problem... or something else. I would see if it still happens at stock.

I do those exact custom FFT's before I go for the 12 hour blend test. I do 1344-1344 for 25 minutes then 1792-1792 for 25 minutes. Is that what you're talking about? I guess I could give IBT another go as I just stick to using Prime these days. I guess memtest might be another thing to try to. I used to use LinX and IBT but I found that I could pass those and still get errors on Prime95 so I just stuck to Prime95...


Thanks for all the replies so far people smile.gif
post #7 of 15
Try here:

http://www.overclock.net/t/1120291/solving-fixing-bsod-124-on-sandybridge-read-op-first

Look for "random BSOD" in the middle of the page, but the whole thread has lots to search.
Edited by samwiches - 4/24/12 at 9:00pm
COMPUTER
(16 items)
 
  
CPUMotherboardGraphicsRAM
3570K Gigabyte GA-Z77X-UD3H Gigabyte GTX 670 Windforce OC 2GB Samsung 30nm 
Hard DriveHard DriveCoolingOS
WD Caviar Blue WD Caviar Black NZXT Havik 140 Windows 7 64bit 
OSMonitorKeyboardPower
Windows 8 64bit ASUS GD235HZ (GD245HQ) 120Hz Dell OCZ GameXStream 850W 
CaseMouseMouse PadAudio
Corsair Carbide 300R Logitech G9 naked Allsop Black Cloth (low profile) Logitech G35 Surround 
  hide details  
Reply
COMPUTER
(16 items)
 
  
CPUMotherboardGraphicsRAM
3570K Gigabyte GA-Z77X-UD3H Gigabyte GTX 670 Windforce OC 2GB Samsung 30nm 
Hard DriveHard DriveCoolingOS
WD Caviar Blue WD Caviar Black NZXT Havik 140 Windows 7 64bit 
OSMonitorKeyboardPower
Windows 8 64bit ASUS GD235HZ (GD245HQ) 120Hz Dell OCZ GameXStream 850W 
CaseMouseMouse PadAudio
Corsair Carbide 300R Logitech G9 naked Allsop Black Cloth (low profile) Logitech G35 Surround 
  hide details  
Reply
post #8 of 15
Thread Starter 
Quote:
Originally Posted by samwiches View Post

Try here:
http://www.overclock.net/t/1120291/solving-fixing-bsod-124-on-sandybridge-read-op-first
Look for "random BSOD" in the middle of the page, but the whole thread has lots to search.

Yeh the Sandy Stable Club is a great place for info. I used munaim1's overclocking guide from there. I was also reading through that section you linked the other day but I don't think it quite relates to my problem, at least not when I don't actually know if it's a BSOD 124. But I have been thinking that the VCCIO and/or PLL might need a bit of tweaking. I am running them on Auto, but when I had a 4.1Ghz OC on my last board I felt that putting the VCCIO up to 1.1v helped me get a bit further in a blend test, then I had to increase the Vcore a little just to finish it off. Next time I get a blue screen I'm gonna take note of the code and see if I can find out what it suggests and then probably end up going ahead with trying to up the VCCIO first. Thanks.
post #9 of 15
many short benches > 1 long bench

i can run several 3dmark 2011 passes and older 3dmarks at 4.0 1.47, everything fine, then i launch crysis2 some minutes and BSOD

same for other games, benchs, etc
pote reload
(14 items)
 
  
CPUMotherboardGraphicsRAM
intel 3570k@4.4@1.25 gigabyte z77z-ud3h gigabyte gtx460 768mb oc 850/2100 8gb ddr3 1600 corair vengeance blue 
Hard DriveOptical DriveCoolingOS
samsung 500gb hd502hj, 2x crucial m4 64gb raid 0 sony optiarc 24x hyper 212+ win8 x64 
MonitorPowerCaseMouse
envision lcd wide 19 + lg tv lcds 32" 32ld330 1... corsair vx 550w cheapo steelseries ikari laser 
  hide details  
Reply
pote reload
(14 items)
 
  
CPUMotherboardGraphicsRAM
intel 3570k@4.4@1.25 gigabyte z77z-ud3h gigabyte gtx460 768mb oc 850/2100 8gb ddr3 1600 corair vengeance blue 
Hard DriveOptical DriveCoolingOS
samsung 500gb hd502hj, 2x crucial m4 64gb raid 0 sony optiarc 24x hyper 212+ win8 x64 
MonitorPowerCaseMouse
envision lcd wide 19 + lg tv lcds 32" 32ld330 1... corsair vx 550w cheapo steelseries ikari laser 
  hide details  
Reply
post #10 of 15
Thread Starter 
Hey guys I'm trying to get help over at the sandy stable club as well as here so I thought I would copy+paste my most recent post from there into this thread instead of re-writing it slightly different or whatever. Sorry if you read the posts from there also and get deja vu lol...

I just managed to make my computer Blue Screen again doing the custom 1792 FFT test with 90% RAM usage. It failed within seconds. Passed a 12 hour standard blend test with these settings though which made me laugh! Anyways the thing I haven't been doing, which I will now always do when stress testing is have a really heavy RAM usage. Which leads me to my next point - Since it passed a 12 hour standard blend test but failed the custom 1792 test with really high RAM usage, does that indicate that it's more likely to be my RAM that is instable than the CPU? But also, the Blue Screen code is: 0x00000101 which means more Vcore is needed, right? Hope someone can help me solve this! I'm glad that I at least managed to create a Blue Screen error again without having to wait weeks smile.gif
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
  • Damn it's this situation again... CPU is stable with 12 hours of Prime95 but sometimes crashes when gaming @_@
Overclock.net › Forums › Intel › Intel CPUs › Damn it's this situation again... CPU is stable with 12 hours of Prime95 but sometimes crashes when gaming @_@