Overclock.net › Forums › Intel › Intel CPUs › Having problems with my overclock
New Posts  All Forums:Forum Nav:

Having problems with my overclock - Page 2

post #11 of 26
Thread Starter 
Quote:
Originally Posted by kschat;12019653 
Ok good, remember to watch your temps whenever you bump your vcore.



This is a nice tutorial, it will definitely help a lot! I have another one that might help as well. It explains all the aspects of the Nehalem architecture and tells you what everything does:

http://www.maximumpc.com/article/features/ultimate_core_i7_overclocking_guide_we_push_nehalem_its_limits

So far, CoreTemp is reporting idle temps of 42C and high-temps around 73C (This is while Prime95 is running).

How do these temps sound given that I'm running an air-cooled system?
post #12 of 26
Quote:
Originally Posted by MrDoomMaster;12022783 
So far, CoreTemp is reporting idle temps of 42C and high-temps around 73C (This is while Prime95 is running).

How do these temps sound given that I'm running an air-cooled system?

For 1.31 vcore, yeah these temps are really good. The max I let my temps get when running P95 is 85* C.
baby cakes
(13 items)
 
Macbook 4,1
(13 items)
 
 
CPUMotherboardGraphicsRAM
i7 930 [4.01Ghz vCore 1.28125 HT on] GA-X58A-UD3R ZOTAC GTX 460 1GB SLI [840/1680/1900 @stock volts] CORSAIR XMS3 6GB (3 x 2GB) 1600Mhz 
Hard DriveOptical DriveOSMonitor
C300 64GB SATA III, 2x F3 1TB 7200rpm RAID 0 Sony Optiarc 24X DVD/CD Ubuntu 14.04 22" Dell SP2009W 1680x1050 
PowerCase
CORSAIR HX 750W Cooler Master HAF 922 
CPUMotherboardGraphicsRAM
Core 2 Duo 2.4Ghz Penryn T8300 Some logical board GMA X3100 4GB (2x2GB) DDR2 667Mhz 
Hard DriveOptical DriveOSMonitor
Hitachi 160 GB 5400 RPM SATA II Combo drive OSX 10.6.4 (Snow leopard) 13.3" 1280x800 TFT 
PowerCase
Dying battery White macbook case 
  hide details  
Reply
baby cakes
(13 items)
 
Macbook 4,1
(13 items)
 
 
CPUMotherboardGraphicsRAM
i7 930 [4.01Ghz vCore 1.28125 HT on] GA-X58A-UD3R ZOTAC GTX 460 1GB SLI [840/1680/1900 @stock volts] CORSAIR XMS3 6GB (3 x 2GB) 1600Mhz 
Hard DriveOptical DriveOSMonitor
C300 64GB SATA III, 2x F3 1TB 7200rpm RAID 0 Sony Optiarc 24X DVD/CD Ubuntu 14.04 22" Dell SP2009W 1680x1050 
PowerCase
CORSAIR HX 750W Cooler Master HAF 922 
CPUMotherboardGraphicsRAM
Core 2 Duo 2.4Ghz Penryn T8300 Some logical board GMA X3100 4GB (2x2GB) DDR2 667Mhz 
Hard DriveOptical DriveOSMonitor
Hitachi 160 GB 5400 RPM SATA II Combo drive OSX 10.6.4 (Snow leopard) 13.3" 1280x800 TFT 
PowerCase
Dying battery White macbook case 
  hide details  
Reply
post #13 of 26
Thread Starter 
Well I keep getting blue screens and I keep bumping up my VCore by 1 notch. Right now it's a little over 1.26. The last blue screen I had was 0x000000C5 and I'm not sure what that means. Google isn't showing me many results for the C5 stop code.

Any idea what 0xC5 means? Doing a Prime95 blend at a 1.26 VCore is pushing a temperature of over 80C for me right now. If I leave prime running for more than an hour, i think it even goes over 85C. I don't know how much higher I can afford to bump up my VCore with these temps.

Any ideas?
post #14 of 26
Thread Starter 
Quote:
Originally Posted by MrDoomMaster;12153368 
Well I keep getting blue screens and I keep bumping up my VCore by 1 notch. Right now it's a little over 1.26. The last blue screen I had was 0x000000C5 and I'm not sure what that means. Google isn't showing me many results for the C5 stop code.

