Jump to content

(Win 10) Photo and Designer crash when system has been running longer...


Recommended Posts

Just in case someone wants to try and read a dmp file: https://www.wikihow.com/Read-Dump-Files

 

iMac 27" Late 2019 Fully Loaded, iMac 27" Late 2013 both running Catalina 10.15.7 - Affinity Designer, Photo & Publisher, Adobe, Inkscape, Blender, C4D, Sketchup, Pepakura Designer + more... XP-Pen Artist-22E, - iPad Pro 12.9 B|  

Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions

Link to comment
Share on other sites

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. 

Link to comment
Share on other sites

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
...
...

 

☛ Affinity Designer 1.10.5 ◆ Affinity Photo 1.10.5 ◆ OSX El Capitan

Link to comment
Share on other sites

9 minutes ago, v_kyr said:

Those are dmp (dump) files!

Typo on Mac lol

iMac 27" Late 2019 Fully Loaded, iMac 27" Late 2013 both running Catalina 10.15.7 - Affinity Designer, Photo & Publisher, Adobe, Inkscape, Blender, C4D, Sketchup, Pepakura Designer + more... XP-Pen Artist-22E, - iPad Pro 12.9 B|  

Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions

Link to comment
Share on other sites

iMac 27" Late 2019 Fully Loaded, iMac 27" Late 2013 both running Catalina 10.15.7 - Affinity Designer, Photo & Publisher, Adobe, Inkscape, Blender, C4D, Sketchup, Pepakura Designer + more... XP-Pen Artist-22E, - iPad Pro 12.9 B|  

Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions

Link to comment
Share on other sites

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 ...

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.

☛ Affinity Designer 1.10.5 ◆ Affinity Photo 1.10.5 ◆ OSX El Capitan

Link to comment
Share on other sites

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....

Link to comment
Share on other sites

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.

AMD Ryzen 5 5600G | 32 GB DDR4 3200MHz | Sapphire RX 5600 XT 6 GB | Windows 11 Pro (22H2 Build 22622.586)
Affinity Suite V1.10.5.1342
Better translations with: https://www.deepl.com/translator  
SVG preview in Windows Explorer with "SVG-See  Download SVG-See

It's nice to be important, but it's more important to be nice.

Link to comment
Share on other sites

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 .

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...
 Share

×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.