Hi Guys/Gals,I am recently getting errer messages that makes me wonder why. After flying for sometimes hours, sometimes half an hour and sometimes just after 10 minutes. FSX just freezes, sound still going and sometimes add-ons on a networked PC are also still going.The two error messages popping up are 1. Your PC ran out of memory, restart FSX with different graphic, scenery and traffic settings. 2. Unhandeled exception has occurred. Exception from HResult:0xC000014B.What is causing these errors?Running Win7 64bit, 6 Gig DDr3 Corsair RAM, GTX560ti graphics and P6T Assus Mobo, i7-960 @ 3.2Ghz.Any suggestions muchly appreciatedcheersRichard

Hi Guys/Gals,I am recently getting errer messages that makes me wonder why. After flying for sometimes hours, sometimes half an hour and sometimes just after 10 minutes. FSX just freezes, sound still going and sometimes add-ons on a networked PC are also still going.The two error messages popping up are 1. Your PC ran out of memory, restart FSX with different graphic, scenery and traffic settings. 2. Unhandeled exception has occurred. Exception from HResult:0xC000014B.What is causing these errors?Running Win7 64bit, 6 Gig DDr3 Corsair RAM, GTX560ti graphics and P6T Assus Mobo, i7-960 @ 3.2Ghz.Any suggestions muchly appreciatedcheersRichard

ORBX people say that during development they've found top end sysems with nVidia cards are run inwindow mode rather than Full Screen-might be worth a try if you're running in full screen mode.

rebuild your fsx.cfg file, don't push fsx to its limits. run with a system managed page file. check for duplicate afcad files. make sure all your airport scenery and airplanes are up to date. get latest version of any extras you use like fsuipc. get latest nvidia drivers and all other windows updates. etc

Any suggestions muchly appreciated

Check out the following link, especially the last couple of posts and the link to NickN - http://forum.avsim.net/topic/360114-oom-with-high-end-system/.Best regards,Jim

ORBX people say that during development they've found top end sysems with nVidia cards are run inwindow mode rather than Full Screen-might be worth a try if you're running in full screen mode.

Thanks for that mate but unfortunately I have to run things full screen. You see am running 4 monitors, two to the vid card and two connected via DVI to USB adapters and in windows mode those extra mon only show eighter black immages or immages but non operative. In full screen all 4 monitors running just fine as Win7 lets you move windows in full screen mode.Thanks anyways and cheersRichard

rebuild your fsx.cfg file, don't push fsx to its limits. run with a system managed page file. check for duplicate afcad files. make sure all your airport scenery and airplanes are up to date. get latest version of any extras you use like fsuipc. get latest nvidia drivers and all other windows updates. etc

Hi and thanks for comeback. I have done all that mate. Not running FSX full bore, drivers all up to date and not much add-ons at that and even not using add-ons like REX2 or FSScne total and Minimum AI stuff, it is still unstable.Thanks anyways and cheersRichard

Check out the following link, especially the last couple of posts and the link to NickN - http://forum.avsim.n...igh-end-system/.Best regards,Jim

Thanks a lot Jim, have gone and had a look-see as suggested. Most of the things I have done already if not more.Tried diff fsx.cfg files etc etc. Now I know my gear is not, what people would say, a topline gaming pc, but I have read posts of guys with high end systems still battling the OOM problem. I was just thinking of upgrading my gear but with those guys and their top gear still battling the OOMs, I wonder. I am getting OOM just flying over average scenery areas. Suggestions of turning down this turning down that etc etc. I wonder why have a top machine if you still have to turn down your sliders to 50 percent or less to not get OOM or better FPS.Yet I also read posts where people claiming to have all their sliders at full blast with a top PC.Who knows, I am afraid I am loosing my interest in trying to do a bit of Non-Error flying.BTW I am also getting another, yes another error message occasionally, on top of all the other ones and it goes like this"Unhadled exeption has occurred in your apps. If you click continue the apps will ignore the error and will continue. If you click quit the apps will close immediately."Then it has something about enabling JIT debugging. How do you do that.Looks like besides money to by the good gear you also have to be a Guru in IT.Sorry to bother you with all this Jim and others reading this. But many thanks for the help so far much appreciated.Have a nice day and cheers for nowRichard

