boxed checked to send crash information with indentifier

[Understatement]

Hi new and here, I love affinity the concepts are brilliant it is the funnest toy uh hmm tool in my fantasy digital world I enjoy. It is chocked full of very smart ideas I will be discovering in it for a long time. It also can be a living rorschach . Any who...

Affinity Photo crashes regularly when doing projects. I tend to be top heavy in my work at times and if you click something too soon after activation of a task for the program this is one of the most common reasons. These crashes are becoming almost every time I use the program now. See my system setup and graphics card etc..

I was wondering because I send identifiable crash information automatically can I have an assessment of my the crash causes? 

System information

OS Name             Microsoft Windows 10 Home

Version                10.0.19042 Build 19042

Other OS Description     Not Available

OS Manufacturer             Microsoft Corporation

System Name    TS2

System Manufacturer    Micro-Star International Co., Ltd.

System Model   GE75 Raider 10SF

System Type      x64-based PC

System SKU        17E9.1

Processor            Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz, 2592 Mhz, 6 Core(s), 12 Logical Processor(s)

BIOS Version/Date          American Megatrends Inc. E17E9IMS.10D, 11/17/2020

SMBIOS Version               3.2

Embedded Controller Version    255.255

BIOS Mode         UEFI

BaseBoard Manufacturer             Micro-Star International Co., Ltd.

BaseBoard Product         MS-17E9

BaseBoard Version          REV:1.0

Platform Role    Mobile

Secure Boot State            On

PCR7 Configuration         Elevation Required to View

Windows Directory         C:\WINDOWS

System Directory             C:\WINDOWS\system32

Boot Device        \Device\HarddiskVolume1

Locale   United States

Hardware Abstraction Layer        Version = "10.0.19041.1151"

User Name         n/a

Time Zone          n/a

Installed Physical Memory (RAM)             32.0 GB

Total Physical Memory  31.8 GB

Available Physical Memory          25.9 GB

Total Virtual Memory     36.6 GB

Available Virtual Memory             29.0 GB

Page File Space 4.75 GB

Page File              C:\pagefile.sys

Kernel DMA Protection On

Virtualization-based security      Not enabled

Device Encryption Support          Elevation Required to View

Hyper-V - VM Monitor Mode Extensions              Yes

Hyper-V - Second Level Address Translation Extensions Yes

Hyper-V - Virtualization Enabled in Firmware      Yes

Hyper-V - Data Execution Protection       Yes

Display

Name    NVIDIA GeForce RTX 2070

PNP Device ID   PCI\VEN_10DE&DEV_1F14&SUBSYS_12BC1462&REV_A1\4&443BD0D&0&0008

Adapter Type    NVIDIA GeForce RTX 2070, NVIDIA compatible

Adapter Description       NVIDIA GeForce RTX 2070

Adapter RAM    (1,048,576) bytes

Installed Drivers                C:\WINDOWS\System32\DriverStore\FileRepository\nvmisi.inf_amd64_649d1583f8a63e67\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvmisi.inf_amd64_649d1583f8a63e67\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvmisi.inf_amd64_649d1583f8a63e67\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvmisi.inf_amd64_649d1583f8a63e67\nvldumdx.dll

Driver Version   30.0.15.1109

INF File oem94.inf (Section098 section)

Color Planes       Not Available

Color Table Entries          Not Available

Resolution          Not Available

Bits/Pixel             Not Available

Memory Address             0xC4000000-0xC4FFFFFF

Memory Address             0xB0000000-0xBFFFFFFF

Memory Address             0xC0000000-0xC1FFFFFF

IRQ Channel       IRQ 4294967286

Driver                C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVMISI.INF_AMD64_649D1583F8A63E67\NVLDDMKM.SYS (30.0.15.1109, 40.34 MB (42,299,864 bytes), 1/10/2022 10:07 AM)

               

Name    Intel(R) UHD Graphics

PNP Device ID   PCI\VEN_8086&DEV_9BC4&SUBSYS_12BC1462&REV_05\3&11583659&1&10

Adapter Type    Intel(R) UHD Graphics Family, Intel Corporation compatible

Adapter Description       Intel(R) UHD Graphics

Adapter RAM    1.00 GB (1,073,741,824 bytes)

Installed Drivers                C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_a6f2bd19df3d42e0\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_a6f2bd19df3d42e0\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_a6f2bd19df3d42e0\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_a6f2bd19df3d42e0\igd12umd64.dll

Driver Version   30.0.101.1191

INF File oem10.inf (iCML_w10_DS section)

Color Planes       Not Available

Color Table Entries          4294967296

Resolution          1920 x 1080 x 144 hertz

Bits/Pixel             32

Memory Address             0xC3000000-0xC3FFFFFF

Memory Address             0xA0000000-0xAFFFFFFF

I/O Port                0x00005000-0x0000503F

IRQ Channel       IRQ 4294967290

Driver                C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\IIGD_DCH.INF_AMD64_A6F2BD19DF3D42E0\IGDKMD64.SYS (30.0.101.1191, 29.68 MB (31,116,944 bytes), 1/6/2022 1:19 PM)

 

System/conflict/sharing

Memory Address 0xC5200000-0xC52FFFFF           Intel(R) PCI Express Root Port #15 - 06B6

Memory Address 0xC5200000-0xC52FFFFF           Killer E2500 Gigabit Ethernet Controller #2

               

I/O Port 0x00000070-0x00000070              Motherboard resources

I/O Port 0x00000070-0x00000070              System CMOS/real time clock

               