Any idea what 0xC5 means? Doing a Prime95 blend at a 1.26 VCore is pushing a temperature of over 80C for me right now. If I leave prime running for more than an hour, i think it even goes over 85C. I don't know how much higher I can afford to bump up my VCore with these temps.

Any ideas?

Any info on this guys? I just got another BSoD... this time 0x00000024 (ntfs.sys). I was doing a bunch of downloading when this happened, not sure if it has any relevance to my overclock.
post #15 of 26
Quote:
Originally Posted by MrDoomMaster;12172096 
Any info on this guys? I just got another BSoD... this time 0x00000024 (ntfs.sys). I was doing a bunch of downloading when this happened, not sure if it has any relevance to my overclock.

It's been a while since I've look at your thread, can you post what all your settings are at the moment. 1.26 vcore isn't that much. What is your qpi/vtt? Maybe try reseating your heat sink.
baby cakes
(13 items)
 
Macbook 4,1
(13 items)
 
 
CPUMotherboardGraphicsRAM
i7 930 [4.01Ghz vCore 1.28125 HT on] GA-X58A-UD3R ZOTAC GTX 460 1GB SLI [840/1680/1900 @stock volts] CORSAIR XMS3 6GB (3 x 2GB) 1600Mhz 
Hard DriveOptical DriveOSMonitor
C300 64GB SATA III, 2x F3 1TB 7200rpm RAID 0 Sony Optiarc 24X DVD/CD Ubuntu 14.04 22" Dell SP2009W 1680x1050 
PowerCase
CORSAIR HX 750W Cooler Master HAF 922 
CPUMotherboardGraphicsRAM
Core 2 Duo 2.4Ghz Penryn T8300 Some logical board GMA X3100 4GB (2x2GB) DDR2 667Mhz 
Hard DriveOptical DriveOSMonitor
Hitachi 160 GB 5400 RPM SATA II Combo drive OSX 10.6.4 (Snow leopard) 13.3" 1280x800 TFT 
PowerCase
Dying battery White macbook case 
  hide details  
Reply
baby cakes
(13 items)
 
Macbook 4,1
(13 items)
 
 
CPUMotherboardGraphicsRAM
i7 930 [4.01Ghz vCore 1.28125 HT on] GA-X58A-UD3R ZOTAC GTX 460 1GB SLI [840/1680/1900 @stock volts] CORSAIR XMS3 6GB (3 x 2GB) 1600Mhz 
Hard DriveOptical DriveOSMonitor
C300 64GB SATA III, 2x F3 1TB 7200rpm RAID 0 Sony Optiarc 24X DVD/CD Ubuntu 14.04 22" Dell SP2009W 1680x1050 
PowerCase
CORSAIR HX 750W Cooler Master HAF 922 
CPUMotherboardGraphicsRAM
Core 2 Duo 2.4Ghz Penryn T8300 Some logical board GMA X3100 4GB (2x2GB) DDR2 667Mhz 
Hard DriveOptical DriveOSMonitor
Hitachi 160 GB 5400 RPM SATA II Combo drive OSX 10.6.4 (Snow leopard) 13.3" 1280x800 TFT 
PowerCase
Dying battery White macbook case 
  hide details  
Reply
post #16 of 26
Thread Starter 
Quote:
Originally Posted by kschat;12175329 
It's been a while since I've look at your thread, can you post what all your settings are at the moment. 1.26 vcore isn't that much. What is your qpi/vtt? Maybe try reseating your heat sink.

Have a look at the screenshots on my first post. Everything has remained the same except for my VCore.
post #17 of 26
Thread Starter 
So it seems that I'm still getting the same BSoDs lately. The stop code is 0x00000109, and it says "modification of system code or a critical data structure was detected". It seems like a memory issue at this point.

My CPU VCore has been bumped up to 1.29, and I can't run Prime95 for over 10-15 minutes without temps getting to 85-90C. I need to bump my VCore down a bit since these temps are too high. Upping my vcore isn't a solution anymore. What else can I do?
post #18 of 26
Odd stoppage there Mr... I am pretty much a slave to the same BSOD code lists everyone else is but here's one just for reference:

