charley Posted March 11, 2021 Posted March 11, 2021 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. The preference selection Hardware Acceleration option is not enabled for OpenCL compute acceleration. I have attached logs files from two instances. acd2492f-eb04-497c-bc55-8c3648a3706c.dmp def26821-d6a4-46fe-a621-f377e4e8178f.dmp Quote
v_kyr Posted March 11, 2021 Posted March 11, 2021 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 ... ... Gabe 1 Quote ☛ 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
mds1256 Posted March 12, 2021 Posted March 12, 2021 Also getting this on Win 10, when opening files. My graphics are Intel UHD. Quote
PeteMacca Posted March 12, 2021 Posted March 12, 2021 3 hours ago, mds1256 said: Also getting this on Win 10, when opening files. My graphics are Intel UHD. I was having the same problem with AP 1.9.1 & Intel UHD 620. I thought I had the latest driver (both Windows Update & Lenovo told me so - release date: 2020). Then I ran an update utility from Intel (Intel Driver & Support Assistant) which installed a 2021 version of the driver..., and now Hardware Acceleration works just fine. Mark Ingram 1 Quote
mds1256 Posted March 12, 2021 Posted March 12, 2021 4 minutes ago, PeteMacca said: I was having the same problem with AP 1.9.1 & Intel UHD 620. I thought I had the latest driver (both Windows Update & Lenovo told me so - release date: 2020). Then I ran an update utility from Intel (Intel Driver & Support Assistant) which installed a 2021 version of the driver..., and now Hardware Acceleration works just fine. Thanks for this I’ll give it a go and let you know how I get on. Quote
hexaae Posted March 29, 2021 Posted March 29, 2021 Argh! Same here: Affinity Photo and Designer 1.9.1.979 are unusable with NVidia Open CL Hardware acceleration enabled and studio drivers 461.92. Once the HW acceleration is disabled, both won't crash anymore. Was working fine up to 460.xx I guess. Crash log example: Descrizione Percorso dell'applicazione che ha generato l'errore: C:\Program Files\Affinity\Photo\Photo.exe Firma del problema Nome evento problema: APPCRASH Nome applicazione: Photo.exe Versione applicazione: 1.9.1.979 Timestamp applicazione: 60350423 Nome modulo con errori: KERNELBASE.dll Versione modulo con errori: 10.0.19041.804 Timestamp modulo con errori: 0e9c5eae Codice eccezione: 80000003 Offset eccezione: 00000000000c9ad2 Versione SO: 10.0.19042.2.0.0.256.48 ID impostazioni locali: 1040 Informazioni aggiuntive 1: e097 Ulteriori informazioni 2: e09767feb916c54f68e77c8419cd22cc Ulteriori informazioni 3: 7fc3 Ulteriori informazioni 4: 7fc37b48a854644f569973e66a64c791 Ulteriori informazioni sul problema ID bucket: 4000e7e5ef3fc74684a3688372df0ab7 (1487147215739620023) Windows 10 Pro 19042.870, NVidia SD 461.92, i7-8750H, 32GB RAM Quote ASUS Gaming Laptop GL703GS CPU: i7-8750H, RAM: 32GB DDR4@2666, Gfx: GTX 1070 8GB GDDR5, Screen: G-Sync AUO B173HAN03.2 17" 1080p 144Hz, HD: SSD + NVMe, Audio: Realtek HD (ALC295), Controllers: Hori Fighting Stick Mini, XBox One bt controller, ROG Strix Carry wireless/bt mouse.
mds1256 Posted March 29, 2021 Posted March 29, 2021 On 3/12/2021 at 7:55 PM, PeteMacca said: I was having the same problem with AP 1.9.1 & Intel UHD 620. I thought I had the latest driver (both Windows Update & Lenovo told me so - release date: 2020). Then I ran an update utility from Intel (Intel Driver & Support Assistant) which installed a 2021 version of the driver..., and now Hardware Acceleration works just fine. Just to confirm this worked for me, sorry forgot to come back to this forum. Quote
Recommended Posts
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.