Jump to content

Archived

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

CaptainKen

Can anyone PLEASE help me?

Recommended Posts

My problem is with Megascenery Earth 2.  I have 15 states that I bought.  Some work terrific - some are disasters.  By disaster, I mean that FSX just shuts down completely.  The problem is with Nevada, Ohio and Indiana in particular.  Other states work just fine.  I have installed per manufacturer's instructions.  The CTD happens somewhere during the flight - maybe 5 minutes in, may be 20 minutes in.  It's like it gets to a part of the state, can't find the scenery and just crashes.  I have a good computer, great video card, get great FPS and am using windows 7 64 bit.  Florida works flawlessly - so does NY, Alabama, north Carolina, Tennessee, Arkansas and Texas.  What could the problem possibly be?  I have "uninstalled" the scenery from fsx (settings/scenery display), then reloaded.  No luck.

 

I have contacted the Megascenery people via their help/support, but so far heard back nothing via email.  This has happened to me about 15 times.

 

Maybe I am doing something wrong.  I just don't know what it is.  I installed the scenery via purchased disks.  I have spent over $500 on this so far, so please understand my frustration.  If anyone has any ideas, please post them.  I was so desperate that a week ago, I completely uninstalled FSX, and re-installed it.  After the hours of re-loading all my stuff, I tried again.  This morning I flew Birmingham Alabama to Tallahassee Fl - NO Problems.  @ hours later, I tried to fly form Nebraska to SD.  But about 5 minutes into the flight it shut down - same issue, only I don't know what it is.  As I said before, I did follow the Mfr. instructions as best I know them.  I have stuff turned way - up in fsx, but still get good frame rates - so that isn't the problem.

 

An\y ideas?  Thanks to anyone responding to this in advance.  I appreciate your effort.

 

Ken

Share this post


Link to post
Share on other sites

Any error messages generated? If so, please post the message.

Share this post


Link to post
Share on other sites

Go to Event Viewer and see if there is an error log from FSX. Pasting the log here may be helpful.

Share this post


Link to post
Share on other sites

OK here is the last one

 

 

  fsx.exe

 

      10.0.61472.0

 

      475e17d3

 

      util.dll

 

      10.0.61472.0

 

      475e180d

 

      c0000005

 

      00022d5a

 

      be0

 

      01ce7a651e9df8f0

 

      C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

 

      C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\util.dll

 

      fa80e350-e65d-11e2-8ce8-00038a000015

 


If this helps you help me, here is the previous one - I won't post the others till I hear from you - I don't want to waste froum space - anyhow here it is:

 

  fsx.exe

 

      10.0.61472.0

 

      475e17d3

 

      XAudio2_6.dll

 

      9.28.1886.0

 

      4b6b0791

 

      c0000005

 

      0002cbef

 

      a8

 

      01ce7a47e3ab0610

 

      C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

 

      C:\Windows\SysWow64\XAudio2_6.dll

 

      7f28afc0-e63b-11e2-8ce8-00038a000015

 

Share this post


Link to post
Share on other sites

This is an automatic message.

 

This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

  • The most likely reason is that the post was off topic.
  • The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
  • The images might not have been "illustrative" or "explanatory" in nature.
  • The topic could have been moved because we deemed it to be more appropriately placed elsewhere.
Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

Share this post


Link to post
Share on other sites

Crash was caused by the XAudio2_6.dll.  People who have had this crash have had to update their sound card drivers.  If you have an internal sound card like from Creative Blaster, download and install that driver.  If you only have the sound that is built into your MB, then you need to update that too.  I would recommend you download and run one of those scanners that looks for drivers on your computer.  I use Driver Scanner.  Once downloaded, run it and it will see if any drivers need to be updated.  If so, it will offer to download and update all of the old drivers you have installed but you will have to purchase the product and register it first.  Some who are Internet savvy can take a look at the drivers that are out of date and do a search and go online and find the updated drivers and install them. 

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

