Why does Affinity Photo keep crashing when saving on my PC

[Chillr2021]

My PC is 4 years old now with this spec

Asus Z170-K Motherboard
Intel Core i5-6600K Skylake CPU, 4 Cores, 3.5 - 3.9GHz
32GB DDR4 2133MHz Memory
NVIDIA GeForce GTX 750 Ti 2GB Graphics Card
120GB Samsung 850 EVO Solid State Drive with Windows 10 up-to-date
FSP 80 PLUS Silver 750W PSU

These are my Affinity Photo Performance Settings attached below

 

It constantly crashes for me for some reason, more often with saving, it will show a progress of saving then when complete it often comes up with a second progress bar and this one usually gets to the middle and will pause if this stays there for 10-15seconds you know it will just close the program and crash, they usually are saved when you re-open but wish it could just do it without crashing. Sometimes the saving bar is much faster and it works Ok so don't know why when saving the same file without any major changes since the last save will be much slower to save, it makes you scared to save cause you don't know if it will choose to crash.

Files I'm working are 1.5-3.0Gb - are these too large for my PC to save on Affinity Photo?

Basically love to know if my PC is simply not powerful enough for Affinity Photo to run without crashing or do you think there something I can do an upgrade perhaps to assure it won't do these crashes so often. I'd love to be able to save and not worry about it crashing.

I'd also love to know why does the screen go black sometimes and say not responding and why does the saving speed vary on the same file?

 

[walt.farrell]

If it's crashing it might be useful to provide one of the crash reports, if any are generated:

 

[Chillr2021]

Sure Walt, one happened this morning so I'll attach this one.

Cheers

Phil

93812625-5d30-457f-abd5-2ab1200770db.dmp

[NotMyFault]

Your GPU seems quite low spec. 
may try to disable OpenCL - this often helps.

Then check that you have at least 32 GB free space on the system ssd.

During save, Affinity tends to create large temporary files. 

As you have only 120 GB ssd I assume you are storing the actual documents on another drive. Do you have additional internal disks?
Saving to external disks or NAS is a possible cause of issues.

[Chillr2021]

12 hours ago, NotMyFault said:

Your GPU seems quite low spec. 
may try to disable OpenCL - this often helps.

Then check that you have at least 32 GB free space on the system ssd.

During save, Affinity tends to create large temporary files. 

As you have only 120 GB ssd I assume you are storing the actual documents on another drive. Do you have additional internal disks?
Saving to external disks or NAS is a possible cause of issues.

Thanks for helping NotMyFault, Yeah at the time when I bought it I guess didn't think it mattered too much as wasn't needed it for any gaming but yeah wished I'd of invested a bit more if this is what makes it lag. Out of curiosity what graphic card would you recommend that would be adequate to not causing Affinity photo to crash.

I'm a little unsure if it's best to buy a Mac Mini end of this year or next year, upgrading this one unsure if it's worth it now as it's coming up to the 5 year mark this year.

The openCL compute acceleration is actually already disabled, won't enable on mine at all as it says not compatible with my GPU and need a modern one.

I have 33.5 GB free

Can Affinity be set to use a scratch disk I have a 'Crucial MX300 525 GB SSD drive'  I bought to use as a scratch disk when I used Photoshop

I always save to a mirrored two 2TB internal sata drive setup

Cheers

Phil

[v_kyr]

On 1/12/2022 at 3:00 PM, Chillr2021 said:

Sure Walt, one happened this morning so I'll attach this one.

 

93812625-5d30-457f-abd5-2ab1200770db.dmp 741.05 kB · 1 download

The EXCEPTION_ACCESS_VIOLATION error on Win indicates that the software is trying to access a protected memory area and this incorrect access is denied.

Quote

Operating system: Windows NT
                  6.2.19041 1348
CPU: amd64
     family 6 model 94 stepping 3
     4 CPUs

GPU: UNKNOWN

Crash reason:  EXCEPTION_ACCESS_VIOLATION_READ
Crash address: 0x20e30c5b890
Process uptime: 2749 seconds

