OOM at 3.2GB instead of 4GB

[JSilva 42]

For some reason, I get OOMs at 3.2GB instead of 4GB. I am using Process Explorer for monitoring VAS. I am using Windows 7 SP1 64 bit.

[ryanbatc 13,137]

Are you sure FSX is saying "Your computer has run out of available memory" ?  I'm wondering if it's some other sort of CTD and not a true OOM...  What does windows event viewer say?  Go to START->Run -> type "eventvwr" (without quotes) and browse to the Windows Logs, Application to see what caused it.  Most recent events are at the top.

[Bob Scott 7,783]

The OOM occurs when a memory allocation request is made and there is no contiguous block of VAS available to fill the request.  Memory fragmentation may (usually does) account for an OOM well short of the 4GB mark as a result...there may still be a significant amount of total free memory, but no contiguous block of free memory large enough to service the request.

 

Regards

[JSilva 42]

Are you sure FSX is saying "Your computer has run out of available memory" ?  I'm wondering if it's some other sort of CTD and not a true OOM...  What does windows event viewer say?  Go to START->Run -> type "eventvwr" (without quotes) and browse to the Windows Logs, Application to see what caused it.  Most recent events are at the top.

It did say "Your computer has run out of available memory". Here is the log.

 

fsx.exe      

10.0.61637.0      

46fadb14      

atidxx32.dll      

8.17.10.545      

535082f8      

c0000005      

000be3a0      

16d0      

01d00cab37a84367      

D:\Microsoft Flight Simulator X\fsx.exe      

C:\Windows\system32\atidxx32.dll      

34f2fe4e-78bd-11e4-856d-54271ebe4ff2

[Jim Young 2,356]

It did say "Your computer has run out of available memory". Here is the log.

The crash or faulting module was caused by your ATI display driver - atidxx32 dll. You might want to try reinstalling it.

 

Best regards,

[ryanbatc 13,137]

The OOM occurs when a memory allocation request is made and there is no contiguous block of VAS available to fill the request.  Memory fragmentation may (usually does) account for an OOM well short of the 4GB mark as a result...there may still be a significant amount of total free memory, but no contiguous block of free memory large enough to service the request.

 

Regards

 At 3.2GB?  I'd say very rarely....  I'm one who usually gets them especially around orbx areas, and it's typically between 3.8-3.9 when the FSX message comes up.

[Jim Young 2,356]

I'm one who usually gets them especially around orbx areas, and it's typically between 3.8-3.9 when the FSX message comes up.

Wow! I've heard of a couple of others getting that much VAS before a crash but it's pretty rare and an indication you probably have your system tuned up with conservative fsx/display driver settings. My sim is usually crashing around 3.5GB's as I have about 400-500 MB's left when the dinging from FSUIPC begins. I use photoscenery, ASN, PMDG aircraft, and FSDT airports 99.9% of the time so probably why there is a slight difference.

 

Best regards,

[Bob Scott 7,783]

 At 3.2GB?  I'd say very rarely....  I'm one who usually gets them especially around orbx areas, and it's typically between 3.8-3.9 when the FSX message comes up.

 I think somewhere in the mid 3 GB range is more normal, but as the OP saw, it *can* happen considerably lower. The module identified in the crash log is not necessarily the cause of the problem--very often, in fact, it is not.  All that means is that the instruction which was at the top of the execution stack when the crash occurred came from within that module's address space.  It's entirely possible to have a problem process with a memory leak or other unhappy behavior cause the issue, but things end up blowing up after calling the video driver or other system process for some routine housekeeping. You have to go through the stack dump to really see what was happening, and often even that doesn't tell a meaningful story.

 

The OP said he was getting OOMs (plural) at 3.2 GB.  If it's happening repeatedly, and in the same module each time, that might indeed point to a video driver issue.  If it happens repeatedly, but with different faulting modules, could be a lot of things...i.e. unstable overclock, corrupted user or system program or module, or even something as arcane as a bad texture on an AI plane transiting through your bubble.

 

A clean driver reinstall is easy enough to do...but if the problem keeps occurring, you need to start looking for the commonalities running through the various failures.  Often time they'll surprise you, like the aforementioned bad texture issue that drove me nuts for a good month before I figured out UT2 was generating the same exact traffic each time because my start place and time was coming from my default flight.  It took 3 weeks to notice that if I changed the time just by an hour or two, the problem went away.  And the faults were occurring in G3D.dll, sim1.dll...all over the map.

 

Good luck

[JSilva 42]