I updated the video and sound drivers with the help of a "pay" service.  Still no solution.  But I know more about the problem - just not the solution.  In the purchased scenery, there are some small "gaps" of missing megascenery.  When the plane nears any of these it crashes.  If I refly, without the megascenery, there is no crash and the flight cannot be completed.  I wrote to the megascenery people, and hopefully will get a reply.  In the mean time, if anyone has any ideas, pleas express them.  I hate the thought of having to turn off the scenery - especially at its price.  Thanks to all who responded and tried to help.

 

Ken

Share this post


Link to post
Share on other sites

That's impossible Ken that any missing scenery would cause an XAudio2_6.dll crash.  If there are gaps in MegaScenery, FSX will then render the default scenery.  Removing the scenery might have reduced some strain on your system as having a lot of MegaScenery installed can cause an OOM or cause your system to slow down considerably.  That's why I only enable the MegaScenery I'll be flying over during a session (I have about 35 MegaSceneries).

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Great information.  Thank you!  That is what I expected to happen.  I take it that you have never had a similar problem as mine then?  SO what could be the problem?  I have plenty of horsepower and fps all through the flights - with or without Megascenery.  I took two more flights, over the same exact areas (1 in Nebraska; 1 in Indiana) and again I got the fsx crashes.  When I don't use the Mega scenery (don't load it for the flight), I have no problem.

 

Again, I appreciate your response - truly!

 

Ken


One more thing Jim - When I downloade the new driver, one "part of it appears to have failed to install.  Here is the message from the Event Tracker - does it make any sense to you?  I tried to install it twice, and got the same results.  However, Device Manager shows an updated driver.  Got any thoughts? 

 

"Product: AMD Accelerated Video Transcoding -- Error 1904.Module C:\Program Files\Common Files\ATI Technologies\Multimedia\atimpenc64.dll failed to register. HRESULT -2147024703. Contact your support personnel."

Share this post


Link to post
Share on other sites

Corrupt megascenery textures. I've had it happen. Reinstall the state. How do they come on the dvd? Copy them onto your computer first and extract/install one at a time. If one of the installs hangs for more than 10 seconds or so reinstall it.

Share this post


Link to post
Share on other sites

 

 


One more thing Jim - When I downloade the new driver, one "part of it appears to have failed to install. Here is the message from the Event Tracker - does it make any sense to you? I tried to install it twice, and got the same results. However, Device Manager shows an updated driver. Got any thoughts?
"Product: AMD Accelerated Video Transcoding -- Error 1904.Module C:\Program Files\Common Files\ATI Technologies\Multimedia\atimpenc64.dll failed to register. HRESULT -2147024703. Contact your support personnel."

 

