Overclock.net › Forums › Intel › Intel CPUs › Computer failing to POST at OC settings after 4.5 years of success?
New Posts  All Forums:Forum Nav:

Computer failing to POST at OC settings after 4.5 years of success?

post #1 of 13
Thread Starter 
So my custom built system is more then 4.5 years old now. When I first got it I instantly overclocked the Q6600 g0 step processor from 2.4 ghz to 3.0 ghz and didn't even have to change the voltage ( left it at the stock 1.28?? something V. and got average temps ) Everything worked fine for 4.5 long years until now. I had upgraded from windows xp to windows 7 ( don't know if this is relevant since it worked fine in windows 7 for a week ) but now my computer refuses to POST at 3.0 ghz and will reset to 2.4 ghz stock settings. Sometimes I'll get lucky and one day it can POST at 3.0 ghz but for the most part it keeps rebooting and reverting to stock settings. My question is there anything in particular that could have caused this? Did something get old inside? The PSU? Should I be worried? Maybe try to bump up the voltage to get a successful POST? If so by how much? Any feedback is much appreciated!

PS: The weather actually got colder so I don't think high temperature can be an issue, especially during bootup.

My system stats:

Q6600 g0 running at stock 1.28??V voltage, used to be able to POST at 3.0 ghz but now can only POST at 2.4 ghz
Gigabyte- P-35-DS3R mobo
4 gigs of OCZ ram at 0.4+ V voltage
GTX 460 764mb running at stock settings
Windows 7 64 bit
Tuniq tower 120 HSF
Thermaltake armor computer case
Edited by Gabb - 11/3/11 at 2:42pm
post #2 of 13
Chances are if you left the voltage stock (auto setting) it has been overvolting your cpu. Four and a half years of overvolting would result in some degradation depending on how much voltage was put through the chip. Does it work on stock settings?
Edited by evilDSM - 11/3/11 at 2:26pm
post #3 of 13
Why not just up the voltage so its stable again? Sorry I know that doesn't answer why but a suggestion none the less.
Rig
(13 items)
 
  
CPUMotherboardGraphicsRAM
Phenom II x4 820 (L3 Cache Unlocked) 3.625Ghz Asus M4A89GTD Pro/USB3 HIS 6950 2GB Unlocked 840/1325 1.1v 4GB Corsair XMS2 CL9 1333 
Hard DriveOptical DriveOSMonitor
OCZ Vertex 2 50GB 640GB WD Black/500GB WD Samsung DVD Burner x24 Windows 7 Ultimate x64 3x Samsung SyncMaster E2320x Eyefinity - 6048x1080 
PowerCase
OCZ ModXStream Pro 600W Cooler Master 310 Mid Case 
  hide details  
Reply
Rig
(13 items)
 
  
CPUMotherboardGraphicsRAM
Phenom II x4 820 (L3 Cache Unlocked) 3.625Ghz Asus M4A89GTD Pro/USB3 HIS 6950 2GB Unlocked 840/1325 1.1v 4GB Corsair XMS2 CL9 1333 
Hard DriveOptical DriveOSMonitor
OCZ Vertex 2 50GB 640GB WD Black/500GB WD Samsung DVD Burner x24 Windows 7 Ultimate x64 3x Samsung SyncMaster E2320x Eyefinity - 6048x1080 
PowerCase
OCZ ModXStream Pro 600W Cooler Master 310 Mid Case 
  hide details  
Reply
post #4 of 13
it is starting to seem like Intels just don't last when OCed I have heard plenty of people having issues with i7-920s and some i5s dying. yet I have not seen anybody with AMDs dying after being OCed for a while. but most the time it is because they ran with way too high Vcore voltages. if you were running stock and temps were kept at safe levels it is probably not core degradation. and plus that wouldn't happen suddenly. do you mean that you are running .4v above stock on ram voltage or 0.4v because neither of those make sense if you are running at 0.4v above stock I would say that it is your ram causing these issues.
Sandy Thunder
(18 items)
 
QuickSilver X1
(15 items)
 
 
CPUMotherboardGraphicsRAM
i7-3930k C1 4.6GHz @1.344v Sabertooth X79 2x EVGA GTX 560 Ti SC SLI 900/2106 Dominator 1866 16GB 9-10-9-27 
Hard DriveHard DriveCoolingOS
Crucial M4 64GB 'Cuda 320GB XSPC Rasa 750 RX240 push/pull + Alphacool UT60 ... Win 7 Pro x64 
MonitorMonitorMonitorKeyboard
Asus VE198D 19" Samsung 920NW 19" Samsung 906BW 19" Logitech G510s 
PowerCaseMouseMouse Pad
Corsair HX850M Carbide 400R Cyborg M.M.O. 7 Corsair MM200 
AudioOther
Bose Music Monitor Nuforce Icon HDP 
CPUMotherboardGraphicsRAM
Phenom II x6 1090T BE Sabertooth 990FX Radeon HD 5770 1GB Corsair Veangence Blue 
Hard DriveOptical DriveCoolingOS
WD Caviar Black 1TB  Lite ON 16x DVD-R/RW ThermalRight Silver Arrow Windows 7 Professional 64 bit 
MonitorKeyboardPowerCase
Syncmaster 921BW 19" & Syncmaster 965 19" and S... Apple aluminum wired keyboard Corsair TX650 Silverstone TJ05 with window and thermal contro... 
MouseMouse PadAudio
logitech mx air None Monsoon MM-700 
  hide details  
Reply
Sandy Thunder
(18 items)
 
