Affinity 1.9.1.979 crashes on file open with Windows 10

[charley]

Affinity 1.9.1.979 crashes on file open

I just did a new windows 10 install and installed affinity   1.9.1.979. When I try to open an image file, Affinity crashes so this new version is not usable. I had the same problem with my previous windows installation .. the 1.9.1.979  version crashed on any attempt to open a file so I went back to an earlier Affinity version which I was able to work with. I was hoping with a new windows install the problem would go away but that does not look like the case. n

[v_kyr]

High and welcome!

This could be related to as default enabled Affinity OpenCL performance hardware acceleration and your GPU drivers, in such cases you can try this tool here on Win, or instead perform the steps manually to disable OpenCL hardware acceleration (see this FAQ for manually disabling OpenCL). Restart Affinity afterwards and see if it fixes the problem.

If that doesn't help, you may want to look if you can find some actual Affinity crash report file which might tell the cause, see ...

• [FAQ] Where to find Crash Reports

Other than the above (in case nothing applies) the Windows system logs might too can give the one or other hint for possible crashes and their cause ...

• How to View Windows 10 Crash Logs and Error Logs

• How to view crash logs in Windows 10

[charley]

14 minutes ago, v_kyr said:

High and welcome!

This could be related to as default enabled Affinity OpenCL performance hardware acceleration and your GPU drivers, in such cases you can try this tool here on Win, or instead perform the steps manually to disable OpenCL hardware acceleration (see this FAQ for manually disabling OpenCL). Restart Affinity afterwards and see if it fixes the problem.

If that doesn't help, you may want to look if you can find some actual Affinity crash report file which might tell the cause, see ...

• [FAQ] Where to find Crash Reports

Other than the above (in case nothing applies) the Windows system logs might too can give the one or other hint for possible crashes and their cause ...

• How to View Windows 10 Crash Logs and Error Logs

• How to view crash logs in Windows 10

Quote

Under preferences the Hardware Acceleration is not ticked so it does not seem to be enabled. I have located the crash files where should I send them?

 

 

Edited March 11, 2021 by charley

[v_kyr]

15 minutes ago, charley said:

Under preferences the Hardware Acceleration is not ticked so it does not seem to be enabled. ...

For sureness I would look also to the  PerformancePreferences.xml in %AppData%\<APPNAME>\1.0\Settings\ then. Look if there is in that XML file always an entry ...

-->  <UseHardwareAcceleration>False</UseHardwareAcceleration>

... if not you have to apply one at the end!

15 minutes ago, charley said:

I have located the crash files where should I send them?

For the crash files make a related new posting into the appropriate Affinity app related Windows bugs section and attach your dump file to that posting then.

[charley]

44 minutes ago, v_kyr said:

For sureness I would look also to the  PerformancePreferences.xml in %AppData%\<APPNAME>\1.0\Settings\ then. Look if there is in that XML file always an entry ...

-->  <UseHardwareAcceleration>False</UseHardwareAcceleration>

... if not you have to apply one at the end!

For the crash files make a related new posting into the appropriate Affinity app related Windows bugs section and attach your dump file to that posting then.

Seems to be set correctly..

<?xml version="1.0" encoding="UTF-8"?>
-<Settings xsi:type="Serif.Interop.Persona.Settings.PerformanceSettings" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
-<RAMUsageLimit>
<UnitType>Megabyte</UnitType>
<Value>8192</Value>
</RAMUsageLimit>
-<DiskWarningLimit>
<UnitType>Megabyte</UnitType>
<Value>32768</Value>
</DiskWarningLimit>
<UndoLimit>1024</UndoLimit>
<ViewQuality>0</ViewQuality>
-<AutoSaveInterval>
<UnitType>Number</UnitType>
<Value>300</Value>
</AutoSaveInterval>
<UsePerfectClipping>False</UsePerfectClipping>
<UseDithering>True</UseDithering>
<RetinaPassIndex>0</RetinaPassIndex>
<UseHardwareAcceleration>False</UseHardwareAcceleration>
</Settings>

[v_kyr]

Yes that looks Ok and hardware acceleration should be disabled/not be used. - Then your crash reports have to tell what is the cause of all evil then!

You don't use CaptureOne too or?

Did you already tried the  Affinity Photo Windows Customer Beta - 1.9.2.997  version, if that works Ok or crashes too?

[charley]

50 minutes ago, v_kyr said:

Yes that looks Ok and hardware acceleration should be disabled/not be used. - Then your crash reports have to tell what is the cause of all evil then!

You don't use CaptureOne too or?

Did you already tried the  Affinity Photo Windows Customer Beta - 1.9.2.997  version, if that works Ok or crashes too?

Do not have  CaptureOne .. this is a fresh windows install.  Affinity is the only program installed except for a password manager .. so the PC is pretty clean. I uninstalled 1.9.1.979  and tried 1.9.2.997 but it behaves the same. Performance hardware acceleration remains off after the beta install.

[v_kyr]

Then post your crash reports to the Photo Bugs found on Windows forum section for analysis.

[charley]

13 minutes ago, v_kyr said:

Then post your crash reports to the Photo Bugs found on Windows forum section for analysis.

Done ..

 

[v_kyr]

12 minutes ago, charley said:

Done ..

Fine, though both of your crash reports do tell here, a crash due to a read access violation in nvwgf2umx.dll which is part of the Nvidia graphics driver!

Quote

Operating system: Windows NT
                  6.2.19041 804