This is how one person fixed this problem (see Post #8) - http://www.guru3d.com/news_story/download_amd_catalyst_13_5_beta_2_and_13_4_whql_drivers,4.html.

 

 

 


I took two more flights, over the same exact areas (1 in Nebraska; 1 in Indiana) and again I got the fsx crashes.

 

I can't help you on this one as I have Nebraska and Indiana and have flown in and around them several times and no crashes.  If you have a lot of addon scenery installed and activated in the Scenery Library, then all of that scenery is going to load during your flight and it is going to take your computer down and totally trash it.  This is why I downloaded and install Scenery Config Editor.  With that I can open up the Scenery Config Editor before I start up FSX.  I can disable every addon scenery (not any of the default) except for the areas I will be flying over in a flightplan.  This way only those sceneries will be loaded that you activate and then Save in the Scenery Config Editor.  Then you can start up FSX and FSX will immediately see the changes to the Scenery Library.  I think you need to fix the first problem before getting into the MSE crashes.  You should download and run AppCrashView as it provides more information that the Microsoft error report - http://www.nirsoft.net/utils/app_crash_view.html.  It should show you every crash you had since you started up Windows but the last few crashes are the most important. Click on one and copy and paste the report here in this topic and we can take a look at it.  I can assure you that it will not be the fault of the MegaScenery people though.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Again THANKS so much for your continued effort and help.  We MAY be getting somewhere.  I downloaded the AppCrash application you sent e.  And it provides some wonderful information.

 

I looked at about 2 dozen fsx crashes (all very recently), and in EVERY case some of the information is identical.  In EVERY case the fault module (as you can see below) is :  util.dll

 

What ever that thing is, I think is causing the problem.  As you requested here is the information from the most recent fsx crash: 

 

Process File:  fsx.exe 

Event Name:  Stopped working 7/6/2013 1:03:29 PM 

User Name:  Ken 

Exception Code:  0xc0000005 

Exception Offset:  0x00022d5a 

Fault Module Name:  util.dll 

Fault Module Version:  10.0.61472.0 

Process Path:  C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator  X\fsx.exe 

Report File Size:  33,630 

Report Path:  C:\Users\Ken\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_1828fa5aaebd1e4352f178e7f26f9de528aaa_05dc7b7f\Report.wer 

 

Jim, in all 20 that I looked at, Exception Code, Exception Offset, Fault Module Name and Fault Module Version are identical.  I don't know what it means, but it being the same makes me hopeful.

 

And again, I appreciate your help much more than you can possibly know.

 

Ken
 

Share this post


Link to post
Share on other sites

The util.dll ctd has been centered around with a problem with installed scenery.  It's finding the scenery that is the culprit that's the hard part.  I would disable all of the addon scenery (keep all of the default enabled) then run FSX and see if the problem still occurs.  If not, it is one of those installed sceneries.  I'm thinking an airport scenery addon is most likely the cause but it doesn't hurt to disable them all.  Once you determine it must be one of the addons, then reenable addon sceneries 3-4 at a time until the ctd reoccurs. 

 

I still would like to see a full crash report as it tells me whether or not you have the latest versions of Microsoft Visuals installed. 

 

The Exception Code 005 occurs almost every time there is an FSX crash. It means you had a memory_access_violation.  It usually means you do not have sufficient resources to run FSX/FSX Addons.  It could be a corrupted addon installation too as a product could be calling for a particular piece of scenery like an object and it is not there or where it is suppose to be so FSX crashes.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Exception code 0xC0000005 occurs when an application attempts to access an address it's not allowed to. The uUnderlying fault may be quite remote - often an uninitialised pointer - and very difficult to track down. For instance this simple C snippet causes one: 
 

int *pi;

pi = 0;
*pi = 1;

Share this post


Link to post
Share on other sites

OK Jim - I'll post what I think you are looking for - the "complete file" of a fsx crash.  I've been on the phone for three hours with the Tech Service I use (pay for) for help with the computer.  This guy was very patient - we tried about a dozen flights, all in the problem Indiana area.  He thinks it is a "compatibility" issue between FSX and the mega scenery - but quite frankly, I'm not sure.  Again, we tried it without the Indiana megascenery and again no crash.  However, as soon as the megascenery is used, within 5 minutes fsx crashes.  He tried to run this program in many different compatibility modes - but none would fly the plane in Indiana with Megascenery enabled.

 

Again I thank you for your continued support and that of the other gents writing in too.  But I think I'm screwed.  I just can't imagine why mine crashes and other people's do not.  Until someone gets a solution, I guess I just cannot use the megascenery in the problem areas.  The only regret is the wasted money.  I still have not gotten a reply back from the Megascenery people.  If you get any more ideas, I'll try anything - just suggest it.  Until then, here is the file you requested to view.

 

Ken

Version=1
EventType=APPCRASH
EventTime=130177763065678000
ReportType=2
Consent=1
UploadTime=130177763066778000
ReportIdentifier=9ac6ad81-e7ef-11e2-987c-00038a000015
IntegratorReportIdentifier=9ac6ad80-e7ef-11e2-987c-00038a000015
WOW64=1
Response.BucketId=600423621
Response.BucketTable=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.61472.0
Sig[2].Name=Application Timestamp
Sig[2].Value=475e17d3
Sig[3].Name=Fault Module Name
Sig[3].Value=util.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.61472.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=475e180d
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00022d5a
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 Information 1
DynamicSig[22].Value=fb8b
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=fb8bd1bf7dcc44d047c58f37f56ad727
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=fa63
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=fa63c80ebf2b9d98cfa9fc211d9a92ad
UI[2]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
UI[3]=Microsoft Flight Simulator® 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]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.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\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[7]=C:\Windows\syswow64\GDI32.dll
LoadedModule[8]=C:\Windows\syswow64\USER32.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\syswow64\LPK.dll
LoadedModule[15]=C:\Windows\syswow64\USP10.dll
LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[17]=C:\Windows\syswow64\ole32.dll
LoadedModule[18]=C:\Windows\system32\apphelp.dll
LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[20]=C:\Windows\system32\UxTheme.dll
LoadedModule[21]=C:\Windows\system32\WINMM.dll
LoadedModule[22]=C:\Windows\system32\samcli.dll
LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[24]=C:\Windows\system32\MSACM32.dll
LoadedModule[25]=C:\Windows\system32\VERSION.dll
LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[27]=C:\Windows\system32\sfc.dll
LoadedModule[28]=C:\Windows\system32\sfc_os.DLL
LoadedModule[29]=C:\Windows\system32\USERENV.dll
LoadedModule[30]=C:\Windows\system32\profapi.dll
LoadedModule[31]=C:\Windows\system32\dwmapi.dll
LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[35]=C:\Windows\syswow64\urlmon.dll
LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[43]=C:\Windows\syswow64\iertutil.dll
LoadedModule[44]=C:\Windows\syswow64\WININET.dll
LoadedModule[45]=C:\Windows\system32\MPR.dll
LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll
LoadedModule[50]=C:\Windows\system32\mscms.dll
LoadedModule[51]=C:\Windows\system32\DDRAW.dll
LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[54]=C:\Windows\syswow64\IMM32.dll
LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[57]=C:\Windows\syswow64\NSI.dll
LoadedModule[58]=C:\Windows\system32\msi.dll
LoadedModule[59]=C:\Windows\AppPatch\AcXtrnal.DLL
LoadedModule[60]=C:\Windows\system32\SHUNIMPL.DLL
LoadedModule[61]=C:\Windows\system32\SortServer2003Compat.dll
LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[63]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\language.dll
LoadedModule[64]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLL
LoadedModule[65]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[66]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ablscpt.dll
LoadedModule[67]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\flight.dll
LoadedModule[68]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ai_player.dll
LoadedModule[69]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\acontain.dll
LoadedModule[70]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\controls.dll
LoadedModule[71]=C:\Windows\system32\DINPUT8.dll
LoadedModule[72]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsui.dll
LoadedModule[73]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\atc.dll
LoadedModule[74]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\facilities.dll
LoadedModule[75]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\demo.dll
LoadedModule[76]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\main.dll
LoadedModule[77]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fe.dll
LoadedModule[78]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\util.dll
LoadedModule[79]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simprop.dll
LoadedModule[80]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g2d.dll
LoadedModule[81]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[82]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[83]=C:\Windows\system32\d3d9.dll
LoadedModule[84]=C:\Windows\system32\d3d8thk.dll
LoadedModule[85]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g3d.dll
LoadedModule[86]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\panels.dll
LoadedModule[87]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\multiplayer.dll
LoadedModule[88]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ui.dll
LoadedModule[89]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sound.dll
LoadedModule[90]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sim1.dll
LoadedModule[91]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simscheduler.dll
LoadedModule[92]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\visualfx.dll
LoadedModule[93]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\window.dll
LoadedModule[94]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\terrain.dll
LoadedModule[95]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\weather.dll
LoadedModule[96]=C:\Windows\system32\DSOUND.dll
LoadedModule[97]=C:\Windows\system32\POWRPROF.dll
LoadedModule[98]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\symmap.dll
LoadedModule[99]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dll
LoadedModule[100]=C:\Windows\system32\MSIMG32.dll
LoadedModule[101]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\xuipc.dll
LoadedModule[102]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\livingwater.dll
LoadedModule[103]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fs-traffic.dll
LoadedModule[104]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\gps.dll
LoadedModule[105]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[106]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[107]=C:\Windows\system32\RICHED20.DLL
LoadedModule[108]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[109]=C:\Windows\system32\rsaenh.dll
LoadedModule[110]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[111]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[112]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[113]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[114]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[115]=C:\Windows\system32\wbemcomn.dll
LoadedModule[116]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[117]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[118]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[119]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[120]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[121]=C:\Windows\system32\dxgi.dll
LoadedModule[122]=C:\Windows\system32\d3d11.dll
LoadedModule[123]=C:\Windows\system32\aticfx32.dll
LoadedModule[124]=C:\Windows\system32\atiu9pag.dll
LoadedModule[125]=C:\Windows\system32\atiumdag.dll
LoadedModule[126]=C:\Windows\system32\atiumdva.dll
LoadedModule[127]=C:\Windows\system32\atiuxpag.dll
LoadedModule[128]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[129]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[130]=C:\Windows\system32\d3d10_1.dll
LoadedModule[131]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[132]=C:\Windows\SysWOW64\dxdiagn.dll
LoadedModule[133]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[134]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[135]=C:\Windows\system32\winbrand.dll
LoadedModule[136]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[137]=C:\Windows\system32\WINSTA.dll
LoadedModule[138]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[139]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll
LoadedModule[140]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[141]=C:\Windows\SysWOW64\wer.dll
LoadedModule[142]=C:\Windows\System32\Wpc.dll
LoadedModule[143]=C:\Windows\System32\wevtapi.dll
LoadedModule[144]=C:\Windows\System32\msxml6.dll
LoadedModule[145]=C:\Windows\system32\SAMLIB.dll
LoadedModule[146]=C:\Windows\system32\netutils.dll
LoadedModule[147]=C:\Windows\system32\uiautomationcore.dll
LoadedModule[148]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[149]=C:\Windows\system32\OLEACC.dll
LoadedModule[150]=C:\Windows\System32\MMDevApi.dll
LoadedModule[151]=C:\Windows\System32\PROPSYS.dll
LoadedModule[152]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[153]=C:\Windows\system32\HID.DLL
LoadedModule[154]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[155]=C:\Windows\system32\wdmaud.drv
LoadedModule[156]=C:\Windows\system32\ksuser.dll
LoadedModule[157]=C:\Windows\system32\AVRT.dll
LoadedModule[158]=C:\Windows\system32\msacm32.drv
LoadedModule[159]=C:\Windows\system32\midimap.dll
LoadedModule[160]=C:\Windows\system32\dinput.DLL
LoadedModule[161]=C:\Windows\System32\wship6.dll
LoadedModule[162]=C:\Windows\System32\wshtcpip.dll
LoadedModule[163]=C:\Program Files (x86)\FSDiscover!\FSDiscoverFSX.dll
LoadedModule[164]=C:\Windows\system32\OPENGL32.dll
LoadedModule[165]=C:\Windows\system32\GLU32.dll
LoadedModule[166]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[167]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\iFly737NG.dll
LoadedModule[168]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[169]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FeelThere\E170\EJetH.dll
LoadedModule[170]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\A2A_Feel.dll
LoadedModule[171]=C:\Windows\SysWow64\XAudio2_6.dll
LoadedModule[172]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\AccuFeelMenu.dll
LoadedModule[173]=C:\Windows\system32\msadp32.acm
LoadedModule[174]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[175]=C:\Windows\SysWOW64\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[176]=C:\Windows\SysWOW64\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[177]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[178]=C:\Windows\system32\Secur32.dll
LoadedModule[179]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[180]=C:\Windows\system32\WINNSI.DLL
LoadedModule[181]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[182]=C:\Windows\system32\msimtf.dll
LoadedModule[183]=C:\Windows\system32\msls31.dll
LoadedModule[184]=C:\Windows\system32\d2d1.dll
LoadedModule[185]=C:\Windows\system32\DWrite.dll
LoadedModule[186]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[187]=C:\Windows\system32\MLANG.dll
LoadedModule[188]=C:\Windows\system32\ntmarta.dll
LoadedModule[189]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[190]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\jf_146.GAU
LoadedModule[191]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\jf_146-200_fmc.GAU
LoadedModule[192]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\VAGauge.GAU
LoadedModule[193]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\VAInfo.GAU
LoadedModule[194]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
LoadedModule[195]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\CLS_FSX_CONFIG.DLL
LoadedModule[196]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\CLS_FSX_SOUND2.GAU
LoadedModule[197]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\CLS_FSX_TCAS.DLL
LoadedModule[198]=C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll
LoadedModule[199]=C:\Windows\system32\explorerframe.dll
LoadedModule[200]=C:\Windows\system32\DUser.dll
LoadedModule[201]=C:\Windows\system32\DUI70.dll
LoadedModule[202]=C:\Windows\system32\EhStorShell.dll
LoadedModule[203]=C:\Windows\system32\ntshrui.dll
LoadedModule[204]=C:\Windows\system32\srvcli.dll
LoadedModule[205]=C:\Windows\system32\cscapi.dll
LoadedModule[206]=C:\Windows\system32\slc.dll
LoadedModule[207]=C:\Windows\System32\StructuredQuery.dll
LoadedModule[208]=C:\Windows\SysWOW64\actxprxy.dll
LoadedModule[209]=C:\Program Files (x86)\Internet Explorer\ieproxy.dll
LoadedModule[210]=C:\Windows\SysWOW64\thumbcache.dll
LoadedModule[211]=C:\Windows\system32\SearchFolder.dll
LoadedModule[212]=C:\Windows\system32\SHDOCVW.dll
LoadedModule[213]=C:\Windows\System32\drprov.dll
LoadedModule[214]=C:\Windows\System32\ntlanman.dll
LoadedModule[215]=C:\Windows\System32\davclnt.dll
LoadedModule[216]=C:\Windows\System32\DAVHLPR.dll
LoadedModule[217]=C:\Windows\system32\wkscli.dll
LoadedModule[218]=C:\Windows\system32\PortableDeviceApi.dll
LoadedModule[219]=C:\Windows\system32\PortableDeviceTypes.dll
LoadedModule[220]=C:\Windows\system32\LINKINFO.dll
LoadedModule[221]=C:\Windows\system32\NetworkExplorer.dll
LoadedModule[222]=C:\Windows\system32\EhStorAPI.dll
LoadedModule[223]=C:\Windows\system32\zipfldr.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Flight Simulator®
AppPath=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
 

