FSX Freeze, no error

[1251452 0]

Hello everyone,

 

I have just done an fsx reinstall from an old one which kept crashing.  I thought that by installing to the C drive, I could fix these problems, but to no avail.  Every time I load up the aerosoft airbus x at an airport, everything works fine until all of a sudden, the entire game would freeze.  No "not responding" boxes, app crash view does not produce any errors, and neither does windows error reporter.  The game just freezes, it doesn't even cloud over with white like some others do.  At most times, the CPU will max out to 100% on all cores.  It only happens with the aerosoft airbus at European airports.   I use some Aerosoft airports and UK2000 EGLL.  System is intel I7 4770K overclocked to 4.1.  EVGA GTX 750 1gb.  I have followed all the steps in the guide, nothing worked.

 

Thanks in advance!

[Jim Young 2,356]

You could run Process Monitor and monitor just FSX as described on Page 4 of the CTD Guide. That's how I discovered an unexplained freeze at the same location on every flight. You need to write down the time of the freeze so you can try to find it in the Process Monitor log and see what was loading. If it was AI aircraft, then you have a winner. Something wrong with the AI Program.

 

I doubt there is a problem with the Aerosoft Airbus X as a lot of people have that and are having no problems (or they are just not reporting them here). The Aerosoft airports and UK2000 EGLL are hard on fps but they do not cause freezes.

 

When the CPU is maxing out at 100% on all cores, it means you have a lot of things loading. Photoscenery will do this so disable any photoscenery you are not using. I had the same thing occurring (100% CPU usage) when I installed 40 States here in the USA. So, you have to see what all is loading (with the Process Monitor) to get a clue as to what's eating up the CPU usage.

 

Best regards,

[1251452 0]

Thanks for the quick response,

 

I think I found the cause of the problem, the affinity mask tweak I employed in the cfg.  I forgot to remove it in my earlier diagnostics.  Once that was removed, the freezes were gone.  However, now when I exit fsx, I get an error message involving unloading fmgs.dll.  I will post the error report as soon as I can.

 

Thanks again!

[Jim Young 2,356]

I get an error message involving unloading fmgs.dll. I will post the error report as soon as I can.

Perhaps the following link will help - http://forum.aerosoft.com/index.php?/topic/75242-intolerable-fmgsdll-fatal-error/.

 

A lot of freezes/crashes can be fixed immediately by rebuilding the FSX.cfg as many put in tweaks where the parameters are wrong or it is conflicting with your computer system operation. I do not believe in tweaks but know everyone has to have them to make them feel like they are getting great performance. I have not seen one tweak yet that works since 2007.

 

Glad you were able to troubleshoot and fix part of your problem.

 

Best regards,

[1251452 0]

Thanks very much, I'll check out the link.

[1251452 0]

Unfortunately the success was short lived.  I tried to fly today, fsx crashed 50 times (I was counting) I never got to push back even.  I have tried everything again the ctd guide, still crashing.

[Jim Young 2,356]

Well, the problem is your Aerosoft aircraft so you need to go there and see if they have a fix for your problem. The CTD Guide handles only the more common crashes.

 

Best regards,

[1251452 0]

ok, thanks I'll go to aerosoft's support.  I rebuild the cfg and everything seems to work, but I didn't get a chance to fully test everything.

[Jim Young 2,356]

You stated you did everything suggested in the CTD Guide so I did not recommend that you rebuild your config. Rebuilding your fsx.cfg is probably the best way to fix most CTD's as a lot of people throw in worthless tweaks that actually bring down your system if not configured properly for YOUR computer system.

 

Best regards,

[1251452 0]

Thanks for the reply,

 

I did do everything including rebuilding the cfg.  Before, that didn't work, but I did it again and all of a sudden, everything seemed to work better.  I'll test everything further.

 

Thanks