how likely is it to kill the cpu


Recommended Posts

actually i think a more accurate answer than simple vcore shortening life, is rather heat shortening the life of your cpu. you can raise your vcore all you want if you can keep it cool, but generally this is hard. so what you should be asking is how hot can your cpu run safely?

to be honest, i think cpus can take pretty high temps pretty well. if they're under 50 deg you're pretty good. even if you were to go to like 55 deg or something, so your lifespan goes from 10 years to 5 years... i dont think its worth being too concerned about, most ppl get new computers every 3 years anyway. your cpu is already old so you might as well get the most out of it.

actually i think a more accurate answer than simple vcore shortening life, is rather heat shortening the life of your cpu. you can raise your vcore all you want if you can keep it cool, but generally this is hard. so what you should be asking is how hot can your cpu run safely?

to be honest, i think cpus can take pretty high temps pretty well. if they're under 50 deg you're pretty good. even if you were to go to like 55 deg or something, so your lifespan goes from 10 years to 5 years... i dont think its worth being too concerned about, most ppl get new computers every 3 years anyway. your cpu is already old so you might as well get the most out of it.

i concur, its not the volt, its the heat that will inevitably will shorten the life, key is if you keep the heat down the cpu should have a normal lifespan. my rig runs @ 25c idle and 32c load with is below normal however am clocked 2.8c @ 3.5ghz

Altho i agree with every1 that it's the heat is Public Enemy #1, sending more volts thru the tiny transistors inside the CPU doesn't do it any favours. :no:

The main problem is you can pretty much tell what damage heat is doing with sensors and cooling and stuff... how u gonna tell if u just fried a few 0.13 micron transistors??

On the flip side, as long as u don't go crazy most CPU's will last well beyond the point u find them slow, dull and in need of upgrading so i wouldn't lose too much sleep!

At the end of the day it all comes down to choice. Red pill or blue pill? Play it safe and respect the silicon shrine or go full force assuming you'll upgrade soon anyway.

well..my heat is no problem :) when idle i reached a temp of 15 degrees (more often just 18)...and when in full load, for about 1 hour, i reached the 24degrees....and i'm running a 2.6Ghz @ 3.3Ghz i just think i should cool my northbridge to :p it's just a heatsink now...@ 40degrees or smth

god i just love my watercooling :p

but isn;t raising your Vcore mostly ment to stabilize your cpu speed? not to accelerate it?

actually i think a more accurate answer than simple vcore shortening life, is rather heat shortening the life of your cpu. you can raise your vcore all you want if you can keep it cool, but generally this is hard. so what you should be asking is how hot can your cpu run safely?

to be honest, i think cpus can take pretty high temps pretty well. if they're under 50 deg you're pretty good. even if you were to go to like 55 deg or something, so your lifespan goes from 10 years to 5 years... i dont think its worth being too concerned about, most ppl get new computers every 3 years anyway. your cpu is already old so you might as well get the most out of it.

i concur, its not the volt, its the heat that will inevitably will shorten the life, key is if you keep the heat down the cpu should have a normal lifespan. my rig runs @ 25c idle and 32c load with is below normal however am clocked 2.8c @ 3.5ghz

well yea but it's the voltage that CREATES the heat. hence people saying that vcore kills the cpu. but everyone is right, if you can keep your cpu cool, you can go as far as your psu will allow. i have a friend that went to 2.26V on his barton. personally i don't touch 1.9V. i don't have enough money to risk that kind of a thing.

BTW... nice temps. way to make me jealous! jerk face! :D

Its not realy the heat that kills a CPU, its electrons jumping the little gaps in the proc. Once an e- jumps it preatymuch burns in a bridge and others follow hense the proc is dead. Both heat and voltage increase the probility of this. If you raise the voltagem, the diffrence above one of these gaps is going to increase, and the electron will be more likley to jump the gap. Heat also has an effect of 'loosing' everything up. Of corse if your proce gets up to 90c its just gonna send out pumes of smoke and you can screw the whole electron theorie.

As for raising the vcore, you can preaty much send it up to 2v and have it last a minimum of three years. After thoes three years, youll be able to buy a faster proc for like 50$. It will barley set you back for the preformance increase you recive.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Lego Batman 2026 hahahaha. You thought I couldn't reply back???
    • The problem isn't with Epic, it's with the platform holders like Steam and Nintendo, they should be a lot more strict in their review process.
    • Hello, Installed here without issue. Regards, Aryeh Goretsky
    • Microsoft updates Visual Studio Code with easier language model discovery and in-app search by Paul Hill Microsoft has released Visual Studio Code 1.125, its latest weekly release. This week, the company has focused on discovering and installing extra language models via the Marketplace; searching the web and securely browsing over remote connections without leaving VS Code; choosing how long VS Code waits before installing extension updates; and delivering managed Copilot settings through existing device management tooling. In older versions of VS Code, extensions could contribute their own model providers, but to find these extensions, you needed the right tags to search for in the Extension view. Now, the Language Models editor gives you an Install Model Providers button that opens the Extensions view, which is filtered to extensions that contribute model providers, making it easier to find and install them. Once you install a provider, its model will appear in the model picker. If you use the integrated browser much, you can now look up information without leaving VS Code by typing a query into the integrated browser’s address bar. It will use your configured search engine, the same way a standalone browser does. You can use workbench.browser.searchEngine to pick a search engine. When the browser is opened in a remote workspace, it's now possible to proxy HTTP(S) traffic via the remote connection. This allows you to connect to any ports or services that can only be accessed from the remote machine. If you read our coverage from two weeks ago about VS Code 1.123, you might have seen that extension updates have a two-hour delay as a safety measure. In this update, Microsoft is giving you the ability to configure the time of the delay. You can find it under extensions.autoUpdateDelay. Finally, with this update, admins can deliver managed GitHub Copilot settings through native device management (MDM) channels on Windows and macOS, in addition to account-based enterprise settings files. Settings delivered via MDM appear as policy-enforced in VS Code and can’t be overridden locally. Future updates will extend the supported policy keys across Copilot surfaces. You can download the update from the Visual Studio Code website now.
  • Recent Achievements

    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
    • One Month Later
      Vincian earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      543
    2. 2
      +Edouard
      171
    3. 3
      PsYcHoKiLLa
      82
    4. 4
      ATLien_0
      64
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!