Share this post


Link to post
Share on other sites

Thanks!  Your MS Visuals 2005 and 2008 are up-to-date.  MSV 2010 did not load but few FSX addons is using it.  Believe PMDG is using it now for their products.

 

MegaSceneryEarth stuff cannot cause a crash unless you have a lot of it installed (like me).  For one, the setup program will not allow a corrupted .bgl scenery file to be installed and will come back with an error report or tell you to download the setup again.  If you are missing scenery, default textures will be used where the photoscenery did not cover.  That's how I found a lot of missing files during the setup of 35 MegaSceneryEarth States.  As I mentioned above, it is known that MegaSceneryEarth will crash your computer if you have too many States enabled.  If you have too many States, they will eat up your system resources during startup of FSX and during the flight.  I have MegaSceneryEarth Indiana installed and it has not crashed my system.  Did you try disabling any other MSE State and then running just Indiana?  Just go into the Scenery Library and uncheck all the MSE States except Indiana that's installed.

 

The scenery folder should contain 308 .bgl files equaling 12.6 GB's.  There were 11 setup files to install.  I'm telling you this as it might have been possible that another State setup program got installed in the Indiana folder.  So maybe that kind of corruption could have caused your crashes.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Thanks Jim - Only Indiana is running, plus default fsx of course.  I'm going to count the bgl's now, and will report back - my computer says 12.6 GBs, BUT ONLY 307 FILES AND 1 FOLDER.  ORIGINALLY, when I installed Indiana, I mistakenly put some Iowa into it.  However, I moved the Iowa files.  I also completely uninstalled Indiana, and completely reinstalled it. 

 

