Jump to content
Sign in to follow this  
Followers 0
Flyers28

Need your help deciphering Report.....

By Flyers28, in Crash To Desktop (CTD) Forum

Recommended Posts

Flyers28    0

Flyers28
Posted

I am beyond frustrated.  Had a bunch of CTD's the other day but they were all before I took off.  Deleted cfg file and today half way into my flight it crashes.  I have no idea what is causing this all of a sudden so i Copied the report and hopefully someone that understands what this says can help me find a solution. The only Addon i have is REX.  I had some textures for the default cessna, but deleted those yesterday when I was getting all the crashes thinking they were the culprit but I guess not. 

 

Version=1
EventType=APPCRASH
EventTime=130553043909591581
ReportType=2
Consent=1
UploadTime=130553043910182026
ReportIdentifier=7c3b5312-3d40-11e4-8272-40167e20846a
IntegratorReportIdentifier=7c3b5311-3d40-11e4-8272-40167e20846a
WOW64=1
Response.BucketId=e646f79f5164c3c19411a460e2fb5f68
Response.BucketTable=1
Response.LegacyBucketId=73349593307
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.61637.0
Sig[2].Name=Application Timestamp
Sig[2].Value=46fadb14
Sig[3].Name=Fault Module Name
Sig[3].Value=ntdll.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.3.9600.17114
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=53648f36
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00040ab4
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=E:\FSX\fsx.exe
UI[3]=A fatal error occurred.
UI[4]=Windows can check online for a solution to the problem and try to restart the program.
UI[5]=Check online for a solution and restart the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=E:\FSX\fsx.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\apphelp.dll
LoadedModule[5]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[6]=C:\Windows\SYSTEM32\msvcrt.dll
LoadedModule[7]=C:\Windows\SYSTEM32\USER32.dll
LoadedModule[8]=C:\Windows\SYSTEM32\GDI32.dll
LoadedModule[9]=C:\Windows\SYSTEM32\SHELL32.dll
LoadedModule[10]=C:\Windows\SYSTEM32\SHLWAPI.dll
LoadedModule[11]=C:\Windows\SYSTEM32\OLEAUT32.dll
LoadedModule[12]=C:\Windows\SYSTEM32\MPR.dll
LoadedModule[13]=C:\Windows\SYSTEM32\SETUPAPI.dll
LoadedModule[14]=C:\Windows\SYSTEM32\sfc.dll
LoadedModule[15]=C:\Windows\SYSTEM32\WINSPOOL.DRV
LoadedModule[16]=C:\Windows\SYSTEM32\RPCRT4.dll
LoadedModule[17]=C:\Windows\SYSTEM32\combase.dll
LoadedModule[18]=C:\Windows\SYSTEM32\CFGMGR32.dll
LoadedModule[19]=C:\Windows\SYSTEM32\SspiCli.dll
LoadedModule[20]=C:\Windows\SYSTEM32\sfc_os.DLL
LoadedModule[21]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[22]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[23]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[24]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[25]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.16384_none_7c55c866aa0c3ff0\COMCTL32.dll
LoadedModule[26]=C:\Windows\SYSTEM32\mscms.dll
LoadedModule[27]=C:\Windows\SYSTEM32\ADVAPI32.dll
LoadedModule[28]=C:\Windows\SYSTEM32\ole32.dll
LoadedModule[29]=C:\Windows\SYSTEM32\WINMM.dll
LoadedModule[30]=C:\Windows\SYSTEM32\DDRAW.dll
LoadedModule[31]=C:\Windows\SYSTEM32\USERENV.dll
LoadedModule[32]=C:\Windows\SYSTEM32\COMDLG32.dll
LoadedModule[33]=C:\Windows\SYSTEM32\IMM32.dll
LoadedModule[34]=C:\Windows\SYSTEM32\WS2_32.dll
LoadedModule[35]=C:\Windows\SYSTEM32\dwmapi.dll
LoadedModule[36]=C:\Windows\SYSTEM32\msi.dll
LoadedModule[37]=C:\Windows\SYSTEM32\WINMMBASE.dll
LoadedModule[38]=C:\Windows\SYSTEM32\DCIMAN32.dll
LoadedModule[39]=C:\Windows\SYSTEM32\profapi.dll
LoadedModule[40]=C:\Windows\SYSTEM32\SHCORE.DLL
LoadedModule[41]=C:\Windows\SYSTEM32\MSCTF.dll
LoadedModule[42]=C:\Windows\SYSTEM32\NSI.dll
LoadedModule[43]=C:\Windows\SYSTEM32\DEVOBJ.dll
LoadedModule[44]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6229_none_cbee8c4a4710d003\MFC80.DLL
LoadedModule[45]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCR80.dll
LoadedModule[46]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6229_none_03c6cf28205ff947\MFC80ENU.DLL
LoadedModule[47]=E:\FSX\language.dll
LoadedModule[48]=E:\FSX\API.DLL
LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCP80.dll
LoadedModule[50]=E:\FSX\ablscpt.dll
LoadedModule[51]=E:\FSX\acontain.dll
LoadedModule[52]=E:\FSX\ai_player.dll
LoadedModule[53]=E:\FSX\atc.dll
LoadedModule[54]=E:\FSX\controls.dll
LoadedModule[55]=E:\FSX\demo.dll
LoadedModule[56]=E:\FSX\facilities.dll
LoadedModule[57]=E:\FSX\fe.dll
LoadedModule[58]=E:\FSX\flight.dll
LoadedModule[59]=E:\FSX\fsui.dll
LoadedModule[60]=E:\FSX\g2d.dll
LoadedModule[61]=E:\FSX\g3d.dll
LoadedModule[62]=E:\FSX\gps.dll
LoadedModule[63]=E:\FSX\livingwater.dll
LoadedModule[64]=E:\FSX\main.dll
LoadedModule[65]=E:\FSX\multiplayer.dll
LoadedModule[66]=E:\FSX\panels.dll
LoadedModule[67]=E:\FSX\sim1.dll
LoadedModule[68]=E:\FSX\simprop.dll
LoadedModule[69]=E:\FSX\simscheduler.dll
LoadedModule[70]=E:\FSX\sound.dll
LoadedModule[71]=E:\FSX\symmap.dll
LoadedModule[72]=E:\FSX\terrain.dll
LoadedModule[73]=E:\FSX\fs-traffic.dll
LoadedModule[74]=E:\FSX\ui.dll
LoadedModule[75]=E:\FSX\util.dll
LoadedModule[76]=E:\FSX\visualfx.dll
LoadedModule[77]=E:\FSX\weather.dll
LoadedModule[78]=E:\FSX\window.dll
LoadedModule[79]=E:\FSX\xuipc.dll
LoadedModule[80]=C:\Windows\SYSTEM32\MSWSOCK.dll
LoadedModule[81]=C:\Windows\SYSTEM32\SHFOLDER.dll
LoadedModule[82]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[83]=C:\Windows\SYSTEM32\POWRPROF.dll
LoadedModule[84]=C:\Windows\SYSTEM32\DINPUT8.dll
LoadedModule[85]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.17227_none_dad9452e5bcb7986\gdiplus.dll
LoadedModule[86]=C:\Windows\SYSTEM32\d3dx9_34.dll
LoadedModule[87]=C:\Windows\SYSTEM32\d3dx10_34.dll
LoadedModule[88]=C:\Windows\SYSTEM32\d3d9.dll
LoadedModule[89]=C:\Windows\SYSTEM32\DSOUND.dll
LoadedModule[90]=C:\Windows\SYSTEM32\WININET.dll
LoadedModule[91]=C:\Windows\SYSTEM32\MSACM32.dll
LoadedModule[92]=C:\Windows\SYSTEM32\MSIMG32.dll
LoadedModule[93]=C:\Windows\SYSTEM32\iertutil.dll
LoadedModule[94]=C:\Windows\SYSTEM32\kernel.appcore.dll
LoadedModule[95]=C:\Windows\system32\uxtheme.dll
LoadedModule[96]=C:\Program Files (x86)\Stardock\ModernMix\MMix_32.dll
LoadedModule[97]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[98]=C:\Windows\system32\rsaenh.dll
LoadedModule[99]=C:\Windows\SYSTEM32\bcrypt.dll
LoadedModule[100]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL
LoadedModule[101]=C:\Windows\SYSTEM32\clbcatq.dll
LoadedModule[102]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[103]=C:\Windows\SYSTEM32\dxgi.dll
LoadedModule[104]=C:\Windows\SYSTEM32\d3d11.dll
LoadedModule[105]=C:\Windows\SYSTEM32\nvd3dum.dll
LoadedModule[106]=C:\Windows\SYSTEM32\PSAPI.DLL
LoadedModule[107]=C:\Windows\system32\nvspcap.dll
LoadedModule[108]=C:\Windows\SYSTEM32\CRYPT32.dll
LoadedModule[109]=C:\Windows\SYSTEM32\MSASN1.dll
LoadedModule[110]=C:\Windows\system32\nvapi.dll
LoadedModule[111]=C:\Windows\SYSTEM32\D3DCompiler_34.dll
LoadedModule[112]=C:\Windows\SYSTEM32\WindowsCodecs.dll
LoadedModule[113]=C:\Windows\SYSTEM32\d3d10_1.dll
LoadedModule[114]=C:\Windows\SYSTEM32\d3d10_1core.dll
LoadedModule[115]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[116]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[117]=C:\Windows\SYSTEM32\wbemcomn.dll
LoadedModule[118]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[119]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[120]=C:\Windows\system32\winbrand.dll
LoadedModule[121]=C:\Windows\SYSTEM32\WINTRUST.dll
LoadedModule[122]=C:\Windows\SYSTEM32\WTSAPI32.DLL
LoadedModule[123]=C:\Windows\SYSTEM32\WINSTA.dll
LoadedModule[124]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_a9efdb8b01377ea7\COMCTL32.dll
LoadedModule[125]=C:\Windows\SYSTEM32\msxml6.dll
LoadedModule[126]=C:\Windows\SYSTEM32\uiautomationcore.dll
LoadedModule[127]=C:\Windows\SYSTEM32\sxs.dll
LoadedModule[128]=C:\Windows\System32\MMDevApi.dll
LoadedModule[129]=C:\Windows\SYSTEM32\AUDIOSES.DLL
LoadedModule[130]=C:\Windows\SYSTEM32\RICHED20.DLL
LoadedModule[131]=C:\Windows\SYSTEM32\USP10.dll
LoadedModule[132]=C:\Windows\SYSTEM32\msls31.dll
LoadedModule[133]=C:\Windows\SYSTEM32\HID.DLL
LoadedModule[134]=C:\Windows\SYSTEM32\XInput9_1_0.dll
LoadedModule[135]=C:\Windows\SYSTEM32\wdmaud.drv
LoadedModule[136]=C:\Windows\SYSTEM32\ksuser.dll
LoadedModule[137]=C:\Windows\SYSTEM32\AVRT.dll
LoadedModule[138]=C:\Windows\SYSTEM32\msacm32.drv
LoadedModule[139]=C:\Windows\SYSTEM32\midimap.dll
LoadedModule[140]=C:\Windows\SYSTEM32\dinput.DLL
LoadedModule[141]=C:\Windows\SYSTEM32\XInput1_4.dll
LoadedModule[142]=C:\Windows\SYSTEM32\ieframe.dll
LoadedModule[143]=C:\Windows\SYSTEM32\PROPSYS.dll
LoadedModule[144]=C:\Windows\SYSTEM32\Secur32.dll
LoadedModule[145]=C:\Windows\SYSTEM32\mshtml.dll
LoadedModule[146]=C:\Windows\system32\msimtf.dll
LoadedModule[147]=C:\Windows\SYSTEM32\d2d1.dll
LoadedModule[148]=C:\Windows\SYSTEM32\DWrite.dll
LoadedModule[149]=C:\Windows\SYSTEM32\d3d10warp.dll
LoadedModule[150]=C:\Windows\SYSTEM32\MLANG.dll
LoadedModule[151]=C:\Windows\SYSTEM32\imagehlp.dll
LoadedModule[152]=C:\Windows\SYSTEM32\ncrypt.dll
LoadedModule[153]=C:\Windows\SYSTEM32\NTASN1.dll
LoadedModule[154]=C:\Windows\SYSTEM32\gpapi.dll
LoadedModule[155]=C:\Windows\SYSTEM32\cryptnet.dll
LoadedModule[156]=C:\Windows\SYSTEM32\WLDAP32.dll
LoadedModule[157]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[158]=C:\Windows\SYSTEM32\WINNSI.DLL
LoadedModule[159]=C:\Windows\SYSTEM32\msadp32.acm
LoadedModule[160]=C:\Windows\SYSTEM32\ntmarta.dll
LoadedModule[161]=E:\FSX\GAUGES\Cessna.DLL
LoadedModule[162]=E:\FSX\GAUGES\Cessna172.DLL
LoadedModule[163]=E:\FSX\GAUGES\Cessna182s.DLL
LoadedModule[164]=E:\FSX\GAUGES\CessnaWAlpha.DLL
LoadedModule[165]=E:\FSX\GAUGES\Bendix_King_Radio.DLL
LoadedModule[166]=E:\FSX\GAUGES\Bell_206B.DLL
LoadedModule[167]=C:\Windows\SYSTEM32\dxdiagn.dll
LoadedModule[168]=C:\Windows\SYSTEM32\nvwgf2um.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft® Flight Simulator X
AppPath=E:\FSX\fsx.exe
ApplicationIdentity=00000000000000000000000000000000
 

