Franiac

I am pretty shure AMIP uses hardware acceleration, too. Maybe OpenCL, maybe not, that I don't know.

This is far from a bad hint. First I was not sure but now... I realized Affinity works more stable if nothing is opened simultaneously. In my case if I open up Brave Browser (Chromium) and watch something (YouTube or Twitch) while working in Affinity it most likely crashes very quickly while using the standard transform tools and so on. @Callum So here's maybe another path you could dig in: Try launching addinional programs that simultaneously use hardware acceleration. It definitely messes with Affinity. If I stop the YouTube/Twitch video in Brave, Affinity holds up 10 times longer without crashing. Press "play" again, and Affinity is gone in 60 seconds...

My .NET version is 528372, which means .NET 4.8. As a professional .NET Software Engineer I highly doublt an update to the latest 4.8.1 will have any effect. There are so many .NET applications out there running Windows Forms or WPF frontends on .NET 4.8. If you read the official release notes it is highly unlikely that there will be any improvement on the current matter. And if the .NET runtime had any rendering issues on AMD graphics cards, the Microsoft forums would already explode. I do not know the internal processing structure of Affinity Photo, but crashing a display driver is usually caused by direct unsafe rendering calls via the graphics API. What does Affinity use in Windows? DirectX, OpenGL or Vulkan? I am sure it is Metal for MacOS, right? Since all crashes on my end have to do with transformations, adjustments, layers, cropping and such, my guess is that Affinity delegates those tasks directly to the GPU for acceleration and somehow manages to tear it down. Also, I am open to help in any way possible. Meaning running debug builds for logging and such. I really want V2 to work... I mean... I kinda paid for it

I have found this in the Windows Event Viewer: Application: Photo.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at <Module>.Affinity.LayersExpandedState.OnDocumentClosed(Affinity.LayersExpandedState*, Kernel.Counted<DocumentController const >*) at Serif.Interop.Persona.Data.LayersDataSource.InteropService_CloseDocumentNotification(System.Object, Serif.Interop.Persona.CloseDocumentNotificationEventArgs) at Serif.Interop.Persona.CloseDocumentNotificationHandler.Invoke(System.Object, Serif.Interop.Persona.CloseDocumentNotificationEventArgs) at Serif.Interop.Persona.Services.InteropService.OnCloseDocumentNotification(Serif.Interop.Persona.NativeWrapper<Kernel::NonCounted<Kernel::Notification> >) at Serif.Interop.Persona.Services.InteropService.HandleNotification(Kernel.Counted<Kernel::Notification>*, Boolean) at Serif.Interop.Persona.Services.InteropService.OnNotify(Kernel.Counted<Kernel::Notification>*) at <Module>.GetNotificationDispatch.<lambda_2bcb078db99a2694ff26461d0eed393e>.()()(?GetNotificationDispatch@@$$FYA?AV?$function@$$A6AXXZ@std@@V?$Counted@VNotification@Kernel@@@Kernel@@@Z.__l2.<lambda_2bcb078db99a2694ff26461d0eed393e>*) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at Photo.Application.Main(System.String[]) But I think this is not the actual error stacktrace but the .NET runtime struggling to handle the application crash due to the display driver crash. There is the possibility that when the display driver crashes, after a minute of waiting, Windows manages to restart the driver. Explorer windows or Browsers are still open and running, but Affinity Photo always get completely killed.

@Callum I totally forgot to attach those... but see the timestamps of those dump files, that's how frequent Affinity crashes. 0c2447c0-f11e-4d6c-986b-55f9847d68fb.dmp 3b21b511-d80f-4185-868d-86081942aa51.dmp 8c3b08db-ed0b-4252-940b-5d86ef351ed7.dmp 09fc49b1-f744-49e5-a25d-3ff9fb34e03b.dmp

@Callum I am running the lastest possible updates on my Win 10 Pro. I have tried to re-install the driver multiple times (including DDU for removal) and also tried the non-optional WHQL driver 22.5.x. I have tried with/without Adrenaline Software but it does not make any difference. The thing keeps crashing. Btw. I can also confirm that V1 runs perfectly fine, so there must be something going on in V2. Also tried disabling FreeSync temporarily but that also has no effect (would be weird anyways, since it is only a handshake between GPU and Display and does not interfere with rendering).

Same for me. Using a lot of different audio/photo/video software and Affinity Photo/Designer/Publisher are the only applications that cause this issue. The AMD display driver just crashes and the displays freeze. It happens on all kind of different tasks like dragging, selecting, opening images. I cannot put my finger on it when it exactly happens since it is not reproducable every time. Affinity Suite V2 crashes about every 3-5 minutes, sometimes even less, which makes it basically unusable. After a restart, the Adrenaline Software has a notification indicating that the display driver crashed unexpectedly. What is interesting is the fact that I too have a 6800XT and a similar setup compared to the OP: CPU: AMD Ryzen 7 5800X3DGPU: AMD Radeon RX 6800 XT (Driver: AMD Software: Adrenalin Edition Version 22.11.2)RAM: 32GB @ 3200MHzDisplays: 2x 1440p (165Hz FreeSync)OS: Windows 10 Pro Version 22H2 (OS Build 19045.2251)