You see am running 4 monitors, two to the vid card and two connected via DVI to USB adapters

Isn't it possible they're overloading your system?

"Unhadled exeption has occurred in your apps. If you click continue the apps will ignore the error and will continue. If you click quit the apps will close immediately."Then it has something about enabling JIT debugging. How do you do that.

That's probably caused by access restrictions. Do you have UAC disabled? Have you tried running FSX as the Administrator (right click FSX.exe and select Run as Administrator). You should look at the Event Viewer and see what it is saying when this error occurs. Another possibility I found on the Internet was a corrupted installation of Microsoft.net. You might want to download it again and reinstall.

I wonder why have a top machine if you still have to turn down your sliders to 50 percent or less to not get OOM or better FPS.

As NickN said in the link I provided, FSX can only see a certain amount of memory and anything above and beyond 4 gigs is used by other apps on your computer. FSX is an old application and doesn't manage memory allocations as well as Microsoft Flight (for instance). You do not need to turn your settings down 50%. Most of mine are maxed out but I know I will lose enjoyment of FSX if I don't bring some of them back a little and allow some breathing room. System managed size for VM is recommended too. Microsoft.net Framework manages memory for FSX (and any other game). That is one of its many functions. So, if it's not installed properly, corrupted, or not up to date, then you could have problems. I agree with mgh above regarding the possibility of your four monitors overloading your system. Many individuals with multi-monitors have reported a reduction in FPS when using FSX. Return to just one monitor and see if this fixes your problem(s). Best regards,Jim

Microsoft.net Framework manages memory for FSX (and any other game). That is one of its many functions. So, if it's not installed properly, corrupted, or not up to date, then you could have problems.

I want to add there are several versions of dotnet and FSX and FSX addons use different versions. So, the latest is dotnet framework 4.0. Many of FSX applications were developed with prior versions. I have versions v1.0, v1.1, v2.0, v3.0, v3.5, v4.0, v2.0 x64, v3.0 x64, v3.5 x64, and v 4.0 x64 or 10 different versions installed. If an addon was developed with v3.5, then you will need to have this version installed. Most of the time the developer installs the correct version with their addon but that might not always be the case. I think a lot of people are having crashes as they do not have the proper version of dotnet framework installed for a FSX application. They have the latest but not the proper one. This could happen if one reinstalls Windows then moves FSX back into the directory then uses the FlightOne registry repair utility to get the registry fixed with the proper registry settings for FSX. According to Microsoft, versions are not backward compatible. To check what versions are installed on your system, check C:WindowsMicrosoft.NetFramework and Framework x64 (if you have a 64 bit OS). The same goes with Microsoft Visuals C++ Redistributables which I have discussed before (i.e., you need MSV's from 2005, 2008, and 2010 installed). Once all the versions are installed, then you need to run Windows update to make sure each version has the latest update.Best regards,Jim

FSX just freezes, sound still going and sometimes add-ons on a networked PC are also still going.The two error messages popping up are 1. Your PC ran out of memory, restart FSX with different graphic, scenery and traffic settings. 2. Unhandeled exception has occurred. Exception from HResult:0xC000014B.What is causing these errors?Running Win7 64bit, 6 Gig DDr3 Corsair RAM, GTX560ti graphics and P6T Assus Mobo, i7-960 @ 3.2Ghz.

Good morning Richard: I think you have a couple or three issues here. (Note: All of what Jim and MGH said, too)1). The "Just freezes" problem is most likely to be caused by the incompatibility with the Win7 version of the UIAutomationCore.dll's found in the system folders. To fix this (even if this is not the prime cause of one of these problems - do it anyway - it's likely to show up with all Win7 pc's.) go here http://dl.dropbox.co...in_fsx_root.dll , download this version, copy it into the ROOT folder of FSX, and rename it to the name quoted here in this post. 2). This is not an "OOM" problem, as that one comes up with a different error message. This message refers to virtual memory - which is combined total of physical and disk swap space. If the swap space has minimal contiguous space - the total useable is reduced, and may well impact any running app. To fix this, go to your "My Computer" folder, right-click it, select "Properties", select "Advanced system settings"-->"Performance" -->Settings button, -->"Advanced", and then, in the "Virtual memory" box, click the "Change" button. I don't see anywhere, where you have quoted a drive, or drives, so I'll create an example: normal protocol is to set swap space at 1.5 times you physical memory: I like 2.0 times, so --> put a check in the "Custom size:" -- make your "Initial size (MB)" [ 12288 ] and the "Maximum size (MB):" also [ 12288 ]. When done - press "Set" and "OK". Done.Allowing Windows to self-manage the Paging file inevitably causes the available contiguous space to slowly diminish - and hence you will "run out of memory" and get that message. We can stop this happening by simply setting a fixed size and this will prevent Windows from altering it. Once you've set that size - then de-frag that space with this tool from Microsoft:- http://technet.micro...s/bb897426.aspx . 3). The "0xC000014B" error looks to be related to simconnect and ports: Pete Dowson in a two-page thread with Guenseli - http://forum.simflig...ult-0xc000014b/ had a similar failure, with Pete eventually fixing it through an updated version of FSUIPC - so what I would suggest you do in a first attempt to fix this final issue is to read through that post to it's conclusion, and then download his latest version - http://forum.simflig...pdated-modules/ .. I've pasted this link, as the Schiratti link has been hacked (I think) Choose the "Install complete FSUIPC version 4.81.**I also recommend upping that 960 proc speed to at least 4 gig, so that it can better handle the not insignificant load which you're piling on to it.**Cheers,

