I can't seem to find much info on this online, but a common issue i'm having during a longer flight is that suddenly p3d v2.3 will crash to the desktop with the error surrounding atc.dll.

 

Im running windows 8.1 U1 x64 (not using compatibility mode), with UAC enabled (not running fsx as admin.. its installed on another drive letter).

 

I've stripped down my dll.xml to pretty much just FSUIPC at this point, so i'm unsure its anything there.. maybe related to an addon..

 

I'm unclear what causes this dll to crash or what it relates to?

 

(I've also gotten window.dll crash and d3dcsx_43.dll (this one when changing scenery settings), once an msvcr100.dll and another time ntdll.dll.. but more often than not its just atc.dll lately (if at all).

 

Any thoughts on this one.. trying to figure out what to isolate first based on what atc.dll does..

For now im now testing with a stripped down scenery.cfg with very little installed.

 

Thanks

I've got an update to my issues with crashing and out of memory errors.. so far.. it would seem, since setting my 4930k cpu clock down to a fixed 3.9 (which i believe is the turbo speed anyway), down from the 4.4ghz i had it at, as well as lowering ram from 2400 mhz to 1866.. i havent been able to replicate an error..

 

This is slightly strange, in that i was prime95 24 hours stable long ago, though perhaps i am no longer stable with that overclock.

 

Next step after more error free flights would be to bump the ram back up, test.. wait.. then go back to 4.4.. confirm errors.. then do some prime95 testing on a spare harddrive (i have a test partition on this OS drive, split from the other, but i feel still unsafe to overclock test even with dual partitions, hence i use a separate drive to be safe, cloned)

 

I had read about stability causing errors, but i thought that was primarily ntdll.dll and also not the cause of the out of memory message box (which occurs even if VAS limits are not hit for me when it did).

I thought maybe i was out of woods.. well not quite..

 

On exiting a saved flight, midway in flight (like the first 1 minute).. i closed with control C.. on program exit still getting random crashes..

 

They center around random dlls.. whether its atc.dll or another dll.. it always shows up in conjunction with a .net runtime error 1026 prepar3d.exe process was terminated due to an unhandled exception framework 4.0.30319 exception code 0x0000005

 

From digging around on the net i came across a note that perhaps doing the "vista" uiautomation dll trick would help (putting in the root of p3d, like back in fsx days)..

 

I did this, so far it has not crashed.. holding breath.

Just an update to my dll issues:  I'm still running in non overclocked mode and still getting the random dll crash on an exit of the program.  Its typically atc.dll..

 

Going back to trying thinned down dll.xml files to see if there is a conflict there somewhere.

Thank you for posting your progress. It will be instructive for all of us.

 

Graham

There are minor issues where the file atc.dll, responsible for containing the viewing graphics display during game play, encounters errors in displaying multiple image streams, especially when it renders multiple overlays. If you have multiple displays and/or multiple Windows open, there is probably a conflict or problem with the configuration. Troubleshoot.

 

I had similar crashes a couple of years ago on a less powerful system. I ran memtest86 and the IntelBurnTest and my computer passed every time. No problems whatsoever with memory. But, every time I ran FSX, I would get these types of crashes. In the BIOS, I saw that my memory settings were set to Auto which meant my ASUS board would manage the memory settings for me. Wrong! I looked at CPU-Z and saw that my memory was not set up properly with the settings as shown under the SPD tab. I went into the BIOS and changed those settings to what was shown under the SPD tab and my crashes went away. Totally. I later found out that some ASUS boards had issues managing system memory properly. I now use the X.M.P. profile in the BIOS for any overclocking. So I think this is what is causing your crashes. If you do not have your overclock set to the X.M.P. profile, then you will have to manually make sure your memory is set to the settings as shown under the SPD tab in the CPU-Z.

 

Best regards,

There are minor issues where the file atc.dll, responsible for containing the viewing graphics display during game play, encounters errors in displaying multiple image streams, especially when it renders multiple overlays. If you have multiple displays and/or multiple Windows open, there is probably a conflict or problem with the configuration. Troubleshoot.

 

I had similar crashes a couple of years ago on a less powerful system. I ran memtest86 and the IntelBurnTest and my computer passed every time. No problems whatsoever with memory. But, every time I ran FSX, I would get these types of crashes. In the BIOS, I saw that my memory settings were set to Auto which meant my ASUS board would manage the memory settings for me. Wrong! I looked at CPU-Z and saw that my memory was not set up properly with the settings as shown under the SPD tab. I went into the BIOS and changed those settings to what was shown under the SPD tab and my crashes went away. Totally. I later found out that some ASUS boards had issues managing system memory properly. I now use the X.M.P. profile in the BIOS for any overclocking. So I think this is what is causing your crashes. If you do not have your overclock set to the X.M.P. profile, then you will have to manually make sure your memory is set to the settings as shown under the SPD tab in the CPU-Z.

 

Best regards,

Hi there,

 

Thanks for that tidbit of info to check.. Unfortunately on my system the memory is already set to xmp, everything looks good in cpuz..

 

I'm still trying to isolate the cause of the random crash.

 

It's been more specific lately..  I have a saved flight that kept crashing just after it would load.. it seemed dependent on 2 things..

One it was at KJFK.. if i had US Cities X and Flytampa KBUF enabled in the scenery library at the same time, it seemed to occur about once every other load.. this was perhaps a coincidence.. (i even tried excluding kbuf related bgls in the us cities scenery, thinking maybe something was conflicting between them) or maybe it was because they aren't truly "p3d-compatible"..

 

But i think that was a premature assessment.. now i'm thinking perhaps its a few of my imported aircraft.. ultimately i may end up pulling those out and retesting, but for now i took out the one in question.

 

In this case the saved flight was saved with the Realair Cessna 172.. i removed it, relaunched in visualization only mode.. so far 3 attempts in, no crashes..

 

Of course i'll still get the random crash on closing the program, though again, this could be scenery or aircraft related.. time to rinse and repeat in a more "sterile" test to be sure

 

Oh, the crash that possibly is associated with the addon craft.. has been pretty consistent.. d3dcsx_43.dll (c:\windows\system32) a directx module

same thing is happening on P3D V3 too