Flayn Posted June 20, 2021 Share Posted June 20, 2021 Affinity crashed when I used the photo stacking function After starting again a bug report window was displayed I clicked submit, which caused an instant crash Now affinity wont start anymore I tried uninstall and reinstall of the latest and previous versions, nothing helped. Quote Link to comment Share on other sites More sharing options...
Komatös Posted June 20, 2021 Share Posted June 20, 2021 Hold CTRL if you start Photo. Quote AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.2161) Affinity Suite V 2.5.5 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF I am not old, I have matured like a good scotch! Link to comment Share on other sites More sharing options...
Flayn Posted June 20, 2021 Author Share Posted June 20, 2021 2 hours ago, Komatös said: Hold CTRL if you start Photo. Thanks for responding, but it still won't start Quote Link to comment Share on other sites More sharing options...
Komatös Posted June 20, 2021 Share Posted June 20, 2021 Ok, let's see if there is a crash report. Press Windows key + R. Copy & Paste or type %AppData%\Affinity\photo\1.0\Crashreports\reports. Click OK or press Enter. If there is more than one .dmp file in the folder, please attach the file with the latest timestamp to the next post. The log.txt is also of interest. You can find it in the folder 1.0. What else you can do: Rename the folder 1.0 to e.g. 1.0_bkup. Then restart APhoto. When APhoto should start, go to the preferences --> performance in APhoto and deactivate the hardware acceleration. Quote AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.2161) Affinity Suite V 2.5.5 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF I am not old, I have matured like a good scotch! Link to comment Share on other sites More sharing options...
Flayn Posted June 20, 2021 Author Share Posted June 20, 2021 5 minutes ago, Komatös said: Ok, let's see if there is a crash report. Press Windows key + R. Copy & Paste or type %AppData%\Affinity\photo\1.0\Crashreports\reports. Click OK or press Enter. If there is more than one .dmp file in the folder, please attach the file with the latest timestamp to the next post. The log.txt is also of interest. You can find it in the folder 1.0. What else you can do: Rename the folder 1.0 to e.g. 1.0_bkup. Then restart APhoto. When APhoto should start, go to the preferences --> performance in APhoto and deactivate the hardware acceleration. There is no crashreport and renaming the folder did not help. Maybe it could be related to a windows update that I just installed? I installed KB5003637, KB4023057 and the .NET Core security path 3.1.16 via windows update. I also found several entries in the EventViewer. Most of them are from my starts of affinity Name der fehlerhaften Anwendung: Photo.exe, Version: 1.9.2.1035, Zeitstempel: 0x60619cc7 Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.19041.964, Zeitstempel: 0x812662a7 Ausnahmecode: 0xe0434352 Fehleroffset: 0x0000000000034b89 ID des fehlerhaften Prozesses: 0x1b80 Startzeit der fehlerhaften Anwendung: 0x01d7650e9cf20a5a Pfad der fehlerhaften Anwendung: C:\Program Files\Affinity\Photo\Photo.exe Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\KERNELBASE.dll Berichtskennung: a0d1c015-1c1c-4801-9549-80c08dbd81f9 Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: This one might also be interesting: Application: Photo.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at MS.Win32.UnsafeNativeMethods.GetIconInfo(System.Runtime.InteropServices.HandleRef, ICONINFO ByRef) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) Last one is related to the setup Anwendung: SetupUI.exe Frameworkversion: v4.0.30319 Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet. Ausnahmeinformationen: System.TypeLoadException bei SetupUI.MainWindow..ctor() bei SetupUI.App.OnStartup(System.Windows.StartupEventArgs) bei System.Windows.Application.<.ctor>b__1_0(System.Object) bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) bei System.Windows.Threading.DispatcherOperation.InvokeImpl() bei System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object) bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) bei MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) bei System.Windows.Threading.DispatcherOperation.Invoke() bei System.Windows.Threading.Dispatcher.ProcessQueue() bei System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) bei MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) bei System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) bei MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) bei MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) bei System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) bei System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame) bei System.Windows.Application.RunDispatcher(System.Object) bei System.Windows.Application.RunInternal(System.Windows.Window) bei System.Windows.Application.Run(System.Windows.Window) bei System.Windows.Application.Run() bei SetupUI.App.Main() Quote Link to comment Share on other sites More sharing options...
Flayn Posted June 20, 2021 Author Share Posted June 20, 2021 (edited) So, after collecting all the info for the post above I tried "one last time" to install the latest version. Now it is working!!! I dont know why, but I can live with that. Thanks for helping komatös and greetings from Dortmund Edited June 20, 2021 by Flayn Komatös 1 Quote Link to comment Share on other sites More sharing options...
Komatös Posted June 20, 2021 Share Posted June 20, 2021 Das ist erfreulich zu lesen. Ich wünsche dir einen entspannten Restsonntag. Liebe Grüße aus Hamburg Flayn 1 Quote AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.2161) Affinity Suite V 2.5.5 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF I am not old, I have matured like a good scotch! Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.