Jump to content

Publisher 1.7.3 on Windows crashes on Save

Recommended Posts


I'm having a problem saving some files with Publisher on a PC with Windows 10 Version 1903 (OS Build 18362.449), although this was happening on a previous Windows build or two as well.

The problem has occurred on publications which have had a single page with a single table on the page. When I use either Save or Save As, I can get as far as naming the file but as soon as I click to Save, I get the 'blue screen of death'. Attached is a photo of the screen showing the Windows crash information.

Publications which have single or multiple pages of text, or text plus images, seem to save OK. It's the presence of the table that seems to dictate the crash.

I have also had to avoid using the Glyphs tool in any publication, as this too has caused regular crashes, with cldflt.sys featuring in the Windows crash report, as with the above crashes.

Anything I can do to prevent either of these types of crash happening?

Many thanks


Share this post

Link to post
Share on other sites


Unfortunately, I can't offer you much assistance with what, exactly, is causing these BSODs but a number of Serif/Affinity staff have posted in several threads to state that none of the Affinity range of products is capable of actually causing these total system crashes. This page gives a list of topics in the forum where users are reporting various BSOD episodes.



Win 10 Pro, i7 6700K, 32Gb RAM, AMD Radeon R7 360 and Intel HD530 Graphics


Long-time user of Serif products, chiefly PagePlus and PhotoPlus, but also WebPlus, CraftArtistProfessional and DrawPlus.  Delighted to be using Affinity Designer, Photo, and now Publisher.

Share this post

Link to post
Share on other sites

Thank you for your replies and suggestions. I hadn't thought of searching for BSOD in the forum, so I hadn't found those posts. They do echo my problem and it's clearly a Windows OS gremlin from the last couple of updates. I did try CarlM's cldflt.sys corruption solutions, but those don't solve the problem. I'll have to try rolling back to an earlier Windows build and see if that resolves it.

Share this post

Link to post
Share on other sites

I solved the problem with a clean install  of Windows 10. Nothing else would fix it. Another benefit was that it got rid of a lot of unwanted rubbish from my primary drive as well! It wasn't an Affinity problem but a Windows gremlin, so thank you for pointing me in the right direction.

Share this post

Link to post
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.

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.


  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.