BSOD Codes
0x101 = increase vcore
0x124 = increase/decrease vcore or QPI/VTT...have to test to see which one it is
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1E = increase vcore
0x3B = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)

At 1.29 getting up in the 90s with a 920 has got me concerned. Are you talking core temps or dye temps? What kind of cooling are you using on your CPU? And then if your dye temp is 85-90 then your individual core temps on a 920 would be in the 100s... at least if my readings are any indication on the 45nm chips. So I'd caution you about overheating. Whether that's the error code or not- 1.29 and 85-90C temps are not good. Not three mile island, yet... but definitely two mile island.

If you're working a 920 with DO stepping at 3.8 I think you're almost out of the ballpark in terms of vcore. No disrespect to anyone's opinion and each chip is different but I'd be surprised if you even needed 1.2... You'd probably shave 10-15C off your temp if you dropped that down to 1.2 and started again. Maybe you hit a 101.. great! Bump it up a notch or two and try again. At least we KNOW what it is!

Also, I noticed your IOH Vcore was at 1.3? I'm no expert but I think IOH is usually 1.10 or so isn't it? I would return that to auto (or 1.10) because believe you me, a 9800GTX doesn't need extra coal. In fact, people with 3 Fermie GTX cards wouldn't have their IOH up that high. (those of you running tri-sli GTX580s excluded wink.gif )

Additionally, I noticed your QPI is actually underclocked. An average number for your QPI Link Data Rate would be about x36... which = ~6400. I wouldn't be surprised if you had that option or something close available to you. Currently at 1.3qpi I would say that is WAY overvolted (stock is 1.2) and probably also generating too much heat.

