>> In my case heat can't be the problem regarding the CPU. But I have thought about other components. Maybe the CPU isn't the only component that gets overclockedThat's true, 'cept you've had the board Running 240. Try manually setting the ram to the lowest speed available with the FSB at 220. It appears your mobo can actually decrease ram speed below 2x the FSB. I think you are suggesting this is happening automatically, but set this ram speed manually. Also the PCI buss is driven by the FSB speed. Again, it appears the mobo is maintaining the PCI buss's default speed, but manually set this speed anyway.If you can't increase the CPU's voltage, that's really about it. It's probably just as well you can't. This is where an O/Cer can get into trouble. Higher volts means higher current, means higher heat, means a higher at-risk CPU. The mfg provides - concrete - limits for both CPU heat and volts. As long as an O/Cer stays within these you're OK. HowEveR, as you approach these limits everything else becomes more critical. The power supply Must be stable and capable (no spiking, maintains volts/amps), cooling Must work (max-temp shutdown limits set And working), affected clocks Must be controlled (PCI/RAM auto speed-set Is working or manually set), etc, etc. At these higher levels of clocks, volts and temps ya - Gotta - pay attention or something Will go PooF.This all is for the computer hobbiest that is really willing to pay close attention to his hardware. My Q6600 at 3.6Ghz is magical compared its default 2.4Ghz . . . but it has come at cost. I Have to pay attention to the computer. I'm running well within clock/volt and temp limits. It's been fine for over a year now and can recommend this setup to anyone (Actually, I never even shut it off). However this is a hobby for me. I Like to pay attention, but it might not be for everyone.This basic method of O/Cing will get a user 90%+ of the performance advantage available by Any means. Going for that last 10% is where one really needs to have that fire extinguisher (and a credit card!) at-the-ready.

>Overclocking doesn't damage components at all, it's the>uninformed, uneducated, cheap parts-buying rookie that pushes>things too far without having the experience or wisdom to>follow directions correctly.Sorry, but there I disagree: changing the freq settings cannot damage components, but when you start to play with voltage levels it can get dangerous. There's a reason why overclocking voids most warranties.

The normal (without defect failure) loss of a processor over time due to any overclocking is called

http://forums.avsim.net/dcboard.php?az=sho...mode=full#43944The only time damage occurs in a 'properly' clocked system is if the components were defective to begin with or the user is trying to push components not designed with overhead (purchase the right parts the first time). Otherwise damage comes from user error and not understanding what they are doing and knowing the limits of the components installed.We accept those things when we clock and if done correctly it will not reduce the useful life of the products, at all.I

>>Also, if you don't pay attention, you can damage components.>We have an uberclocker on the boards here that has provided>advice that has damaged member's equipment. Watch out for>that. Ok, Sam. Who is he/she or this is just some provocation?! Your post should be alterted to a mod. You should remove your PMDG sig, because these kind of posts shouldn't be connected with PMDG.Ulf BCore2Duo X6800 3.3GHz4GB RAM Corsair XMS2-8500C5BFG 8800GTX, Creative SB X-FiFSX Acc/SP2, Vista 32

:-erks He shows up, spits his geek squad advice, and when he's called out on it he runs & hides...until his next opportunity! LOL!-jk

Sorry 'bout all the noise, but in any case be careful with this. "Paying attention" with an overclock can get a user magical performance increases, but firey uberclock prescriptions really can cause serious hardware problems. Once a system's hardware starts to operate beyond its actual capability, its software will invariably start to exhibit inexplicable characteristics. You'll find your computer becoming an increasingly unfriendly partner. That can be hard on the family. At some point you may even need to put it under your arm and take it down to your local computer therapist! After all, your computer is an old friend that needs some kind attention. The best advice is to simply use any advice as a guide to figure it out yourself. After all, learning about computers is a great hobby.