Share this post

Link to post
Share on other sites

Jim Young    2,356

Jim Young
Posted

An ntdll.dll crash usually means a bad setting in your overclock or BIOS setting. CPU voltage too high too low. If you have MyTrafficX installed, disable and see if this fixes the problem.

 

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

Flyers28    0

Flyers28
Posted

Thanks for responding...your a busy man around these forums firehawk.  I do not have MytrafficX.  Computer is less than a month old and purchased through Digital Storm who does all the setup and benchmarks.  I do not believe they overclocked the cpu, but will check when i get home.

Share this post

Link to post
Share on other sites

Jim Young    2,356

Jim Young
Posted

According to the AVSIM CTD Guide:

 

NTDLL.dll – Several possibilities as follows:

 

Heap metadata can become corrupted and it has been identified by Microsoft as one of the most common causes of application failures. When an application crash shows the faulting module as ntdll.dll along with the Memory Access Violation (0xc0000005), then Windows places the application on a watch list and, if the application crashes at least four times or more in an hour, the fault tolerant heap service will configure the application to use the fault tolerant heap service in the future (Source - Chapter 10, Memory Management, Windows Internals, Part 2: Covering Windows Server 2008 R2 and Windows 7 by Mark E. Russinovich, David A Solomon, and Alex Ionescu). The service is part of the Security Center service so you need to make sure this service is turned on.

 

