Search the Community

Only drivers or something else running with system privileges can cause a BSOD. Yes, other software (such as one of the Affinity apps) can call the driver, and then a BSOD can result because of something the driver did. But at that point, one of the following has happened: The application made a correct call to the driver and passed good data, and the driver passed the data to the system or to the hardware, and the hardware failed. Or, the application made a correct call to the driver and passed good data, and the driver has an error and failed. Or, the application made an incorrect call to the driver, and the driver failed to validate the data that it was passed, and the driver failed. Only #3 might be viewed as a problem with the application. But even there, the driver is supposed to validate its data, because it runs with higher privileges and therefore cannot trust anything that the application passes to it. So, in case #3 yes, there is an error in the application, but there would not be a BSOD without a more serious error in the driver. What should happen in #3 is that the driver properly validates the data it has been given, and then the driver crashes the application, not the system. Then you have an application failure, and a clear culprit and something obvious to point the finger at.

What I said was they cannot directly cause a BSOD, so for example it is the driver that causes the BSOD, not the Affinity app. IOW, the Affinity app calls the driver which in turn causes the BSOD, so the app is the indirect cause. Do you disagree?

Our software runs in user mode so cannot directly cause a BSOD. Only kernel-mode applications (i.e. drivers) are capable of that. There is likely a driver issue on the system such as an out of date one or perhaps a conflict somewhere. I'm not sure if you have any utilities that can run a scan and check for any of these potential issues but it may be worth looking at. Try updating your GPU drivers (even better, uninstall and re-install them) and see if that helps, then check for any peripheral drivers such as gaming mice, keyboards. If you can, find out what the polling rate is for the mouse. Anything above 1000 polling rate can cause poor performance (we're currently looking into this).

It seems my BSOD post has sparked a lively discussion resulting in a lot of thoughtful input. Even with my limited knowledge, I can see what a complex issue this is with no easy solutions . Meanwhile back at the ranch, attached is my BSOD report from today. I also include an image of what I was doing in AP, putting together a presentation of how to identify old Art Nouveau tiles, I managed to do the one slide before the crash. Because of the deadline, nothing for it but to go back to Photoshop, I have just completed fifteen more slides with no problem.

Hi @Richard H, Welcome to the Affinity Forums Sorry to see you're having trouble & our apologies for the delayed response here! As Walt previously confirmed: The Affinity applications aren't able to directly cause a BSOD error - however it's certainly possible the app is using hardware/software that other apps aren't using, which triggers the issue within Windows. I'd recommend also using Windows Reliability Monitor as this may contain more information as to the cause of this, however the error messages/event viewer screenshots provided do seem to point to a potential hardware issue. It may be the internal iGPU within your Intel CPU causing this issue, so please make sure these drivers are also up to date, alongside your Nvidia drivers. Equally, please check for any BIOS updates from the manufacturer, as these can also reduce BSOD errors. I hope this helps!

Are you getting anything from the Windows Event Log around the time of the BSOD? That may provide more information about what's going on. I'm not sure exactly what effect switching to WARP has. It does some processing using software, not the GPU, but I don't know the details of what that means. Obviously the GPU must still be involved somewhere in getting the image on to the screen. Probably not, but you may have some hardware, firmware, or overclocking issue that you aren't finding with your other applications. The list of what can cause that BSOD error is pretty long: https://www.softwaretestinghelp.com/clock-watchdog-timeout-error-fixed/

Welcome to the Serif Affinity forums. The .dmp file seems to indicate a problem in libraster.dll which is (I think) part of the Affinity application. However, the Affinity applications cannot directly cause BSOD errors, as they run with application privileges, and BSODs indicate that something running with elevated (System) privileges has had a fault. When you get a BSOD it generally either means you have a hardware issue, or more likely (with the Affinity applications) a GPU Driver issue. Have you checked to see if your GPU drivers are up-to-date?

