Dear Karol, This is said in the mildest, least confrontational manner, please do not regard this a "Troll Bait". :0) Overclocking is the premier way to create unstability. The manufacturers have made the most emphatic statements that the Official stated clock frequencies are the recommended MAX. I know of no chip brand that does NOT VOID their warrantee for overclocking. The mainframe manufacturers actually 'underclock' systems that are sold to customers that DEMAND reliability. On overclocked systems the errors that occur most are the most difficult to diagnose and resolve. Intermittant, random lockups, hangs, seg faults, corrupted data are only the start of the catalog of greif caused by chips stressed to their limit of reliability. Even one in a billion bytes of data corrupted can be stored and propagated into other apps and data. PC usually do NOT use ECC RAM so there is little or no chance that corrupted data will always be detected. Have you ever heard of a computer that printed a check for millions of $'s instead of tens of $'s? I have. Overclocking is a concept promoted by Marketeers to gull the unsuspecting gullable customers; it has the ring of "Something forr Free". IMHO :0} ......... PeterB On Tuesday 10 December 2002 04:32 pm, Karol Pietrzak wrote:
This cannot be / is not normal. Since when do you have to under-clock your computer to get stability? What CPU/motherboard combo are you using?
Hell, here on my box, I'm running an overclocked 1.6GHz AthlonXP CPU w/ overclocked PC2700 RAM on an overclocked NVidia Ti500. No problems.
At least it's "working 100% again", right?
On Wednesday 11 December 2002 05:26, jaakko tamminen wrote:
Hi
Next thing would be to slow things down a little in BIOS.. ie. set memory-speed and processor speed a bit slower, and see if it has any effect.
I had similar problem when I had tuned the BIOS to get maximum speed.. I had to slow down a bit, and now it is working 100% again.
-- -- Proud to be a SuSE Linux User since 5.2 --