I'll count and get back.

Share this post


Link to post
Share on other sites

 

 


BUT ONLY 307 FILES AND 1 FOLDER.

 

I was just looking at mine again and it shows one of the 308 files I mentioned earlier as being a ReadMeInstall document. So you should have 307. It's very difficult for me to understand how this scenery could be causing your computer to crash. I can remove 10 of the files and Indiana will successfully load. I would download and run Scenery Config Editor - http://fs-sceditor.sourceforge.net/actions.html .  You could have a corrupted scenery.dat file.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Thank heavens I have found someone with the same issue as me.  For example, I am using Utah and can start my flight in KSCL, but as soon as I head south anywhere near BCE (Bryce Canyon) then crash.   I have MI, FL, NY installed (no issues) but then in the last week I have installed CO, CT, UT and the all CTD somewhere.

 

I have found that I will get several different modules as the culprit in the APPCRASH file.  (util.dll, ntdll.dll, msvcr80.dll, fscopi~1.ocx)  although util.dll seems to be the most common.

 

If I remove the scenery, no issue. 

 

I have not started isolated it to a specific tile, but if it is likely just a corrupt tile at installation, I can start Isolating.   I just found it interesting that the files purchased in the last 2 weeks are all having this issue and the ones purchased a month or so more, run great.


 

 


