michaelengl

Simulator Crashed and failure Active Sky "Cannot control amb

Recommended Posts


I have problems with my P3Dv4 (latest version). If the simulator is loading the it takes 2 sec. to load ChasePlane (or EZDOK) and then I can use it. In this Moment i hear a USB connected sound. At the same time my simulator crashed.

If ChasePlane is active in exe.xml there are  3 failures and the software Active Sky  prompt "Cannot control ambient weather parameters" 

1. Name der fehlerhaften Anwendung: PREPAR3D.EXE, Version: 4.3.29.25520, Zeitstempel: 0x5b2c3263
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.17134.376, Zeitstempel: 0x60d78cf9
Ausnahmecode: 0xc0000374
Fehleroffset: 0x00000000000f4d7b
ID des fehlerhaften Prozesses: 0x3434
Startzeit der fehlerhaften Anwendung: 0x01d4737db9783be4
Pfad der fehlerhaften Anwendung: D:\_P3Dv4\PREPAR3D.EXE
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: ae451073-6b60-4cb9-aeda-bd405c773980
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 


2. Application: ChasePlane.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at Microsoft.Win32.NativeMethods.ShellExecuteEx(ShellExecuteInfo)
at System.Diagnostics.ShellExecuteHelper.ShellExecuteFunction()
at System.Diagnostics.ShellExecuteHelper.ShellExecuteOnSTAThread()
at System.Diagnostics.Process.StartWithShellExecuteEx(System.Diagnostics.ProcessStartInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(System.Diagnostics.ProcessStartInfo)
at A.Y.A()
at A.Y..ctor(ChasePlane.MainWindow, System.Windows.Window, System.Collections.Generic.List`1<a.ab>)
at ChasePlane.MainWindow..ctor()
at a.aB.A()
at a.aB.A(System.Object, System.Windows.StartupEventArgs)
at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
at System.Windows.Application.<.ctor>b__1_0(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run(System.Windows.Window)
at a.aB.c()


3. Name der fehlerhaften Anwendung: ChasePlane.exe, Version: 1.0.9.0, Zeitstempel: 0x5bc2bfe5
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.17134.376, Zeitstempel: 0x4358e406
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00046adc
ID des fehlerhaften Prozesses: 0xab8
Startzeit der fehlerhaften Anwendung: 0x01d4737dcfab26a6
Pfad der fehlerhaften Anwendung: D:\Program Files (x86)\OldProp Solutions Inc\ChasePlane\ChasePlane.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: 73d59367-e6b7-48db-a8e5-8c1d92af9e98
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

If ChasePlane was deactivated I get also 3 failure:

1. Name der fehlerhaften Anwendung: PREPAR3D.EXE, Version: 4.3.29.25520, Zeitstempel: 0x5b2c3263
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.17134.254, Zeitstempel: 0xa5a334d4
Ausnahmecode: 0xc0000374
Fehleroffset: 0x00000000000f4d3b
ID des fehlerhaften Prozesses: 0x19b4
Startzeit der fehlerhaften Anwendung: 0x01d47369dd3270c1
Pfad der fehlerhaften Anwendung: D:\_P3Dv4\PREPAR3D.EXE
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: c3016c34-1d0d-4112-92ac-b3e8a8575b8d
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

2. Die erweiterbare Leistungsindikator-DLL rdyboost kann nicht geladen werden. Die ersten vier Bytes (DWORD) des Datenbereichs enthalten den Windows-Fehlercode.

 

If ChasePlane was not active and I have restart ProSim the I hear also the USC connected sound an P3D crash. Is anybody know what could be the reason. All drivers are the latest, Shaders deleted and the normal procedures in this forum i have made.

Best Michael 


3.Die Open-Prozedur für den Dienst "BITS" in der DLL "C:\Windows\System32\bitsperf.dll" war nicht erfolgreich. Die Leistungsdaten für diesen Dienst sind nicht verfügbar. Die ersten vier Bytes (DWORD) des Datenbereichs enthalten den Fehlercode.

Share this post


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

See page 35, AVSIM CTD Guide, for solutions found for the ntdll.dll error around the Internet.  Could be bad overclock, bad memory module, bad textures, incompatible add-ons, bad p3d.cfg, etc., etc.  Too many possible causes.

Share this post


Link to post
Share on other sites

Had the same problem couple days ago.

6 x times crashes on the flight from EDDM-ESSA. Crash over Dresden (entering ORBX Germany North) failure message : ASP4..ambient....... Active sky has nothing to do with the problem. It happens without ASP4 too.
1. I fixed my crashes (always happened at the same location) with this:
https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system

in ORBX Germany North had flashing lights

2. The flashing lights / pylons in ORBX Germany North: I solved this problem,
changing settings from 8xMSAA to 4xSSAA

hope I could help

best regards, Mav

 

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