Frederick Felix Posted December 14, 2018 Posted December 14, 2018 Hello; This is a repeat issue for the past 2 betas. When quitting AFpub beta I always have to close my saved document first, otherwise the program will always crash whether I use File->Exit to quit or click the 'X' top-right corner. Windows 7 will display their error box "Affinity Publisher has stopped working". The only option that works is to force AFpub to stop. I was able to get the Windows trace. Problem signature: Problem Event Name: BEX64 Application Name: Publisher.exe Application Version: 1.7.0.192 Application Timestamp: 5bfed485 Fault Module Name: ucrtbase.DLL Fault Module Version: 10.0.15063.468 Fault Module Timestamp: 5ba8b66e Exception Offset: 0000000000072219 Exception Code: c0000417 Exception Data: 0000000000000000 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: 9f8b Additional Information 2: 9f8b9e65c45917b76d1544dac954816c Additional Information 3: 1a58 Additional Information 4: 1a58ac9ad0411bd7ee3edab15590239c I don't know if this is OS related or a graphics driver issue, or whether it's a known problem with the beta program. So far, document contents aren't affected, but that may be because I close it first. The issue happens everytime I use AFpub beta. My GPU is GeForce GTX 1050 Ti, driver version 398.82 My OS is Windows 7 Home Premium Service Pack 1 My CPU is an Intel i7 920 (64-bit Operating System) Hope this helps.
Staff Jon P Posted December 18, 2018 Staff Posted December 18, 2018 Hi Frederick, This isn't a known issue, it seems to be something fairly unique to your machine. The faulting module is a windows one so my guess is that it's a potential OS problem. Can you confirm if your Windows is fully up to date? Thanks Serif Europe Ltd. - www.serif.com
Frederick Felix Posted January 11, 2019 Author Posted January 11, 2019 Hello; Yes Windows does an update every month. I should also say that my version of Affinity Publisher has been updated to 1.7.0.206, and as a result the issue no longer occurs. Since it wasn't a known issue, I'm not sure what changed or got fixed. However please let the powers know, the issue seems to have been resolved.
Recommended Posts