Jump to content

Affinity Designer 2 (Windows) Crashes When Used with Wacom One 13.


Recommended Posts

I tried using Affinity Designer 2.1.1 - Windows and (Affinity Designer 2 Photo - Windows) with my Wacom One 13 but it crashes every time.

I updated the Wacom drivers but it still crashes.

I'm not sure if this helps at all but here's the information from the event viewer log:

Faulting application name: Designer.exe, version: 2.1.1.1847, time stamp: 0x6486f32a
Faulting module name: nvwgf2umx.dll, version: 10.18.13.6497, time stamp: 0x57106937
Exception code: 0xc0000005
Fault offset: 0x0000000000173cf7
Faulting process id: 0x26c0
Faulting application start time: 0x01d9cffcb60f9b8d
Faulting application path: C:\Program Files\WindowsApps\SerifEuropeLtd.AffinityDesigner2_2.1.1.1847_x64__3cqzy0nppv2rt\App\Designer.exe
Faulting module path: C:\WINDOWS\SYSTEM32\nvwgf2umx.dll
Report Id: 05b1c48e-4ab7-490e-9516-01e1c59e1765
Faulting package full name: SerifEuropeLtd.AffinityDesigner2_2.1.1.1847_x64__3cqzy0nppv2rt
Faulting package-relative application ID: SerifEuropeLtd.AffinityDesigner2

This is on a Windows 10 machine.  I've also contacted Wacom to see if they can assist.

Thanks.

= Steve

 

Link to comment
Share on other sites

  • Staff

Form your crash report the fault is being caused by your GeForce drivers can you please check that your are running the latest Nvidia Drivers and you can also try turning off the OpenCL acceleration in the Performance section of Affinity Designer 2 settings.

Link to comment
Share on other sites

7 hours ago, Speed said:

I just tried VectorStyler, Xara Designer Pro, Krita, Inkscape and Gimp on my Wacom tablet and they all work fine.  It's just the Affinity products that crash.

Well Affinity apps are known to be always very weak/picky in terms of OpenCL hardware acceleration with GPU drivers. Thus retry with disabled OpenCL hardware acceleration in ADe (disable it in the ADe preferences) for the Wacom tablet.

As that's also a problem many Win gamers do encounter, see therefor also related to nvwgf2umx.dll ...

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

16 hours ago, v_kyr said:

Well Affinity apps are known to be always very weak/picky in terms of OpenCL hardware acceleration with GPU drivers. Thus retry with disabled OpenCL hardware acceleration in ADe (disable it in the ADe preferences) for the Wacom tablet.

Is this what you mean?  I disabled it but it still crashed.

Diabled Hardware Acceleration.jpg

Link to comment
Share on other sites

5 hours ago, Speed said:

I tried all of the solutions in the links but AD and AP still crash.  Just to reiterate, AD and AP work fine on my monitor - it's when they're moved to the Wacom tablet that they crash.

Then Affinity seems to have some problem with the device, you have to look after possible by Affinity generated crash reports and attach them here for the mods/devs to take a further look after, in order to find out the crash problems.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

Hope you are well now.

From the DMP file stacktrace it looks like the KernelBase. dll (which is used to launch .exe applications) and is used/accessed in turn by the clr.dll  + mscorlib.ni.dll (.Net Runtime library stuff), has crashed due to some managed exception here. - The Affinity devs have probably to look at this and load it through the dev env debugger.

Quote

Operating system: Windows NT
                  6.2.19041 3155
CPU: amd64
     family 6 model 94 stepping 3
     8 CPUs

Crash reason:  MANAGED_EXCEPTION_CODE_V4
Crash address: 0x00007ffa9d2acf19
Crashing instruction: `nop dword [rax + rax * 1]`
Memory accessed by instruction:
  0. Address: 0x0000fff53eec0ae2
     Size: 4
Process uptime: 4 seconds