Okay, about the driver reinstall, I ordered a new GPU a few days ago (which should arrive today). It is an Nvidia GTX 970. If it is the bad textures in AI Aircraft, I can either reinstall FSX (as I'm using default AI Traffic) or disable the AI Traffic. I did have some OOMs with different modules crashing. This is another log but this time is ntdll.dll.

 

 fsx.exe      

10.0.61637.0      

46fadb14      

ntdll.dll      

6.1.7601.18247      

521ea8e7      

c0000374      

000ce753      

50c      

01d01245abf39b72      

D:\Microsoft Flight Simulator X\fsx.exe      

C:\Windows\SysWOW64\ntdll.dll      

0873a4d7-7e4d-11e4-8ed2-10c37b922399

[JSilva 42]

My EVGA GTX 970 FTW ACX 2.0 finally arrived. But since I planned to get it at christmas, I won't install it until christmas (in other words, 34 hrs 57 mins at minimum). I think I know what to expect, I uninstall the entire driver (14.4) using the Display Driver Uninstaller (so that no instance of the driver is found), shut the PC down, remove the AMD Radeon HD 7850 2GB Sapphire OC Edition and replace it with the GTX 970, turn the PC on, install the most recent driver (that works fine with FSX and Prepar3D v2.4 (and no beta)), and finally download a patch that fixes the HDMI RGB (as I use HDMI (I read that the recent driver, the problem would be fixed but it is a beta and I read that the PAPI Lights might not work on Prepar3D v2.4)).

[Jim Young 2,356]

One of the causes for the ntdll.dll faulting module is MyTrafficX v5.4c. One of the AI schedules is believed to be corrupted. The fix is to not use the 2012 or 2013 AI schedule on the developers website but just the schedule that is installed when you install the program (you get more AI with the default). It is believed one of the schedules is calling a flight plan and the aircraft required for the flight plan is not available or cannot be found. Some others have found an object in one of the many AFCAD's installed with MyTrafficX causes the problem too. I have gone back to v5.4b and have seen no problems. Others, have reinstalled 5.4c and not used the AI schedules on-line and have had no problems.

 

The Exception Code c0000374 indicates Heap Corruption. The AVSIM CTD Guide has guidance regarding Heap Corruption (see Page 7). The CTD Guide also provides known/probable causes for the NTDLL crash in the last section.

 

Best regards,

[JSilva 42]

One of the causes for the ntdll.dll faulting module is MyTrafficX v5.4c. One of the AI schedules is believed to be corrupted. The fix is to not use the 2012 or 2013 AI schedule on the developers website but just the schedule that is installed when you install the program (you get more AI with the default). It is believed one of the schedules is calling a flight plan and the aircraft required for the flight plan is not available or cannot be found. Some others have found an object in one of the many AFCAD's installed with MyTrafficX causes the problem too. I have gone back to v5.4b and have seen no problems. Others, have reinstalled 5.4c and not used the AI schedules on-line and have had no problems.

 

The Exception Code c0000374 indicates Heap Corruption. The AVSIM CTD Guide has guidance regarding Heap Corruption (see Page 7). The CTD Guide also provides known/probable causes for the NTDLL crash in the last section.

 

Best regards,

I thought I said I use default AI (as in I don't use MyTrafficX). I am certain I already installed the Fix It program at the time. I remember the previous flight, I got a CTD instead of an OOM (and at that time, I get pinging noises). This is the log for that one:

 

  fsx.exe      

10.0.61637.0      

46fadb14      

KERNELBASE.dll      

6.1.7601.18409      

53159a86      

e06d7363      

0000c42d

[JSilva 42]

I installed the GTX 970 and the good news is that the graphical glitch on DX10 (with the fixer) ended. However, when I did a flight from OTHH-EGLL using a PMDG 777-300 ER, I got an OOM a few moments after I decended past 10,000ft. This happened 10 minutes ago. Again, it is still at 3.2GB rather than the usual 4GB limit (using both FSUIPC and Process Explorer). Before anyone asks me for a log, I don't think a log was produced (unlike the previous where they did).

[Slayer 190]

So an obvious question: Did your himemfix line somehow get removed from your config? That would explain it as it frees up a few hundred megs more for the program to use closer to the 4GB mark

 

Also for the T7 there is an option for lower  sound files in the operation center that can reduce your memory footprint a little, maybe enough so that you can finish your flights.

[Jim Young 2,356]

 

 

t is still at 3.2GB rather than the usual 4GB limit (using both FSUIPC and Process Explorer).

 

If it is showing 3.2GB in your Process Monitor, it means you only have 800 MB's (approx) left.  For the FSUIPC program, it should be showing you have about 800000KB left and that shouldn't cause an OOM as an OOM usually occurs with between 400 and 500 MB's left and you will hear an audible warning from FSUIPC.  The FSUIPC.log is generated every time you restart fsx and ends when you close fsx.  It is located in the FSX/Modules folder.

 

Best regards,