I am experiencing computer freezes using ASN, RC4, and FSX. These usually occur about 30 mins into the flight. I have excluded as_rv, as_btstrap.dll and as_connect.dll from Kaspersky AV.I am using FSUIPC 4.9.2 as recommended. My Affinity mask is set to 84 (4 cores, + HT).This has happened with different aircraft.

 

I just ran a long flight using AS2012 and RA duke V2 and had no freezes or other problems. It appears that the problem only happens when running ASN.

 

Dale

I am experiencing computer freezes using ASN, RC4, and FSX. These usually occur about 30 mins into the flight. I have excluded as_rv, as_btstrap.dll and as_connect.dll from Kaspersky AV.I am using FSUIPC 4.9.2 as recommended. My Affinity mask is set to 84 (4 cores, + HT).This has happened with different aircraft.

 

I just ran a long flight using AS2012 and RA duke V2 and had no freezes or other problems. It appears that the problem only happens when running ASN.

 

Dale

A complete fatal freeze?  I have had micro-stutter, when the clouds were redrawing, mostly a second and then animation begins again. I have had a few of 3-5 seconds though. I don't know what that might be, but no fatal totals, and no O.O.M/ Freeze of any kind, no matter how severe the weather is.  That one or more second-delay of animation also happens on cloud draws in XPX as well using SkyMaxx 3D Pro.  Must be a common thing....

Yep, it's very frustrating - the flight was going really well, easily holding 30 fps, then suddenly, with no warning, everything just stops. Everything - FSX, RC4, even the cursor. I had to use task manager to stop each program. No error messages, so I ran appcrashview and got the following:

 

