voom Posted April 30, 2021 Share Posted April 30, 2021 ...but not after the system is freshly booted, even when the same apps are already running. This started only yesterday, even though there was no update or newly installed app. Here is a log-dump from today for Photo... Since it is not a textfile I need your help to find the cause... 4f0c13f0-9bf3-4585-9b7e-7d681e2a4a8b.dmp Quote Link to comment Share on other sites More sharing options...
firstdefence Posted May 1, 2021 Share Posted May 1, 2021 Just in case someone wants to try and read a dmp file: https://www.wikihow.com/Read-Dump-Files voom 1 Quote iMac 27" 2019 Somona 14.3.1, iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9 (Please refrain from licking the screen while using this forum) Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions Link to comment Share on other sites More sharing options...
voom Posted May 1, 2021 Author Share Posted May 1, 2021 Thanks. The Nirsoft-Tool (I loaded the specific dump attached here, too) finds "no crash", so I installed the debugger. When performing an exception analysis on the file, the results are not comprehensible for me. Quote Link to comment Share on other sites More sharing options...
v_kyr Posted May 1, 2021 Share Posted May 1, 2021 5 hours ago, firstdefence said: Just in case someone wants to try and read a dmg file ... Those are dmp (dump) files! 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 Link to comment Share on other sites More sharing options...
v_kyr Posted May 1, 2021 Share Posted May 1, 2021 16 hours ago, voom said: Here is a log-dump from today for Photo... Since it is not a textfile I need your help to find the cause... Quote Operating system: Windows NT 6.2.19041 928 CPU: amd64 family 6 model 94 stepping 3 8 CPUs GPU: UNKNOWN Crash reason: 0xe0434352 / 0x00000001 Crash address: 0x7ffd06114b59 Process uptime: 8 seconds Thread 0 (crashed) 0 KERNELBASE.dll + 0x34b59 rax = 0x0000001c9eff9840 rdx = 0x0000000000000000 rcx = 0x0000000000000030 rbx = 0x00000000e0434352 rsi = 0x0000000000000001 rdi = 0x0000000000000005 rbp = 0x0000001c9effa3a0 rsp = 0x0000001c9eff9fc0 r8 = 0x00007ffd089849ef r9 = 0x0000000000000000 r10 = 0x0000000000000000 r11 = 0x000001cfe5220001 r12 = 0x0000000000004000 r13 = 0x000001cfbcbb58e8 r14 = 0x0000001c9effa158 r15 = 0x0000000000000000 rip = 0x00007ffd06114b59 Found by: given as instruction pointer in context 1 PresentationFramework.ni.dll + 0x10e63af rbp = 0x0000001c9effa4b0 rsp = 0x0000001c9effa3b0 rip = 0x00007ffcc10763af Found by: previous frame's frame pointer 2 PresentationCore.ni.dll + 0x35558b rbp = 0x0000001c9effa520 rsp = 0x0000001c9effa4c0 rip = 0x00007ffcc1a0558b Found by: previous frame's frame pointer 3 PresentationCore.ni.dll + 0x35487a rbp = 0x0000001c9effa600 rsp = 0x0000001c9effa530 rip = 0x00007ffcc1a0487a Found by: previous frame's frame pointer 4 PresentationCore.ni.dll + 0x37fa44 rsp = 0x0000001c9effa610 rip = 0x00007ffcc1a2fa44 Found by: stack scanning 5 clr.dll + 0x4e65 rsp = 0x0000001c9effa630 rip = 0x00007ffce3574e65 Found by: stack scanning ... ... 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 Link to comment Share on other sites More sharing options...
firstdefence Posted May 1, 2021 Share Posted May 1, 2021 9 minutes ago, v_kyr said: Those are dmp (dump) files! Typo on Mac lol v_kyr 1 Quote iMac 27" 2019 Somona 14.3.1, iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9 (Please refrain from licking the screen while using this forum) Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions Link to comment Share on other sites More sharing options...
voom Posted May 1, 2021 Author Share Posted May 1, 2021 What would I have to to, to show that information from the dmp with the MS debugger...? Secondly: what does that tell me and what could I do now? Quote Link to comment Share on other sites More sharing options...
firstdefence Posted May 1, 2021 Share Posted May 1, 2021 If you do a search using the crash reason code you get: https://answers.microsoft.com/en-us/protect/forum/protect_other-protect_scanning-windows_10/0xe0434352/372110fa-2a7c-4ab6-904f-d5f45fa4d1c4 Quote iMac 27" 2019 Somona 14.3.1, iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9 (Please refrain from licking the screen while using this forum) Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions Link to comment Share on other sites More sharing options...
v_kyr Posted May 1, 2021 Share Posted May 1, 2021 You (from your side) can with the MS Debugger just step back (backtrace) into a binary memory representation of the causes. Personally I would probably use the latest WinDbg for such purposes, see for example ... How to open and analyze crash dump files on Windows 10 Speicherabbilddateien im Visual Studio-Debugger (switch to read in english on the right side there) However, since you don't have the Affinity app and used libs etc. related source codes to step in, it's questionable if it is overall of much use for you at all here. - Meaning here, that it's more a task @Mark Ingramcan make a real use of and then reproduce and tell the exact cause of that problem! Thus you may want to file it in as a Affinity Photo Win10 bug report, as far as it hasn't been aready done before and thus is a known or so far in a Beta fixed one! - Possibly it could be some already known hardware acceleration (OpenCL, GPU driver) related bug, or also something related in that context with third party apps. 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 Link to comment Share on other sites More sharing options...
IanSG Posted May 1, 2021 Share Posted May 1, 2021 It's possible the crashes are caused by overheating - try checking the fans are running, grills etc are unobstructed and heatsinks are dust free. Quote AP, AD & APub user, running Win10 Link to comment Share on other sites More sharing options...
voom Posted May 1, 2021 Author Share Posted May 1, 2021 Thanks for all the tipps... I probably got the wrong forum; I came from an older thread where the Affinity staff asked for a dump in this forum, so I stayed in this forum and posted here I don't think that it's overheating.... Quote Link to comment Share on other sites More sharing options...
Staff Gabe Posted May 5, 2021 Staff Share Posted May 5, 2021 Hi all, it does look like an .net. Can you check your Event viewer and see if you have any more hints? Event Viewer (Local) > Windows Logs > Application Quote Link to comment Share on other sites More sharing options...
Komatös Posted May 5, 2021 Share Posted May 5, 2021 In the meantime, I would recommend running sfc /scannow. Press Windows key + R, type sfc /scannow in the input field, hold down the Shift and Control keys and press Enter or click OK. Quote AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 23H2 (22631.3296) AMD A10-9600P | dGPU R7 M340 (2 GB) | 8 GB DDR4 2133 MHz | Windows 10 Home 22H2 (1945.3803) Affinity Suite V 2.4 & Beta 2.(latest) Better translations with: https://www.deepl.com/translator Interested in a robust (selfhosted) PDF Solution? Have a look at Stirling PDF Life is too short to have meaningless discussions! Link to comment Share on other sites More sharing options...
voom Posted May 5, 2021 Author Share Posted May 5, 2021 32 minutes ago, Gabe said: Hi all, it does look like an .net. Can you check your Event viewer and see if you have any more hints? Event Viewer (Local) > Windows Logs > Application On that day the only .net related error, or application errors, refer to some freemakeserviceutility process. All Freemake-apps have been uninstalled for a long time, but this remained and even seems to be loaded. I removed that, has no use obviously anyway. I doubt though, that that could have had sth. to do with it . Quote Link to comment Share on other sites More sharing options...
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.