QuickSilver X1
(15 items)
 
 
CPUMotherboardGraphicsRAM
i7-3930k C1 4.6GHz @1.344v Sabertooth X79 2x EVGA GTX 560 Ti SC SLI 900/2106 Dominator 1866 16GB 9-10-9-27 
Hard DriveHard DriveCoolingOS
Crucial M4 64GB 'Cuda 320GB XSPC Rasa 750 RX240 push/pull + Alphacool UT60 ... Win 7 Pro x64 
MonitorMonitorMonitorKeyboard
Asus VE198D 19" Samsung 920NW 19" Samsung 906BW 19" Logitech G510s 
PowerCaseMouseMouse Pad
Corsair HX850M Carbide 400R Cyborg M.M.O. 7 Corsair MM200 
AudioOther
Bose Music Monitor Nuforce Icon HDP 
CPUMotherboardGraphicsRAM
Phenom II x6 1090T BE Sabertooth 990FX Radeon HD 5770 1GB Corsair Veangence Blue 
Hard DriveOptical DriveCoolingOS
WD Caviar Black 1TB  Lite ON 16x DVD-R/RW ThermalRight Silver Arrow Windows 7 Professional 64 bit 
MonitorKeyboardPowerCase
Syncmaster 921BW 19" & Syncmaster 965 19" and S... Apple aluminum wired keyboard Corsair TX650 Silverstone TJ05 with window and thermal contro... 
MouseMouse PadAudio
logitech mx air None Monsoon MM-700 
  hide details  
Reply
post #5 of 13
Test the cpu in another system. Try and get it to post at 3.0. If it does the same thing as the system it is currently in you know what the problem is. If not start the process of elmination.
My pc
(16 items)
 
  
CPUMotherboardGraphicsGraphics
i5 2500k@4.7ghz Biostar tp67xe 7850 1050/1250mhz gt520 1010 /2020mhz 1040mhz 
RAMHard DriveOptical DriveCooling
ddr3 1600mhz mushkin redline 500g seagate,500g wd, 640g wd, in raid 1 lg 22x optical drive h60 push/pull 
OSPowerCaseAudio
win7 home premium tr2 rx-850w cm 690 Sound Blaster X-Fi Titanium 
  hide details  
Reply
My pc
(16 items)
 
  
CPUMotherboardGraphicsGraphics
i5 2500k@4.7ghz Biostar tp67xe 7850 1050/1250mhz gt520 1010 /2020mhz 1040mhz 
RAMHard DriveOptical DriveCooling
ddr3 1600mhz mushkin redline 500g seagate,500g wd, 640g wd, in raid 1 lg 22x optical drive h60 push/pull 
OSPowerCaseAudio
win7 home premium tr2 rx-850w cm 690 Sound Blaster X-Fi Titanium 
  hide details  
Reply
post #6 of 13
Thread Starter 
Sorry some clarification I meant:
Q6600 g0 running at stock 1.28??V voltage, used to be able to POST at 3.0 ghz but now can only POST at 2.4 ghz
with
4 gigs of OCZ ram at 0.4+ V voltage

if I do up the voltage how much should I up it by? I literally have no idea, all I know is V.1.55 will kill any processor
post #7 of 13
Quote:
Originally Posted by Gabb View Post
Sorry some clarification I meant:
Q6600 g0 running at stock 1.28??V voltage, used to be able to POST at 3.0 ghz but now can only POST at 2.4 ghz
with
4 gigs of OCZ ram at 0.4+ V voltage

if I do up the voltage how much should I up it by? I literally have no idea, all I know is V.1.55 will kill any processor
The thing is when you say stock did you manually set that voltage to 1.28v or did you not touch the voltage setting which is set on auto by default i think. If i were to overclock my processor to lets say 1.0GHz over stock and didn't manually set my voltage it would give it the voltage it thinks it needs to be stable. In a lot of cases this would be a lot more than needed. When you apply voltage go in small increments. try 1.300v and make sure you monitor your temps!
post #8 of 13
Thread Starter 
Quote:
Originally Posted by evilDSM View Post
The thing is when you say stock did you manually set that voltage to 1.28v or did you not touch the voltage setting which is set on auto by default i think. If i were to overclock my processor to lets say 1.0GHz over stock and didn't manually set my voltage it would give it the voltage it thinks it needs to be stable. In a lot of cases this would be a lot more than needed. When you apply voltage go in small increments. try 1.300v and make sure you monitor your temps!
I did not touch the voltage and my mobo stock voltage setting is at 1.28v. I know this is the stock voltage setting because it does not change when I change the FSB to 266 or 333 so I know the voltage is not set at auto adjust but is left at stock 1.28v, otherwise if it was auto it would adjust when I change the FSB. I'll try going up to 1.30 V and see if that's good. Whats the highest I should go up too? Is 1.40 V dangerous for the processor? 1.55 V is the kill factor right?
post #9 of 13
Quote:
Originally Posted by Gabb View Post
I did not touch the voltage and my mobo stock voltage setting is at 1.28v. I know this is the stock voltage setting because it does not change when I change the FSB to 266 or 333 so I know the voltage is not set at auto adjust but is left at stock 1.28v, otherwise if it was auto it would adjust when I change the FSB. I'll try going up to 1.30 V and see if that's good. Whats the highest I should go up too? Is 1.40 V dangerous for the processor? 1.55 V is the kill factor right?
Okay in that case then it probably did not over volt it. As for safe voltage it all depends what people think safe is. Here is what I could dig up.

Quote:
The recommended maximum voltage threshold is 1.372v. Note, the 62c threshold is for CPUs operating at stock FSB and under the voltage threshold, for an overclocked Q6600, it is recommended to keep the temps under 55c.
post #10 of 13
Thread Starter 
Quote:
Originally Posted by evilDSM View Post
Okay in that case then it probably did not over volt it. As for safe voltage it all depends what people think safe is. Here is what I could dig up.
Thanks for the info that is useful information
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › Computer failing to POST at OC settings after 4.5 years of success?