I am attempting to run the Coolsky Super 80 Pro within Lockheed Martin's Perpar3D flight simulator, but each time I load the plane, and configure the gauges as they are needed for flight, I notice that somehow the Direct X Diagnostic Tool is triggered in the task manager under the simulator details, causing the game to freeze, and eventually CTD. I have tested the same plane and configuration within Microsoft Flight Simulator: Steam Edition with the same results. I was able to grab a log file from FSX after the crash which showed the access violation error as being the cause of the crash. But would that also tie in to the diagnostic tool being engaged? I also produced a log file for P3D in Windows 10, during the crash event, and it read similarly, which is why the 7 log file is subbed in, as it was easiest to find at the time of posting. Both OS's suffer the issue in short. NOTE: I HAVE ALREADY been in contact with the official Super 80 Pro forums, going so far as to having the developers send me additional, unpublished gauge files to test in my simulator. Each of them has caused this issue to trigger. 

What could that be? Thanks.

Microsoft (R) Windows Debugger Version 10.0.17061.1000 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [E:\Steam\steamapps\common\FSX\fsx_62615_crash_2018_1_21T2_46_9C1.mdmp] Comment: 'Minidump: C:\Steam\steamapps\common\FSX\fsx.exe ' User Mini Dump File: Only registers, stack and portions of memory are available Symbol search path is: srv* Executable search path is: Windows 7 Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible Product: WinNt, suite: SingleUserTS Machine Name: Debug session time: Sat Jan 20 20:46:09.000 2018 (UTC - 6:00) System Uptime: not available Process Uptime: 0 days 0:01:55.000 ................................................................ ................................................................ ................................................................ .................... This dump file has an exception of interest stored in it. The stored exception information can be accessed via .ecxr. (47c.984): Access violation - code c0000005 (first/second chance not available) eax=00000000 ebx=00000000 ecx=4f4f5828 edx=6c05d5a0 esi=00000ee0 edi=04929549 eip=77430c72 esp=002ad37c ebp=002ad38c iopl=0 nv up ei pl zr na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246 ntdll!ZwGetContextThread+0x12: 77430c72 83c404 add esp,4 ************* Path validation summary ************** Response Time (ms) Location Deferred srv*

On 1/29/2018 at 8:56 PM, pilotguy251 said:

What could that be? Thanks.

Microsoft (R) Windows Debugger Version 10.0.17061.1000 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [E:\Steam\steamapps\common\FSX\fsx_62615_crash_2018_1_21T2_46_9C1.mdmp] Comment: 'Minidump: C:\Steam\steamapps\common\FSX\fsx.exe ' User Mini Dump File: Only registers, stack and portions of memory are available Symbol search path is: srv* Executable search path is: Windows 7 Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible Product: WinNt, suite: SingleUserTS Machine Name: Debug session time: Sat Jan 20 20:46:09.000 2018 (UTC - 6:00) System Uptime: not available Process Uptime: 0 days 0:01:55.000 ................................................................ ................................................................ ................................................................ .................... This dump file has an exception of interest stored in it. The stored exception information can be accessed via .ecxr. (47c.984): Access violation - code c0000005 (first/second chance not available) eax=00000000 ebx=00000000 ecx=4f4f5828 edx=6c05d5a0 esi=00000ee0 edi=04929549 eip=77430c72 esp=002ad37c ebp=002ad38c iopl=0 nv up ei pl zr na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246 ntdll!ZwGetContextThread+0x12: 77430c72 83c404 add esp,4 ************* Path validation summary ************** Response Time (ms) Location Deferred srv*

It looks like you might be working with 2 FSX installations. Did you move FSX from your C drive to your E drive? There might be something trying to load something from the wrong folder. 

Access violation indicates that security blocked something. 

This is normal when you have a CTD.  The Microsoft Aces Team (developers) thought, in 2006, they would be able to diagnose a crash if you reported it.  It makes a copy of your FSX.cfg and runs DXDiag so they will have the latest information regarding the crash.  Unfortunately it never worked.  They discovered that AVSIM was planning to publish an AVSIM CTD Guide which provided information regarding crashes and some tools to diagnose them and perhaps solve the cause for the crash.  It appears you had an ntdll.dll as the faulting module which is quite common in FSX.  The Access violation code c000005 means you had a Memory Access Violation.  Please check out the AVSIM CTD Guide (link in my signature) for more information about ntdll.dll errors and probable causes/solutions to the error.

Best regards,

Jim