CPU: amd64
     family 6 model 60 stepping 3
     8 CPUs

GPU: UNKNOWN

Crash reason:  EXCEPTION_ACCESS_VIOLATION_READ
Crash address: 0xffffffffffffffff
Process uptime: 575 seconds

Thread 71 (crashed)
 0  nvwgf2umx.dll + 0xedf5e
    rax = 0x0000013ce9852450   rdx = 0x0000000000000001
    rcx = 0x000c0c0c7d7d7d41   rbx = 0x0000013ce98a9400
    rsi = 0x0000013ce98a9400   rdi = 0x000c0c0c7d7d7d41
    rbp = 0x0000000000000002   rsp = 0x00000026db8bec20
     r8 = 0x00007ffd97844f00    r9 = 0x00000000000007d0
    r10 = 0x0000000000000000   r11 = 0x0000000000000246
    r12 = 0x0000000000000000   r13 = 0x0000000000000002
    r14 = 0x00000026db8bec90   r15 = 0x0000013ce98b4328
    rip = 0x00007ffd96dbdf5e
    Found by: given as instruction pointer in context
 1  nvwgf2umx.dll + 0xb173a
    rsp = 0x00000026db8bec70   rip = 0x00007ffd96d8173a
    Found by: stack scanning
 2  d3d11.dll + 0x1cb878
    rsp = 0x00000026db8beca8   rip = 0x00007ffdb7b8b878
    Found by: stack scanning
 3  d3d11.dll + 0x1ea210
    rsp = 0x00000026db8becb8   rip = 0x00007ffdb7baa210
    Found by: stack scanning
 4  d3d11.dll + 0x1ea210
    rsp = 0x00000026db8bece8   rip = 0x00007ffdb7baa210
    Found by: stack scanning
 5  d3d11.dll + 0x43183
    rsp = 0x00000026db8becf0   rip = 0x00007ffdb7a03183
    Found by: stack scanning
 6  d3d11.dll + 0x434f6
    rsp = 0x00000026db8bed00   rip = 0x00007ffdb7a034f6
    Found by: stack scanning
 7  d3d11.dll + 0x3bf12

 

[charley]

6 minutes ago, v_kyr said:

Fine, though both of your crash reports do tell here, a crash due to a read access violation in nvwgf2umx.dll which is part of the Nvidia graphics driver!

 

I fell back to Affinity 1.8.5 and everything works OK but any version later than Affinity 1.8.5 the issues reappears, so some change between Affinity 1.8.5 and 1.9.0 caused something to change. For the time being I will run using 1.8.5. 

[v_kyr]

v1.9.0 -> v1.9.1 introduced OpenCL GPU hardware acceleration support, in contrast to just OpenGL before and that makes now many problems under Windows with graphics card drivers.

[charley]

6 minutes ago, v_kyr said:

v1.9.0 -> v1.9.1 introduced OpenCL GPU hardware acceleration support, in contrast to just OpenGL before and that makes now many problems under Windows with graphics card drivers.

If it helps .. here is the crash report from the v1.9.0 failure .. based on what you mentioned I am guess it will have the issue. 

8c9f7a14-51eb-4fba-8543-f4eb6e28a31e.dmp

[v_kyr]

13 minutes ago, charley said:

If it helps .. here is the crash report from the v1.9.0 failure .. based on what you mentioned I am guess it will have the issue. 

8c9f7a14-51eb-4fba-8543-f4eb6e28a31e.dmp 3.24 MB · 0 downloads

Yip shows the same stuff here ...

Quote

Operating system: Windows NT
                  6.2.19041 804
CPU: amd64
     family 6 model 60 stepping 3
     8 CPUs

GPU: UNKNOWN

Crash reason:  EXCEPTION_ACCESS_VIOLATION_READ
Crash address: 0x200020
Process uptime: 28 seconds

Thread 77 (crashed)
 0  nvwgf2umx.dll + 0xedf5e
    rax = 0x0000014be81b9f50   rdx = 0x0000000000000001
    rcx = 0x0000000000200020   rbx = 0x0000014be8075400
    rsi = 0x0000014be8075400   rdi = 0x0000000000200020
    rbp = 0x0000000000000002   rsp = 0x0000003ba08beab0
     r8 = 0x00007ffd35b24f00    r9 = 0x0000000000000004
    r10 = 0x0000000000000000   r11 = 0x0000000000000246
    r12 = 0x0000000000000000   r13 = 0x0000000000000002
    r14 = 0x0000003ba08beb20   r15 = 0x0000014be7fbcc6c
    rip = 0x00007ffd3509df5e
    Found by: given as instruction pointer in context
 1  nvwgf2umx.dll + 0xb173a
    rsp = 0x0000003ba08beb00   rip = 0x00007ffd3506173a
    Found by: stack scanning
 2  d3d11.dll + 0x1cb878
    rsp = 0x0000003ba08beb38   rip = 0x00007ffdb7b8b878
    Found by: stack scanning
 3  d3d11.dll + 0x1ea210
    rsp = 0x0000003ba08beb48   rip = 0x00007ffdb7baa210
    Found by: stack scanning
 4  d3d11.dll + 0x1ea210
    rsp = 0x0000003ba08beb78   rip = 0x00007ffdb7baa210

 

[charley]

Looks like same culprit nvwgf2umx.dll. I looked for windows 10 crash and error logs but did not see any. Guess since windows does not crash none were reported.

 

[v_kyr]

Affinity crashes here due to that read access violation, which gives then this exception and in turn generates the crash report.