Affinity designer keeps crashing on windows ten

[NickTK2024]

Good afternoon all, 

I have an issue with my affinity designer on windows 10.

When I am using my affinity designer on windows 10 with 16gb of ram. After a few minutes of use/strokes of my vector pen, affinity designer becomes "not responding" the only way to use it again is to use my task manager. 

This is a constant loop and is affecting my output of work for my business. 

Please help me :(

[v_kyr]

Hi and welcome!

Do you make use of Graphics card related Open CL hardware acceleration in Affinity Designer, is that option enabled under the Designer Preferences -> Performance settings? - If yes try to disable that, restart Designer and try if it behaves differently then. - You can also check your Win OS installed GPU driver version in case Affinity has problems with that one.

Otherwise if the above don't change anything, look for possible written out crash reports and post them into the forum for further inspection.

[NickTK2024]

Good afternoon @v_kyr, thank you so much for reply

I have investigated these and nothing improves.

I cannot upload the dmp file. it seems to be "uploading" constantly with no resolution.

 

[NickTK2024]

the.dmp file has now attached 😫

157775f3-621f-4348-ae22-267a6c108713.dmp

[v_kyr]

What graphics card (GPU) and GPU driver do you have/use in your Win box? - Did you tried to disabled OpenCL hardware acceleration in the performance preferences of  AD?

Your dump file tells that the app crashes in KERNALBASE.dll due to an read access violation, which indicates that the software is trying to access a protected memory area and this incorrect access is denied here ...

Quote

Operating system: Windows NT
                  6.2.19041 1023
CPU: amd64
     family 6 model 158 stepping 10
     12 CPUs

GPU: UNKNOWN

Crash reason:  EXCEPTION_ACCESS_VIOLATION_READ
Crash address: 0x0
Process uptime: 13 seconds

Thread 0 (crashed)
 0  KERNELBASE.dll + 0x34ed9
    rax = 0x000000cc00000009   rdx = 0x00000221520f2640
    rcx = 0x0000000000000000   rbx = 0x000002212dae1a50
    rsi = 0x000002212d4daff8   rdi = 0x000002212dae1a50
    rbp = 0x000000ccee3fe600   rsp = 0x000000ccee3fdea0
     r8 = 0x0000000000000000    r9 = 0x000000ccee3fd898
    r10 = 0x0000000000000004   r11 = 0x00000221520f2ba0
    r12 = 0x000002212b307210   r13 = 0x0000000000008000
    r14 = 0x0000000000000000   r15 = 0x0000000000000000
    rip = 0x00007fff84bc4ed9
    Found by: given as instruction pointer in context
 1  Serif.Interop.Persona.ni.dll + 0x288f8bd
    rbp = 0x000000ccee3fe6c0   rsp = 0x000000ccee3fe610
    rip = 0x00007ffea071f8bd
    Found by: previous frame's frame pointer
 2  Serif.Interop.Persona.ni.dll + 0x2889fa0
    rbp = 0x000000ccee3fe720   rsp = 0x000000ccee3fe6d0
    rip = 0x00007ffea0719fa0
    Found by: previous frame's frame pointer
 3  Serif.Interop.Persona.ni.dll + 0x2834158
    rbp = 0x000000ccee3fe7a0   rsp = 0x000000ccee3fe730
    rip = 0x00007ffea06c4158
    Found by: previous frame's frame pointer
 4  clr.dll + 0x224e
    rbp = 0x000000ccee3fe7d0   rsp = 0x000000ccee3fe7b0
    rip = 0x00007fff6a85224e
    Found by: previous frame's frame pointer
 5  clr.dll + 0x251e
    rbp = 0x000000ccee3fe7d0   rsp = 0x000000ccee3fe7d0
    rip = 0x00007fff6a85251e
    Found by: stack scanning
 6  Serif.Interop.Persona.dll + 0x9a043d
    rsp = 0x000000ccee3fe840   rip = 0x00007ffea3c5043d
    Found by: stack scanning
 7  USER32.dll + 0xfe74
    rsp = 0x000000ccee3fe850   rip = 0x00007fff863cfe74
    Found by: stack scanning
 8  USER32.dll + 0xe858
    rsp = 0x000000ccee3fe880   rip = 0x00007fff863ce858
    Found by: stack scanning
 9  clr.dll + 0x16b260
    rsp = 0x000000ccee3fe8c0   rip = 0x00007fff6a9bb260
    Found by: stack scanning
10  WindowsBase.ni.dll + 0x1b108
    rsp = 0x000000ccee3fe8f0   rip = 0x00007ffee3ceb108
    Found by: stack scanning
11  clr.dll + 0x19fcc6
    rsp = 0x000000ccee3fe900   rip = 0x00007fff6a9efcc6
    Found by: stack scanning
12  WindowsBase.ni.dll + 0x1b108
    rsp = 0x000000ccee3fe910   rip = 0x00007ffee3ceb108
    Found by: stack scanning
...

 

[NickTK2024]

Graphics card is NVIDIA GeForce RTX 2060

the driver details are:

NVIDIA

10/01/2022

30.0.15.1123

yes i have disabled CL

[v_kyr]

 

 

 

[NickTK2024]

I have changed the things required and downloaded the driver.

 

It is still doing it

[v_kyr]

Make a posting into the Designer Bugs found on Windows forum section, so the devs can take a look at it. Add your crash dump file and all related informations (Win version, Affinity Designer version, GPU type and driver version etc.).

Also take a look at which Affinity Designer release version you actualy use and if some beta version allready may have fixed some issues here!

[NickTK2024]

Good morning. sorry for not coming back to you sooner. When i use the vector brush tool i have the issues. when I use any other too, the not responding happens. Very strange indeed

[stokerg]

On 1/17/2022 at 9:10 AM, Nick Tophilia Kreations said:

Good morning. sorry for not coming back to you sooner. When i use the vector brush tool i have the issues. when I use any other too, the not responding happens. Very strange indeed

I've had a look at the DMP file and sadly it doesn't show anything other what @v_kyrhas pointed out.

Could you just try going into Preferences again and setting the Display to WARP and then restart the app and see if the same happens when you use any of the tools?

Also, does the program actually crash as in close down or does it freeze and stay on screen? 

[NickTK2024]

Good afternoon. 

It freezes and stays on screen.

I have changed it to warp but still does the same thing

[stokerg]

22 hours ago, Nick Tophilia Kreations said:

I have changed it to warp but still does the same thing

 

Can you just try causing the freeze and calling up Task Manager and right clicking on Affinity Designer and select Create Dump.  That will then create a dump file of whats happening.  If you can then upload the file to our Dropbox here.  As Designer isn't crashing and closing, i suspect the previous DMP file you posted was from an earlier crash.  This new one should tell us more  

Also it would be worth just trying the beta, which you can download from here and see if this acts any better.  It installs alongside the release build and gets its own shortcut.

[AlessioFB]

Hi,

I am also experimenting many crashes (mostly while using brushes).

It just crashed to I created the DMP file from Task Manager. (It's 3 GB, where should I upload it?)

I already ran a scan for corrupted files and I already deactivated graphic acceleration.

Edited January 20, 2022 by AlessioFB

[NunoF]

Hello

Same here. Started today.

Nothing changed expect installing a few new fonts but I have removed them again and freezes after a few clicks and then crashes.

Last version.