You might get an NTDLL.dll shown as the faulting module if you have MyTrafficX 5.4c installed. It is believed to be caused by an AI scheduling programming error. A fix was being worked on.

 

An NTDLL.dll crash can also occur if your system overheats or you have wrong voltages set for your installed RAM or CPU but this is less likely as you will most likely get a BSOD instead of a CTD.

 

I got this crash several times until I discovered by RAM settings in the BIOS did not match the settings as shown in the CPU-Z under the SPD Tab.  For instance, I had my overclock profile set at X.M.P (the best) and, under the SPD Tab in the CPU-Z, my timings and voltages did not match those under the XMP column.  I made sure they were set properly and the CTD went away. 

 

There is really no known solution for this crash that fits everyone who gets the ntdll.dll CTD.  Systems are just not set up the same.  Some have tweaks in their FSX.cfg, some do not.  Some are overclock, some are not.  Sliders are set high in some, and sliders in others are not set very high.  Yet they all get the crash.  So you have to conduct an investigation for the cause of your crash yourself as you are the only one who has access to your computer.  The AVSIM CTD Guide (and this forum) provide some clues or areas you can research.  When I get a crash that I do not know why it happened, I'll click on the search box above, type in the faulting module (ntdll.dll), click on the word Google (this will open up several more options) and select search This Forum.  That's just a suggestion.  Many others go to Google and search the whole Internet.  Perhaps others will come here and give you even more suggestions but the information in the CTD Guide is fairly current (an update will be posted someday soon).  Another reason found for the crash by one individual was a corrupt alpha channel in an AIA Embraer 190 from Lufthansa Cityline. He/she removed the aircraft and the crashes went away.

 