I've been experiencing the same P3D Freeze and Crashes pointing to dxdiag.exe as well as one other .dll for a 3rd party aircraft builder . .  I had MSFT on the phone twice now for over an hour (paid support) to clean up all  kinds of driver issues and C++ redist 1534 errors and assorted other WIN10 1809 "actual Bugs". ASll that sorted out now. running GTX980 and 16Gig i7 4790 at 4Ghz WIN10x64.  . . and it's still there. running dxdiag.exe shows "no issues" for 3x27" monitors and sound. I may roll back the GTX980 drivers but this happened long before my last driver upgrade to GeForce 417.71 about mid Jan 2019. The other .dll crashes have not reappeared since fixing input device drivers so it's down to dxdiag alone now.

Any additional suggestions welcome . . as a note for people who may be struggling also . . here are those two WIN10 BUGS I found fixes for below

Cheers cookednlh

================== WIN10 64 build 1809 BUG ===========================

This is a followup to the OPEN ticket about my crashing P3D libcef.dll issue. Definitely C++ Redist 2015 issue was involved and clearly a Microsoft BUG . . . but there is another called 1534 UserProfile Warning! . . I have flown successfully now for a few hours with no P3D Crash and no more references to libcef.dll or Dxdiag.exe . . and no Warnings that would cause a P3D Pause of several seconds just before the CRASH. The most recent major update WIN10 1809 (Oct 2018) failed to delete 2 obsolete REG Keys that would pause P3D with warnings until it gave up and crashed. I will keep close watch on my Event Manager but unless I see something new, I think this issue is now closed.

I believe I now have the answer, ( from "sevenmm1985" published here https://social.technet.microsoft.com/Fo ... networking in October 2018 . .which should be noted for anyone who needs it.

He had the same issue and wrote this. I have done this fix and it appears to work . . no more 1534 Warnings in the system . .period. P3D v4.4 running smoothly again.

===============sevenmm1985 wrote=================
Finally found a FIX for 1534 error !

1. Open Regedit and navigate to the following two keys
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileNotification
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\ProfileNotification
2. Under ProfileNotification check if you have the TDL key
3. Export the TDL key at each location
4. Delete the TDL key at each location
5. Reboot PC to verify

Note:
You'll need take ownership of the TDL Key to be able to delete it.

Works for me like a charm with no downsides.

After this fix the 1534 barage has stopped in my OS :)

================= END=======================

 

============ Redistributable C++ 2015 2017 CONFLICT ========================

When you try to install Visual C++ 2015 (x86 and x64) version 14.0.24215 after installing Visual C++ 2017 redistributable you get the error message

"0x80070666 - Another version of this product is already installed. Installation of this version cannot continue.To configure or remove the existing version of this product, use Add/Remove programs on the control panel.

The registry locations used to see if Visual C++ 2015 (x86 and x64) version 14.0.24215 is installed get removed or replaced after you install Visual C++ 2017 (x86 and x64) version 14.15.26706.0.

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\14.0\VC\Runtimes\x64

and

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\14.0\VC\Runtimes\x86

I assume we still need Visual C++ 2015 redistributables.

So if we try to install Visual C++ 2015 (x86 and x64) version 14.0.24215 after Visual C++ 2017 (x86 and x64) version 14.15.26706.0 we get the "0x80070666 - Another version of this product is already installed. Installation of this version cannot continue.To configure or remove the existing version of this product, use Add/Remove programs on the control panel. "

And if we install the Visual C++ 2015 (x86 and x64) version 14.0.24215 before Visual C++ 2017 (x86 and x64) version 14.15.26706.0 it replaces the registry locations and no longer appears in Control Panel.

When you uninstall Visual C++ 2017 (x86 and x64) version 14.15.26706.0 it also removes the Visual C++ 2015 (x86 and x64) version 14.0.24215 from the control panel and registry.

As a workaround to this error 0x80070666, people are manually doing the following:

1. open command prompt

2. change your directory to the relevant folder. I.e.

>cd C:\Users\<user>\Downloads:

3. run the following from the command line and call up the 2015 redist pkg with this command:

vc_redist.x64.exe /uninstall

or

vc_redist.x86.exe /uninstall

4. a popup will show with the option to repair the installation. The repair succeeded and is able to install.

Hopefully this can be fixed in the next Visual C++ 2017 (x86 and x64) version so that we don’t need to create work arounds.

 

 

 

 

The AVSIM CTD Guide tells you what Redistributables you need as the program is very old.  Why you are trying to install msv's 2017 is beyond my comprehension.  Only need that if an addon calls for it but not to run FSX,