Jump to content

Sign in to follow this  
arnobg

FSX CTD during exterior view change

Recommended Posts

For some time now while flying the PMDG 737 NGX if I change to exterior spot view when in the air, or landed at my destination I get a CTD. Anyone else have this or know a fix?

Share this post


Link to post
Share on other sites

Recommend you run AppCrashView and post the results of the latest crash here.  The link to AppCrashView program and instructions are on page 1-2 of the AVSIM CTD Guide.  Most crashes can be fixed by moving your fsx.cfg to a temporary directory, restarting FSX and letting the config rebuild.  If this works for you, then it tells you that your settings were either too high or you have bad tweaks employed.

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

Recommend you run AppCrashView and post the results of the latest crash here.  The link to AppCrashView program and instructions are on page 1-2 of the AVSIM CTD Guide.  Most crashes can be fixed by moving your fsx.cfg to a temporary directory, restarting FSX and letting the config rebuild.  If this works for you, then it tells you that your settings were either too high or you have bad tweaks employed.

 

Best regards,

 

It's not showing up in appcrash but it is in event viewer. Here's the latest one from event viewer this morning where it crashed during exterior spot viewing on departure in overcast conditions:

 

This is with a re-built config with no tweaks except HIGHMEMFIX

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0xbc0
Faulting application start time: 0x01d0415c1e9da038
Faulting application path: C:\FSX\fsx.exe
Faulting module path: unknown
Report Id: 0c42af99-ad52-11e4-b33d-448a5b9d887d

Share this post


Link to post
Share on other sites

Hi Brett,

 

The Event does not show anything.  It must not be serious as there was no Windows Error Report (.wer).  If you shutdown FSX before Windows does it, then there won't be a report made and sent to Microsoft.

 

