Sign in to follow this  
tanker

ASN and Computer Freezes

Recommended Posts

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

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

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....

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

 

Vic

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.  

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Let us know if that works Craig.

 

 

Vic

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

I have a feeling that when Pete Dowson returns from holiday and puts out a new version, some of these issues will be resolved. At least I sure HOPE so!

 

Vic

Share this post


Link to post
Share on other sites
Hi Daniel and Vic!

 

     I am pleased to report that I just completed a 3 hour flight complete with missed approach and rough destination weather with no lockups using Daniel's suggestion about unlocked frame rates.  I did use the B744 though so I will need to confirm it with NGX or ConcordeX since they have greater demand on resources.  Anyway, NO LOCKUPS for the first time on flights over 2 hours with ASN.  It makes no sense so again, is it a fluke?  My FPS varied between 35 and 75 most of the way with all sliders to the right and CDD at 105nm in ASN with enhanced weather, etc.  I also was using the ASN weather gauge and 100% UT2 traffic.   I will try a totally different long flight with a different aircraft tomorrow and will keep you posted.

 

   Have you tried any other flights with your hypothesis, Daniel?  If it keeps working then we can file this issue and begin enjoying the flights again with this great weather generator.  I will continue to use your method until I get a failure and I hope that never happens.  Thanks for the insight.

  • Upvote 1

Share this post


Link to post
Share on other sites

Craig:

 

That is really good news. Happy for you! I was hoping that could fix the problem, but of course you never know as set ups differ etc. 

 

Is it a fluke? I don't think so. I have had these 8 minute freezes consistently lately when flying the NGX and 777. I was always expecting it and it happened almost every single time. Expecially if the flights were - well, say more than 2 hours in duration. 

 

I am absolutely positive that after I set unlimited frames in FSX I haven't had a single freeze in the NGX. Haven't checked the 777 yet, but have made many many successful flights with the NGX. 

 

I Have win7, nividia with latest driver,no external frame limiter, ASN, FSUIPC, FSInn.

 

