OOMS

[colfmedion 1]

Hi,

My Operating System
    Windows 10 Pro 64-bit
CPU
    Intel Core i7 4770K @ 3.50GHz    28 °C
    Haswell 22nm Technology
RAM
    16.0GB Dual-Channel DDR3 @ 1199MHz (11-13-13-32)
Motherboard
    ASUSTeK COMPUTER INC. MAXIMUS VI HERO (SOCKET 1150)    29 °C
Graphics
    U28D590 (2560x1440@59Hz)
    2047MB NVIDIA GeForce GTX 980 Ti (ZOTAC International)    36 °C
Storage
    238GB Crucial_CT256M550SSD1 (SSD)    28 °C
    111GB Samsung SSD 840 Series (SSD)    24 °C
    931GB SAMSUNG HD103UJ (SATA)    27 °C
Optical Drives
    ATAPI iHAS324 E
    HL-DT-ST DVDRAM GH24NSD1
Audio
    Sound Blaster Z.

 

My Problem:
Prior to Windows Creator Autumn Update I could throw anything at FSX and never get OOMS. Since the update and all updates following on from the Autumn Update I am lucky if I get 10 minutes before I get OOMS. By anything - I have a lot of Paid for Add On Scenery including All New York Airports including Manhattan X, UK 2000 Scenery -Heathrow, Gatwick, Manchester and others, Aerosoft Schipol and AES, Airport Enhancer, Steves DX10, RexWorld Airports, etc. I must emphasise that prior to Creator Autumn Update I could run everything with no hint of OOMS. My OS is on one SSD and FSX is on its own SSD. All other programs and media files are on a separate 1000gb HD. I have tried every permutation I can think of _ Completely fresh install of FSX (the basics and then with the Acceleration Pack) on different SSDs and different HDs, rebuild of FSX CFG etc, etc. Even a barebones FSX with nothing more than original FSX Files still gives me OOMS. I have been wrestling with this since Autumn of 2017. I have even gone back to prior the Autumn Update and Fresh installations of Windows 10 but I still get the same results. I have tried FSX Steam Edition with same results. I have currently loaded XPlane 11 which does not give me OOMS which is to be expected but it is a whole new learning curve and whilst I will persevere with it I have spent years on FSX and its predecesors and arrived at what I considered to be Heaven. But that has now gone. For the short time I am able to fly in FSX it is everything I could hope for - I am just a "Dream" pilot. I am still convinced (myself!!) that it is something so very simple but what it is I have no idea.
I would be more than grateful for any advice to help me get back to "Heaven" if possible.
Thanks
Colfmedion

[vicsim 1]

Have you tried Windows 7?  I am not really sure why you are experiencing that issue.  I run Windows 10 pro 1709 16299, what version are you running? I am also on FSX-SE and have 6 add ons running with the Aerosoft A318/319 pack as well as several payware airports....no issues.  Run Winver on your machine and see what version you are running, see if there is another update available.

[Jim Young 2,356]

As stated on page 19, AVSIM CTD Guide, we recommend installing a previous version of the uiautomationcore.dll if you have the boxed version of FSX (FSX-SE already had a version installed when you install that).  That file has some bearing on system memory utilization.  When I first set up my computer early last year and installed Windows 10 for the first time, I could not get FSX to run at all until I put the uiautomationcore.dll in my main FSX folder.  However, just last month I had to reinstall FSX and all of my addons as I did a Windows 10 reset (do not recommend!!).  This time I left the uiautomationcore.dll and it is working great without it.  It might be that the installing the latest Windows Updates fixed it and we no longer need the uiautomationcore.dll. 

There have been a lot of Windows Updates since the Autumn 1709 version.  X-Plane 11 uses a lot more resources so not sure why it is not giving you an OOM and FSX is crashing with an OOM.  An OOM is mostly caused by high FSX settings (in X-Plane you can set your sliders high and not have any problems).  FSX cannot handle high slider settings.  It is impossible to run with high settings in FSX for any length of time.  It simply eats up Virtual Address Space (VAS) way too fast if you do that.  The higher the settings, the faster the crash.  Autogen in FSX eats a lot of VAS too so those settings must never be above normal.  AI uses a lot of VAS too.  There is no solution to this problem other than buying a 64-bit application like X-Plane or P3DV4.

