This is okay because components are made to run at a certain max stable speed they can go further it just comes with some risk. (This isn’t how monitor OCs work, though.) You are taking your clock speed and pushing it over its normal limit. Overclocking ATi for me is best in Ati tray tools - because you can play with latencies and get even better results, than normal OC.Ĭheck my sig, and if you have any questions I'll be glad to help if I can.So, what does overclocking do? Well, on its surface it’s pretty simple in general, PC overclocking is the process where you set your computer components to higher clock speeds for better performance. (along other things) so NHC is probably the best software for Pentium M/Ati platform. Undervolting of Pentium M can be done in Notebook Hardware Control. The new Ati tray tools will have volting ability for ati x1xxx series. Ati x700 doesn't show almost any heat increase while OC'd and undervolted CPU at 5% overclock is cooler than on default speed and voltage. I also covered heat and instability - and found that undervolting can help a lot in getting much cooler gaming temps - in my case from 76 or 80 down to 67. On the other hand My BIOS has OC ability and I can overclock for 5%, and temp is not a issue at all. I successfully did it on Asus M6N (1,6 GHz Banias was faster than 2,0 GHz at the time), and I know people are overclocking Acers, but I haven't found any for my current comp. The problem is finding the right one that works with your platform. CPU is much harder - all of the tools are in fact FSB overclock tools that raise the FSB speed by 5-15% giving you higher end CPU freqs. GPU is easier to overclock and it is the fastest way to get more fps. (synthetic bench) FEAR goes up by 10 fps on 800圆00 and all settings on max. In my case it is from 2170 to 3195 3dmark05. I did quite a lot of articles on it, and I can say that if you know what are you doing - you can safely overclock CPU/GPU and get from 5 to 25% gaming performance increase at even lower temperatures than on default.
0 kommentar(er)