I tried to fly form Nebraska to SD. But about 5 minutes into the flight it shut down - same issue, only

 

I too had an issue in Nebraska, coming from LA 75 - 100 miles in from the CO border.   Just curious if we are crashing with the same tile.

Share this post


Link to post
Share on other sites

Download this http://download.cnet.com/Process-Explorer/3000-2094_4-10223605.html and run it while FSX is up. Right click on the headings to open the select columns menu. Go to Process Memory and check Virtual Size. I place it next to the CPU and GPU columns. Because FSX is a 32bit application it has a limited memory space of 4Gb. If FSX Virtual Size starts to approach 2,400,000 K then you are setting up for an OOM and CTD.

 

I use MegaScenery Earth in several states and only load those that are in my flight path. Also consider that flying over a state at say FL350 isn't going to give you the kind of detail that photorealistic apps like MSE are designed for  so consider turning it off for your commercial cross country flights. Weather programs like REX also take up the program VAS when loadingweather into FSX. Take a look at the discussions here http://forum.avsim.net/topic/412418-looks-really-great-but-i-cant-buy-it/. This is happening when you use apps with high demand such as PMDG 737-800 NGX, REX Essential + Overdrive and MegaSceneryEarth at the same time. The last app to feed at the trough gets blamed for the crash but it is really systemic and a limitation of FSX and any other 32bit app.

 

