Mike Christelow Posted January 24 Share Posted January 24 Hi, I've been using Publisher for a few months and have had no issues until today, 24.01.24. Was working on a document this morning (which I've been working on for months), made a small updated (added a couple hundred words) and saved it, then closed Publisher. All appeared OK. Come to open the document this afternoon, Publisher opens, says Loading 1 document and then simply exits. There's no message, the document never displays. I've tried with a backup copy, exactly the same. Tried with a previous generation backup, same outcome. Have also tried opening Publisher with Ctrl and clearing the suggested items, no difference. Have also tried opening Publisher and creating a new document, same outcome. Because the same result applies whichever version of my document (current - backup 1 - backup 2 etc) I try to open, this suggests an environmental issue rather than something inherent in the document. Nothing has changed that I'm aware of on my PC (Win10) but something clearly has changed otherwise I wouldn't be getting this issue. My source document (afpub file) is 809,510KB in size, images embedded rather than linked. This is the content of Log.txt - [2024-01-24T16:14:09.404+0000] Affinity Publisher 2 [2024-01-24T16:14:09.407+0000] IsSandboxed: Yes [2024-01-24T16:14:09.408+0000] AppDataPathForCurrentUser: C:\Users\Mike Christelow\.affinity\Publisher\2.0 [2024-01-24T16:14:09.408+0000] AppDataPathForCurrentUserPersisted: C:\Users\Mike Christelow\.affinity\Publisher\2.0 [2024-01-24T16:14:09.408+0000] AppDataPathForAllUsers: C:\ProgramData\Affinity\Publisher\2.0 [2024-01-24T16:14:09.409+0000] CommonDataPathForCurrentUser: C:\Users\Mike Christelow\AppData\Local\Publishers\3cqzy0nppv2rt\Affinity\Common\2.0 [2024-01-24T16:14:09.409+0000] CommonDataPathForCurrentUserPersisted: C:\Users\Mike Christelow\.affinity\Common\2.0 [2024-01-24T16:14:09.410+0000] CommonDataPathForCurrentUserPersistedBuildInvariant: C:\Users\Mike Christelow\.affinity\Common\2.0 [2024-01-24T16:14:09.411+0000] CommonDataPathForAllUsers: C:\ProgramData\Affinity\Common\2.0 [2024-01-24T16:14:09.411+0000] TempPathForCurrentUser: C:\Users\Mike Christelow\.affinity\Publisher\2.0\temp [2024-01-24T16:14:11.031+0000] Skipping check for updates (no update available in recent check) [OpenCL] Not available [2024-01-24T16:14:19.400+0000] Installed [DXCore] Found 2 adapters NVIDIA GeForce 9600 GT Version: 21.21.13.4201 IsHardware: Yes Supports D3D12 Feature Level 12.0: No HardwareID: PCI\VEN_10DE&DEV_0622&SUBSYS_20250000&REV_A1 LUID: 0xC345 Microsoft Basic Render Driver Version: 10.0.19041.3636 IsHardware: No Supports D3D12 Feature Level 12.0: Yes HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00 LUID: 0xCAC3 [2024-01-24T16:14:32.520+0000] Wintab: Failed to load Wintab32.dll [2024-01-24T16:14:32.520+0000] Wintab: Failed to create tablet context [2024-01-24T16:15:16.870+0000] Attempting to create Direct3D device on default adapter Not sure of the relevance of the two entries immediately before the last line here. There appear to be .dmp files for every attempt and 'failure' but I can't open them so could do with some advice on what to do next please; I've attached the latest .dmp file here... 106,000 words is a lot of effort so far and I can't afford to lose them. Any advice or help would be very much appreciated. TIA, MikeC 05f91acc-9a1e-4aae-85b8-9e4ac8510892.dmp Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted January 24 Share Posted January 24 Issues like this are often related to faults in the graphic drivers, and specifically to their handling of the OpenCL hardware acceleration functions. If Windows updated yesterday, it might have installed a faulty version of your GPU driver. As a start, you might open the application Settings, Performance, and if Hardware Acceleration (OpenCL) is enabled try turning it off. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.1.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
Mike Christelow Posted January 24 Author Share Posted January 24 Thanks Walt, Hardware Acceleration (OpenCL) is disabled. When I try to enable it, the response is that my graphics card (NVIDIA GeForce 9600GT) or driver is currently unsupported. Which I don't really understand as I've been using that card since I first installed Affinity. Mike walt.farrell 1 Quote Link to comment Share on other sites More sharing options...
Staff NathanC Posted January 25 Staff Share Posted January 25 Hi @Mike Christelow, Can you confirm if the issue is specific to that document only, or does this happen when creating new files or when opening other publisher docs? If the app fails to create a new document/open any existing documents, this can be an indication of a GPU/Driver based issue on your device which is causing Affinity to crash when rendering the canvas/page area, as while OpenCL may not be for your Graphics card the app will still likely be using your GPU as the app renderer. I've provided some potential solutions to run through below. Update your GPU Drivers Make sure that you have the latest available drivers installed for your GPU, I've linked the Nvidia search tool below. If given the option during the driver installation, check 'Perform Clean installation'. https://www.nvidia.com/download/find.aspx Once you have updated your drivers, restart your PC and then try creating a new document, if that works try loading the existing document again. Reset drivers via DDU If it still freezes/crashes, try doing a complete uninstall of your graphics card drivers using a dedicated tool for this purpose (Such as DDU linked below) and then restart and install your graphics card drivers (using the link above to search) to completely refresh them. https://www.guru3d.com/files-details/display-driver-uninstaller-download.html -- Let me know how it goes. If the crashes persist after trying both of the above, could you possibly upload a few more recent crash reports? I attempted to debug your uploaded one but it fails to debug successfully. Many thanks Quote Link to comment Share on other sites More sharing options...
Mike Christelow Posted January 26 Author Share Posted January 26 Hi Nathan, Thanks for this - I've managed to get Publisher working again after running your recommended DDU utility. Happy days. Whatever it was that goosed my system also trashed the MS Photos app. I still have issues with the latter by I have workarounds for that... MIkeC 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.