Hi, @shaprackand welcome to the forums. If the laptop produces a BSOD, it is not due to Affinity Photo but to another device driver, another software component running in the background or even a hardware problem. It would be interesting to know the error code that is displayed when a BSOD occurs.

Hi Kaltzboy, The Affinity applications aren't able to cause a BSOD, as they are user-mode applications. Only kernel-mode applications (i.e. drivers) are capable of that. I would recommend trying the solutions provided by Hens in most cases this can be caused by a GPU driver so perhaps ensure that you have reinstalled the latest version and if the BSOD still persists perhaps try rolling back to an older driver. Thanks C

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.

That's certainly an interesting development - I can confirm the Affinity apps are not capable of directly causing a BSOD, so this is a good indication of the issue causing the crashing, but confirms it's not the Affinity app itself at fault. The majority of information online for this stop code shown refer to System Files or drivers - both of which we've already checked above. Therefore can you please restart the machine in Safe Mode, then try these steps once more for me?

Thanks for confirming that for me - it's very likely the crashing in Designer upon export is caused by the same issue that triggers the BSOD, but we can certainly double check for you. Firstly, can you please open Windows Run (Windows Key + R) then paste the following string and press OK: %AppData%\Affinity\Designer\1.0\CrashReports\reports In the window that opens, please select the 3 most recently created .DMP files, then upload these to your reply here. Secondly, we're aware of the latest Windows updates causing crashing in WPF apps, including Affinity - please check the following FAQ for more information and steps on how to remove this update to stop the crashing - Many thanks in advance!

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

Hello @M.Hildt and welcome to the forums. A BSOD indicates that there is a faulty driver, a hardware defect/missconfiguration or can be triggerd by a third-party app. To investigate the BSOD the error code is needed. All the hardware can also be helpful.

Similar problem here. Both Designer and Photo are opening to the app, then immediately closing. By app, I mean it's they are getting past the splash screen, and look ready for me to start working. I don't even get to click on any menus before they close out. No error messages. Reinstalled Photo, no change Tried to run from .exe as Admin. No change. Attached .dmp files for both. Modified dates are not recent. I have been having a problem of the whole computer randomly shutting off with a BSOD. Dell is shipping a new part (memory, if I recall corectly) The behaviour of Photo and Designer is new. Rest of apps on the machine are working. Windows Event Viewer reports: PHOTO: Log Name: Application Source: .NET Runtime Date: 12-Sep-2022 8:33:59 PM Event ID: 1026 Task Category: None Level: Error Keywords: Classic User: N/A Computer: SimonDell Description: 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.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[]) Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1026</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2022-09-13T00:33:59.0457711Z" /> <EventRecordID>60072</EventRecordID> <Correlation /> <Execution ProcessID="12172" ThreadID="0" /> <Channel>Application</Channel> <Computer>SimonDell</Computer> <Security /> </System> <EventData> <Data>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.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[]) </Data> </EventData> </Event> DESIGNER: Log Name: Application Source: .NET Runtime Date: 12-Sep-2022 8:37:13 PM Event ID: 1026 Task Category: None Level: Error Keywords: Classic User: N/A Computer: SimonDell Description: Application: Designer.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException 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 Designer.Application.Main(System.String[]) Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1026</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2022-09-13T00:37:13.4528249Z" /> <EventRecordID>60073</EventRecordID> <Correlation /> <Execution ProcessID="10180" ThreadID="0" /> <Channel>Application</Channel> <Computer>SimonDell</Computer> <Security /> </System> <EventData> <Data>Application: Designer.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException 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 Designer.Application.Main(System.String[]) </Data> </EventData> </Event> 08cce613-c6ef-422a-927b-dbbc13cd08c5.dmp 932cffb4-1dab-4a94-9783-08eadd4b2039.dmp

