Dear Word Not Allowed,I was just reading different stuff here on Avsim and I thought I ask the knowledgeable guys around here. If you don't mind I'd like to ask a few questions regarding FSX performance. Many things are written here and there but it would be great to get some personal recommendations.I have a PC which isn't bad but could be much better by overclocking and stuff like that. It's an I7 930 at 2.8 GHz (no overclocking as of yet, because I only have the default Intel cooler). 6 GB RAM, Win 7 Home Premium 64, and the graphics card is Nvidia GTX470 with 1280 MB memory. This is my system, in a nuthsell.I can run basic stuff without issues, almost everything maxed out (except auogen which is set to very dense, cloud draw distance isn't at max and a few boxes unchecked). Certain 3rd party addon airports run fine, even complex ones sometimes, but I usually have to forget about the big, crowded cities such as NY or London... those make my system crawl 3-8 FPS which is crap.However, recently applying Bojote's tweaks using his application, things are now better, and I can run even the PMDG NGX more or less fine, almost everything maxed out. I also added BP=0, Highmemfix=1, and many of those tweaks, but I recently removed the BP=0.However, I got blue screen with the NGX more than once, which started with a weird eerie buzzing sound, and then all froze, and finally a blue screen came up with some text that the system had to stop to prevent damages or something like that. It only happened with the NGX. The sound was heard for 3-5 minutes with variable intensity and then became constant and the PC just froze. Maybe I should have exited FSX when I noticed the sound corruption, as a sign of an approaching crash.In fact, I'd like to improve my system - and I'd love to know what should I do, at least, what could improve my FSX experience, so I can fly to big complex cities with less tweaks, and such.- Should I overclock my 2.8 GHz CPU (no idea how to do that but first I am sure I need a proper cooler) to let's say 3.6 GHz?- Should I get more RAM (I have 6 GB)- Or is my video card too weak? When switching from virtual cockpit to spot plane view, it takes 1-5 seconds for the PMDG NGX textures to load, andf when going back to the cockpit, again, 1-5 seconds...I have recently downloaded NVidia Inspector, I might be looking for some recommeneded settings for that, too. I also tried the external FPS limited but I think it didn't work for some reason. I set it up properly, limited FSX to 25 FPS, the application created the .bat file but when I launched FSX (via ASE) I still got much higher FPS than 25 so it seems the limiter didn't limit:-)In fact, I'd like to improve this and that - I know it's a much more complex topic than something which could be answered in a short reply but we'll see. I also cannot buy too many things like new CPU, new card, just slowly, one by one, so that's why I would like to ask someone knowledgeable, what should I get first.Your kind response is greatly appreciated,Sincerely,Zsolt

some members say the 6 GB could affect fsx so opt for 4 or 8 gb. keep HT off.FSX fps (internal) should be unlimited and fps limiter should be @30.You should OC the cpu.

Thank you Iron Maiden, I will first buy a proper cooler and then definitely overclock. FPS internally set to unlimited and NVidia Inspector is set to 30 FPS - but I am not sure if it actually works because sometimes I see higher FPS than 30.

Thank you Iron Maiden, I will first buy a proper cooler and then definitely overclock. FPS internally set to unlimited and NVidia Inspector is set to 30 FPS - but I am not sure if it actually works because sometimes I see higher FPS than 30.

hmmm did you follow nicks nvidia guide for fsx ? you need to use the java version for the fps limiter which you can download from bojotes auto tuning site.

As I said, you need to figure out why your FSX produced such crashes. The reason is not FSX per se. It's in my opinion the hardware that is faulty, or the badly configured software.6GB is a non-issue when it comes to FSX. Not for 1366 chip (triple-channel). Just if you ever upgrade to 1155 chip, you need to be aware that you would need two sticks, instead of 3.But first of all:Google Linx, Prime95, rthdribl, CoreTemp, CPUZ and GPUZ.Configure Linx for 200 runs 4096mb and run it, with CoreTemp open. See what your CPU temp is going to. If it's kicking over 80c, stop Linx, and report back.Then run rthdribl, with GPUZ, and see what your GPU Temp is going to. Shouldn't be much over 50c I think (never been at home with GPU temps, since my GPU is so cool, due to watercooling that I've never been concerned about it).In the end, leave rthdribl running maximized, run Prime95 parallel to rthdribl, blend mode. Leave monitors like CPUZ and GPUZ open so you can monitor.This is what one would call a hardcore heat testing. Also tests if the PSU is up to the task, because these two pull very much out of the PSU and heat up the computer real good.And post that BSOD, so we can have a look at it!

Thank you Iron Maiden, I will first buy a proper cooler and then definitely overclock. FPS internally set to unlimited and NVidia Inspector is set to 30 FPS - but I am not sure if it actually works because sometimes I see higher FPS than 30.

You shouldn't be running unlimited in FSX. The best smoothness (for me) has always been with locked FSX.Btw. you DID a clean install of all drivers (chipset, network, gpu, windows updates), now did you?

Thanks a lot for the detailed guide, Word Not Allowed - I will do as per instructed and report back.I think the answer is yes to the question if I did a clean install - basically everything was done for me by the retailer who built the computer for me. All I actually do is update the Nvidia driver whenever a new one comes out, but nothing else. Having a limited knowledge of these kind of things I prefer not to dig deep in something I am unfamiliar with. This is why I am also afraid of overclocking itself, first I need to figure out how to install the cooler which I will order soon:-) But first, I will do this "hardcore heating test" as suggested. Basically, is it possible that insufficient cooling (overheating) caused the buzzing sound freeze and shortly after the BSOD and the computer stopping?Just one more question - how can I "post" the blue screen? When it happened, the computer simply stopped, after a blue screen with with white text on it, but I don't have the chance to copy/paste/save that text. Or is there an error report about it somewhere, which I can see after I restart the computer?Thanks a lot,Zsolt

