Ok my sim froze again, or hung up, this is what app view said. it might be my Norten, or something also, my virtual airline was not responding ether, at least thats what the task manager said, but that might be because it was connected to fsx. PFPX and Topcat  were also running.

 

Version=1

EventType=AppHangB1

EventTime=130295530138707644

ReportType=1

Consent=1

UploadTime=130295530140457744

ReportIdentifier=60dea00c-530b-11e3-a877-60a44c56c9be

IntegratorReportIdentifier=60dea00d-530b-11e3-a877-60a44c56c9be

WOW64=1

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=fsx.exe

Sig[1].Name=Application Version

Sig[1].Value=10.0.61637.0

Sig[2].Name=Application Timestamp

Sig[2].Value=46fadb14

Sig[3].Name=Hang Signature

Sig[3].Value=82b2

Sig[4].Name=Hang Type

Sig[4].Value=2048

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=6.1.7601.2.1.0.768.3

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=1033

DynamicSig[22].Name=Additional Hang Signature 1

DynamicSig[22].Value=82b2ec27310ede0eb31202d31bb54ad8

DynamicSig[23].Name=Additional Hang Signature 2

DynamicSig[23].Value=27a2

DynamicSig[24].Name=Additional Hang Signature 3

DynamicSig[24].Value=27a2f60553a11ca9c23a0cdae3e56837

DynamicSig[25].Name=Additional Hang Signature 4

DynamicSig[25].Value=82b2

DynamicSig[26].Name=Additional Hang Signature 5

DynamicSig[26].Value=82b2ec27310ede0eb31202d31bb54ad8

DynamicSig[27].Name=Additional Hang Signature 6

DynamicSig[27].Value=27a2

DynamicSig[28].Name=Additional Hang Signature 7

DynamicSig[28].Value=27a2f60553a11ca9c23a0cdae3e56837

UI[3]=Microsoft Flight Simulator® is not responding

UI[4]=If you close the program, you might lose information.

UI[5]=Close the program

UI[6]=Close the program

UI[7]=Close the program

FriendlyEventName=Stopped responding and was closed

ConsentKey=AppHangXProcB1

AppName=Microsoft Flight Simulator®

AppPath=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

ReportDescription=A problem caused this program to stop interacting with Windows.

Exactly where did the your application hang up?  In my experience, applications that hang are caused by other things running in the background and/or too many Windows open.  Each Window that is open takes up a lot of system resources.  Things running in the background could be programs, like your Internet browser, did not properly shut down.  So I think that's what is happening.  Something else in the background is taking up resources and you need to shut those processes down before running FSX.  When you get the AppHang again, check to see what processes are running in the background in the Task Manager (Ctrl-Alt-Del).  If Internet Explorer or whatever browser you are using to get on the Internet is still running in the background, then shut it down.  You may have to disable any addon scenery you will not be using for a flight too.  Some photoscenery and other commercial addon scenery loads in the background whether you are flying in that location or not.  This takes up a lot of resources.  So I don't think there is a problem with FSX.

 

Best regards,

Jim

Hi do as Jim suggested. I in the other hand had a similar crash like yours just a few days ago . The only difference in these crashes it only occur with any scenery that had to used the addon manager like flightbeam , fsdreamteam , etc.....   Before i suggest what  i did to fix the problem please tell me if you get CTD only using scenery like fsdreamteam , flightbeam or any other developer scenery that uses the add on manager ?
 

is it possible to tell what caused the hang up this time?

 

Version=1

EventType=AppHangB1

EventTime=130334435527431721

ReportType=1

Consent=1

UploadTime=130334435529421835

ReportIdentifier=bfd4be7c-766d-11e3-b033-60a44c56c9be

IntegratorReportIdentifier=bfd4be7d-766d-11e3-b033-60a44c56c9be

WOW64=1

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=fsx.exe

Sig[1].Name=Application Version

Sig[1].Value=10.0.61637.0

Sig[2].Name=Application Timestamp

Sig[2].Value=46fadb14

Sig[3].Name=Hang Signature

Sig[3].Value=85ad

Sig[4].Name=Hang Type

Sig[4].Value=2048

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=6.1.7601.2.1.0.768.3

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=1033

DynamicSig[22].Name=Additional Hang Signature 1

DynamicSig[22].Value=85ad09a246adeff460d18025afbb8a18

DynamicSig[23].Name=Additional Hang Signature 2

DynamicSig[23].Value=21c9

DynamicSig[24].Name=Additional Hang Signature 3

DynamicSig[24].Value=21c90e35d9e030c066344696a6c70df7

DynamicSig[25].Name=Additional Hang Signature 4

DynamicSig[25].Value=85ad

DynamicSig[26].Name=Additional Hang Signature 5

DynamicSig[26].Value=85ad09a246adeff460d18025afbb8a18

DynamicSig[27].Name=Additional Hang Signature 6

DynamicSig[27].Value=21c9

DynamicSig[28].Name=Additional Hang Signature 7

DynamicSig[28].Value=21c90e35d9e030c066344696a6c70df7

UI[3]=Microsoft Flight Simulator® is not responding

UI[4]=If you close the program, you might lose information.

UI[5]=Close the program

UI[6]=Close the program

UI[7]=Close the program

FriendlyEventName=Stopped responding and was closed

ConsentKey=AppHangXProcB1

AppName=Microsoft Flight Simulator®

AppPath=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

ReportDescription=A problem caused this program to stop interacting with Windows.

 

 

is it possible to tell what caused the hang up this time?

 

It's impossible.  AppHangB1's are difficult to diagnose.  You will have to investigate.  Most are caused by high settings but a module could have created the crash too.  So you have to go into your dll.xml and start disabling modules.  The dll.xml is in the same folder as your fsx.cfg.  Open the file with Notepad (Notepad++ is even better - freeware on the Internet).  You just need to disable the line that says the following:

 

<Disabled>False</Disabled>  Change the false to True. 

 

You can disable them all, run fsx and see if that fixes the problem.  If so, it is one of those modules that is not installed properly or something is wrong with it.  Or, you can disable them one at a time which could be a very lengthy process.

 

Make sure your main fsx folder is shared (right click on the folder to see if it is shared.  If not, get it shared or better yet, download TakeOwnership and install it.  Then right click the main FSX folder and select Take Ownership.  Do this for any modules located on other HDD's or not in the main fsx folder.

 

You need to review the AVSIM CTD Guide (see pinned topic in this forum) for more tips and possible solutions to freezes or AppHangs.

 

Best regards,