Version=1
EventType=AppHangB1
EventTime=129990107379249297
ReportType=3
Consent=1
ReportIdentifier=9c41306f-3d43-11e2-9e31-50465d6f59f1
IntegratorReportIdentifier=9c413070-3d43-11e2-9e31-50465d6f59f1
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=rcv4.exe
Sig[1].Name=Application Version
Sig[1].Value=4.3.0.3845
Sig[2].Name=Application Timestamp
Sig[2].Value=45cb842d
Sig[3].Name=Hang Signature
Sig[3].Value=0c08
Sig[4].Name=Hang Type
Sig[4].Value=0
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=0c08d1dd43552422d4aae19b4249b7e4
DynamicSig[23].Name=Additional Hang Signature 2
DynamicSig[23].Value=43a7
DynamicSig[24].Name=Additional Hang Signature 3
DynamicSig[24].Value=43a7a9a3564ad52affdb38143918bcc7
DynamicSig[25].Name=Additional Hang Signature 4
DynamicSig[25].Value=0c08
DynamicSig[26].Name=Additional Hang Signature 5
DynamicSig[26].Value=0c08d1dd43552422d4aae19b4249b7e4
DynamicSig[27].Name=Additional Hang Signature 6
DynamicSig[27].Value=43a7
DynamicSig[28].Name=Additional Hang Signature 7
DynamicSig[28].Value=43a7a9a3564ad52affdb38143918bcc7
UI[3]=Radar Contact V4.2 is not responding
UI[4]=Windows can check online for a solution. If you close the program, you might lose information.
UI[5]=Check for a solution and close the program
UI[6]=Check for a solution and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\rcv4x\rcv4.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\MSVBVM60.DLL
LoadedModule[5]=C:\Windows\syswow64\USER32.dll
LoadedModule[6]=C:\Windows\syswow64\GDI32.dll
LoadedModule[7]=C:\Windows\syswow64\LPK.dll
LoadedModule[8]=C:\Windows\syswow64\USP10.dll
LoadedModule[9]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[10]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[11]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[12]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[13]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[14]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[15]=C:\Windows\syswow64\ole32.dll
LoadedModule[16]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[17]=C:\Windows\system32\IMM32.DLL
LoadedModule[18]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[19]=C:\Windows\system32\uxtheme.dll
LoadedModule[20]=C:\Windows\system32\SXS.DLL
LoadedModule[21]=C:\Windows\system32\asycfilt.dll
LoadedModule[22]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[23]=C:\Windows\system32\rsaenh.dll
LoadedModule[24]=C:\Windows\system32\dwmapi.dll
LoadedModule[25]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[26]=C:\Windows\SysWow64\comdlg32.ocx
LoadedModule[27]=C:\Windows\syswow64\comdlg32.dll
LoadedModule[28]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[29]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll
LoadedModule[30]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[31]=C:\Windows\SysWow64\mscomct2.ocx
LoadedModule[32]=C:\Windows\SysWow64\MSCOMCTL.OCX
LoadedModule[33]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.DLL
LoadedModule[34]=C:\Windows\system32\VERSION.DLL
LoadedModule[35]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[36]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[37]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[38]=C:\Windows\system32\propsys.dll
LoadedModule[39]=C:\Windows\system32\ntmarta.dll
LoadedModule[40]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[41]=C:\Windows\system32\profapi.dll
LoadedModule[42]=C:\Windows\system32\SearchFolder.dll
LoadedModule[43]=C:\Windows\system32\XmlLite.dll
LoadedModule[44]=C:\Windows\system32\LINKINFO.dll
LoadedModule[45]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[46]=C:\Windows\system32\ntshrui.dll
LoadedModule[47]=C:\Windows\system32\srvcli.dll
LoadedModule[48]=C:\Windows\system32\cscapi.dll
LoadedModule[49]=C:\Windows\system32\slc.dll
LoadedModule[50]=C:\Windows\system32\DUser.dll
LoadedModule[51]=C:\Windows\system32\DUI70.dll
LoadedModule[52]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[53]=C:\Windows\system32\apphelp.dll
LoadedModule[54]=C:\Windows\system32\EhStorShell.dll
LoadedModule[55]=C:\Windows\system32\IconCodecService.dll
LoadedModule[56]=C:\Windows\system32\msls31.dll
LoadedModule[57]=C:\Windows\System32\StructuredQuery.dll
LoadedModule[58]=C:\Windows\System32\Secur32.dll
LoadedModule[59]=C:\Windows\system32\mssprxy.dll
LoadedModule[60]=C:\Windows\SysWOW64\thumbcache.dll
LoadedModule[61]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[62]=C:\Windows\system32\SHDOCVW.dll
LoadedModule[63]=C:\Windows\system32\ieframe.DLL
LoadedModule[64]=C:\Windows\system32\OLEACC.dll
LoadedModule[65]=C:\Windows\syswow64\iertutil.dll
LoadedModule[66]=C:\Windows\system32\NetworkExplorer.dll
LoadedModule[67]=C:\Windows\system32\MPR.dll
LoadedModule[68]=C:\Windows\System32\drprov.dll
LoadedModule[69]=C:\Windows\System32\WINSTA.dll
LoadedModule[70]=C:\Windows\System32\ntlanman.dll
LoadedModule[71]=C:\Windows\System32\davclnt.dll
LoadedModule[72]=C:\Windows\System32\DAVHLPR.dll
LoadedModule[73]=C:\Windows\system32\WINMM.dll
LoadedModule[74]=C:\Windows\system32\wkscli.dll
LoadedModule[75]=C:\Windows\system32\netutils.dll
LoadedModule[76]=C:\Windows\system32\PortableDeviceApi.dll
LoadedModule[77]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[78]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[79]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[80]=C:\Windows\SysWOW64\actxprxy.dll
LoadedModule[81]=C:\Windows\system32\EhStorAPI.dll
LoadedModule[82]=C:\Windows\system32\MMDevAPI.DLL
LoadedModule[83]=C:\Windows\system32\wdmaud.drv
LoadedModule[84]=C:\Windows\system32\ksuser.dll
LoadedModule[85]=C:\Windows\system32\AVRT.dll
LoadedModule[86]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[87]=C:\Windows\system32\msacm32.drv
LoadedModule[88]=C:\Windows\system32\MSACM32.dll
LoadedModule[89]=C:\Windows\system32\midimap.dll
FriendlyEventName=Stopped responding and was closed
ConsentKey=AppHangXProcB1
AppName=Radar Contact V4.2
AppPath=C:\Program Files (x86)\rcv4x\rcv4.exe
ReportDescription=A problem caused this program to stop interacting with Windows

 

Unfortunately, I don't know what most of this means.

 

Dale

It appears to be a problem with RadarContact. If you don't use RC do you still get the freeze?

 

Vic

Not that its the same issue per say but I had problems with approximately 5 sec freezes (FSX unresponsive).  My fix was uninstalling FSInn. 

 

I have not tried to reload FSInn, but ASN and other programs seem to be butting heads.  I recommend that you try disabling some modules that load via the dll.txt file until you can narrow down the exact modules that conflict.  Maybe its just a module loading issue.

It appears to be a problem with RadarContact. If you don't use RC do you still get the freeze?

 

Vic

Not sure - I will try a flight without RC4. I did several flights with RC4 and ASN during the trial period without problems, but they were all fairly short flights.

 

