Herby

Thanks again Jim. I should have done this before. I did follow your advice and got rid of this OOM problem. Now I need to rebuild my fsx.cfg. Do you have any advice on where to start? Should I go first in the GUI and adjust scenery, aircraft, traffic... settings or should I try first to set the tweaks like bufferpools, affinity mask...?

I can't believe that I never saw this guide before. Just had a quick look and it looks excellent! Thank you. Lastly, I made a few changes in my fsx.cfg following instructions from FSLabs forum but didn't have time to check if I finally reached my goal. If not, I will definitively follow your advice and reset this fsx.cfg. For information, I installed the whole system following the tutorial from Nick on simforum and I didn't make much change to fsx.cfg before trying venetubo.

Yes, I did. Just checked and it is still on auto and running at 100MHz. I made a few more tests during those last days. Since I slightly increased the vcore (+ 0,010v), I went into new stress test (4 hours of prime95 and 8 hours of OCCT). All tests finished without any error. So I don't know what to think about this OC... Stable or not??? On the other hand, I processed my fsx.cfg file through venetubo.com. Now, all a/c seem to run fine (I need to make more test to be sure) except the concorde x. Only with this a/c, each time I come close to a big scenery like EGLL UK2000 or Mega airport CDG, I have this error message: "Your computer has run out of available memory. Please restart Flight Simulator and select different graphics, scenery or traffic settings." I made a test without OC and had this problem again. So I assume it is not linked to the overclocking settings. This problem appears to happen a lot with the concorde x. I'm now looking on the FSLabs forum for a solution.

I didn't make it very clear in my first post but when I say "First, I did install a light FSX (with only the main addons and sceneries) in order to test and fine tune the system and its overclocking settings.", I actually went through a serie of long stress test. To be more precise, I ran a 6 hours OCCT test, another 6 hours with the intel burn test and another 6 hours of memory test without issue. But maybe I should run such tests again now that I have reinstalled the system, shouldn't I? Well, this is half true, half funny. After running all those tests without any errors, I still had some CTD and BSOD while running FSX. The BSOD error code indicated a lack of vcore. So in my case, I'd say that FSX was the ultimate stability test for OC! I kept testing FSX those last few days. It appears that the last change I made (adding AffinityMask=14 in fsx.cfg) really saved the day. Since that, I got rid of most of the problems. I made several flights in various conditions with different a/c on different sceneries without any issues. Only one problem remains: I have some CTD due to nvd3dum.dll only with the concordeX from FSLabs. I will make some tests without OC to see if this is linked to the OC settings. Thank you TheGrunt and Jim for your inputs. I'll post here as soon as I get new infos.

I'm afraid that you're damn right. Since I have no problem at all when I remove the OC and run the CPU at stock speed, I come to the same conclusion. What I don't understand is why the system was stable even when overclocked before I reinstall windows and is now completely unstable with the same BIOS settings. I have a backup of the previous instsllation. So I'm now trying to replicate one by one the settings of the previous fsx.cfg. So far, I've only added this line: [JOBSCHEDULER] AffinityMask=14 And it seems to have a positive effect; no more CTD so far but I have to make more test, different aircrafts in different sceneries to be sure that the problem is definitively solved. And this takes a lot of time.

I don't have ENB nor SweetFX installed and no d3d9.dll in my FSX folder. However, I just made 2 small test flight and didn't have any issue. I don't know exactly what fixed this d3d9.dll problem but here's what I've done: As said before, I installed .NET V4.5. After that, I had a few update to install through windows update. I installed them and some optional updates that were pending (some KBxxxxxx). After that, I had a 0x3B BSOD during the next flight due to an insufficient vcore. So I raised the vcore a bit and that's it. I will make a few more flight to be sure that everything is stable before marking this thread as solved. Thanks again Jim for your kind help.

Thanks Jim for this. I followed your instructions. The repair tool didn't find any error. However, I installed .NET v4.5 and ran a windows update. Since that, I don't have this gdiplus.dll error but now, I have CTD due to d3d9.dll. This crash happens even faster than the previous one (less than 5 minutes after starting the flight). I'm really suspecting all this to be caused by a temperature issue. I live in a tropical country and it's now mid day. Temp in the room is over 30C. I monitored the system and CPU temp on the last attempt but the chipset only reached 45C and the hottest CPU core was only 75C. Not that hot but I can notice that FSX crash really faster during the day than during the night.

Hi, I have a new rig dedicated to FSX (see signature for details). First, I did install a light FSX (with only the main addons and sceneries) in order to test and fine tune the system and its overclocking settings. I ended up with 2 OC profiles (4.5GHz and 4.6GHz). Since everything was running fine and stable, I made a full clean reinstall of windows and FSX with all the addons. But now that everything is properly installed, I always have CTD during flight. This only occures when the CPU is overclocked. With the CPU at stock speed, no CTD. At 4.5GHz, the CTD usually occurs on final approach, when the destination airport is loading I guess. At 4.6GHz, it happens anywhere between 10 to 15 mns of flight. The win7 error log indicates that the crash comes from the gdiplus.dll module. I did search around for this error but didn't find anything helpfull. So far, I only tried to raise the CPU vcore but it didn't help. I don't know what to do to solve this issue so any advice is welcome. Thanks, Herby.

Unfortunately, 2400MHz RAM is really hard to find in my country. So I ill probably recycle some old RAM and wait for an opportunity to buy it oversea. Thanks for this advice.

Hi, I'm about to buy a new computer almost fully dedicated to FSX. After days of searching, I come out with this configuration: - Thermaltake Level 10 GTS Mid Tower Not a lot to say about the tower. I picked up this one because it can fit a big radiator and a big graphic card and it's well ventilated to allow overclocking and I even have the option to fit a water-cooling system. - Cooler Master 625W V2.3 Extreme 2 Not sure if this PSU is powerful enough... - 8GB Kit (2x4GB) DDR3 Kingston HyperX KIT BLUE 1600 - Intel Core i5-3570K AS you can imagine, the goal is to overclock it. I heard that FSX cannot use the hyperthreading, that's why I didn't choose a I7 CPU. - GIGABYTE GA-Z77X-D3H I think this mobo has all it takes to make a good overclocking. I already have 2 old HDD (one 250GB and one 500GB). I'll use the first one to install 2 win7-64bit OS (one for general use and one for FSX only). The second drive will be for the FSX installation folder and other data. I will deal with this for now. I'll have to wait a bit before buying the graphic card, a screen and a good cooling system for the overclocking. What do you think about this setup? Is-there anything I can change that will boost up the performance of the machine without increasing the price too much? Until I have enough money to buy a screen, I plan to run FSX via a remote desktop; but I'm not sure if it is possible... Also, even if I can't buy it right now, I'm still wondering what kind of cooling system I should choose (air or water cooling)? I live in a tropical country where the temperature rarely falls below 30°C so I need a 'serious cooling system'! All expert advices and comments are welcome. Best regards, Herby.