Thread 0 (crashed)
 0  libraster.dll + 0x20b0882
    rax = 0x0000000000000000   rdx = 0x00007ffa82dc3fa8
    rcx = 0x0000020e30c5b890   rbx = 0x0000020e30316f78
    rsi = 0x0000020e30316cb0   rdi = 0x0000738ec47e4e50
    rbp = 0x0000020e30317020   rsp = 0x000000e067ffece0
     r8 = 0x0000020e30316cb0    r9 = 0x0000738ec47e4e50
    r10 = 0x0000020e15f600f0   r11 = 0x000000e067ffec40
    r12 = 0x00007ffa7fe329c8   r13 = 0x0000000000000001
    r14 = 0x000000e067ffedd8   r15 = 0x0000020e30316cb0
    rip = 0x00007ffa81ee0882
    Found by: given as instruction pointer in context
 1  libraster.dll + 0x2e0d160
    rbp = 0x0000020e30317020   rsp = 0x000000e067ffecf8
    rip = 0x00007ffa82c3d160
    Found by: stack scanning
 2  ucrtbase.dll + 0x142d6
    rbp = 0x0000020e30317020   rsp = 0x000000e067ffed10
    rip = 0x00007ffaec8d42d6
    Found by: stack scanning
 3  ucrtbase.dll + 0x160ae
    rbp = 0x0000020e30317020   rsp = 0x000000e067ffed30
    rip = 0x00007ffaec8d60ae
    Found by: stack scanning
 4  0x7ffa7fe30000
    rbp = 0x0000020e30317020   rsp = 0x000000e067ffed50
    rip = 0x00007ffa7fe30000
    Found by: stack scanning

Reasons could be due to some Antivus software, common OS related access protections ... etc.

[Chillr2021]

Hi v_kyr

I'm using Norton 360 if that's any help, just recently subscribed for another year. Unsure what I can now then.

[v_kyr]

1 hour ago, Chillr2021 said:

Hi v_kyr

I'm using Norton 360 if that's any help, just recently subscribed for another year. Unsure what I can now then.

You have to find out if it is possibly the cause here or not. So temporary disable Norton and see if that changes anything for the APh behavior then or not.

[R C-R]

8 hours ago, Chillr2021 said:

Can Affinity be set to use a scratch disk...

AFAIK, it cannot, at least not without resorting to some kind of symlink hack that may end up causing more problems than it solves.

[DWright]

From the crash report the issue is occurring due to an issue reading from the Windows page file, you can try and assign the page file to your scratch drive, the following link shows how to do this

https://www.maketecheasier.com/change-pagefile-size-location-windows/

[Chillr2021]

2 hours ago, DWright said:

From the crash report the issue is occurring due to an issue reading from the Windows page file, you can try and assign the page file to your scratch drive, the following link shows how to do this

https://www.maketecheasier.com/change-pagefile-size-location-windows/

Thanks DWright,

So I've currently got it set to 

unticked - automatically manage paging file size for all drives
C drive page file size 800-4980
selected drive c drive
initial size 800MB
maximum size 4980MB

unticked both of these
system managed file
no paging file

If I change to scratch disk what should I set this to the initial size and maximum the same as I had for c drive drive or something different

Cheers,

Phil

 

[SeanCarrie0612]

Heyah! So, I'm having similar issues with Affinity Photo crashing so often and so bad I have to restart my computer EVERY TIME! It happens when I'm done with a photo and try and close out of said photo, then affinity just freezes and I have to restart Affinity or my computer. Also sometimes when saving or exporting it bugs out and takes for ever to save or export. I swear these issues happened a few updates ago. If I remember correctly it started acting up after this one update sometime ago, I do not remember when exactly. Also when I try to open more then one photo at a time it bugs out and crashes. I constantly have to have the task manager open to keep closing Affinity.....I think there's other weird things that happen and cause it to crash, but these ones are the ones I deal with most and are horrifically annoying......Is there anyone else here that has these same or similar issues? 

I'm not the most computer smart person, but I can try and see if I can get my computer specs. I bought a gaming PC for this so I'm not entirely sure what's in it. I don't think this is part of the problem but just thinking it may be helpful.

 

I attached a photo of what happens. It bugs out and whenever I click on the screen anywhere it does this, then it says it' not responding. I either have to restart Affinity or wait for however long it takes for Affinity to catch up and respond. 

 

Thanks in advance to anyone who replies! 

Edited January 20, 2022 by SeanCarrie0612
wanted to upload an image.