Good luck,

Share this post


Link to post
Share on other sites

Rick,

 

I completely understand what you are saying and those are good ideas. But I have taken those other apps out of the equation.  I have been testing with FSX weather engine, clear skies, and the fsx default ultralight.  I can load up my flight with no issue in the center of the state and fly with great FPS.  Then I try to start a flight @ KASE (CO) or KBCE (UT) and get the error when the loading screen is only at 30-40% loaded.

 

I have also removed UTX - US and FS Global Ultimate - NAM for I thought there might be a conflict with those and the MSE UTAH scenery.  My error and System Setup is here if needed.  http://forum.avsim.net/topic/413174-megasceneryearth-20-ctd-issues/#entry2710679

 

I am just going to try to isolate a couple tiles at a time as suggested above.  The question is how to fix those tiles and how much determination I have  ;)

Share this post


Link to post
Share on other sites

I take it that MSE v2.0 is the common denominator. Try loading ProcessExplorer and run FSX through a failure. PE gives more informaton about what's going on in the computer than any similar program I've tried. You can isolate .EXEs, .DLLs and .NET calls. I have seen this type of complaint in PMDG, REX and MSE forums. I'm surprised that MSE hasn't responded to you. Maybe you should label your post something like "MSE CRASHES MY SYSTEM EVERY TIME I RUN IT (And I want my money back)!  You'd be surprised how something like that gets their attention.

 