>Sorry 'bout all the noise, but in any case be careful with>this. "Paying attention" with an overclock can get a user>magical performance increases, but firey uberclock>prescriptions really can cause serious hardware problems. Once>a system's hardware starts to operate beyond its actual>capability, its software will invariably start to exhibit>inexplicable characteristics. You'll find your computer>becoming an increasingly unfriendly partner. That can be hard>on the family. At some point you may even need to put it under>your arm and take it down to your local computer therapist!>After all, your computer is an old friend that needs some kind>attention. >>The best advice is to simply use any advice as a guide to>figure it out yourself. After all, learning about computers is>a great hobby.I appreciate your cautious advisory, but those giving the overclocking advice in the first place are just as cautious up-front. I've been lurking these forums for quite some time (reading without posting) and have yet to see anyone give truly dangerous advice. Bottom line: you have to know what your hardware is capable of (this means *every* major system component including cooling and power, motherboard and ram, processor and graphics card), and understand that there is a risk involved in any serious overclocking endeavor, especially when voltage adjustments come into play.

Just in case, concerning my comments below, I wasn't calling the original poster of this thread a rookie, it was directed elsewhere.don't want any misunderstandings.

>>> In my case heat can't be the problem regarding the CPU.>But I have thought about other components. Maybe the CPU isn't>the only component that gets overclocked>>That's true, 'cept you've had the board Running 240. Try>manually setting the ram to the lowest speed available with>the FSB at 220. It appears your mobo can actually decrease ram>speed below 2x the FSB. I think you are suggesting this is>happening automatically, but set this ram speed manually. Also>the PCI buss is driven by the FSB speed. Again, it appears the>mobo is maintaining the PCI buss's default speed, but manually>set this speed anyway.>When I filled all memory slots the RAM was automatic set to 360 MHz.I could change that by forcing 2:1 400 MHz. But OC did change the RAM speed. I think the PCI buss gives two choices one stanfard and one slightly gigher speed. CPU-Z reports about 1.5 V fore core voltage. Isn't that already fairly high?The Asus support has suggested that certain FSB frequencies might work bad regardless if it's not to high. Meaning that if FSB 240 don't work maybe 239 will work.

>The best advice is to simply use any advice as a guide to>figure it out yourself. After all, learning about computers is>a great hobby.Correct so I suggest you let people learn without your full blown BS and chicken little warningsThis the last time I am going to communicate directly with you you always say the proof is in the pudding... well I got news for you this is your sim shot from another threadhttp://forums.avsim.net/user_files/194514.jpgI'll be quite honest.. if my sim looked like that and I had to fly that blurry mess with little or no autogen I would throw my computer out the windowMy sim does not look like that and I doubt anyone who is on the right hardware and clocked correctly deals with what you do in that imageThe proof is in the puddinSee ya in New York http://forums.avsim.net/user_files/194515.jpgCan It SamTo the OP... I do apologize as it was not my intent to hijack your thread however someone here made a blatant and completely false accusation and it needed to be dealt with accordingly.If I had the time to look in-depth into your clock problem I would however right now I am tied up with other things.

>If you can't increase the CPU's voltage, that's really about>it. It's probably just as well you can't. This is where an>O/Cer can get into trouble. Higher volts means higher current,>means higher heat, means a higher at-risk CPU. >A mistake from my side. I just discovered that I can change voltage up to some 1.7 V. Also I can manually set PCI buss speed and HT link speed. Maybe it was because those were at AUTO that my system crashed?

Possibly. Find out the safe volts and temps for that AMD CPU. If you reset volts, don't trust the bios settings. Get a trial of Everest and check Both volts and temps with that. "HT link" is AMD-ish. I've never understood exactly how that fits the AMD grand-plan. Give us a run down on what you learned. As we were discussing, the best outcome of all this "advice" is to help a user ask the right questions, then research, research, research. Ignore the bluster. Go get 'em!

Why don't you post some more pics of your sim, Sam? Show us all how your advice pays off? Show us all what can be attained without listening to the dangerous "uberclockers"!Got get em! FSX in all it's mustard colored, blurry glory!-jk

Guys, please stop using this forum as a boxing ring.You both have a lot of talent and knowledge and we all thank you for that but your quarrels are really boring now.Thanks.David