eftee74 Posted November 27, 2022 Share Posted November 27, 2022 I'm having unspected crashes recently. Today I had a stange memory error message, shown in the picture. Never happened before. Traslation is: The instruction at 0x00007FF8BDE21420 referenced memory at 0x0000000000000000. The memory could non be read. Quote Link to comment Share on other sites More sharing options...
Staff NathanC Posted December 8, 2022 Staff Share Posted December 8, 2022 Hi @eftee74, The error in your screenshot indicates a physical memory error which has the potential to appear on any program, and can be caused by an number of factors, I've linked an article below which goes into more detail on this issue and provides some potential solutions. https://windowsreport.com/instruction-referenced-memory-windows-10/ Quote Link to comment Share on other sites More sharing options...
eftee74 Posted December 8, 2022 Author Share Posted December 8, 2022 Thank you for your answer. I have already tried most of the fix mentioned in that page. Nevertheless AP is the only software showing that issue. Moreover sometimes the application crashes without any memory error. In this cases no option to recover from autosave. Quote Link to comment Share on other sites More sharing options...
Staff NathanC Posted December 9, 2022 Staff Share Posted December 9, 2022 Could you provide me with a few recent crash report(s)? Many thanks Quote Link to comment Share on other sites More sharing options...
eftee74 Posted December 9, 2022 Author Share Posted December 9, 2022 I don't have that folder. I'm using V1. Anyway I found this folder C:\Users\xxxxx\AppData\Roaming\Affinity\Photo\1.0\CrashReports\reports\ but it's empty. Quote Link to comment Share on other sites More sharing options...
Staff NathanC Posted December 9, 2022 Staff Share Posted December 9, 2022 Apologies, I had meant to link the V1 FAQ but it appears you found the correct folder. It's possible app isn't able to generate a crash report possibly due to Windows crashing it out with the memory error, preventing the app from generating a report. To confirm whether or not this is an issue with the program or your OS/Hardware, you could try the below: - It's unlikely to be related but disable Hardware Acceleration under edit > preferences > performance and reset the app. - Completely re-install the app from scratch: Rename the 'Photo' folder in %APPDATA%/Affinity to 'Photo.old' and then uninstall the app using the Microsoft uninstall trouble-shooter linked here: https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d After uninstalling, re-download and install the app from the affinity store. - Create a new temporary Windows user and run the app from the new user to see if it crashes You may not have run into this error on other apps as it could only be encountered on more memory intensive apps, such as Photo (dependant on the file(s) open), it may be worth monitoring your memory usage in task manager whilst in Photo. Could you also send a screenshot of your 'System information' page which shows your hardware specs? Quote Link to comment Share on other sites More sharing options...
eftee74 Posted December 9, 2022 Author Share Posted December 9, 2022 I'm testing AP V1 without HW acceleration and also increased ram usage limit to 32 GB (max) from 24 for. Main system specification are: Win 10 22H2, Gigabyte AB350 Gaming 3, Ryzen 7 1700, RAM 32 GB 2666 MHz DDR4, Radeon RX 580 4 GB, Samsung evo 860 (system), Samsung evo 850 (data). Quote Link to comment Share on other sites More sharing options...
eftee74 Posted December 18, 2022 Author Share Posted December 18, 2022 I decided to upgrade to V2. Anyway thanks for the reply. I hope it won't be necessary a new topic in V2's section. 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.