Search the Community

Hello! Please forgive me if there are some expressions that are not correct because I am translating Japanese text. Bug Description BSoD occurred when moving the layer level adjustment window of Affinity Photo2 to another screen. I disabled the hardware acceleration function, but it had no effect. Environment where the bug occurred Monitor1:LG 27UP650 (3840x2160, DisplayPort) Monitor2:Wacom Cintiq DTK-1660 (1920x1080, HDMI) Monitor3:LG 22MP68VQ (1920x1080, DVI) CPU: AMD Ryzen7 3700X GPU:AMD Radeon RX580 (DriverVersion:22.20.27.09-230330a-390451C) Memory:32GB OS:Windows11 Home (Version:23H2, Build:22631.2715, Lang:Japanese) Application:Affinity Photo2 (Version:2.3.0) Stop Code:UNEXPECTED_KERNEL_MODE_TRAP How to reproduce the bug Open a PSD file in Affinity Photo2. Open the Levels Adjustment window. Move the level adjustment window displayed in Monitor1 to Monitor2. While the window is being moved, if the mouse cursor is on the Windows taskbar, the level adjustment window will move violently and BSoD will occur. movie.mp4

Hello, I just purchased Affinity Photo (current version) on my system and have been in a few days encountering already 2 BSOD. I cannot reproduce this issue which has been appearing randomly while editing Fuji XT2/XH1 raw files. 1st time was when switching to liquify mode, 2nd time was when shifting the clarity cursor (before clicking develop raw). The BSOD message does not refer to a specific file (as I understand it may happen with Affinity Photo based on other posts I read) but mentioned: IRQL NOT LESS OR EQUAL (first BSOD) PAGE FAULT IN NON PAGED AREA (second BSOD) I am using the last version of Windows 10 1909 with last proposed updates installed. I know these kind of issues often relate to faulty hardware (ram, ssd) however, my system is quite recent (1 year old), very stable, and I have never encountered a single BSOD since I built it. This occured only twice and while using Affinity Photo. Thank you for your assistance. Maxime

I have new Surface Laptop 2 with the latest Windows 10 Pro. Tried Affinity Designer trial version from the Microsoft Store, liked it and purchased the full version from the Microsoft Store. The trial version worked fine, without issues. The full version was installed as a second version, leaving the trial version visible. That was slightly annoying, so I uninstalled the trial version. This may have caused some registry errors. When starting the full version of Affinity Designer, the Blue Screen Of Death (BSOD) emerged after five seconds, referring to cldflt.sys. Uninstalling and reinstalling the AD did not help. Followed one cldflt.sys fix and changed using regedit the DWORD value of Start from 2 to 3. No help. Changed Start value back to 2. Noting from the other topic in this forum that the bug may be related to OneDrive, I refreshed the OneDrive connection -> the Designer application started without the BSOD for the first time. Now the AD causes BSOD sometimes when trying to open or save files from the OneDrive. Many users have complained similar situations and the response has been similar - AD cannot crash the system. But that is exactly what it does. I have not experienced BSOD with any other applications in three years with my business laptops. Disabling the OneDrive is not an option as I have to make my living with this system. The OS is a fresh install for the new laptop, so I cannot remove any earlier updates. What could be the root cause for the cldflt.sys error? Which register values should work with AD? Could this be related to the response time from OneDrive?

Hi, I've just bought Affinity Photo on the Microsoft store, installed fine but has not started up once correctly. The splash screen loads, then I get a BSOD - every time I've tried to run the application. It's reporting cldflt.sys as having failed. I'm on a Microsoft Surface Pro (5th Gen) Windows 10 Pro Version 10.0.18362 Build 18362 I have designer and it starts and runs fine. I tried running Microsofts DISM Tool and SFC tool as described here: https://support.microsoft.com/en-gb/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system Both completed successfully, Photo still causes BSOD Read it might be linked to OneDrive - Tried exiting OneDrive, still get BSOD This is really dissapointing for a £50 new purchase.

Not impressed! This is the first time I've ever had BSOD on Win10 and Affinity Designer just did it twice trying to dock a pop out menu. Yes I'm using the latest version Yes I can recreate, it happen twice in a row doing exactly the same action. Its' only happened in the one document, but not willing to keep killing my OS just to test that. System details: Windows 10 Pro - latest updates etc. What happened? - It killed my OS and forced a restart, what did I expect... Not that! Steps to recreate: Load document Try to drag pop out tabs for character and paragraph options to be docked around the bottom right corner of the screen The menu will start to stutter, the system will lock up and then the OS will exit to the BSOD forcing a system restart. Screenshots: I could record on my phone but I'd rather not keep blue screening my system unless absolutely necessary. No unusual hardware Did it used to work? - Don't know

Hello, I've come across an issue in which Publisher seems to be crashing Windows upon trying to save a document. I'm guessing that it's due to some update that Microsoft released over the weekend as everything was fine last week and nothing else that I know of had changed. To reproduce: Open Publisher Create a new document or open an existing document Attempt to save After choosing a location and name and pressing the save button, Windows crashes. The BSOD claims that cldflt.sys failed, giving a stop code of SYSTEM_SERVICE_EXCEPTION. The file does end up getting created, but trying to open it afterwards gives a "file type not supported" error. The bug happened every time I tried to save, regardless of whether the file being saved was already in existence or new. A little poking around on the web suggested that uninstalling cloud services might help, so I tried removing OneDrive and sync services with Google. This did nothing. In the end, the only thing I was able to do to get everything working again was to roll back to a backup from before this weekend's OS updates happened. The provided file is what was produced from one occurrence of the issue. Thanks, Dan. Test.afpub

Just FYI, I rebooted my Windows 10 laptop this morning to finish installing Windows update KB4517389, and after that I experienced several Windows failures, BSOD when using the menus in the Affinity applications. Once in Photo (don't remember what menu I item I clicked) and twice in Publisher using Text > Show Special Characters. The failures pointed to ddflt.sys (or, perhaps, cldflt.sys) After removing that update things are working smoothly again. I understand that it is most likely an error in that Windows Update, and not in the Affinity Applications. I am not finding anything via Google (yet) about errors in that update.

We've had users report that when trying to launch our apps on Windows they're getting a Blue Screen of Death message relating to cldflt.sys. This is also affecting other apps including Microsoft's Visual Studio as reported on the Microsoft Developer Forums. This BSOD error started appearing after Microsoft released the Windows 10 KB4517389 update. Microsoft released a Windows 10 update on 10/12/19 (KB4530684) which includes the below fix. Please download and install this update and try opening the Affinity app again to see if your issue is resolved. Addresses an issue that might cause error 0x3B in cldflt.sys on some devices.

Hi, Seems it is quite easy to produce a BSOD with the latest NVIDIA drivers as in this thread I reported earlier for the Production Version: https://forum.affinity.serif.com/index.php?/topic/43230-ap-15269-bsod-after-update-nvidia-driver-38476/ In this case it was resizing a transparent layer beyond the bounds of the image (i.e. a frame) and changing the blend mode. The image is 500MB+ if you want. Again no problem with the Intel GPU as the base.

Hi, i have regular BSoD on try to save file on HDD. :unsure: After restart windows auto recovery work fine. I try to take video PC configuration: Operating System: Windows 10 64-bit Version: 10 System architecture: Intel CPU Family:6, Model:10, Stepping:7 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, AVX Physical processor count: 4 Processor speed: 3300 MHz Built-in memory: 16334 MB Free memory: 12256 MB Memory available: 14522 MB Memory used: 70 % Display: 1 Display Bounds: top=0, left=0, bottom=1080, right=1920 log.txt