[colfmedion 1]

Hi,

Thanks for responses.

I am currently on Windows 10 Pro 1709 16299. Have just downloaded latest version of the FSX Configuration Guide so I will have a look at that. Do have the uiautomationcore.dll installed but not sure what version. Like I said,I have tried every setting and installation I can think of including the very basic FSX and with everything set to absolute minimum and yet I still get the OOMS. I will keep trying.

 

[Jim Young 2,356]

1 hour ago, colfmedion said:

I am currently on Windows 10 Pro 1709 16299

Should have version 16299.248.

1 hour ago, colfmedion said:

Have just downloaded latest version of the FSX Configuration Guide

That guide might help too but there are more suggestions for fixing the OOM in the AVSIM CTD Guide.

 

1 hour ago, colfmedion said:

Do have the uiautomationcore.dll installed but not sure what version

If you want to know, just go to your main FSX folder, right click on uiautomationcore.dll and select Properties and then look under the Details tab.

1 hour ago, colfmedion said:

I can think of including the very basic FSX and with everything set to absolute minimum and yet I still get the OOMS

If you have FSX at basic and absolute minimum sliders, then something is seriously wrong with your computer.  The settings in the AVSIM FSX Configuration Guide should work on most systems.  Still, with those settings, you will likely run out of VAS after 2 hours of flight.  OOM's are only caused by one thing - running out of Virtual Address Space (VAS).  Microsoft gave you only 4GB's with Windows 10, 64 bit (much less with Windows 10, 32-bit).  When that is used up, FSX will crash.  There is no setting or configuration that can stop that from happening and today's modern systems makes it happen even faster as textures and scenery and gauges and sound are just loaded a lot faster and filling up VAS a little faster.

[colfmedion 1]

Have checked and all versions are up to date. I had a VAS monitor installed but I wasn't using it. Took it off and downloaded a fresh copy. It is RED from initially loading FSX and gives me 3mb of VAS!! Have just done a flight from Philly to Newark which only takes about 20 minutes and after about 10 minutes VAS is down to 0!! About 5 minutes later as I am coming in to land FSX crashes - OOMS. I get the same results using FSX Steam but as expected XPlane 11 is fine. I am no expert but it would suggest to me that PC is okay but could be wrong.

I guess I will keep fiddiling with it and hope the problem disappears as quickly as it came. I will download AVSIM CTD Guide and study that

Colfmedion

[Jim Young 2,356]

Your computer is more than able to run FSX with the latest update of Windows 10 (I had the i7 4770K before updating to this system).  I have it installed with the latest update (updated to 16299.251 last night).  For FSX, nothing can change except the addons.  I have my FSX config settings set as in the AVSIM FSX Configuration Guide.  Things are a little blurry some places even with max texture resolution.  That's because the video card, no matter how powerful, cannot render fast enough when setting are set high.  But at FSDT airports, things are crystal clear and I have been getting FPS in the 50's and 60's (which does not eliminate the "blurries".  You can have 200 fps and still have the blurries).  As in the AVSIM FSX guide, I have unlimited frames and probably should reset to 30 fps).  You would think with my system overclocked to 5GHz, you would not see the blurries or have issues whatsoever, but you do as the engine is b-a-d.

My VAS starts out at less than 2GB's but it stays that way most of the flight until the end then I'm in the MB's and, when I get below 500 MB's on approach, I get scared.  I use to have many flights where they were monitored by the FSUIPC utility to prove I was getting 50-60 fps most of the flight and showed the best/worst VAS readings during the flight.  I lost them when I had to reset Windows 10 (which told me at the beginning of the reset that it would not harm FSX or my addons but it destroyed everything).  I will try to do another flight in the PMDG 737 (anything higher like the 777 or 747 is not recommended) and provide the log.  I do remember several flights at 200MB's on approach.

 

[Jim Young 2,356]

As promised, here's a report (log) of a flight from KLAX to KSFO today -