When you run out of Virtual Address Space (VAS) (Windows only gives FSX 4 GB's) or when you run low on VAS, FSX will freeze up or you will get an Out of Memory (OOM) CTD.  An OOM will not usually show up in a crash report or event viewer but it might show the api.dll as the faulting module.  An OOM or freeze will happen periodically and not on every flight or every flight session.  On one flight there may be little or no weather but in other times really heavy weather in the area.  Just a lot of circumstances.  So you need to investigate whether you are running low on VAS or not and you can do that by using the registered or unregistered version of the FSUIPC utility and set it up as shown in the AVSIM CTD Guide, page 3.  I have my VAS usage logged to the FSUIPC.log and after a flight I can look at the log and see if I was running low on VAS or not. 

 

If you have lots of VAS and the sim still is crashing or freezing, then it is something else but I am pretty sure VAS is the culprit, especially since the faulting module in your error report is unknown.

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

Hi Brett,

 

The Event does not show anything.  It must not be serious as there was no Windows Error Report (.wer).  If you shutdown FSX before Windows does it, then there won't be a report made and sent to Microsoft.

 

When you run out of Virtual Address Space (VAS) (Windows only gives FSX 4 GB's) or when you run low on VAS, FSX will freeze up or you will get an Out of Memory (OOM) CTD.  An OOM will not usually show up in a crash report or event viewer but it might show the api.dll as the faulting module.  An OOM or freeze will happen periodically and not on every flight or every flight session.  On one flight there may be little or no weather but in other times really heavy weather in the area.  Just a lot of circumstances.  So you need to investigate whether you are running low on VAS or not and you can do that by using the registered or unregistered version of the FSUIPC utility and set it up as shown in the AVSIM CTD Guide, page 3.  I have my VAS usage logged to the FSUIPC.log and after a flight I can look at the log and see if I was running low on VAS or not. 

 

If you have lots of VAS and the sim still is crashing or freezing, then it is something else but I am pretty sure VAS is the culprit, especially since the faulting module in your error report is unknown.

 

Best regards,

 

Thank you I will look into the VAS on the guide however, I have not been getting the FSUIPC beep warning prior to the crash, and it ONLY happens when switching to an exterior view in most cases, at the end of an hour flight.

 

One thing I am curious of is the add-on manager that comes with FSDT LAX. I notice it has tweaks in it but I can't tell if they're always being applied to the .cfg or not, I hope not.

Share this post


Link to post
Share on other sites

 

 


I notice it has tweaks in it but I can't tell if they're always being applied to the .cfg or not, I hope not.

 

As long as you don't hit the save to FSX button you should be okay.  I just checked and hit the default button and it did not return my settings to the default but kept them  as they currently are.  I think that if you do enable the tweaks and decide you don't want them, you click the default and those settings you had saved will be removed from your config.  Scary tweaks.  Mostly made for old generation computers that needed some help. 

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

I just had a crash mid flight again while switching to an exterior view with good weather. I did the VAS monitor like you mentioned and results are below. This crash said it had something to do with Simconnect, any thoughts?

 

Here's my log:

 

640 System time = 05/02/2015 12:57:51
      640 FLT path = "C:\Users\Brett\Documents\Flight Simulator X Files\"
      656 Trying to connect to SimConnect Acc/SP2 Oct07 ...
      656 FS path = "C:\FSX\"
      780 LogOptions=00000000 00000001
      780 SIM1 Frictions access gained
      780 Wind smoothing fix is fully installed
      780 G3D.DLL fix attempt installed ok
      780 SimConnect_Open succeeded: waiting to check version okay
      780 Trying to use SimConnect Acc/SP2 Oct07
     7208 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
     7208 Initialising SimConnect data requests now
     7208 FSUIPC Menu entry added
     7208 C:\FSX\FLIGHTS\OTHER\FLTSIM.FLT
     7208 C:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR
    53914 C:\FSX\SimObjects\Airplanes\RealAir Duke Turbine V2\RealAir_Duke_Turbine_v2.AIR
    87720 System time = 05/02/2015 12:59:19, Simulator time = 12:58:52 (17:58Z)
    87720 Aircraft="RealAir Beech Duke Turbine V2 N626N Winglets Ventral"
    88718 Starting everything now ...
    89732 Ready for ASN WX radar
    92041 Advanced Weather Interface Enabled
    92166 Weather Mode now = Theme
   110527 Sim stopped: average frame rate for last 23 secs = 29.7 fps
   890454 Sim stopped: average frame rate for last 763 secs = 28.9 fps
  3067963 Sim stopped: average frame rate for last 2131 secs = 29.3 fps
  3076964 c:\users\brett\documents\flight simulator x files\midflight.FLT
  3515889 Sim stopped: average frame rate for last 434 secs = 29.8 fps
  3543392 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
  3863272 Sim stopped: average frame rate for last 269 secs = 22.3 fps
  3930851 Sim stopped: average frame rate for last 50 secs = 27.3 fps
  3946046 Monitor IPC:024C (S32) = 1898792
  3956108 Monitor IPC:024C (S32) = 1898784
  3966154 Monitor IPC:024C (S32) = 1928016
  3976216 Monitor IPC:024C (S32) = 1927028
  3986247 Monitor IPC:024C (S32) = 1910132
  3996309 Monitor IPC:024C (S32) = 1909620
  4006403 Monitor IPC:024C (S32) = 2240452
  4046464 Monitor IPC:024C (S32) = 2239940
  4066557 Monitor IPC:024C (S32) = 2236632
  4106664 Monitor IPC:024C (S32) = 2235608
  4116726 Monitor IPC:024C (S32) = 2235604
  4126726 Monitor IPC:024C (S32) = 2237656
  4166928 Monitor IPC:024C (S32) = 2236120
  4176974 Monitor IPC:024C (S32) = 2237144
  4237268 Monitor IPC:024C (S32) = 2236632
  4247268 Monitor IPC:024C (S32) = 2237144
  4257268 Monitor IPC:024C (S32) = 2037404
  4267299 Monitor IPC:024C (S32) = 1912820
  4277361 Monitor IPC:024C (S32) = 1912324
  4297454 Monitor IPC:024C (S32) = 1911812
  4307469 Monitor IPC:024C (S32) = 1912324
  4327499 Monitor IPC:024C (S32) = 1903904
  4337561 Monitor IPC:024C (S32) = 1911416
  4347577 Monitor IPC:024C (S32) = 1911928
  4357592 Monitor IPC:024C (S32) = 1910732
  4367623 Monitor IPC:024C (S32) = 1911244
  4417808 Monitor IPC:024C (S32) = 1910732
  4427839 Monitor IPC:024C (S32) = 1912440
  4457932 Monitor IPC:024C (S32) = 1911756
  4467994 Monitor IPC:024C (S32) = 1910560
  4478056 Monitor IPC:024C (S32) = 1910732
  4488087 Monitor IPC:024C (S32) = 1910216
  4498102 Monitor IPC:024C (S32) = 1854748
  4508164 Monitor IPC:024C (S32) = 1874908
  4518195 Monitor IPC:024C (S32) = 1901056
  4528257 Monitor IPC:024C (S32) = 2239468
  4538272 Monitor IPC:024C (S32) = 2239980
  4568365 Monitor IPC:024C (S32) = 2240492
  4628597 Monitor IPC:024C (S32) = 1907988
  4638612 Monitor IPC:024C (S32) = 1910724
  4648643 Monitor IPC:024C (S32) = 1911236
  4658658 Monitor IPC:024C (S32) = 1909700
  4668705 Monitor IPC:024C (S32) = 1910212
  4678751 Monitor IPC:024C (S32) = 1909700
  4688766 Monitor IPC:024C (S32) = 1909356
  4698813 Monitor IPC:024C (S32) = 1910380
  4708859 Monitor IPC:024C (S32) = 1909868
  4728937 Monitor IPC:024C (S32) = 1903884
  4738952 Monitor IPC:024C (S32) = 1904904
  4759029 Monitor IPC:024C (S32) = 1879952
  4769076 Monitor IPC:024C (S32) = 1884740
  4779107 Monitor IPC:024C (S32) = 1894832
  4799184 Monitor IPC:024C (S32) = 1894140
 
crash_zpsabc18817.png

Share this post


Link to post
Share on other sites

This crash said it had something to do with Simconnect, any thoughts?

 

According to page 12 of the AVSIM CTD Guide:

 

HRESULT: 0xc000014B error – Mostly occurs in networked computers. This is a Microsoft.net error. The 0xc000014B is a "broken pipe" exception. A pipe is a communication channel between two applications (such as FSX/P3D and an add-on program like ASN or OPUS, or network). SimConnect offers add-ons the possibility to use pipes to communication with FSX. A "broken pipe" is a situation where one of the pipes no longer exists, while the other tries to communicate using the pipe. A typical scenario would be fsx crashing and then ASN or OPUS tried to use the pipe (communications channel) and the “pipe” was broken. The 014B exception would then occur. Check your network setup or an application that uses SimConnect and troubleshoot.

 

Run the Microsoft.net Repair Tool – Whenever you get a Microsoft.net error like above or Microsoft Visual C++ error (faulting module), run the Microsoft.net repair tool. (link in the AVSIM CTD Guide).

 

I see that it properly loaded in the FSUIPC report but something must have happened during the flight to cause it to crash.

 

I don't know what the following lines in your report mean:

 

110527 Sim stopped: average frame rate for last 23 secs = 29.7 fps

890454 Sim stopped: average frame rate for last 763 secs = 28.9 fps

3067963 Sim stopped: average frame rate for last 2131 secs = 29.3 fps

3076964 c:\users\brett\documents\flight simulator x files\midflight.FLT

3515889 Sim stopped: average frame rate for last 434 secs = 29.8 fps

3543392 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y

3863272 Sim stopped: average frame rate for last 269 secs = 22.3 fps

3930851 Sim stopped: average frame rate for last 50 secs = 27.3 fps

 

I have never seen anything like that in any FSUIPC report before. If you are trying to use a saved flt (midflight.flt), a lot of people have had crashes doing that as not all of the data is still around that was there when you first saved the flight. Other than that, I am brain dead on saving flights and how they are used.

 

That doesn't look like a proper fsuipc.log. There's nothing at the end or did your flight crash. In any case, the report is meaningless unless the flight is completed.

 

Here is one of my FSUIPC logs...

 

 

********* FSUIPC4, Version 4.936 by Pete Dowson *********

Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"

Running inside FSX on Windows 7

Module base=65DE0000

User Name=

User Addr=

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

218 System time = 27/01/2015 15:44:08

218 FLT path = "C:\Users\JimY\Documents\Flight Simulator X Files\"

250 Trying to connect to SimConnect Acc/SP2 Oct07 ...

250 FS path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

343 LogOptions=00000000 00000001

343 SIM1 Frictions access gained

343 Wind smoothing fix is fully installed

343 G3D.DLL fix attempt installed ok

343 SimConnect_Open succeeded: waiting to check version okay

343 Trying to use SimConnect Acc/SP2 Oct07

3619 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

3619 Initialising SimConnect data requests now

3619 FSUIPC Menu entry added

3619 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT

3619 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

3900 Monitor IPC:024C (S32) = 3535532 At FSX setup page - 3.37GBs (enabled ASN and ProATC-X before starting up FSX)

13728 Monitor IPC:024C (S32) = 3428644

23790 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\PMDG 777-300ER\B777-300ER.AIR

23837 Monitor IPC:024C (S32) = 3064736 Selected the PMDG 777 - 2.92GBs

34008 Monitor IPC:024C (S32) = 2658224

43930 Monitor IPC:024C (S32) = 2679208

64148 Monitor IPC:024C (S32) = 2678696

74194 Monitor IPC:024C (S32) = 2692440

84256 Monitor IPC:024C (S32) = 2614816

94240 Monitor IPC:024C (S32) = 2503404

104224 Monitor IPC:024C (S32) = 2461584

114645 Monitor IPC:024C (S32) = 2212028

124645 Monitor IPC:024C (S32) = 2021196 Selected location and time - 1.93GBs (major drop in amount of VAS left but almost 2GB's remaining)

127406 System time = 27/01/2015 15:46:16, Simulator time = 14:44:12 (20:44Z)

127406 Aircraft="PMDG 777-323ER American Airlines"

129793 Weather Mode now = Theme

131946 Starting everything now ...

133178 Advanced Weather Interface Enabled

133646 Ready for ASN WX radar

134582 Monitor IPC:024C (S32) = 1654296 Sitting at Gate at FSDT KORD - 1.58GBs (another major drop after loading FSX and getting to the gate)

144613 Monitor IPC:024C (S32) = 1661156

154644 Monitor IPC:024C (S32) = 1658176

164690 Monitor IPC:024C (S32) = 1697904

174706 Monitor IPC:024C (S32) = 1726616

184768 Monitor IPC:024C (S32) = 1728664

194830 Monitor IPC:024C (S32) = 1684792

204861 Monitor IPC:024C (S32) = 1679540

214907 Monitor IPC:024C (S32) = 1620088

224922 Monitor IPC:024C (S32) = 1574152

234969 Monitor IPC:024C (S32) = 1544456

245031 Monitor IPC:024C (S32) = 1527916

255062 Monitor IPC:024C (S32) = 1527404

275139 Monitor IPC:024C (S32) = 1511212

295216 Monitor IPC:024C (S32) = 1510076

305232 Monitor IPC:024C (S32) = 1496952

325325 Monitor IPC:024C (S32) = 1480760

335355 Monitor IPC:024C (S32) = 1452888

345402 Monitor IPC:024C (S32) = 1433960

355464 Monitor IPC:024C (S32) = 1425156

365510 Monitor IPC:024C (S32) = 1413612

375572 Monitor IPC:024C (S32) = 1421680

395587 Monitor IPC:024C (S32) = 1421004

405603 Monitor IPC:024C (S32) = 1422212

415634 Monitor IPC:024C (S32) = 1417868

425649 Monitor IPC:024C (S32) = 1425968

435695 Monitor IPC:024C (S32) = 1454696

445742 Monitor IPC:024C (S32) = 1454124

455819 Monitor IPC:024C (S32) = 1446000

465866 Monitor IPC:024C (S32) = 1450592

475897 Monitor IPC:024C (S32) = 1424488

485943 Monitor IPC:024C (S32) = 1408168

495943 Monitor IPC:024C (S32) = 1383988

505974 Monitor IPC:024C (S32) = 1389416

515989 Monitor IPC:024C (S32) = 1404228

526020 Monitor IPC:024C (S32) = 1400232

536051 Monitor IPC:024C (S32) = 1395188

546082 Monitor IPC:024C (S32) = 1395620

556097 Monitor IPC:024C (S32) = 1459844

566159 Monitor IPC:024C (S32) = 1467284

576237 Monitor IPC:024C (S32) = 1470188

586267 Monitor IPC:024C (S32) = 1476260

596298 Monitor IPC:024C (S32) = 1479220

606314 Monitor IPC:024C (S32) = 1481004

626391 Monitor IPC:024C (S32) = 1377908

636406 Monitor IPC:024C (S32) = 1399624

646453 Monitor IPC:024C (S32) = 1401220

656499 Monitor IPC:024C (S32) = 1340332

666514 Monitor IPC:024C (S32) = 1300060

676576 Monitor IPC:024C (S32) = 1391920

686592 Monitor IPC:024C (S32) = 1392628

696607 Monitor IPC:024C (S32) = 1411020

706607 Monitor IPC:024C (S32) = 1410164

716622 Monitor IPC:024C (S32) = 1361764

726668 Monitor IPC:024C (S32) = 1362404

736715 Monitor IPC:024C (S32) = 1363172

746761 Monitor IPC:024C (S32) = 1365140

756792 Monitor IPC:024C (S32) = 1358496

766854 Monitor IPC:024C (S32) = 1362496

776885 Monitor IPC:024C (S32) = 1358980

786947 Monitor IPC:024C (S32) = 1353936

796994 Monitor IPC:024C (S32) = 1355904 Waypoint Mobile - 1.29GBs

807056 Monitor IPC:024C (S32) = 1357956

817071 Monitor IPC:024C (S32) = 1360948

827102 Monitor IPC:024C (S32) = 1358980

837133 Monitor IPC:024C (S32) = 1358040

847164 Monitor IPC:024C (S32) = 1357424

857163 Monitor IPC:024C (S32) = 1354260

867178 Monitor IPC:024C (S32) = 1350624

877225 Monitor IPC:024C (S32) = 1345892

887271 Monitor IPC:024C (S32) = 1338276

897333 Monitor IPC:024C (S32) = 1339340

907349 Monitor IPC:024C (S32) = 1348056

927426 Monitor IPC:024C (S32) = 1383584

937441 Monitor IPC:024C (S32) = 1382716 waypoint ADIME - 1.32GBs

947503 Monitor IPC:024C (S32) = 1383872

957534 Monitor IPC:024C (S32) = 1384044

967549 Monitor IPC:024C (S32) = 1381584

997658 Monitor IPC:024C (S32) = 1382652

1007657 Monitor IPC:024C (S32) = 1375704

1017704 Monitor IPC:024C (S32) = 1366712

1027766 Monitor IPC:024C (S32) = 1368680

1037766 Monitor IPC:024C (S32) = 1360448

1047796 Monitor IPC:024C (S32) = 1363396

1057858 Monitor IPC:024C (S32) = 1366472

1067921 Monitor IPC:024C (S32) = 1355704

1077967 Monitor IPC:024C (S32) = 1357392

1087982 Monitor IPC:024C (S32) = 1365632

1098029 Monitor IPC:024C (S32) = 1368916

1118106 Monitor IPC:024C (S32) = 1370456 waypoint OTENS (nearing TOC - FL280) - 1.31GBs

1128153 Monitor IPC:024C (S32) = 1371824

1138152 Monitor IPC:024C (S32) = 1370440

1148167 Monitor IPC:024C (S32) = 1336104

1158214 Monitor IPC:024C (S32) = 1336956

1169228 Monitor IPC:024C (S32) = 1355040

1179040 Monitor IPC:024C (S32) = 1323184

1189040 Monitor IPC:024C (S32) = 1258076

1199117 Monitor IPC:024C (S32) = 1307652

1209117 Monitor IPC:024C (S32) = 1301696

1219148 Monitor IPC:024C (S32) = 1254224

1229148 Monitor IPC:024C (S32) = 1320076

1239194 Monitor IPC:024C (S32) = 1314344

1249256 Monitor IPC:024C (S32) = 1330636

1259303 Monitor IPC:024C (S32) = 1330056

1269333 Monitor IPC:024C (S32) = 1320488

1279349 Monitor IPC:024C (S32) = 1317240

1289489 Monitor IPC:024C (S32) = 1316032

1299520 Monitor IPC:024C (S32) = 1318516

1309566 Monitor IPC:024C (S32) = 1263360

1319597 Monitor IPC:024C (S32) = 1298712

1329628 Monitor IPC:024C (S32) = 1298196

1339705 Monitor IPC:024C (S32) = 1293044

1349705 Monitor IPC:024C (S32) = 1292296 waypoint RIEKE - 1.23GBs

1359720 Monitor IPC:024C (S32) = 1289012

1379813 Monitor IPC:024C (S32) = 1288016

1389844 Monitor IPC:024C (S32) = 1235040

1399844 Monitor IPC:024C (S32) = 1270652

1409906 Monitor IPC:024C (S32) = 1270140

1419937 Monitor IPC:024C (S32) = 1277000

1429952 Monitor IPC:024C (S32) = 1259000

1439999 Monitor IPC:024C (S32) = 1258144

1450014 Monitor IPC:024C (S32) = 1257632

1470107 Monitor IPC:024C (S32) = 1258656

1480153 Monitor IPC:024C (S32) = 1256264

1490184 Monitor IPC:024C (S32) = 1212404

1500199 Monitor IPC:024C (S32) = 1274388

1510277 Monitor IPC:024C (S32) = 1277724

1520308 Monitor IPC:024C (S32) = 1273556

1530370 Monitor IPC:024C (S32) = 1275496 waypoint GAABE - 1.22GBs

1540416 Monitor IPC:024C (S32) = 1275572

1550463 Monitor IPC:024C (S32) = 1289364

1560478 Monitor IPC:024C (S32) = 1290732

1570525 Monitor IPC:024C (S32) = 1286836

1580587 Monitor IPC:024C (S32) = 1296404

1590617 Monitor IPC:024C (S32) = 1283908

1600680 Monitor IPC:024C (S32) = 1277076

1610726 Monitor IPC:024C (S32) = 1288612

1620788 Monitor IPC:024C (S32) = 1286644 waypoint SPOOL - 1.23GBs

1630803 Monitor IPC:024C (S32) = 1277076

1640834 Monitor IPC:024C (S32) = 1276432

1650849 Monitor IPC:024C (S32) = 1283264

1660912 Monitor IPC:024C (S32) = 1281896

1670942 Monitor IPC:024C (S32) = 1299380

1680973 Monitor IPC:024C (S32) = 1300440

1690989 Monitor IPC:024C (S32) = 1295804

1701019 Monitor IPC:024C (S32) = 1294160

1711035 Monitor IPC:024C (S32) = 1292832

1721081 Monitor IPC:024C (S32) = 1301040 waypoint AIR - 1.24GBs

1731096 Monitor IPC:024C (S32) = 1290632

1741158 Monitor IPC:024C (S32) = 1291784

1761205 Monitor IPC:024C (S32) = 1287764

1771204 Monitor IPC:024C (S32) = 1278796

1781219 Monitor IPC:024C (S32) = 1280740

1791250 Monitor IPC:024C (S32) = 1291744

1801266 Monitor IPC:024C (S32) = 1292428

1821359 Monitor IPC:024C (S32) = 1289092

1831421 Monitor IPC:024C (S32) = 1204728

1841467 Monitor IPC:024C (S32) = 1266172

1851514 Monitor IPC:024C (S32) = 1266688

1861560 Monitor IPC:024C (S32) = 1267204

1871622 Monitor IPC:024C (S32) = 1217152

1881622 Monitor IPC:024C (S32) = 1253000

1891653 Monitor IPC:024C (S32) = 1208628

1901730 Monitor IPC:024C (S32) = 1273540

1911746 Monitor IPC:024C (S32) = 1274348

1921792 Monitor IPC:024C (S32) = 1271588

1951885 Monitor IPC:024C (S32) = 1272100 TOD - 1.21GBs

1961947 Monitor IPC:024C (S32) = 1271588

1971978 Monitor IPC:024C (S32) = 1274068

1981993 Monitor IPC:024C (S32) = 1272100

1992024 Monitor IPC:024C (S32) = 1282300

2002055 Monitor IPC:024C (S32) = 1292212

2012117 Monitor IPC:024C (S32) = 1288276

2022132 Monitor IPC:024C (S32) = 1291356

2032210 Monitor IPC:024C (S32) = 1286872

2042256 Monitor IPC:024C (S32) = 1289388

2052318 Monitor IPC:024C (S32) = 1286912

2062333 Monitor IPC:024C (S32) = 1288232

2072411 Monitor IPC:024C (S32) = 1289908

2082473 Monitor IPC:024C (S32) = 1291808

2092441 Monitor IPC:024C (S32) = 1292324

2102457 Monitor IPC:024C (S32) = 1284532

2112472 Monitor IPC:024C (S32) = 1288628

2122503 Monitor IPC:024C (S32) = 1287300

2132534 Monitor IPC:024C (S32) = 1285420

2152627 Monitor IPC:024C (S32) = 1232248

2162626 Monitor IPC:024C (S32) = 1238896

2172673 Monitor IPC:024C (S32) = 1233724

2182735 Monitor IPC:024C (S32) = 1232396

2192781 Monitor IPC:024C (S32) = 1241100

2202828 Monitor IPC:024C (S32) = 1241612

2222858 Monitor IPC:024C (S32) = 1241100

2232874 Monitor IPC:024C (S32) = 1240484

2242920 Monitor IPC:024C (S32) = 1248676

2252982 Monitor IPC:024C (S32) = 1249188

2263013 Monitor IPC:024C (S32) = 1247276

2273028 Monitor IPC:024C (S32) = 1246764

2283090 Monitor IPC:024C (S32) = 1247328

2293090 Monitor IPC:024C (S32) = 1245108

2313136 Monitor IPC:024C (S32) = 1199624

2323214 Monitor IPC:024C (S32) = 1268040

2333229 Monitor IPC:024C (S32) = 1252360

2353306 Monitor IPC:024C (S32) = 1251336

2363322 Monitor IPC:024C (S32) = 1252360

2373352 Monitor IPC:024C (S32) = 1251848

2393430 Monitor IPC:024C (S32) = 1250480

2403476 Monitor IPC:024C (S32) = 1249112

2413523 Monitor IPC:024C (S32) = 1248600

2443678 Monitor IPC:024C (S32) = 1250568

2453724 Monitor IPC:024C (S32) = 1247196

2483879 Monitor IPC:024C (S32) = 1247708

2493910 Monitor IPC:024C (S32) = 1248220

2534034 Monitor IPC:024C (S32) = 1248932

2544064 Monitor IPC:024C (S32) = 1247564

2554111 Monitor IPC:024C (S32) = 1246856

2564157 Monitor IPC:024C (S32) = 1248624

2574173 Monitor IPC:024C (S32) = 1246656

2584203 Monitor IPC:024C (S32) = 1249140

2594234 Monitor IPC:024C (S32) = 1247604

2604265 Monitor IPC:024C (S32) = 1260100

2614312 Monitor IPC:024C (S32) = 1260784

2624374 Monitor IPC:024C (S32) = 1256596

2634436 Monitor IPC:024C (S32) = 1255228

2644482 Monitor IPC:024C (S32) = 1255912

2654482 Monitor IPC:024C (S32) = 1257280 waypoint CSN - 1.19

2664544 Monitor IPC:024C (S32) = 1247968

2674544 Monitor IPC:024C (S32) = 1254536

2684559 Monitor IPC:024C (S32) = 1249168

2694574 Monitor IPC:024C (S32) = 1248144

2704636 Monitor IPC:024C (S32) = 1250112

2714667 Monitor IPC:024C (S32) = 1238784

2734729 Monitor IPC:024C (S32) = 1240152

2754775 Monitor IPC:024C (S32) = 1312408

2915331 Monitor IPC:024C (S32) = 1312920

2935424 Monitor IPC:024C (S32) = 1312408

3377203 Monitor IPC:024C (S32) = 1274260

3387203 Monitor IPC:024C (S32) = 1272892

3407358 Monitor IPC:024C (S32) = 1270460

3417405 Monitor IPC:024C (S32) = 1180812

3427467 Monitor IPC:024C (S32) = 1176032

3437467 Monitor IPC:024C (S32) = 1159156

3447497 Monitor IPC:024C (S32) = 1163956

3457513 Monitor IPC:024C (S32) = 1136948 waypoint LUSIE (top of the Approach to Runway 01C FlightBeam KIAD) - 1.08GBs

3467559 Monitor IPC:024C (S32) = 1137884

3477590 Monitor IPC:024C (S32) = 1138056

3487605 Monitor IPC:024C (S32) = 1131732

3497652 Monitor IPC:024C (S32) = 1137656

3507698 Monitor IPC:024C (S32) = 1133956

3517729 Monitor IPC:024C (S32) = 1109444

3527744 Monitor IPC:024C (S32) = 1113120

3537775 Monitor IPC:024C (S32) = 1116456

3547806 Monitor IPC:024C (S32) = 1100364

3557821 Monitor IPC:024C (S32) = 1097880

3567899 Monitor IPC:024C (S32) = 1078092

3577867 Monitor IPC:024C (S32) = 1040760

3587914 Monitor IPC:024C (S32) = 971232 full left turn toward Runway 01C

3597960 Monitor IPC:024C (S32) = 734664

3608022 Monitor IPC:024C (S32) = 731864

3618053 Monitor IPC:024C (S32) = 701532

3628100 Monitor IPC:024C (S32) = 698212

3638115 Monitor IPC:024C (S32) = 695044

3648208 Monitor IPC:024C (S32) = 696412

3658270 Monitor IPC:024C (S32) = 698292

3668286 Monitor IPC:024C (S32) = 700696

3678332 Monitor IPC:024C (S32) = 685104

3688347 Monitor IPC:024C (S32) = 646012

3698409 Monitor IPC:024C (S32) = 628368

3718549 Monitor IPC:024C (S32) = 630272

3728596 Monitor IPC:024C (S32) = 626336 halfway down the approach - 612 MBs

3738642 Monitor IPC:024C (S32) = 631040

3758704 Monitor IPC:024C (S32) = 634976

3768766 Monitor IPC:024C (S32) = 643852

3778812 Monitor IPC:024C (S32) = 641116

3788843 Monitor IPC:024C (S32) = 623332

3798905 Monitor IPC:024C (S32) = 620200

3808905 Monitor IPC:024C (S32) = 614220

3818920 Monitor IPC:024C (S32) = 606216

3828951 Monitor IPC:024C (S32) = 614980

3838951 Monitor IPC:024C (S32) = 611716

3848982 Monitor IPC:024C (S32) = 619720

3859012 Monitor IPC:024C (S32) = 615752

3869074 Monitor IPC:024C (S32) = 560144

3879105 Monitor IPC:024C (S32) = 613812 Touchdown!!! 599 MBs

3919166 Monitor IPC:024C (S32) = 615296

3920009 Sim stopped: average frame rate for last 3793 secs = 26.9 fps

3929244 Monitor IPC:024C (S32) = 534984

3939244 Monitor IPC:024C (S32) = 528844

3969368 Monitor IPC:024C (S32) = 513464 Gate 501 MBs

3972519 Sim stopped: average frame rate for last 50 secs = 18.6 fps

3980007 System time = 27/01/2015 16:50:28, Simulator time = 17:15:06 (22:15Z)

3980007 *** FSUIPC log file being closed

Average frame rate for running time of 3843 secs = 26.8 fps

G3D fix: Passes 119011, Null pointers 0, Bad pointers 0, Separate instances 0

Memory managed: 1720 Allocs, 1720 Freed

********* FSUIPC Log file closed ***********

 

 

 

Best regards,

 


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

I will look into the guide as you mentioned for the simconnect issue however, I am not using multiple computers on my FSX setup, I have a wireless router/modem, and my PC is plugged straight into that. 

 

As far as the odd FSUIPC log, i did have a crash, re-loaded the flight and continued.

Share this post


Link to post
Share on other sites

This is a new one, never seen it before and appcrash picked it up:

 

 

Version=1
EventType=APPCRASH
EventTime=130676602504320927
ReportType=2
Consent=1
ReportIdentifier=b663c11f-ada0-11e4-9e8b-448a5b9d887d
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=ASNext.exe
Sig[1].Name=Application Version
Sig[1].Value=1.0.5410.16208
Sig[2].Name=Application Timestamp
Sig[2].Value=544a85af
Sig[3].Name=Fault Module Name
Sig[3].Value=mscorwks.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=2.0.50727.5485
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=53a121fa
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=001568cf
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
UI[2]=D:\Program Files\ASNext_FSX\ASNext.exe
UI[3]=ASNext has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=D:\Program Files\ASNext_FSX\ASNext.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Windows\syswow64\KERNEL32.dll
LoadedModule[4]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[5]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[7]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[8]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[9]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[10]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[11]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[12]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[13]=C:\Windows\syswow64\GDI32.dll
LoadedModule[14]=C:\Windows\syswow64\USER32.dll
LoadedModule[15]=C:\Windows\syswow64\LPK.dll
LoadedModule[16]=C:\Windows\syswow64\USP10.dll
LoadedModule[17]=C:\Windows\system32\IMM32.DLL
LoadedModule[18]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[19]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
LoadedModule[20]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\MSVCR80.dll
LoadedModule[21]=C:\Windows\syswow64\shell32.dll
LoadedModule[22]=C:\Windows\syswow64\ole32.dll
LoadedModule[23]=C:\Windows\syswow64\profapi.dll
LoadedModule[24]=C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\38bf604432e1a30c954b2ee40d6a2d1c\mscorlib.ni.dll
LoadedModule[25]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsec.dll
LoadedModule[26]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[27]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[28]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[29]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dll
LoadedModule[30]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[31]=C:\Windows\system32\rsaenh.dll
LoadedModule[32]=C:\Windows\syswow64\imagehlp.dll
LoadedModule[33]=C:\Windows\system32\ncrypt.dll
LoadedModule[34]=C:\Windows\system32\bcrypt.dll
LoadedModule[35]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[36]=C:\Windows\syswow64\USERENV.dll
LoadedModule[37]=C:\Windows\system32\GPAPI.dll
LoadedModule[38]=C:\Windows\system32\cryptnet.dll
LoadedModule[39]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[40]=C:\Windows\system32\SensApi.dll
LoadedModule[41]=C:\Windows\system32\uxtheme.dll
LoadedModule[42]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll
LoadedModule[43]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System\908ba9e296e92b4e14bdc2437edac603\System.ni.dll
LoadedModule[44]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Drawing\836e10dfd0811b303553216f5cb092ef\System.Drawing.ni.dll
LoadedModule[45]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Windows.Forms\1453d9e9a4989833ef3db4b22549ba1a\System.Windows.Forms.ni.dll
LoadedModule[46]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[47]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\gdiplus.dll
LoadedModule[48]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[49]=C:\Windows\system32\dwmapi.dll
LoadedModule[50]=C:\Windows\system32\shfolder.dll
LoadedModule[51]=C:\Windows\system32\version.dll
LoadedModule[52]=C:\Windows\syswow64\oleaut32.dll
LoadedModule[53]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.dll
LoadedModule[54]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Configuration\237d509a79aeef6e4635b09450d98f2a\System.Configuration.ni.dll
LoadedModule[55]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Xml\d49908aa93a23c84847b1f8b1b667860\System.Xml.ni.dll
LoadedModule[56]=D:\Program Files\ASNext_FSX\HiFiSimConnect1.dll
LoadedModule[57]=C:\Windows\syswow64\ws2_32.dll
LoadedModule[58]=C:\Windows\syswow64\NSI.dll
LoadedModule[59]=C:\Windows\system32\mswsock.dll
LoadedModule[60]=C:\Windows\System32\wshtcpip.dll
LoadedModule[61]=C:\Windows\System32\wship6.dll
LoadedModule[62]=D:\Program Files\ASNext_FSX\HiFiSimConnect2.dll
LoadedModule[63]=C:\Windows\assembly\GAC_32\Microsoft.FlightSimulator.SimConnect\10.0.61259.0__31bf3856ad364e35\Microsoft.FlightSimulator.SimConnect.dll
LoadedModule[64]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[65]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\MSVCP80.dll
LoadedModule[66]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\msvcm80.dll
LoadedModule[67]=C:\Windows\system32\rasapi32.dll
LoadedModule[68]=C:\Windows\system32\rasman.dll
LoadedModule[69]=C:\Windows\system32\rtutils.dll
LoadedModule[70]=C:\Windows\system32\winhttp.dll
LoadedModule[71]=C:\Windows\system32\webio.dll
LoadedModule[72]=C:\Windows\system32\credssp.dll
LoadedModule[73]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[74]=C:\Windows\system32\WINNSI.DLL
LoadedModule[75]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[76]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[77]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[78]=C:\Windows\system32\DNSAPI.dll
LoadedModule[79]=C:\Windows\system32\rasadhlp.dll
LoadedModule[80]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[81]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualBas#\bb21380c3d4870a81038f30e1a00bcd5\Microsoft.VisualBasic.ni.dll
LoadedModule[82]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Management\99cdfef98595ed91f14936cf52a49c54\System.Management.ni.dll
LoadedModule[83]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\wminet_utils.dll
LoadedModule[84]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[85]=C:\Windows\system32\wbem\wmiutils.dll
LoadedModule[86]=C:\Windows\system32\wbemcomn.dll
LoadedModule[87]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[88]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[89]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[90]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[91]=C:\Windows\System32\comdlg32.dll
LoadedModule[92]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[93]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[94]=C:\Windows\system32\propsys.dll
LoadedModule[95]=C:\Windows\system32\ntmarta.dll
LoadedModule[96]=C:\Windows\system32\explorerframe.dll
LoadedModule[97]=C:\Windows\system32\DUser.dll
LoadedModule[98]=C:\Windows\system32\DUI70.dll
LoadedModule[99]=C:\Windows\system32\apphelp.dll
LoadedModule[100]=C:\Windows\system32\EhStorShell.dll
LoadedModule[101]=C:\Windows\system32\ntshrui.dll
LoadedModule[102]=C:\Windows\system32\srvcli.dll
LoadedModule[103]=C:\Windows\system32\cscapi.dll
LoadedModule[104]=C:\Windows\system32\slc.dll
LoadedModule[105]=C:\Windows\system32\msls31.dll
LoadedModule[106]=C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll
LoadedModule[107]=C:\Windows\system32\XmlLite.dll
LoadedModule[108]=C:\Windows\system32\LINKINFO.dll
LoadedModule[109]=C:\Windows\system32\NetworkExplorer.dll
LoadedModule[110]=C:\Windows\system32\MPR.dll
LoadedModule[111]=C:\Windows\System32\drprov.dll
LoadedModule[112]=C:\Windows\System32\WINSTA.dll
LoadedModule[113]=C:\Windows\System32\ntlanman.dll
LoadedModule[114]=C:\Windows\System32\davclnt.dll
LoadedModule[115]=C:\Windows\System32\DAVHLPR.dll
LoadedModule[116]=C:\Windows\system32\SearchFolder.dll
LoadedModule[117]=C:\Windows\System32\StructuredQuery.dll
LoadedModule[118]=C:\Windows\System32\Secur32.dll
LoadedModule[119]=C:\Windows\system32\netutils.dll
LoadedModule[120]=C:\Windows\SysWOW64\thumbcache.dll
LoadedModule[121]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[122]=C:\Windows\system32\SHDOCVW.dll
LoadedModule[123]=C:\Windows\system32\ieframe.DLL
LoadedModule[124]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[125]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[126]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[127]=C:\Windows\system32\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[128]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[129]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[130]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[131]=C:\Windows\syswow64\iertutil.dll
LoadedModule[132]=C:\Windows\system32\mssprxy.dll
LoadedModule[133]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[134]=C:\Windows\system32\samcli.dll
LoadedModule[135]=C:\Windows\system32\SAMLIB.dll
LoadedModule[136]=C:\Windows\SysWOW64\oleacc.dll
LoadedModule[137]=C:\Windows\system32\wkscli.dll
LoadedModule[138]=C:\Windows\system32\PortableDeviceApi.dll
LoadedModule[139]=C:\Windows\system32\EhStorAPI.dll
LoadedModule[140]=C:\Windows\syswow64\urlmon.dll
LoadedModule[141]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[142]=C:\Windows\syswow64\WININET.dll
File[0].CabName=WERInternalMetadata.xml
File[0].Path=WER7F8D.tmp.WERInternalMetadata.xml
File[0].Flags=65538
File[0].Type=5
File[0].Original.Path=C:\Users\Brett\AppData\Local\Temp\WER7F8D.tmp.WERInternalMetadata.xml
File[1].CabName=memory.hdmp
File[1].Path=WER7F8E.tmp.hdmp
File[1].Flags=2097152
File[1].Type=3
File[1].Original.Path=C:\Users\Brett\AppData\Local\Temp\WER7F8E.tmp.hdmp
File[2].CabName=minidump.mdmp
File[2].Path=WER85B7.tmp.mdmp
File[2].Flags=2162690
File[2].Type=2
File[2].Original.Path=C:\Users\Brett\AppData\Local\Temp\WER85B7.tmp.mdmp
FriendlyEventName=APPCRASH
ConsentKey=APPCRASH
AppName=ASNext
AppPath=D:\Program Files\ASNext_FSX\ASNext.exe
ReportDescription=Stopped working

Share this post


Link to post
Share on other sites

 

 


LoadedModule[65]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\MSVCP80.dll
LoadedModule[66]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\msvcm80.dll

 

You are using a really old version of Microsoft Visual C++2005.  Your version is 4940 and the latest is 6195.  Check out the AVSIM CTD Guide, page 6, where we show you the proper versions.  You need Microsoft Visual C++2005 w/SP1.  We have included a link in the guide for you to follow to get the latest update.

 

ASN crashed and the faulting module is part of Microsoft.net 2.0. On page 7 of the CTD Guide we discuss Microsoft.net.  There's a verification tool where you can verify if the versions installed and whether all components are there and up-to-date.  There is also a Microsoft.net Repair Tool.  For FSX you need dotnet 2.0 through the latest.  I'm not sure which version is used by ASN but I do know they use Microsoft Visual C++2010 for their installation program (or did up to recently).  Most current developers are using later versions of Microsoft.net and Microsoft Visuals as they update/upgrade their programs.  The dotnet 2.0 file that crashed ASN is the latest dotnet 2.0 version. 

 

I would also uninstall ASN completely and reinstall making sure you right click the installation program and run it as the administrator.  You should also have UAC turned off and any anti-virus program as ASN needs to make proper changes to the system registry.

 

At the end of your crash report, I have never seen that information.  It just shows where the windows error reporting dump file is located.  I suspect you added it to your report?

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

You are using a really old version of Microsoft Visual C++2005.  Your version is 4940 and the latest is 6195.  Check out the AVSIM CTD Guide, page 6, where we show you the proper versions.  You need Microsoft Visual C++2005 w/SP1.  We have included a link in the guide for you to follow to get the latest update.

 

ASN crashed and the faulting module is part of Microsoft.net 2.0. On page 7 of the CTD Guide we discuss Microsoft.net.  There's a verification tool where you can verify if the versions installed and whether all components are there and up-to-date.  There is also a Microsoft.net Repair Tool.  For FSX you need dotnet 2.0 through the latest.  I'm not sure which version is used by ASN but I do know they use Microsoft Visual C++2010 for their installation program (or did up to recently).  Most current developers are using later versions of Microsoft.net and Microsoft Visuals as they update/upgrade their programs.  The dotnet 2.0 file that crashed ASN is the latest dotnet 2.0 version. 

 

I would also uninstall ASN completely and reinstall making sure you right click the installation program and run it as the administrator.  You should also have UAC turned off and any anti-virus program as ASN needs to make proper changes to the system registry.

 

At the end of your crash report, I have never seen that information.  It just shows where the windows error reporting dump file is located.  I suspect you added it to your report?

 

Best regards,

 

I'll be honest I'm pretty good using computers, but I can not figure out what Microsoft Visuals files I need using the guide and Microsofts download page. It's a needle in a haystack and there's tons and tons of visuals files that I don't know which one's to get. Single files, packages, all with similar names, none match your description or look like the screenshot in the guide.

 

Is this up to date? I can't find the second file on there is this correct now?

 

 

 

 

Do I need the 2012 files it appears those may be for Windows 8?

 

What about the 2012 files are those just for windows 8?

 

 

[url=http://s40.photobucket.com/user/arnobg/media/visuals_zpsb42b8e1d.png.html'>visuals_zpsb42b8e1d.png

Share this post


Link to post
Share on other sites

Also, when downloading all the older .NET framework files, do I want (x86)?

FSX, FSX-SE, and P3D are all 32 bit applications so you only need the 32 bit (x86) version.

 

The Microsoft Visuals you have installed are all okay except Microsoft Visual C++2005.  You need version 8.0.56336.  Yours is 8.0.50727.42.  Here's the version you want to install - http://www.microsoft.com/en-us/download/details.aspx?id=5638. This is the required SP1 to Microsoft Visual 2005. It was suppose to be included in Acceleration but Acceleration was released too soon to get it included.

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

Thanks for all the help. So far I haven't had a single CTD during view changes/menu use. I'm not sure what solved it but I updated all the things you suggested, and added the UAI.dll file to my main FSX folder.

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  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    35%
    $8,760.00 of $25,000.00 Donate Now
×
×
  • Create New...