To add to that I checked out your memory timings and frequency... and I see you adjusted your timings. Now maybe I interpretted your board wrong but if your frequency is 1159 (can't remember exact number)DDR... meaning 555mhz (underclocked)... volted at 1.65 (max basically)... at 7-7-7-20 timings... I'm pretty sure that could be throwing things off as well. On the off chance I've read it wrong, you could be at 2200mhz frequency DDR and giving you that ~1100 memory (overclocked)... with timings that tight there is NO WAY it's going to pan out for you.

Tell you what:

I'm no pro by any stretch and I invite those who know more about it to chime in- but I think you've gone about trying to overclock too many things at once without getting stability along the way. My suggestion to you would be to hit the reset button. Go into your BIOS, restore defaults and start again. Leave your RAM alone and even if we want to skip a step or two (let's say you start with your current bclock and multiplier) and underclock your ram completely. Leave timings on auto and underclock it out of the way... leave it at stock voltage. Drop your vcore in at 1.25 to be safe, and put your qpi at 1.3.. again, to be safe. (1.3 is a good starting spot if you're going to cheat a bit- it's what I use, anyway wink.gif ) Drop in your QPI data rate as 36xbclock, and your uncore at 2x your memory frequency.

For testing, it doesn't hurt to turn off turbo mode and speed step, and all those other usual suspects I'm sure you've read about. Run your prime. With memory out of the way and QPI back where it's easier to predict, we limit ourselves to the error codes we get. 101? Sure... bump up vcore. 124? Okay... qpi... probably going to need to bump it up a notch.


Run your tests... your 4 million hours of prime, 1000 lines of LinX, IBT for whatever it's rating is x 20 to make people happy in here that you're defining stability to their satisfaction... and if you're all good then step your vcore down a bit... and do it all over again. Get a 101? Okay, well you were at your minimum voltage... put it back to where it was and bingo presto. Your CPU is stable. NOW you can go after your RAM. Underclock it a bit, tighten up some timings... test with memtest or whatever- now the error codes you get WILL be memory related and you'll know it.

Right now you've got memory over or underclocked (again, sorry... not with it tonight), timings adjusted and at theoretical max supported voltage (1.65), bclock up around threshold limits that often need further tuning elsewhere, an underrated QPI with too much voltage...

And NOW you have this huge email to read through. Anyway... like I said, someone might step in about the RAM thing- but one way or the other, over or under, it's still screwed.

Hope this helps more than hurts!
Edited by Eno75 - 2/19/11 at 1:52am
DireWolf
(13 items)
 
  
CPUMotherboardGraphicsRAM
980X Asus P6T Deluxe V2 GTX 460 6G Patriot 
Hard DriveOptical DriveOSMonitor
80GB Intel X-25; 1.5TB WD LG DVD Windows 7 Ultimate 64 24T Syncmaster 
PowerCaseMouse
850W Corsair HAF X G500 
  hide details  
Reply
DireWolf
(13 items)
 
  
CPUMotherboardGraphicsRAM
980X Asus P6T Deluxe V2 GTX 460 6G Patriot 
Hard DriveOptical DriveOSMonitor
80GB Intel X-25; 1.5TB WD LG DVD Windows 7 Ultimate 64 24T Syncmaster 
PowerCaseMouse
850W Corsair HAF X G500 
  hide details  
Reply
post #19 of 26
Thread Starter 
Quote:
Originally Posted by Eno75;12443519 
Odd stoppage there Mr... I am pretty much a slave to the same BSOD code lists everyone else is but here's one just for reference:

BSOD Codes
0x101 = increase vcore
0x124 = increase/decrease vcore or QPI/VTT...have to test to see which one it is
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1E = increase vcore
0x3B = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)

At 1.29 getting up in the 90s with a 920 has got me concerned. Are you talking core temps or dye temps? What kind of cooling are you using on your CPU? And then if your dye temp is 85-90 then your individual core temps on a 920 would be in the 100s... at least if my readings are any indication on the 45nm chips. So I'd caution you about overheating. Whether that's the error code or not- 1.29 and 85-90C temps are not good. Not three mile island, yet... but definitely two mile island.
I'm reading temps using the Core Temp program. I don't know what exactly it is reading the temperature from. At 1.25 vcore, I get a max of about 80-83C during prime95, which is way better.
Quote:
Originally Posted by Eno75;12443519 
If you're working a 920 with DO stepping at 3.8 I think you're almost out of the ballpark in terms of vcore. No disrespect to anyone's opinion and each chip is different but I'd be surprised if you even needed 1.2... You'd probably shave 10-15C off your temp if you dropped that down to 1.2 and started again. Maybe you hit a 101.. great! Bump it up a notch or two and try again. At least we KNOW what it is!

Also, I noticed your IOH Vcore was at 1.3? I'm no expert but I think IOH is usually 1.10 or so isn't it? I would return that to auto (or 1.10) because believe you me, a 9800GTX doesn't need extra coal. In fact, people with 3 Fermie GTX cards wouldn't have their IOH up that high. (those of you running tri-sli GTX580s excluded wink.gif )

Additionally, I noticed your QPI is actually underclocked. An average number for your QPI Link Data Rate would be about x36... which = ~6400. I wouldn't be surprised if you had that option or something close available to you. Currently at 1.3qpi I would say that is WAY overvolted (stock is 1.2) and probably also generating too much heat.
What do you mean QPI? I don't see QPI Link Data Rate anywhere. Could you please explain what you are looking at? Also I'm not sure what x36 means... nor do I know what ~6400 is.
Quote:
Originally Posted by Eno75;12443519 
To add to that I checked out your memory timings and frequency... and I see you adjusted your timings. Now maybe I interpretted your board wrong but if your frequency is 1159 (can't remember exact number)DDR... meaning 555mhz (underclocked)... volted at 1.65 (max basically)... at 7-7-7-20 timings... I'm pretty sure that could be throwing things off as well. On the off chance I've read it wrong, you could be at 2200mhz frequency DDR and giving you that ~1100 memory (overclocked)... with timings that tight there is NO WAY it's going to pan out for you.
I tried moving the DIMM Voltage down to 1.60, but that didn't help out much, even though the memtest I ran for about 10 minutes didn't show any errors.

Quote:
Originally Posted by Eno75;12443519 
Tell you what:

I'm no pro by any stretch and I invite those who know more about it to chime in- but I think you've gone about trying to overclock too many things at once without getting stability along the way. My suggestion to you would be to hit the reset button. Go into your BIOS, restore defaults and start again. Leave your RAM alone and even if we want to skip a step or two (let's say you start with your current bclock and multiplier) and underclock your ram completely. Leave timings on auto and underclock it out of the way... leave it at stock voltage. Drop your vcore in at 1.25 to be safe, and put your qpi at 1.3.. again, to be safe. (1.3 is a good starting spot if you're going to cheat a bit- it's what I use, anyway wink.gif ) Drop in your QPI data rate as 36xbclock, and your uncore at 2x your memory frequency.

For testing, it doesn't hurt to turn off turbo mode and speed step, and all those other usual suspects I'm sure you've read about. Run your prime. With memory out of the way and QPI back where it's easier to predict, we limit ourselves to the error codes we get. 101? Sure... bump up vcore. 124? Okay... qpi... probably going to need to bump it up a notch.


Run your tests... your 4 million hours of prime, 1000 lines of LinX, IBT for whatever it's rating is x 20 to make people happy in here that you're defining stability to their satisfaction... and if you're all good then step your vcore down a bit... and do it all over again. Get a 101? Okay, well you were at your minimum voltage... put it back to where it was and bingo presto. Your CPU is stable. NOW you can go after your RAM. Underclock it a bit, tighten up some timings... test with memtest or whatever- now the error codes you get WILL be memory related and you'll know it.

Right now you've got memory over or underclocked (again, sorry... not with it tonight), timings adjusted and at theoretical max supported voltage (1.65), bclock up around threshold limits that often need further tuning elsewhere, an underrated QPI with too much voltage...

And NOW you have this huge email to read through. Anyway... like I said, someone might step in about the RAM thing- but one way or the other, over or under, it's still screwed.

Hope this helps more than hurts!

Here's the problem. First of all, I'm impatient. I don't want to be spending over a week messing with an overclock. I was hoping it would be easy, but it's actually very frustrating. I honestly have no idea how to overclock. I am going to do some searching later, but I hope there is a step by step tutorial that shows a good process for overclocking and how to adjust values.

Another issue is the damaging effect of overclocking on my OS. If I decide to start over, I don't want my installation of Windows 7 getting wrecked due to memory/CPU instability.

Also, how long do people typically run prime95? I expect that you slighly increment/decrement values and then test. You repeat this process. However, this process could be very slowed down if you have to run prime95 for 24 hours each pass.

As far as stress testing goes, I only have been using memtest & prime95. Is that sufficient or is there more I can use?

My memory timings, as advertised, are 9-9-9-24. I was told earlier on by someone on the forum to try 7-7-7-20. What would you recommend? Do you know of any good overclocking tutorials?
post #20 of 26
Quote:
Originally Posted by MrDoomMaster;12012178 
Hello everyone,

I'm having stability issues with my overclock. I'm not very knowledgeable with the terms & acronyms in the BIOS, especially for voltage control, so I really don't know what each value does. I'm not sure how to adjust my overclock to make it more stable. Up until now I've relied mostly on suggestions from other knowledgeable people.

I've attached screenshots of my various BIOS configuration pages. Based on the values in those images, is there anything I can change to make my system slightly more stable?

Occasionally I will get BSoD's. Also my RAID will lose data and have to rebuild itself sometimes, especially after a BSoD crash. Prime95 and other stress tests work fine, so I'm not sure where the instability is coming from. Anyway, if someone could just have a look over my BIOS configuration and point out anything that could be adjusted for overall improvement, I'm sure that'll have an affect on things!

Thanks in advance.

Your IOH Vcore seems high... what does your board default too...? 1.1v..??
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 2600k @ 4.6ghz HT 1.272v GIGABYTE P67A-UD4-B3 Sapphire HD5870 1GB G.Skill Ripjaws DDR3 1600 (2x2) 
Hard DriveOSMonitorKeyboard
X2 Western Digital Black Sata 500GB (RAID 0) Win7 Ult x64 ASUS 24'in VW246H Logitech 
PowerCaseMouse
Zalman ZM1000-HP CM Storm Scout Logitech 
  hide details  
Reply
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 2600k @ 4.6ghz HT 1.272v GIGABYTE P67A-UD4-B3 Sapphire HD5870 1GB G.Skill Ripjaws DDR3 1600 (2x2) 
Hard DriveOSMonitorKeyboard
X2 Western Digital Black Sata 500GB (RAID 0) Win7 Ult x64 ASUS 24'in VW246H Logitech 
PowerCaseMouse
Zalman ZM1000-HP CM Storm Scout Logitech 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › Having problems with my overclock