Archived

This topic is now archived and is closed to further replies.

Daniel choen

OOM'S

Recommended Posts

Hey,

i am super frustrated, I have been getting 2 errors with the new T7, i have tried to lower the settings without luck maybe you can help me:

 

Log Name:      Application
Source:        Application Error
Date:          9/6/2013 1:45:56 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      user03
Description:
Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000005
Fault offset: 0x0004ff2b
Faulting process id: 0x1310
Faulting application start time: 0x01ceaa6726d28247
Faulting application path: F:\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: ec91ef38-167c-11e3-9afd-50e549419927
Event Xml:
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-09-05T22:45:56.000000000Z" />
    <EventRecordID>26172</EventRecordID>
    <Channel>Application</Channel>
    <Computer>user03</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61472.0</Data>
    <Data>475e17d3</Data>
    <Data>ntdll.dll</Data>
    <Data>6.1.7601.17725</Data>
    <Data>4ec49b8f</Data>
    <Data>c0000005</Data>
    <Data>0004ff2b</Data>
    <Data>1310</Data>
    <Data>01ceaa6726d28247</Data>
    <Data>F:\Microsoft Flight Simulator X\fsx.exe</Data>
    <Data>C:\Windows\SysWOW64\ntdll.dll</Data>
    <Data>ec91ef38-167c-11e3-9afd-50e549419927</Data>
  </EventData>
</Event>
 
Log Name:      Application
Source:        Application Hang
Date:          9/5/2013 9:38:28 PM
Event ID:      1002
Task Category: (101)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      user03
Description:
The program fsx.exe version 10.0.61472.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
 Process ID: 139c
 Start Time: 01ceaa656bc9b6d4
 Termination Time: 196
 Application Path: F:\Microsoft Flight Simulator X\fsx.exe
 Report Id: 
 
Event Xml:
  <System>
    <Provider Name="Application Hang" />
    <EventID Qualifiers="0">1002</EventID>
    <Level>2</Level>
    <Task>101</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-09-05T18:38:28.000000000Z" />
    <EventRecordID>26167</EventRecordID>
    <Channel>Application</Channel>
    <Computer>user03</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61472.0</Data>
    <Data>139c</Data>
    <Data>01ceaa656bc9b6d4</Data>
    <Data>196</Data>
    <Data>F:\Microsoft Flight Simulator X\fsx.exe</Data>
    <Data>
    </Data>
    <Binary>55006E006B006E006F0077006E0000000000</Binary>
  </EventData>
</Event>

 

Share this post


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

I just went through this with the 777.  I kept getting CTD's with the NTDLL.dll as the faulting module (which relates to memory).  I have my fsx settings set lower than the fsx default except the LOD_Radius was set to 6.5.  I lowered that to 5.5 but still got the crash.  I decided to see if I had any corrupted fsx files.  I looked at the dll.xml using Notebook++ (Google) and saw several entries relating to software I had previously uninstalled.  I saw a couple of entries relating to the FSX SDK and I had not installed that yet on my system.  I saw TWO duplicate entries for PMDG.  Editing with Notebook++, I removed those old, non-existent and duplicate entries.  Ran FSX again with the same flight that created the NTDLL.dll error 100% of the time and this time I was able to complete the flight and no CTD.  So maybe, just maybe, this is your problem too.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

I just went through this with the 777.  I kept getting CTD's with the NTDLL.dll as the faulting module (which relates to memory).  I have my fsx settings set lower than the fsx default except the LOD_Radius was set to 6.5.  I lowered that to 5.5 but still got the crash.  I decided to see if I had any corrupted fsx files.  I looked at the dll.xml using Notebook++ (Google) and saw several entries relating to software I had previously uninstalled.  I saw a couple of entries relating to the FSX SDK and I had not installed that yet on my system.  I saw TWO duplicate entries for PMDG.  Editing with Notebook++, I removed those old, non-existent and duplicate entries.  Ran FSX again with the same flight that created the NTDLL.dll error 100% of the time and this time I was able to complete the flight and no CTD.  So maybe, just maybe, this is your problem too.

 

Best regards,

Jim

 

Wow, thank you Jim! I have been experiencing the same CTD as you! I will look through my dll.xml file. 

Share this post


Link to post
Share on other sites

So jim I went through my dll.xml and deleted my entry for accufeel which I uninstalled over a year ago. Hmm!

Share this post


Link to post
Share on other sites

 

 


deleted my entry for accufeel

 

That's one of the software entries I had in mine that I removed.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

yes both accufeel and soundstream have been buggy on my system

Share this post


Link to post
Share on other sites

 

 


That's not an oom btw. It will pop up a box that says fsx has run out of memory

 

you can get OOM errors with FSX without message

Share this post


Link to post
Share on other sites