A tweak like the Bufferpools tweak can cause StackHash type crashes which are similar to ntdll.dll crashes. One time I got a StackHash crash then the next day an ntdll.dll crash then the next day a StackHash and it all turned out to be the fault of MyTrafficX. This is why rebuilding your fsx.cfg will usually fix most problems as you have a parameter that is not working for your computer.

 

Hope this helps.

 

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

Flyers28    0

Flyers28
Posted

Thanks again firehawk.  I will have to do one thing at a time till I find a solution.  Already deleted .cfg file no help.  Next I will drop a few sliders and try that.  From there I will start to look at system settings.

 

Really appreciate the help.  I now have both the CTD guide and the settings Guide on my desktop ready for quick access so I don't make you have to copy/paste and write out a lengthy explanation each time, haha.

Share this post

Link to post
Share on other sites

Flyers28    0

Flyers28
Posted

Any chance my Saitek x45 joystick could cause this error.  The problems did start occurring after I plugged it in.  I just got the stick early this week.  I can not find any drivers for it since saitek does not support it anymore and there does not seem to be Windows 8 drivers.  I just plugged it in and let windows do its thing.  This was brought to my attention on a non FSX support forum.

 

Anybody have this stick and windows 8 and have issues/solutions?

Share this post

Link to post
Share on other sites

Jim Young    2,356

Jim Young
Posted

In the Windows 8 forum there is a long thread about joystick controllers and incompatibility (I mean, it's really long!). Another reason why I do not like Windows 8. What did they do to the code to destroy compatibility???

 

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

Flyers28    0

Flyers28
Posted

In the Windows 8 forum there is a long thread about joystick controllers and incompatibility (I mean, it's really long!). Another reason why I do not like Windows 8. What did they do to the code to destroy compatibility???

 

Best regards,

ugggh I could not agree more.  I hate windows 8.  Windows 7 was finally an OS I could live with.  Wish I had a choice which OS I could have had installed when my pc was built, and I was to lazy to build my own PC this time around. Not to mention I lost my installation disk for Windows 7 so that's not even an option.  So I am stuck with Win8.

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  
Followers 0
Go To Topic Listing

  • 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.
×
×
  • Create New...