Max Gr Posted March 6, 2020 Posted March 6, 2020 (edited) 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 Edited March 6, 2020 by Max Gr Quote
Staff Chris B Posted March 6, 2020 Staff Posted March 6, 2020 Hey Max Gr, welcome to the Affinity Forums. Affinity isn't capable of causing a BSOD—however as you pointed out, faulty hardware or more likely, on a new system, a bad driver. I'm not really qualified to suggest what may be causing the crash, however I have seen the IRQL NOT LESS OR EQUAL BSOD before and it was related to audio drivers. Not to sure about the other one I'm afraid. PaulAffinity 1 Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
Max Gr Posted March 6, 2020 Author Posted March 6, 2020 Thanks for your reply. I understand that Affinity Photo can not cause BSOD by itself. However I am still wondering why these BSOD only happened while using this app whereas the system has been rock stable since one year, including when using other photos editors. Regards, Maxime Quote
Staff Chris B Posted March 6, 2020 Staff Posted March 6, 2020 I completely understand your query. It's likely Affinity Photo is using or hitting something that other applications aren't. I'll see if our developers have any additional info. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
Fritz_H Posted March 8, 2020 Posted March 8, 2020 Just in case you installed the Update: KB4535996 -> un-install it - Microsoft ***** it up again. Fritz Chris B 1 Quote
Max Gr Posted March 8, 2020 Author Posted March 8, 2020 Thanks Fritz. To give an update: Following my last message, I inquired a bit more and checked how the system would behave with the Windows verifier.exe tool activated. This tool stresses the drivers and it appears that each boot of my machine was followed by a BSOD (System thread exception this time). I managed to access the DMP files and they pointed towards a file called hidclass.sys which often relates to input devices. By chance, I found a post on google that suggested that Logitech G-Hub (mouse driver) could be responsible. I uninstalled it and there was no BSOD at startup anymore with verifier.exe activated. Now I am not sure that this was causing the issue in Affinity Photo but it is likely. I have not had BSOD since. Time will confirm. Thanks anyway for your help. Maxime Mark Ingram and Chris B 1 1 Quote
Fritz_H Posted March 8, 2020 Posted March 8, 2020 perhaps you want to un-install the Update anyway: https://www.tomshardware.com/news/-problems-optional-windows-10-update (just one of many Web-Resources regarding that (again) faulty Windows 10-Update. ) Chris B 1 Quote
Max Gr Posted March 8, 2020 Author Posted March 8, 2020 I actually made a clean install of Windows 10 yesterday. Perhaps it was actually on my former install and creating these issues. Anyway, I just checked and it does not seem it has been pushed on my fresh install. I will be careful and deny it if I see it. Thanks. Chris B and Mark Ingram 2 Quote
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.