I loaded up your flight from KASE to KBCE in a Carenado C182T and flew it at 3,000 to 4,000 AGL with no problems so I agree that you must have some corrupt files. MSE told me that they default to FSX standard BGLs if they detect load errors. You really have to get their input. I took a look at common solutions to your app crash and this is the easest solution from http://pcsupport.about.com/od/fixtheproblem/a/ntdlldll.htm.

Cause of Ntdll.dll Errors

The causes of ntdll.dll error messages can vary greatly. However, most ntdll.dll errors result from a corrupt or damaged version of the ntdll.dll file itself, corrupt hardware drivers, or issues between Windows and other programs.

Ntdll.dll errors can sometimes mean that a piece of hardware in your computer is malfunctioning, but this is rare.

How To Fix Ntdll.dll Errors
  1. Restart your computer. The ntdll.dll error you're receiving could be due to a one-time, temporary issue and a simple reboot may resolve the problem completely.
     
  2. Reinstall the program if the ntdll.dll error only displays when you use a specific program.

    If the software program has any updates or
    service packs available, install them too. The software's programmers may have identified an issue with the program that caused the ntdll.dll error and then issued a patch for it.

    Note: Third party software programs that have been installed on your computer are almost always the cause of ntdll.dll errors. The remainder of these troubleshooting steps resolve ntdll.dll issues only rarely.

 

 

 

This is a Bit-- of a problem and I'll check around to see if anyone can come up with something. I will follow this post and hopefully you can get to the bottom of this.

 

Rick

Share this post


Link to post
Share on other sites

I was able to nail it down to 6 tiles last night before I ran out of time.  (Not sure all 6 are an issue, but by removing the set of 6, I was able to fly around with no issue and with great FPS.)   So I am feeling pretty confident that it is a corrupt tile.

 

I was not able to re-install those tiles yet (I of course deleted the installation files, so I need to re-download all of them)  But I am hoping it was just an installation issue.

 

If not, I will definitely try using the ProcessExplorer tool you suggested.

 

Thank you all for your help.  CaptainKen, please keep me posted if you are fortunate enough to find resolution.  Our issues and systems sound very similar.

Share this post


Link to post
Share on other sites

Lots  LOTS of great input here.  I'm sorry that you, cbalow, are experiencing the same problem - but at the same time I am so relieved.  And although I have not specifically mentioned it, I too have the same problem with the NE/CO border.  OR NE/SD also.  And to make it clear, the same crash occurs with the default Cessna from FSX, with NO other programs running except MSE.  It crashes - same place every time.  SO I'm going to try the suggestions in the last couple of posts - and I will report back so everyone can know.  What is GOOD to come out of this is to see all the wonderful people whop are willing to try and help a complete stranger - THAT says magnitudes about the people who fly fsx, and who use this forum.  OK I'm off tor try these suggestions.

 

Heartfelt thanks to all of you.

 

Ken

Share this post


Link to post
Share on other sites

×
×
  • Create New...