Spoiler

 1578 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
     1578 Initialising SimConnect data requests now
     1578 FSUIPC Menu entry added
     1594 G:\FSX\FLIGHTS\OTHER\FLTSIM.FLT
     1594 G:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR
     2547 Monitor IPC:024C (S32) = 3332748
    12531 Monitor IPC:024C (S32) = 3269656
    22594 Monitor IPC:024C (S32) = 3210184
    32594 Monitor IPC:024C (S32) = 3117688
    42844 Monitor IPC:024C (S32) = 3119736
    56000 G:\FSX\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.AIR
    59016 User Aircraft ID 1 supplied, now being used
    59063 Aircraft loaded: running normally now ...
    62719 Monitor IPC:024C (S32) = 1671792
    72844 Monitor IPC:024C (S32) = 1691220
    84359 Monitor IPC:024C (S32) = 1609972
    84719 System time = 08/03/2018 13:11:21, Simulator time = 13:09:58 (21:09Z)
    84719 Aircraft="PMDG 737-800NGX PMDG House Winglets"
    92969 Monitor IPC:024C (S32) = 2236144
   103031 Monitor IPC:024C (S32) = 2188284
   123344 Monitor IPC:024C (S32) = 2105976
   133406 Monitor IPC:024C (S32) = 2104848
   143281 Monitor IPC:024C (S32) = 2101720
   145203 Weather Mode now = Real World
   153406 Monitor IPC:024C (S32) = 2062708
   163469 Monitor IPC:024C (S32) = 1997224
   173531 Monitor IPC:024C (S32) = 1465176
   173531 Starting everything now ...
   184516 **** Restarting traffic scanning due to non-reception ****
   184563 Monitor IPC:024C (S32) = 1020164
   184859 Advanced Weather Interface Enabled
   193656 Monitor IPC:024C (S32) = 1046404
   203719 Monitor IPC:024C (S32) = 1035584
   234000 Monitor IPC:024C (S32) = 1019392
   244078 Monitor IPC:024C (S32) = 950612
   254219 Monitor IPC:024C (S32) = 926304
   264344 Monitor IPC:024C (S32) = 920532
   274484 Monitor IPC:024C (S32) = 916664
   284578 Monitor IPC:024C (S32) = 906476
   294672 Monitor IPC:024C (S32) = 905100
   304766 Monitor IPC:024C (S32) = 888908
   314922 Monitor IPC:024C (S32) = 757636
   325063 Monitor IPC:024C (S32) = 643948
   335250 Monitor IPC:024C (S32) = 592340
   345375 Monitor IPC:024C (S32) = 656200
   355453 Monitor IPC:024C (S32) = 635264
   365578 Monitor IPC:024C (S32) = 793168
   395906 Monitor IPC:024C (S32) = 792376
   406063 Monitor IPC:024C (S32) = 758520
   416156 Monitor IPC:024C (S32) = 755400
   436422 Monitor IPC:024C (S32) = 758248
   456688 Monitor IPC:024C (S32) = 755388
   466844 Monitor IPC:024C (S32) = 757136
   476938 Monitor IPC:024C (S32) = 758232
   497188 Monitor IPC:024C (S32) = 791076
   527547 Monitor IPC:024C (S32) = 773776
   537641 Monitor IPC:024C (S32) = 742124
   547797 Monitor IPC:024C (S32) = 803284
   568094 Monitor IPC:024C (S32) = 686968
   578203 Monitor IPC:024C (S32) = 713764
   588328 Monitor IPC:024C (S32) = 607756
   598391 Monitor IPC:024C (S32) = 630392
   608547 Monitor IPC:024C (S32) = 631688
   618641 Monitor IPC:024C (S32) = 615496
   628781 Monitor IPC:024C (S32) = 693316
   638938 Monitor IPC:024C (S32) = 600948
   649063 Monitor IPC:024C (S32) = 715848
   659172 Monitor IPC:024C (S32) = 715352
   709797 Monitor IPC:024C (S32) = 716444
   719906 Monitor IPC:024C (S32) = 715368
   750266 Monitor IPC:024C (S32) = 651764
   760406 Monitor IPC:024C (S32) = 609688
   770531 Monitor IPC:024C (S32) = 630740
   780625 Monitor IPC:024C (S32) = 632072
   790750 Monitor IPC:024C (S32) = 715220
   800844 Monitor IPC:024C (S32) = 713664
   811000 Monitor IPC:024C (S32) = 725092
   821094 Monitor IPC:024C (S32) = 775128
   831203 Monitor IPC:024C (S32) = 771900
   841297 Monitor IPC:024C (S32) = 717636
   851391 Monitor IPC:024C (S32) = 720032
   861563 Monitor IPC:024C (S32) = 746132
   871672 Monitor IPC:024C (S32) = 747504
   881797 Monitor IPC:024C (S32) = 748076
   891922 Monitor IPC:024C (S32) = 713096
   902016 Monitor IPC:024C (S32) = 711972
   912141 Monitor IPC:024C (S32) = 714812
   922266 Monitor IPC:024C (S32) = 718856
   932359 Monitor IPC:024C (S32) = 726596
   942484 Monitor IPC:024C (S32) = 764532
   952625 Monitor IPC:024C (S32) = 770020
   962703 Monitor IPC:024C (S32) = 762280
   972797 Monitor IPC:024C (S32) = 763652
   982969 Monitor IPC:024C (S32) = 566380
   993109 Monitor IPC:024C (S32) = 545836
  1003297 Monitor IPC:024C (S32) = 570592
  1013438 Monitor IPC:024C (S32) = 569472
  1023594 Monitor IPC:024C (S32) = 561972
  1033734 Monitor IPC:024C (S32) = 571708
  1043906 Monitor IPC:024C (S32) = 541592
  1054063 Monitor IPC:024C (S32) = 547668
  1064188 Monitor IPC:024C (S32) = 562656
  1074391 Monitor IPC:024C (S32) = 637024
  1084500 Monitor IPC:024C (S32) = 702616
  1094688 Monitor IPC:024C (S32) = 758540
  1104781 Monitor IPC:024C (S32) = 901484
  1114984 Monitor IPC:024C (S32) = 880784
  1125125 Monitor IPC:024C (S32) = 961028
  1135234 Monitor IPC:024C (S32) = 953404
  1145391 Monitor IPC:024C (S32) = 918972
  1155500 Monitor IPC:024C (S32) = 930528
  1165641 Monitor IPC:024C (S32) = 943364
  1175797 Monitor IPC:024C (S32) = 922900
  1185891 Monitor IPC:024C (S32) = 939336
  1196031 Monitor IPC:024C (S32) = 520972
  1206172 Monitor IPC:024C (S32) = 891380
  1216313 Monitor IPC:024C (S32) = 929012
  1226422 Monitor IPC:024C (S32) = 929860
  1236594 Monitor IPC:024C (S32) = 934032
  1246688 Monitor IPC:024C (S32) = 928476
  1256844 Monitor IPC:024C (S32) = 932492
  1267031 Monitor IPC:024C (S32) = 946268
  1277078 Monitor IPC:024C (S32) = 947932
  1287219 Monitor IPC:024C (S32) = 947504
  1297328 Monitor IPC:024C (S32) = 946928
  1307438 Monitor IPC:024C (S32) = 947256
  1317563 Monitor IPC:024C (S32) = 1004464
  1327672 Monitor IPC:024C (S32) = 1140948
  1337750 Monitor IPC:024C (S32) = 1131092
  1347891 Monitor IPC:024C (S32) = 1131784
  1357953 Monitor IPC:024C (S32) = 1102892
  1368094 Monitor IPC:024C (S32) = 1131960
  1378219 Monitor IPC:024C (S32) = 1032248
  1388297 Monitor IPC:024C (S32) = 1113548
  1398609 Monitor IPC:024C (S32) = 1108464
  1408531 Monitor IPC:024C (S32) = 1030664
  1418641 Monitor IPC:024C (S32) = 1032888
  1428750 Monitor IPC:024C (S32) = 1097664
  1438828 Monitor IPC:024C (S32) = 1229316
  1448938 Monitor IPC:024C (S32) = 1198588
  1459031 Monitor IPC:024C (S32) = 1034776
  1469141 Monitor IPC:024C (S32) = 1034792
  1479250 Monitor IPC:024C (S32) = 1028848
  1489359 Monitor IPC:024C (S32) = 1027112
  1499484 Monitor IPC:024C (S32) = 1025560
  1509563 Monitor IPC:024C (S32) = 1025532
  1519719 Monitor IPC:024C (S32) = 1023836
  1529813 Monitor IPC:024C (S32) = 1023292
  1539938 Monitor IPC:024C (S32) = 1020864
  1550031 Monitor IPC:024C (S32) = 1020860
  1560109 Monitor IPC:024C (S32) = 1022928
  1570203 Monitor IPC:024C (S32) = 1025140
  1580297 Monitor IPC:024C (S32) = 985892
  1590453 Monitor IPC:024C (S32) = 1010524
  1600547 Monitor IPC:024C (S32) = 1045488
  1610688 Monitor IPC:024C (S32) = 1047864
  1620766 Monitor IPC:024C (S32) = 1045664
  1630891 Monitor IPC:024C (S32) = 1046136
  1641000 Monitor IPC:024C (S32) = 1036376
  1651125 Monitor IPC:024C (S32) = 1185436
  1661250 Monitor IPC:024C (S32) = 1191580
  1671391 Monitor IPC:024C (S32) = 1113908
  1681469 Monitor IPC:024C (S32) = 1114624
  1691609 Monitor IPC:024C (S32) = 1122960
  1701766 Monitor IPC:024C (S32) = 1103864
  1711891 Monitor IPC:024C (S32) = 1164764
  1721969 Monitor IPC:024C (S32) = 1168832
  1732109 Monitor IPC:024C (S32) = 1177024
  1742266 Monitor IPC:024C (S32) = 1119720
  1752391 Monitor IPC:024C (S32) = 1118096
  1762516 Monitor IPC:024C (S32) = 1145088
  1772656 Monitor IPC:024C (S32) = 1075708
  1782781 Monitor IPC:024C (S32) = 1024124
  1792906 Monitor IPC:024C (S32) = 1153240
  1803000 Monitor IPC:024C (S32) = 1180620
  1813141 Monitor IPC:024C (S32) = 1187804
  1823281 Monitor IPC:024C (S32) = 1196864
  1833391 Monitor IPC:024C (S32) = 1124800
  1843500 Monitor IPC:024C (S32) = 1154532
  1853625 Monitor IPC:024C (S32) = 1162152
  1863734 Monitor IPC:024C (S32) = 1137112
  1867563 *** G3D bad pointer trapped and crash prevented ***
  1873813 Monitor IPC:024C (S32) = 1203400
  1883953 Monitor IPC:024C (S32) = 1214216
  1894047 Monitor IPC:024C (S32) = 1218504
  1904172 Monitor IPC:024C (S32) = 1248512
  1914281 Monitor IPC:024C (S32) = 1248416
  1924375 Monitor IPC:024C (S32) = 1249072
  1934484 Monitor IPC:024C (S32) = 1253628
  1944563 Monitor IPC:024C (S32) = 1251188
  1954672 Monitor IPC:024C (S32) = 1250664
  1964813 Monitor IPC:024C (S32) = 1251480
  1974953 Monitor IPC:024C (S32) = 1231696
  1985094 Monitor IPC:024C (S32) = 1191980
  1995203 Monitor IPC:024C (S32) = 1225940
  2005313 Monitor IPC:024C (S32) = 1224508
  2015406 Monitor IPC:024C (S32) = 1223460
  2025500 Monitor IPC:024C (S32) = 1223856
  2035625 Monitor IPC:024C (S32) = 1156244
  2045734 Monitor IPC:024C (S32) = 1160672
  2055859 Monitor IPC:024C (S32) = 1160028
  2065969 Monitor IPC:024C (S32) = 1159176
  2076063 Monitor IPC:024C (S32) = 1164768
  2086172 Monitor IPC:024C (S32) = 1164256
  2096281 Monitor IPC:024C (S32) = 1164456
  2106344 Monitor IPC:024C (S32) = 1168580
  2116469 Monitor IPC:024C (S32) = 1171744
  2126594 Monitor IPC:024C (S32) = 1170252
  2136688 Monitor IPC:024C (S32) = 1170680
  2146813 Monitor IPC:024C (S32) = 1157424
  2156953 Monitor IPC:024C (S32) = 1164928
  2167047 Monitor IPC:024C (S32) = 1169948
  2177188 Monitor IPC:024C (S32) = 1168764
  2187297 Monitor IPC:024C (S32) = 1144656
  2197406 Monitor IPC:024C (S32) = 1147640
  2207500 Monitor IPC:024C (S32) = 1150160
  2217609 Monitor IPC:024C (S32) = 1148728
  2227750 Monitor IPC:024C (S32) = 1143420
  2237875 Monitor IPC:024C (S32) = 1158288
  2248000 Monitor IPC:024C (S32) = 1162384
  2268250 Monitor IPC:024C (S32) = 1171556
  2278391 Monitor IPC:024C (S32) = 1176028
  2288516 Monitor IPC:024C (S32) = 1180216
  2298641 Monitor IPC:024C (S32) = 1206316
  2308734 Monitor IPC:024C (S32) = 1210292
  2318813 Monitor IPC:024C (S32) = 1215284
  2328906 Monitor IPC:024C (S32) = 1234708
  2339016 Monitor IPC:024C (S32) = 1217208
  2349141 Monitor IPC:024C (S32) = 1216592
  2359281 Monitor IPC:024C (S32) = 1216156
  2369391 Monitor IPC:024C (S32) = 1217544
  2389672 Monitor IPC:024C (S32) = 1218916
  2399813 Monitor IPC:024C (S32) = 1216160
  2409938 Monitor IPC:024C (S32) = 1140520
  2430219 Monitor IPC:024C (S32) = 1141256
  2440297 Monitor IPC:024C (S32) = 1123644
  2450391 Monitor IPC:024C (S32) = 1129732
  2460500 Monitor IPC:024C (S32) = 1116928
  2470625 Monitor IPC:024C (S32) = 1144912
  2480750 Monitor IPC:024C (S32) = 1170456
  2490891 Monitor IPC:024C (S32) = 1162180
  2500969 Monitor IPC:024C (S32) = 1161804
  2511094 Monitor IPC:024C (S32) = 1126324
  2521188 Monitor IPC:024C (S32) = 1096556
  2531313 Monitor IPC:024C (S32) = 1124740
  2541422 Monitor IPC:024C (S32) = 1088732
  2551578 Monitor IPC:024C (S32) = 1098196
  2561734 Monitor IPC:024C (S32) = 1099756
  2571828 Monitor IPC:024C (S32) = 1082908
  2581891 Monitor IPC:024C (S32) = 1098960
  2592047 Monitor IPC:024C (S32) = 1088888
  2602156 Monitor IPC:024C (S32) = 1089508
  2612281 Monitor IPC:024C (S32) = 1084256
  2622422 Monitor IPC:024C (S32) = 1075632
  2642641 Monitor IPC:024C (S32) = 1069332
  2652797 Monitor IPC:024C (S32) = 685744
  2662906 Monitor IPC:024C (S32) = 689632
  2673109 Monitor IPC:024C (S32) = 686588
  2683219 Monitor IPC:024C (S32) = 677812
  2693313 Monitor IPC:024C (S32) = 678320
  2703406 Monitor IPC:024C (S32) = 676700
  2713594 Monitor IPC:024C (S32) = 672200
  2723734 Monitor IPC:024C (S32) = 598808
  2733922 Monitor IPC:024C (S32) = 598684
  2744016 Monitor IPC:024C (S32) = 597804
  2754188 Monitor IPC:024C (S32) = 593972
  2764266 Monitor IPC:024C (S32) = 551204
  2774406 Monitor IPC:024C (S32) = 557940
  2784484 Monitor IPC:024C (S32) = 527076
  2794594 Monitor IPC:024C (S32) = 556704
  2804766 Monitor IPC:024C (S32) = 557292
  2814891 Monitor IPC:024C (S32) = 556784
  2825031 Monitor IPC:024C (S32) = 521268
  2835172 Monitor IPC:024C (S32) = 605860
  2845250 Monitor IPC:024C (S32) = 609192
  2855375 Monitor IPC:024C (S32) = 584476
  2865500 Monitor IPC:024C (S32) = 535612
  2875688 Monitor IPC:024C (S32) = 426544
  2885766 Monitor IPC:024C (S32) = 480128
  2906016 Monitor IPC:024C (S32) = 474988
  2916125 Monitor IPC:024C (S32) = 452964
  2926234 Monitor IPC:024C (S32) = 486188
  2936297 Monitor IPC:024C (S32) = 483664
  2946438 Monitor IPC:024C (S32) = 485120
  2956516 Monitor IPC:024C (S32) = 493304
  2966688 Monitor IPC:024C (S32) = 524880
  2976844 Monitor IPC:024C (S32) = 490532
  2986969 Monitor IPC:024C (S32) = 511212
  2996047 Sim stopped: average frame rate for last 2824 secs = 29.6 fps
  2996047    Max AI traffic was 301 aircraft (Deleted 0)
  2997219 Monitor IPC:024C (S32) = 510172
  2998922 === Closing session: waiting for DLLStop to be called ...
  3003313 === DLLStop called ...
  3003313 === Closing external processes we started ...
  3004313 === About to kill any Lua plug-ins still running ...
  3004469 === Closing global Lua thread
  3005469 === About to kill my timers ...
  3005672 === Restoring window procs ...
  3005672 === Unloading libraries ...
  3005672 === stopping other threads ...
  3005672 === ... Memory checking ...
  3005672 === ... Button scanning ...
  3005766 === ... Axis scanning ...
  3005859 === Releasing joystick devices ...
  3005859 === Freeing macro memory
  3005859 === Removing any offset overrides
  3005859 === Clearing any displays left
  3005859 === NOTE: not calling SimConnect_Close ...
  3005859 === AI slots deleted!
  3005859 === Freeing button memory ...
  3005859 === Closing my Windows ...
  3005859 === Freeing FS libraries ...
  3006859 === Closing devices ...
  3006859 === Closing the Log ... Bye Bye! ...
  3006859 System time = 08/03/2018 14:00:04, Simulator time = 11:20:08 (19:20Z)
  3006859 *** FSUIPC log file being closed