Wow, you guys are something. Let me first thank the lot of you for those possible solutions to my probs.First of all Jim, my UAC has been disabled for a while now so starting FSX ad an Admin no change. And indeed using just one or even 2 screens gives me errorless flying but that is not what I have built my cockpt for. I have 3 mons for left,front and right views and on for the RXP garmen GPS.(too much Load?)So actually on my server C: drive i am running WIN7, REX2, My tfc 2010 and FSscene all. My FPS runnig around 15 to 20.So taking your advice Jim I will check out the dotnet framework stuff, My system shows v.2.05, v.3.0, v.3.5 and v.4.03, in the installed programs there are Net framework 1.1, 4 client profile and 4 extended. As far as the MVCs, again showing 2005,(64) 2008 (64), so looks like I am missing 2010.And Paul thanks for the three points stated. So it looks like I am in for a long haul to clear and understand all of that but I will try.As far as my drives, C drive as stated before and FSX is running on its own drive the G: drive and add-ons that can not be networked like RXP GPS.So the virtual memory bit is that for the C or G drive? And my FSUIPC version is 4.75 so I will go and get 4.81 thanks for that.OK you guys, I will try and do all the things suggested while wishing you all a very good day and cheers for nowRichard.

showing 2005,(64) 2008 (64), so looks like I am missing 2010.

You need the MSV's for x86 too as FSX is a 32 bit app and that's what FSX and addon developers used to program FSX. Those are the ones that should have been installed when FSX/Acceleration and any addon was installed. They are definitely required.Best regards,Jim

Thanks Jim, you guys are great. will have a looksee for those MSVs. Done some of the suggestionns Paul and you posted, hopefully getting there. You see years ago all this would have been much clearer to me regarding hardware, and software problems. when years went by the old grey matter started to get cloudy, so pardon me if I sometimes do not get it or sound ignorant. Sorry guys but that's Life I guess.Still will keep on trying and who knows.Thanks again and cheers for nowRichard

so pardon me if I sometimes do not get it or sound ignorant. Sorry guys but that's Life I guess.

Not to worry. This is one of the good things about forums, asking questions whether good or bad. It's all a learning experience most of us have encountered. Hopefully your problem(s) will get fixed and you can Go Fly!Best regards,Jim

You see years ago all this would have been much clearer to me regarding hardware, and software problems. when years went by the old grey matter started to get cloudy, so pardon me if I sometimes do not get it or sound ignorant.

... you're not the only old fart around, Richard... :(