Dale

I updated FSUIPC to 4.9.2.7a and installed the ASN update B5099. Took a flight from KAMA to KABQ, FL 200, RA Turbo Duke, with RC4 and ASN. No freezes! I'll have to try more flights, but I'm hopeful one, or both, updates may have solved my problem.

 

Dale

I am experiencing 'freeze' in all flights over 2 hours with any aircraft while using ASN and I do not have RC.  Uninstalling ASN and using AS2012 for the exact same flight yields NO freezing so it is something to do with ASN.  There have been several other posts on this and most think it is just an overtaxing of memory since ASN is so much more memory demanding than AS2012 but my tests have shown that these are NOT caused by memory issues.

 

I have an earlier registered version of FSUIPC known not to conflict with ASN and I have enabled the memory logging feature while I fly.  I have VISTA 64 and FSX SP2 can therefore access the full 4 GB of VAS and it is this availability of the VAS that I am able to monitor while I fly.

 

If I were to run out of VAS or if FSX/ASN could not find sufficient contiguous memory during a scenery/weather load, FSX would crash with an OOM condition. This is not occurring.  The freezing or locking keeps FSX displayed on the screen with full audio but totally unresponsive to any inputs.  It can only be exited by invoking Task Manager which then displays just a black screen (desktop does not load).  I am always having around 2.0 GB of VAS still available at the time of the locks and the same amount after FSX resumes.  And this is confirmed by the FSUIPC memory monitor window I keep displayed.

 

If, however, no action is taken then FSX will resume as normal on its own after about 8 minutes.   FSX/ASN seems to be attempting to access some data or procedure that is hanging it up but after time is successful.  BTW, these are not lockups related in any way to UIautomationCore.dll issues since they are not caused by extensive menu switching and only seem to occur on flights of over 2 hours inflight duration regardless of FSX/ASN slider settings.

 

Others have reported similar issues but no input yet from Damian.  ASN is to date the most realistic weather simulation and IMHO blows away the competition but this lockup issue is a real deal killer.  I hope that it can be resolved soon.

Have you tried using Process Monitor to log all activity? Perhaps you could see exactly what is happening during that 8 minutes. It might be a tedious process but could help.

 

 

 

Just as a FWIW and not related to ASN - I had the same sort of issue with a commercial application and using process monitor, found that a CD burning application which was NOT being used was trying to initialize and THAT intrfered with the other application. They had no interaction at all except that when the CD tried to initialize when the other was running - got a freeze.

 

 

Vic

Thanks, Vic!

    I am left with the expectation that it could very easily be something like that.  As to ProcMon, I installed it but I am unable to get out of FSX when it locks unless I task mgr out and then I only get a 'black' desktop...nothing else.  Eventually things begin to come back and I am able to open ProcMon but it also has paused during my freeze so it contains no data for that time period!  I am going to try Event Viewer and see if it by chance still will record during that "dark and mysterious" period! LOL! 

 

    There are many on various threads who are experiencing the same issue and they all think they have found a solution,  but lo and behold within a few flights they are back to these forums with the continuing issue still present.  It may be that only HIFI developers can fix this one.  It must be something that their code is attempting to access that is being used by another FSX process at the same time and it is waiting in queue for it to become available.   That would explain the temporary lockup since it never results in an OOM or CTD or any other crash where it displays 'appcrash' dialogue box.

Hmm - might be interesting to look at the last instruction executed in PM and compare with the time code on both FSUIPC log and ASN log.

 

I've not had any with ASN but I've had freezes in FSX  usually related to graphics or sound. Really hard to track down..

 

Vic

I've recently had several of these 8 minute freezes (every other flight or so) and it nearly drove me crazy. My solution was simple enough. All I did was to set frames to unlimited in FSX. Now it is smooth as never before and not a single freeze in countless flights.

 

I fly on Vatsim with FSInn.  

Hi Daniel!

 

      If it would only be that simple!   I have also been flying with frame rates locked, so it will be an easy thing to try.  I don't understand why that would have an effect but if it works....!

 

     Thanks for the info.

Let us know if that works Craig.

 

 

Vic

Hi Daniel!

 

      If it would only be that simple!   I have also been flying with frame rates locked, so it will be an easy thing to try.  I don't understand why that would have an effect but if it works....!

 

     Thanks for the info.

 

Fingers crossed! 

 

I really hope it works for you as well. It was kind of a "when all else fails, let's try this for the heck of it" deal for me.