Thread 0  (crashed)
 0  KERNELBASE.dll + 0x2cf19

     rax = 0x00007ffa9f760571    rdx = 0x00007ffa7dfe672d
     rcx = 0x00007ffa9f3e00f8    rbx = 0x00000000e0434352
     rsi = 0x0000000000000001    rdi = 0x0000000000000005
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffe750
      r8 = 0x00000204dd6d63d0     r9 = 0x00000204dd6e5a58
     r10 = 0x00000204dd6e5a58    r11 = 0x00000000000157ac
     r12 = 0x0000000000004000    r13 = 0x00000204dd6da900
     r14 = 0x0000000774ffe8e8    r15 = 0x0000000000000000
     rip = 0x00007ffa9d2acf19
    Found by: given as instruction pointer in context
 1  clr.dll + 0xbb9ff
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffe770
     rip = 0x00007ffa80c3ba00
    Found by: stack scanning
 2  KERNELBASE.dll + 0x2cf18
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffe788
     rip = 0x00007ffa9d2acf19
    Found by: stack scanning
 3  clr.dll + 0x127dd7
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffe800
     rip = 0x00007ffa80ca7dd8
    Found by: stack scanning
 4  clr.dll + 0x128583
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffe830
     rip = 0x00007ffa80ca8584
    Found by: stack scanning
 5  mscorlib.ni.dll + 0x506f7
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffe850
     rip = 0x00007ffa7db006f8
    Found by: stack scanning
 6  clr.dll + 0x7a04bb
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffe870
     rip = 0x00007ffa813204bc
    Found by: stack scanning
 7  clr.dll + 0x7a04bb
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffe890
     rip = 0x00007ffa813204bc
    Found by: stack scanning
 8  clr.dll + 0x1286b2
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffe950
     rip = 0x00007ffa80ca86b3
    Found by: stack scanning
 9  clr.dll + 0x6e784
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffe990
     rip = 0x00007ffa80bee785
    Found by: stack scanning
10  clr.dll + 0x7e57bf
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffe9e0
     rip = 0x00007ffa813657c0
    Found by: stack scanning
11  mscorlib.ni.dll + 0x50f916
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffea10
     rip = 0x00007ffa7dfbf917
    Found by: stack scanning
12  clr.dll + 0x1285eb
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffeaa8
     rip = 0x00007ffa80ca85ec
    Found by: stack scanning
13  mscorlib.ni.dll + 0x50f916
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffeac0
     rip = 0x00007ffa7dfbf917
    Found by: stack scanning
14  mscorlib.ni.dll + 0xfff
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffead0
     rip = 0x00007ffa7dab1000
    Found by: stack scanning
15  mscorlib.ni.dll + 0x133e72d
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffeb10
     rip = 0x00007ffa7edee72e
    Found by: stack scanning
16  mscorlib.ni.dll + 0x1c0c2f
     rbp = 0x00000204dd6e5b38    rsp = 0x0000000774ffeb60
     rip = 0x00007ffa7dc70c30
    Found by: stack scanning

 

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

Thanks!

It looks like it's not the Wacom drivers because I just connected my XP-Pen Artist 13 graphics display (using its drivers) and it has exactly the same issue - AD crashes.

It has to be something wrong with my system.

= Steve

 

Link to comment
Share on other sites

Attached is a video of Affinity Designer 2 crashing on an XP-Pen Artist 13 drawing display.  The exact same thing happens with the Wacom One drawing display, so it doesn't matter which one I use.

I start AD on my main display, and then move it to the drawing display using <win> <shift> <right arrow>.  As you can see, it suddenly stops responding and then crashes.

Now the interesting thing is that it only crashes when there is a document open (even a blank one).  If there is no document open then it never crashes.

= Steve

Link to comment
Share on other sites

14 hours ago, Speed said:

Attached is a video of Affinity Designer 2 crashing on an XP-Pen Artist 13 drawing display.  The exact same thing happens with the Wacom One drawing display, so it doesn't matter which one I use.
...

Now the interesting thing is that it only crashes when there is a document open (even a blank one).  If there is no document open then it never crashes.

Probably as far as no doc is open there isn't any real GPU usage involved and when a doc is opened the GPU (aka GPU driver) is used for rendering. - Do you also have another, main chip based integrated GPU available on your system, beside the NVidia GeoForce GTX 745, so you maybe can switch GPUs for behavior tryouts?

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

  • 4 weeks later...

So it definitely seems like my crashing problems were due to video drivers.  Even though I completely uninstalled and reinstalled the drivers several times, with reboots in between, the problem persisted.  In the end, I upgraded the GeForce card to a newer model, installed the drivers for it, and now no more crashes!

Thank you for all the suggestions and help!

= Steve

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.