I will try that, I updated bios a few months ago, it is possible it is just a coincidence that I was exporting a file when the BSoD occurred, My system is the first graphics focused machine I have had so it bit of a mashup of parts, I am running a HP z220 work station with 32GB ram intel i7-3770 & dual Nvidia GeForce GT 710. This is one of the first times actually loading the machine properly as I just upgraded from an older Dell gaming rig,(same time as I updated bios) I had some stability issues where the machine would complete crash & BSoD randomly when I first got it, do you think they may be related? Thank for the advice though.

Hey jseawater, If you got the blue screen (BSoD) then that suggests a catastrophic hardware or driver failure somewhere. Affinity is not capable of actually causing a BSoD. I'd recommend removing your graphics drivers and installing fresh ones - do not simply check for updates and install those.

Thanks for the instructions. I already tried all following steps, did not help. - uninstalled the OneDrive - restart, test, BSOD - installed OneDrive from the Store - restart, test, BSOD - uninstalled OneDrive from the Store - restart, test, BSOD - installed OneDrive for Business, on the Outlook 365 package - restart, test, BSOD My laptop is on a hosted business environment, so I may not have found all possible cloud systems. I'd rather not touch on the Sharepoint... Complete system reinstall would take two days (due to some of the special work related software), so that is not an option. I have already spent too much time on trying to solve this issue, it is smarter to wait for updates that fix the issue or use the expensive alternative that does not break my workflow.

Thanks for taking the time to respond to my various messages. I ran the sfc scan as suggested. In fact I had to run it twice, because the window closes by itself when the scan finishes (which I think is odd), so if you aren't watching it you don't know what happened. Anyway, the second time I sat and watched and it reached 100% without any error messages. As to the bugcheck, almost all those I ever remember seeing were due to an attempt to address an illegal location. Presumably the error must occur in the execution of system code (as you suggest, a driver or service), otherwise the application could crash and not the whole O/S. However, as the bugcheck occurred whilst Affinity was in a blocked state, and the blockage occurred twice when attempting "Refine" on the same area of the same image, I would still put money on a bug in Affinity. Presumably it makes a system call with illegal parameters which are not checked ? (If I remember, the European Space Agency crashed their first Ariane 5 launch by not checking the range of an input parameter.) I guess the most sensible thing for me to do is to wait and see if I get a BSOD in any other circumstances before digging deeper, although it would be interesting for someone from Affinity to try to replicate what I did as I sent the jpeg and details of what provokes the problem. Irrespective of the BSOD, the fact that Affinity blocked twice at the same point surely indicates that there is a bug in their code, especially as I was not the first person the see a problem like this? Schönes wochenende, David M.

For such BSODs the real cause of the origin (the error) can be overall difficult to detect and encircle. Wie behebt man CLOCK_WATCHDOG_TIMEOUT Blue Screen (0x00000101) BSOD Error code 101

See: How to Fix intelppm.sys error Windows 10 (english) How to fix error 0xc00002e3 windows 10 Regular freezing and BSOD on Windows 10 - intelppm.sys seems to be the cause ... and so on, do a Google seearch after intelppm.sys ... The first referenced article from above in german instead: So beheben Sie den intelppm.sys-Fehler Windows 10 (deutsch)

Which means that the only way for an Affinity app to directly cause a BSOD is if it somehow could be running with system level privileges....

Of cause I disagree, since software always runs on hardware and as you should know better, a piece of software (an app/program) can be the root cause for a BSOD. So it doen't matter if you write "indirectly" or not, there are plenty of examples how a software can do so, either intentionally or due to programming faults. And since in such cases the software is the cause and origin there is no indirectly, as the machine (the hardware) woudln't crash otherwise when running a well programmed/ behaving software.

This is regarding an app crash dump. Not a BSOD type. Curiously, I think it isn't actually crashing, but is simply sending out a simulated crash dump for some reason. Maybe a testing option is being triggered. The app appears to work fine.

Just keep in mind that as has been mentioned, apps can crash but they cannot directly cause a BSOD (AKA a fatal system error or system crash).