I/O Port 0x00003000-0x00003FFF              Intel(R) PCI Express Root Port #15 - 06B6

I/O Port 0x00003000-0x00003FFF              Killer E2500 Gigabit Ethernet Controller #2

               

Memory Address 0xC4000000-0xC4FFFFFF           NVIDIA GeForce RTX 2070

Memory Address 0xC4000000-0xC4FFFFFF           Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core(TM) PCIe Controller (x16) - 1901

               

IRQ 16   Intel(R) Serial IO I2C Host Controller - 06E8

IRQ 16   High Definition Audio Controller

IRQ 16   Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft)

               

IRQ 18   Killer E2500 Gigabit Ethernet Controller #2

IRQ 18   Intel(R) Serial IO I2C Host Controller - 06EA

               

Memory Address 0xB0000000-0xBFFFFFFF           NVIDIA GeForce RTX 2070

Memory Address 0xB0000000-0xBFFFFFFF           Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core(TM) PCIe Controller (x16) – 1901

 

         Benchmark no load      

[walt.farrell]

17 minutes ago, Understatement said:

I was wondering because I send identifiable crash information automatically can I have an assessment of my the crash causes? 

Welcome to the Serif Affinity forums.

Are you referring to these options in Preferences ?(this screenshot is from the Windows version of Photo)

If so, I'm not aware of any process where Serif examines them and responds automatically. At least, I've never had an unsolicited email from them about a crash.

[Understatement]

The information is sent to the makers automatically.. I have no expectations of it coming back automatically.. forums may allow the manual sharing of the information I sent because i also sent my private identifier.. I assume that is to collect it under a searchable identifier... hope that is helpul

[Understatement]

I thought this was for Affinity Support questions? Is there somewhere else I can get support. This question should get an answer.

[walt.farrell]

46 minutes ago, Understatement said:

I thought this was for Affinity Support questions? Is there somewhere else I can get support. This question should get an answer.

It is, but there are a lot of questions and a relatively small support staff when you compare it with the number of users. Someone from Serif will be here at some point.

[Understatement]

Alright thank you good to know I have lowered my expectations... 

[Callum]

14 hours ago, Understatement said:

Alright thank you good to know I have lowered my expectations... 

Hi Understatement,
Welcome to the forums

I'm sorry to hear the app is crashing intermittently for you please could you tell me if you have Open CL enabled in the performance section of the apps preferences? It may also help me diagnose this if you could provide the full crash log by following the below guide.

 

Thanks
C

[walt.farrell]

13 minutes ago, Callum said:

It may also help me diagnose this if you could provide the full crash log by following the below guide.

I think part of the question was what happens with the crash reports that are automatically uploaded, especially when they include the info to identify the user who had the problem. And I'm responding again, @Callum, because I've wondered about that in the past, too

[Callum]

4 minutes ago, walt.farrell said:

I think part of the question was what happens with the crash reports that are automatically uploaded, especially when they include the info to identify the user who had the problem. And I'm responding again, @Callum, because I've wondered about that in the past, too

From What I know these are just used to influence internal testing etc I imagine it would have to be a very rare case for us to contact someone after receiving one of these reports but its not really my area I'm afraid.

[Understatement]

 

16 hours ago, Callum said:

From What I know these are just used to influence internal testing etc I imagine it would have to be a very rare case for us to contact someone after receiving one of these reports but its not really my area I'm afraid.

 

On 2/13/2022 at 12:20 PM, Understatement said:

The information is sent to the makers automatically.. I have no expectations of it coming back automatically.. forums may allow the manual sharing of the information I sent because i also sent my private identifier.. I assume that is to collect it under a searchable identifier... hope that is helpful

[thomaso]

20 hours ago, Callum said:

From What I know these are just used to influence internal testing etc

@Callum, this thread reminds me to a related checkbox on mac where early app versions still had the option above the buttons in the misc section of app prefs. Where they removed in purpose – or is their disappearance on mac a bug?

 

[R C-R]

6 hours ago, thomaso said:

... this thread reminds me to a related checkbox on mac where early app versions still had the option above the buttons in the misc section of app prefs.

AFAIK, the option to share crash reports with app developers in all recent versions of the macOS is set in System Preferences > Security & Privacy in the Analytics & Improvements section. So maybe what you saw in earlier versions was something else, or was removed because it was redundant?

[thomaso]

1 hour ago, R C-R said:

AFAIK, the option to share crash reports with app developers in all recent versions of the macOS is set in System Preferences > Security & Privacy in the Analytics & Improvements section. So maybe what you saw in earlier versions was something else, or was removed because it was redundant?

As far I understand the text at this two macOS preference checkboxes concern Apple only, respectively Apple sharing my info with app developers (like Serif). So, if I haven't ticked one of this two boxes Apple has nothing to share with Serif. – I am quite sure there was initially a similar checkbox for report sharing with Serif in earlier Affinity versions, at the spot shown in the screenshot. Which could make sense for those users who don't share reports with Apple.

[Understatement]

Thanks guys for the info... this is just a hobby for me I think this is good enough for now. I will make some changes and real world test it when I come back to this in my rotation.

When I have a project in the future I'll revisit again..

[R C-R]

8 minutes ago, thomaso said:

I am quite sure there was initially a similar checkbox for report sharing with Serif in earlier Affinity versions, at the spot shown in the screenshot.

I don't remember anything like that but I will take your word for it that there was. Maybe one of the staff can tell us more about that?