Minimum frame rate was 7.0 fps, Maximum was 109.9 fps
Minimum available memory recorded was 417Mb
Average frame rate for running time of 2824 secs = 29.6 fps
G3D fix: Passes 117681, Null pointers 0, Bad pointers 2, Separate instances 1
Maximum AI traffic for session was 301 aircraft
Memory managed: 1319 Allocs, 1319 Freed
********* FSUIPC Log file closed ***********

The most important info in this report was:

Minimum frame rate was 7.0 fps, Maximum was 109.9 fps
Minimum available memory recorded was 417Mb
Average frame rate for running time of 2824 secs = 29.6 fps

I had FSDT KLAX and FlightBeam KSFO and real weather (not AS16) and UltimateTraffic Live and Orbx SoCal/NoCal.  Also used the PMDG 738NGX.  This was a bit sloppy flight as I really did not have things configured perfectly as I found out my FSUIPC was out of date and I had KLAX and KSFO located under Orbx scenery in the FSX Config.  Still it is pretty close to being very accurate. 

[colfmedion 1]

Log was interesting but the most interesting thing for me is that I cannot get the VAS Monitor to run. I have installed the latest version of FSUIPC and set it up as per the AVSIM CTD Guide - Monitor IPC: 024C (S32) = 0 appears at top of the FSX Windows Mode Screen but the 0 remains throughout but my other VAS Monitor still shows 3mb at start of flight and 0 when OOMS appears which like before was after 15 to 20minutes into flight or just before landing at Newark. I have gone through the Basic FSX Coniguration Guide and AVSIM CTD Guide and set up just about everything as per the guides.Hardware monitors that I have installed do not report any problems with SSD, HDs, CPU or Graphic Card.

I am going to try another Graphic Card over the next few days and if results remain the same I will try and run FSX on another PC and see what happens. I will report back but it will take me several days.

Colmedion

[Jim Young 2,356]

I cannot help you with this one.  If it is showing VAS = 0 then something is seriously wrong with your computer or Windows 10 installation.  Windows 10 is what gives you 4GB's of VAS, not FSX.  It will show 0 for any 64 bit application.