You shouldn't be running unlimited in FSX. The best smoothness (for me) has always been with locked FSX.

It's common knowledge now that higher FPS is achieved by running unlimited frames within FSX and using only an external limiter. This is something I preached for years, but it only sank in after that fella' Nick Needham and later ******* Altuve claimed the same.We lock FPS (again, externally!!!), Zsolt, to avoid FPS surges (especially in exterior view) and to allow the CPU time to render scenery textures. ie NO BLURRIES!

That´s the beauty about FSX, right?Two veterans - Zach and Word Not Allowed - have totally different opinions about locked or unlocked FPS!Myself being Bipolar, I tend to switch between the two settings, right now it´s unlimited in FSX, and limited with FPS Limiter outside...This can change again and very quickly, like mood swings! :Just Kidding:

It's common knowledge now that higher FPS is achieved by running unlimited frames within FSX and using only an external limiter. This is something I preached for years, but it only sank in after that fella' Nick Needham and later ******* Altuve claimed the same.We lock FPS (again, externally!!!), Zsolt, to avoid FPS surges (especially in exterior view) and to allow the CPU time to render scenery textures. ie NO BLURRIES!

A common knowledge, which I was never (never) been able to replicate, over 3 different machines. It does give better FPS, but it gives more stuttering. I've tested this over many driver versions, and as said over 3 different computers.It only prevents blurries from running completely unlimited (of course, duh).Now, maybe I'm doing something wrong, but to my knowledge, which is dare to say, quite extensive, there is nothing I missed.The best stutter-free environment for me has always been BP=0 + locked in FSX. Even with vanilla fsx.cfg results were poorer with locked outside - not the FPS mind you, but stutters. I have one situation I test for comparisons, side view takeoff at KSEA in a 737. And now, I'm not imagining things :lol:I've always said... YMMV. :lol:

This can change again and very quickly, like mood swings! :Just Kidding:

Is also a good thing hehehe...

For years I preached unlocking within and locking without to whoever would listen. But now I find that combination produces blurries. Now I only run with frames limited (35FPS) within resulting in crystal clear rendering 100% of the time.Maybe I am bi-polar too, but with mood swings that take a couple of years! :unsure:Kind regards,

I don't think it's mood swing or anything... I think this comes with differences in drivers and hardware. Right now I see the trends moving towards inside-lock again...

However, I got blue screen with the NGX more than once, which started with a weird eerie buzzing sound, and then all froze, and finally a blue screen came up with some text that the system had to stop to prevent damages or something like that. It only happened with the NGX. The sound was heard for 3-5 minutes with variable intensity and then became constant and the PC just froze. Maybe I should have exited FSX when I noticed the sound corruption, as a sign of an approaching crash.

Zsolt,Actual noises from the computer followed by blue screens is never a good thing and suggests hardware failure. If it has happened several times I strongly advise to refrain from overclocking until the hardware issue is resolved! Overclocking will put additional strain on your system and might cause more damage to your system when parts fail.Can you locate the source of the sound? is it coming from the PSU, GPU, motherbord? I have had a (good quality brand) PSU fail on me. it started with a noise from the PSU at high loads (read FSX)After you have sorted out you're hardware problem you should definatly unlock the "free" performance in your i7 by overclocking. It is good fun and you really notice the difference in FSX.edit sometimes auto correct on the phone is quite annoying

It only happened twice, and on both occassions with the PMDG NGX. Early to say but since I changed back to 4xS [Combined: 1x2 SS + 2x MS (D3D only)] antialiasing from 8xSQ [Combined: 2x2 SS + 2x MS] it seems to be okay - those who have the knowledge might confirm or deny if this has anything to do with my two blue screens. But for sure, before I switched to 8xSQ I had no issues at all, and since I returned to 4xS, again, all runs okay.The eerie buzzing sound? That came from the speaker! It was like a loop of engine sounds, basically the sound froze right before blue screen. I doubt my hardware is faulty, but maybe that push was too much for it. If it happens again, I am gonna investigate it.I will now try locking the FPS inside FSX because stuttering is annoying.Also, when I look around in the cockpit for example, sometimes it seems that certain graphic elements (edges mostly) are tearing when I pan around.Thank you,Zsolt

Just read somewhere here on the awesome Avsim today, that someone locked the FPS at 25, inside FSX...Word Not Allowed´s advise in post #9 had me re-thinking too, thanks man! :Peace:Tested on the "too hot to handle" G73JH, and it works, really... - at 25 FPS, I have no stutters, no hickups, no flashing craziness, it´s smooth as XP-10 silk!Is it my eyes, is it all a dream, wishful thinking, do I have a problem, do I blink too little or maybe too much?What can it be?Try it, people, bipolar or not! :Party:PS: - and no blurries, I guess all the CPU power above the 25 FPS goes to texture rendering etc. - Am I right, wrong, or...?PPS: Next hurdle is the i5 / HD6970 rig, phew, problems ahead I think...

The eerie buzzing sound? That came from the speaker!

:LMAO:So no hardware problems. Enjoy the overclocking