Name: blackbill Date: July 20, 2006 at 11:22:29 Pacific Subject: cpu upgrade OS: xp home CPU/Ram: 3 Ghz prescott, 2g ram Model/Manufacturer: HP/Asus/Intel
Comment:
I've got an asus mobo (P5LD2-VM) with a P4 3ghz hyperthread prescott cpu (overclocked to 3.33)
I'm toying with the idea of upgrading the cpu to intel Pent. D 960 dualcore, 3.6ghz. Does anybody know if this beast can be comfortably overclocked and if so, by about how much?
If you really want to overclock, go with non--vm series... VM = value motherboard and has limited overclocking features such as CPU/RAM/Chipset voltage tweak and lack of FSB adjustments... If you upgrade from 3.33Ghz to 3.6, how much increase can you expect it gain in terms of raw mhz? Lets do some math...
3.6 / 3.33 = ~1.081 ~ 8.1% increase in frequency... Can you say you are going to notice a huge difference in terms of regular usuage and gaming?? In fact, only games like Q4, oblivion and few others take advantage of dual-core and others you lose performance... You have a HP brandname comp, so I don't see any reason you should invest PD 960 o/c 3.6g compared to P4 3.33g...
I certainly value your words... but I don't do too much in the way of gaming. I do mostly video editing and I have just recently gotten into High definition video... a lot of background stuff going on, hence the dual core requirement. I decided to go with the p 950 anyway... it's about $200 less and is only .2g less clockspeed.
As far as the mobo is concerned, one of the big reasons I went with pentium D is so that I did not have to change the mobo... don't want to have to re install xp and programs as well as ditch about 5 years worth of disk images.... otherwise I would have said the heck with it and jumped into the intel extreme edition cpu's
But with a 3.4 I should be able to OC that to at least 3.8 or so, and with the dual core I SHOULD notice improvement in HD rendering (cross my fingers!!!)
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE