Jump to content

Search the Community

Showing results for 'BSOD'.


Didn't find what you were looking for? Try searching for:


More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 117 results

  1. @Bugeye, a failed stop code (BSOD) indicates a problem with a driver (the Affinity software itself cannot cause a BSOD as it runs in user-mode). Unfortunately I can't tell you which driver is causing the problem, but try uninstalling and reinstalling the latest graphics drivers as a start.
  2. Hello, I just purchased Affinity Photo (current version) on my system and have been in a few days encountering already 2 BSOD. I cannot reproduce this issue which has been appearing randomly while editing Fuji XT2/XH1 raw files. 1st time was when switching to liquify mode, 2nd time was when shifting the clarity cursor (before clicking develop raw). The BSOD message does not refer to a specific file (as I understand it may happen with Affinity Photo based on other posts I read) but mentioned: IRQL NOT LESS OR EQUAL (first BSOD) PAGE FAULT IN NON PAGED AREA (second BSOD) I am using the last version of Windows 10 1909 with last proposed updates installed. I know these kind of issues often relate to faulty hardware (ram, ssd) however, my system is quite recent (1 year old), very stable, and I have never encountered a single BSOD since I built it. This occured only twice and while using Affinity Photo. Thank you for your assistance. Maxime
  3. Not impressed! This is the first time I've ever had BSOD on Win10 and Affinity Designer just did it twice trying to dock a pop out menu. Yes I'm using the latest version Yes I can recreate, it happen twice in a row doing exactly the same action. Its' only happened in the one document, but not willing to keep killing my OS just to test that. System details: Windows 10 Pro - latest updates etc. What happened? - It killed my OS and forced a restart, what did I expect... Not that! Steps to recreate: Load document Try to drag pop out tabs for character and paragraph options to be docked around the bottom right corner of the screen The menu will start to stutter, the system will lock up and then the OS will exit to the BSOD forcing a system restart. Screenshots: I could record on my phone but I'd rather not keep blue screening my system unless absolutely necessary. No unusual hardware Did it used to work? - Don't know
  4. I have new Surface Laptop 2 with the latest Windows 10 Pro. Tried Affinity Designer trial version from the Microsoft Store, liked it and purchased the full version from the Microsoft Store. The trial version worked fine, without issues. The full version was installed as a second version, leaving the trial version visible. That was slightly annoying, so I uninstalled the trial version. This may have caused some registry errors. When starting the full version of Affinity Designer, the Blue Screen Of Death (BSOD) emerged after five seconds, referring to cldflt.sys. Uninstalling and reinstalling the AD did not help. Followed one cldflt.sys fix and changed using regedit the DWORD value of Start from 2 to 3. No help. Changed Start value back to 2. Noting from the other topic in this forum that the bug may be related to OneDrive, I refreshed the OneDrive connection -> the Designer application started without the BSOD for the first time. Now the AD causes BSOD sometimes when trying to open or save files from the OneDrive. Many users have complained similar situations and the response has been similar - AD cannot crash the system. But that is exactly what it does. I have not experienced BSOD with any other applications in three years with my business laptops. Disabling the OneDrive is not an option as I have to make my living with this system. The OS is a fresh install for the new laptop, so I cannot remove any earlier updates. What could be the root cause for the cldflt.sys error? Which register values should work with AD? Could this be related to the response time from OneDrive?
  5. Please find all of our FAQ's listed below, if you have any trouble with these please create a new post and we'll be happy to help. Windows OS Enable Legacy Windows Tablet Input Windows Ink option no longer available in Preferences > Tools Welcome screen is missing content and shows Affinity Logo The product key is valid, but there was an error writing the licence file Installer Errors, Setup Failed & Installer Windows UI Issues Which features are supported with the Surface Dial? (Windows) What to do if Affinity is failing to start, crashes on startup or the UI is not displaying correctly (Windows). How can I force Affinity to use my dedicated GPU? (Windows) RAW files appear dark when using a Surface Pro (Windows) I get the error "The data area passed to a system call is too small" when trying to Launch Affinity. Why? (Windows) I get a Blue Screen of Death (BSOD) relating to cldflt.sys when trying to launch Affinity. Why? How to save a copy of Application Logs from Event Viewer? Affinity Installer window not showing (Windows) Will the Affinity Range run on Windows ARM? The software requires a DirectX 10 compatible graphics card in order to run (Windows) Why do I need to enable Windows Aero? Supported Windows Version Not Found Installation failed with error code: (0x00000057), "The parameter is incorrect. " This app can't run on your PC .NET and Affinity apps How do I enable the Windows "No Hardware" Flag? Windows Installation Issues Mac OS Affinity apps and macOS Big Sur Compatibility Affinity apps and Apple Silicon Will the Affinity iPad apps run on macOS Big Sur with Apple Silicon? Why do I get the error "Failed to Open File" or "Failed to Save Document" when using Affinity apps purchased from the Mac App Store? (macOS) Help within Affinity doesn't show any results when searched on macOS Working with Affinity apps through Sidecar Affinity would like to record this computer's screen (Mac OS) Does Affinity support NVIDIA GPUs to use Metal on MacOS? iPad OS Current Apple iPad Store Hardware Compatibility List Supported Raw Cameras on iPad version How to switch seamlessly between Affinity on desktop and iPad How to back up your Affinity documents if you use only an iPad Which iPad models are supported? How do I save my work before reinstalling an Affinity iPadOS app? Licencing & Customer Service How do I receive support for Affinity apps? How do I remove my Licence details? Changing your Affinity Store license from macOS to Windows or vice-versa Bought Affinity Software but cannot log into the Affinity Store Switching software between Microsoft Store and Affinity Store Switching software between Mac App Store and Affinity Store Publisher PDFLib logging How do I add additional Dictionaries to Affinity Publisher? Designer Affinity Designer and Cricut cutting machines Why are strokes expanding after exporting to EPS? I've opened an .EPS file into Affinity but it doesn't look correct, but it looks fine in Adobe Illustrator. Why? Photo List of Supported Raw Cameras (1.8.x) for Desktop & Lens Correction list How to configure plugins in Affinity Photo Workflow of RAW files in Affinity Photo Why can't I import my Macros? General Performance Related Issues Feature Lists and Release Notes Affinity Range Information Can I trial Affinity desktop apps before I buy? Downloading the Latest and Previous versions of Affinity apps? Updates not showing on App Store, Mac App Store and Windows Store I've been asked to provide a screen recording. How do I do this?? Display Colour Management in the Affinity apps How do I download Workbook resources? How do I reset the app back to its default settings? Do you have any downloadable Affinity keyboard shortcut cheat sheets? How do I use the 90 day free trial? How do I install the papers that came with my pack? The app's canvas is not white. What's happening? I've been asked to provide information about my system. How? Can I export or backup my settings? Which Languages are supported in Affinity? Which drawing tablets work with Affinity? Are the Affinity Workbooks available as a PDF or eBook? Are you working on a Digital Asset Management app? What are the recommend system specifications for Affinity apps? Installing creative resources downloaded from the Affinity Store Affinity on Linux? Why are your video tutorials not showing? What exactly do the Clear User Data options clear? CPU or GPU? Where to find Crash Reports File Hash information for latest Affinity apps Third Party (Adobe) File Formats Is it possible to import .AI (Adobe Illustrator) files in Affinity? Is it possible to import .INDD (Adobe InDesign) files into Affinity? How do I enable PSD smart object import support? Can I open and export Adobe files? Does Affinity support Smart Objects in PSD files? Is it possible to export to PSD with editable text? Is it possible to export to .AI (Adobe Illustrator) file format? Fireworks Layered .PNG and Layered .TIFF files Known Issues & Workarounds [FAQ: Problem + Workaround] Stroke width being printed incorrectly on rotated objects (Windows) [FAQ: Problem + Workaround] Crash when scrolling/panning around document [FAQ: By Design] Refining a selection as New Layer with Mask adds distortion [FIXED] Pixel Persona Tool Crash, Undo Limit & File Recovery Interval [FIXED] Scribble shows instead of keyboard when trying to use text tools. [FIXED] iPad apps crashing when accessing Preferences > Fonts on iPadOS 14.
  6. You should've read what I wrote more attentively; it wasn't a typo and I indeed meant SBOD, i.e. Spinning Beachball Of Death, not BSOD (Blue Screen Of Death). I've been a Mac user since 2003, specifically on an iMac G4 which came with Jaguar pre-installed and Panther update CDs (yes, CDs, not a DVD) slipped in the box, and I can distinguish between a KP (Kernel Panic), a BSOD (a Windows-only thing which I also know all too well, having used PCs since 1992) and a SBOD just fine, thank you very much. In all fairness, people also call it by other names and I guess “beachballing” would've been more self-explanatory, but I did think that the “of death” part was more appropriate in this context as Publisher got indeed into a perpetual hang recoverable only by force-quitting it, i.e. the worst kind of “beachballing”. Anyway, back to the issue at hand: for that matter, I hadn't caused Affinity apps to irrecoverably SBOD (i.e. hang) this much – if at all – since I've started trying the first Designer betas, and something tells me that conversion processes such as this should at least trigger a small box with an indeterminate progress bar, IMHO; you see, even the first and last successful attempts were a bit long and made it seem like it hung, even though it didn't straight away. Oh, yes, eventually I did manage to find a workaround: • I created a new document, with facing pages activated and two pages; • I added the remaining pages directly from the original PDF file (it took a bit to process them but it worked); • Finally, I deleted the first two blank pages (maybe it would've worked with a single page, but I didn't want to risk having Publisher stronk out when rearranging the spreads, as that may have been the offending step of the process). Regardless of an upcoming fix, I'd suggest that you add the facing pages option in the PDF import dialog, as this – not specifically with music scores, but with multi-page PDFs in general – should be a very common use case. As a matter of fact, it may be a workable alternative to IDML import for simpler documents (or stuff created with different applications, such as Word, QuarkXPress, etc.), it's something that weirdly not even InDesign can do and that Illustrator is completely horrid at, and also something definitely not worth subscribing to Acrobat DC Pro just to get access to. Affinity Publisher might become an affordable and perpetually licensed de facto alternative for all those basic PDF editing apps for many, many people… Think of the possibilities! As for the score itself, my friend already uploaded the finished video to YouTube, so I'm guessing he won't mind me sharing the relevant files with you for testing, but I'm not assuming anything and will have to check with him first. Stay tuned!
  7. Hi, I've just bought Affinity Photo on the Microsoft store, installed fine but has not started up once correctly. The splash screen loads, then I get a BSOD - every time I've tried to run the application. It's reporting cldflt.sys as having failed. I'm on a Microsoft Surface Pro (5th Gen) Windows 10 Pro Version 10.0.18362 Build 18362 I have designer and it starts and runs fine. I tried running Microsofts DISM Tool and SFC tool as described here: https://support.microsoft.com/en-gb/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system Both completed successfully, Photo still causes BSOD Read it might be linked to OneDrive - Tried exiting OneDrive, still get BSOD This is really dissapointing for a £50 new purchase.
  8. Hello, I've come across an issue in which Publisher seems to be crashing Windows upon trying to save a document. I'm guessing that it's due to some update that Microsoft released over the weekend as everything was fine last week and nothing else that I know of had changed. To reproduce: Open Publisher Create a new document or open an existing document Attempt to save After choosing a location and name and pressing the save button, Windows crashes. The BSOD claims that cldflt.sys failed, giving a stop code of SYSTEM_SERVICE_EXCEPTION. The file does end up getting created, but trying to open it afterwards gives a "file type not supported" error. The bug happened every time I tried to save, regardless of whether the file being saved was already in existence or new. A little poking around on the web suggested that uninstalling cloud services might help, so I tried removing OneDrive and sync services with Google. This did nothing. In the end, the only thing I was able to do to get everything working again was to roll back to a backup from before this weekend's OS updates happened. The provided file is what was produced from one occurrence of the issue. Thanks, Dan. Test.afpub
  9. Just FYI, I rebooted my Windows 10 laptop this morning to finish installing Windows update KB4517389, and after that I experienced several Windows failures, BSOD when using the menus in the Affinity applications. Once in Photo (don't remember what menu I item I clicked) and twice in Publisher using Text > Show Special Characters. The failures pointed to ddflt.sys (or, perhaps, cldflt.sys) After removing that update things are working smoothly again. I understand that it is most likely an error in that Windows Update, and not in the Affinity Applications. I am not finding anything via Google (yet) about errors in that update.
  10. We've had users report that when trying to launch our apps on Windows they're getting a Blue Screen of Death message relating to cldflt.sys. This is also affecting other apps including Microsoft's Visual Studio as reported on the Microsoft Developer Forums. This BSOD error started appearing after Microsoft released the Windows 10 KB4517389 update. Microsoft released a Windows 10 update on 10/12/19 (KB4530684) which includes the below fix. Please download and install this update and try opening the Affinity app again to see if your issue is resolved. Addresses an issue that might cause error 0x3B in cldflt.sys on some devices.
  11. Hi @JGD, We can provide a private upload only link with only staff-access: https://www.dropbox.com/request/FSSDUuceWmTbYLPrMH60 Now back to the issue. Affinity apps cannot cause a BSOD.
  12. Hello Everyone, Ever since I started using Photo I get BSOD's. I first blamed my new laptop (specs below) but now I strongly suspect Photo. I have BSOD's each and every day, sometimes up to multiple a day (imagine...). And whenever I do not have Photo (or Publisher) running I do not get these... I do a lot of video rendering in Powerdirector also, no probs. I always install the latest drivers for both the system (Intel notifies me, then I update) as well as the Geforce drivers (which are recently set to creative, but that did not made a difference). Yesterday I set the default GPU to internal chipset which so far led to no BSOD's... Usually it builds up, the computer starts fanning like crazy, it gets really hot. Then becomes unresponsive, then hangs. Just now I noticed, if I have some images open, with selection marquees, the GPU usage climbs to 80%. I wasn't doing anything actually, took my son to judo. Closing the images returned the system to normal. I still have Photo set to use the internal chipset, not using Geforce. Attached just a few photo's of the latest BSOD's. Laptop specs: 15CL875: 15.6' mat Full HD 144Hz screen met Core i7-8750H, s 16GB DDR4L (3000MHz), Ripjaws 500GB, PCIe NVMe 3.0 x4 SSD, Samsung 970 EVO, 3400MB/s 2300M Intel® Dual Band Wireless-AC 9560 (802.11ac 2.4/5GHz, 1.73Gb
  13. Hi @1.agata, BSOD has been mentioned a few times on the forum. These are normally caused by bad drivers on your system. Affinity applications can’t cause a BSOD directly. You would need to investigate the text that is displayed during the BSOD.
  14. Thanks Fritz. To give an update: Following my last message, I inquired a bit more and checked how the system would behave with the Windows verifier.exe tool activated. This tool stresses the drivers and it appears that each boot of my machine was followed by a BSOD (System thread exception this time). I managed to access the DMP files and they pointed towards a file called hidclass.sys which often relates to input devices. By chance, I found a post on google that suggested that Logitech G-Hub (mouse driver) could be responsible. I uninstalled it and there was no BSOD at startup anymore with verifier.exe activated. Now I am not sure that this was causing the issue in Affinity Photo but it is likely. I have not had BSOD since. Time will confirm. Thanks anyway for your help. Maxime
  15. Thanks for the instructions. I already tried all following steps, did not help. - uninstalled the OneDrive - restart, test, BSOD - installed OneDrive from the Store - restart, test, BSOD - uninstalled OneDrive from the Store - restart, test, BSOD - installed OneDrive for Business, on the Outlook 365 package - restart, test, BSOD My laptop is on a hosted business environment, so I may not have found all possible cloud systems. I'd rather not touch on the Sharepoint... Complete system reinstall would take two days (due to some of the special work related software), so that is not an option. I have already spent too much time on trying to solve this issue, it is smarter to wait for updates that fix the issue or use the expensive alternative that does not break my workflow.
  16. Thanks for your reply. I understand that Affinity Photo can not cause BSOD by itself. However I am still wondering why these BSOD only happened while using this app whereas the system has been rock stable since one year, including when using other photos editors. Regards, Maxime
  17. Hey Max Gr, welcome to the Affinity Forums. Affinity isn't capable of causing a BSOD—however as you pointed out, faulty hardware or more likely, on a new system, a bad driver. I'm not really qualified to suggest what may be causing the crash, however I have seen the IRQL NOT LESS OR EQUAL BSOD before and it was related to audio drivers. Not to sure about the other one I'm afraid.
  18. Hi @Gibsonion, as Walt has already mentioned, user-mode applications are unable to cause BSOD, only kernel-mode software (such as drivers etc) can do that. Crashes in user-mode applications just kill the process that was running (i.e. the Affinity app) whereas crashes in kernel-mode software results in an unrecoverable situation for the operating system (which is why the BSOD is shown). I would suggest looking at display drivers (perhaps uninstalling and reinstalling the latest version). Note: Some anti-virus / anti-malware or even backup programs install drivers that can result in system instability too.
  19. What are the details of the BSOD error? (That is, what did Windows say had failed.n A screenshot (perhaps via your phone) would be useful for that, unless you wrote it down when it happened.) By the way, BSODs are (I understand) caused by driver-mode (or deeper, more privileged) code, not by application code. The Affinity applications have no driver-mode code, according to Serif, and so they cannot directly cause BSOD failures. Given your description, I will take a wild guess that the error was reported against cldflt.sys, which is a driver module for Windows cloud services such as OneDrive. And Microsoft has issued various updates that have caused that problem, and some that have fixed it. When the error occurs, it can affect any application, even potions of Windows itself. If that is the reported error, then the following FAQ may be relevant:
  20. The BSOD isn't caused by Affinity. User-mode applications are unable to cause a BSOD, only bad drivers, or faulty hardware. In your case, it's a driver for a cloud storage provider (e.g. OneDrive, Dropbox, Google Drive, etc). Cldflt.sys is a proxy for your real cloud storage driver, so it can be difficult to know which provider is at fault. Unfortunately you're not the only one affected (and we're not the only app affected) - http://www.google.com/search?q=Cldflt.sys+BSOD We have an FAQ relating to this issue -
  21. Thanks for the tip, Scott! Unfortunately, that did not solve my BSOD. The crashing point has evolved over time, initially I could not get the Designer even running. Now I get the BSOD when saving (with save as...) a file. The Designer store app version has clearly some different code than anywhere else. Many tend to blame Microsoft's updates for the BSOD as other applications have caused BSODs after the update. But who knows... perhaps somewhere exists an open source library that Serif's developers have been using to get the Designer into the MS Store? Other parties may have used that same faulty library causing the problem. Serif's responses on this forum have been just shrugging the problem towards Microsoft. I am still waiting for a permanent solution, either from Serif or Microsoft. I wonder if has anyone with Surface and MS Store app purchase got the Designer up and running?
  22. The latest Windows update KB4524570 changed the symptoms, now the blue screen comes when trying to save or open a file. I have no means to tell who is to blame for the bug, Affinity or Microsoft. At least multiple users having the same setup and path are coming up: Surface, Store, cldflt.sys and OneDrive... My solution is utterly stupid to use even for a temporarily solution. I am an entrepreneur using my Surface to earn my living. Currently the Affinity software is the only one causing BSOD. I have not experienced BSOD in years with my business laptops. So far the best solution is to avoid using Affinity Designer and use other graphics tools instead. As I see it, the 50 eur purchase price has granted me right to complain about the matter. I don't even care to calculate what a single BSOD costs for me in terms of wasted working time.
  23. Thanks for confirming that, I recommend downloading the following software and monitoring your GPU, as if you've tried wiping and reinstalling drivers and are still seeing this issue, it's certainly possible that this is caused by your GPU overheating, or possibly starting to fail. Hardware Monitor will allow you to keep an eye on this whilst you use Affinity and should hopefully point you towards the hardware you need to investigate, https://openhardwaremonitor.org/ If you'd like to try and generate a BSOD or error when the system crashes for further information you can try turning "Automatically restart" ON in System Properties > Startup and Recovery > Settings > System Failure. Please see the below link for more info here - https://www.thewindowsclub.com/disable-automatic-restart-system-failure-windows I hope this helps!
  24. Hey Guys, ran your error search - says folder is empty. As for graphics drivers they are updated to latest version. PC specs are: OS Version: Microsoft Windows 10 Home, 64 bit, Build 18363, Installed 20200417161950.000000+480 Processor: Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz, Intel64 Family 6 Model 158 Stepping 12, CPU Count: 16 Total Physical RAM: 32 GB Graphics Card: NVIDIA GeForce GTX 1050 Ti Hard Drives: C :232 GB (175 GB Free); D : 931 GB (882 GB Free); F: 3726 GB (1877 GB Free); K: 931 GB (918 GB Free); Motherboard: ASRock Z370M Pro4 System: American Megatrends Inc., ver ALASKA - 1072009, s/n To Be Filled By O.E.M. Antivirus: Windows Defender, Enabled and Updated Walt, there is no BSOD, just into reboot sir, no error messages of any description.
  25. An Affinity application cannot cause that, because it runs in user mode. That's a sign of a driver issue of some sort, a Windows flaw, or a hardware error. From your description of what you're doing I would guess it's a graphics driver problem, and updating to a more recent version of the graphics card driver may help. If you get a Blue Screen of Death (BSOD) there will be an error message with important information about what went wrong. Please provide that if you can. Otherwies, the Event Viewer will be able to provide information about what went wrong, which will also be usefu
×
×
  • 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.