Let me know how if anything changes (it shouldn't)  ^_^

 

Best regards

Share this post


Link to post
Share on other sites

Good Morning, Daniel (at least it is over here!):

 

      I am glad I heard back from you.  Hopefully with your permission, I have alerted those having the same problem in the HIFI forum about your find.  For the past week, every day seemed to bring about a new theory from somebody and now they have fell silent waited for "us" to confirm your find.  I am glad I heard back that you have yet to have a failure.  My system sounds similar to yours but I have VISTA 64 which is the same OS technology so we should have similar results.

 

    I did notice one thing, however.  That is that now that I am able to complete flights and with FSUIPC wind smoothing disabled, I am occasionally getting the sudden aileron roll problem just before touchdown.  When NGX first came out this was solved by using a registered version of FSUIPC with wind smoothing.  Damian (HIFI) claimed that the new ASN program made the wind smoothing setting  unnecessary because there no longer would be the sudden wind shifts.  I agree.  I have not observed sudden wind shifts with ASN, but this sudden hard roll just before touchdown without any indicated wind shear or wake turbulence as an apparent cause is a point of concern if it continues to happen.  Just a heads up if you have had any such incidents.

    

   Since you have extensively tested the NGX, I will skip that test and try a long flight in the MD11 followed by one in the ConcordeX.  I hope that others who are reading this will also try this and report their results.

Share this post


Link to post
Share on other sites

Good morning to you as well, Craig.

 

I wasn't even aware that the issue was so common. I am just glad I could be of assistance.

 

Can't say I've encountered the aileron roll problem though, so I don't have a take on that. :-)

Share this post


Link to post
Share on other sites

Be interested to hear what your results will be with the PMDG 777 on longer flights.  I don't have the plane but I have noticed that there seem to be other issues with it that are causing problems which promise to be alleviated when they release SP1.  So you may experience lockups but due to something not yet fixed in the PMDG model itself and unrelated to 'our' issue.  Do you have ConcordeX?  A test in that model for a long, say 3 hour, transatlantic flight would be telling since it is almost as resource demanding as the NGX.  

Share this post


Link to post
Share on other sites

Hi!

 

I installed FSUIPC but FSX still freezes. Sometimes after a couple of hours, sometimes after as long 9-10 hours of flight. When it freezes I can still hear the sound but can't do anything else. I haven't enabled anything in FSUIPC as many says it's that that causes the freeze. When running AS 2012 I never have problems.

 

VERY FRUSTRATING!!!

 

So I'll try to set the framerate to unlimited and see if I get as lucky as you guys. Will give feedback here when I tried.

Hi!

 

I installed FSUIPC but FSX still freezes. Sometimes after a couple of hours, sometimes after as long 9-10 hours of flight. When it freezes I can still hear the sound but can't do anything else. I haven't enabled anything in FSUIPC as many says it's that that causes the freeze. When running AS 2012 I never have problems.

 

VERY FRUSTRATING!!!

 

So I'll try to set the framerate to unlimited and see if I get as lucky as you guys. Will give feedback here when I tried.

Share this post


Link to post
Share on other sites

Sorry to hear that 'Laban4'.  

 

Since these are lockups (and, yes, you are experiencing exactly what we have been experiencing) they are not permanent crashes but only long pauses while FSX/ASN is completing some mysterious processing.  It will take 8 minutes of patience and then the flight can continue without incident.  Granted it is not what we want to deal with, but after a 9-10 hour flight, the last thing you need to do is close FSX. 

 

The first thing to note (and my testing has confirmed it) this does not seem to be a memory-related issue, however, I have manually increased my VM in windows to 12 GB (formula being 2.5 X VAS and FSX can access up to 4 GB VAS if you have a 64 bit OS.  If 32 bit, then it will be limited to 3 GB).  

 

FSX/ASN both need 'contiguous' memory sequences for updates so increasing VM will allow FSX the maximum resources during your flights.   That adjustment alone eliminated any lockups on short flights for me even with NGX (memory-gobbler!) but this did not end the problem for me on flights lasting over 2 hours.  It would lockup and take 8 minutes to clear.

 

So far setting unlimited frame rates (and disabling any external frame rate limiter) has eliminated the lockups on the longer flights we have tested so far.

 

BTW, if you include your name in the post or in your signature, it will be easier for us to communicate with you.

 

Give these suggestions a try.  The more people we have testing the sooner we can all determine whether this will do the trick but I haven't a clue why changing our frame rate settings would affect our outcome.  But if it works....

Share this post


Link to post
Share on other sites

Hi!

 

VM and VAS? I'm not so good at computers. If increasing as you mentioned, can that help the freeze? And how do I increase it manually?

 

As I wrote before I'll try to set framerate to unlimited and see what hapends. If it still freezes I will try to see for how long. The clock on the panel is in UTC, so it'll be easy to see for how long it has froozen.

 

Best regards/Alex

Share this post


Link to post
Share on other sites

Hi Alex!

 

    I have VISTA 64 so on my machine I pull up control panel and click on system and when the display comes up I select 'advanced system setting' and if you look closely you will see in the middle of the next display something referring to Virtual Memory.  Just click on that and you have several options.  I select to set it "manually' and since FSX can only access 4 GB paging (VAS) I set it to 2.5 x that or 12 GB.  If you have Windows 7 the setup should be very similar if not exactly the same.

 

   As for the time to recover it you still get a "lockup", you will not be able to tell from your FSX clock since everything just stops for that 8 minutes and then resumes at the exact point it stopped.  I just use the clock on my cell phone so I don't disturb the FSX display.

 

    The good news is that I just completed a long 3+ hour flight in the MD11 and again no lockups with frames set to unlimited so for some reason it seems to work.  Daniel (in a previous post) came up with the idea and, last I checked, he is having the same successes that I am having, and believe me, every flight was locking up at about the 2 hour inflight point before so I think it may be the solution as mystifying as it may be.  I guess we'll leave it to the Devs to figure out why it works.

 

Cheers!


@ Daniel:

 

     Completed the test for MD11:  3.2 hours inflight time with heavy weather departure and destination include Thunderstorms, and windshear and very heavy traffic for the first 2 hours and absolutey smooth performance with no stutters or lockups.  Maintained a constant 2.2 GB available VAS throughout the entire flight.  FPS was a little low first part of the flight (15-22 fps) but it was unnoticeable.  As soon as I got out of heavy weather and low heavy traffic my frames went from 35-45 with occasionally as high as 70 fps.

 

     I have one last plane I want to run through the paces and that is the ConcordeX because next to the NGX and 777 it is the most resource demanding.  As I mentioned in the above post...it is a mystery why this works, Daniel, but it is truly a stroke of genius on your part.  We will leave it to the HiFi Devs to figure out why it works.

 

      Oh, yes, and no sudden aileron rolls this trip.  Must have just been a fluke with the B744.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this