stringy Posted February 26 Posted February 26 (edited) I have a new desktop and I have loaded affinity 2.6 on it but every time I try to export an affinity file it locks up the computer, sometimes it blue screens and shuts down other times it just freezes needing a reboot. The new desktop far exceeds the spec of the old one, Windows 11, 32gb ram, 1tb hard drive, i7 processor, Nvidia GeForce gtx 1070 graphics card I had the same issue whether the graphics card acceleration was on or off in setting I uninstalled 2.6 and installed 2.5 and the issue seems to be resolved. I have tried exactly the same on my old desktop running 2.6 without any issues, this is lower spec but on windows 10. So to me it seems to be an issue with 2.6 running windows 11 but surely others are running this setup without issues? Edited February 27 by stringy wrong photo attached Quote
Ron P. Posted February 27 Posted February 27 Welcome to the forums @stringy, I provided a link that explains what you're experiencing, and how to go about correcting it. Your screenshot shows your PC is having a problem accessing your boot drive, the drive it uses to boot from. https://www.tomshardware.com/how-to/fix-inaccessible-boot-device-bsod Quote Affinity Photo 2.6..; Affinity Designer 2.6..; Affinity Publisher 2.6..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win11 Home Version:24H2, Build: 26100.1742: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD; Wacom Intuos 3 PTZ-431W
stringy Posted February 27 Author Posted February 27 6 hours ago, Ron P. said: Welcome to the forums @stringy, I provided a link that explains what you're experiencing, and how to go about correcting it. Your screenshot shows your PC is having a problem accessing your boot drive, the drive it uses to boot from. https://www.tomshardware.com/how-to/fix-inaccessible-boot-device-bsod Hi Ron Thank you for the reply. I noticed that I an inadvertently put the incorrect image of error message on my original, this has now been corrected. Sorry for the confusion The boot device error image that I put on did occur once and I took the photo but them seems to have fixed itself and reading your boot device article it says that it can get corrected. The blue screen that seems to occur is the irql stop code error. Now maybe there is still some connection to the boot error I am not sure. I have though found that the error does not occur at all when I revert back to version 2.5 from 2.6 on my new Windows 11 pc but on on old windows 10 desktop v2.6 has no problems? But there must be thousands of users on win11 running 2.6 without issues? Quote
Ron P. Posted February 27 Posted February 27 That error code is a system kernel fail. According to Serif, their Affinity apps are User level, not system, and can not cause a system crash, a BSOD crash. However it can be pushing some element of your PC to the point where if it is weak, that element will in turn cause the crash. Here's a link to explain the ntoskrl BSOD crash. https://helpdeskgeek.com/why-ntoskrnl-exe-causes-high-cpu-and-how-to-fix-it/ Quote Affinity Photo 2.6..; Affinity Designer 2.6..; Affinity Publisher 2.6..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win11 Home Version:24H2, Build: 26100.1742: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD; Wacom Intuos 3 PTZ-431W
Staff Callum Posted March 5 Staff Posted March 5 Hi @stringy Is this something you are still having issues with at all? Thanks C Quote Please tag me using @ in your reply so I can be sure to respond ASAP.
stringy Posted March 5 Author Posted March 5 I had a very similar problem after upgrading to 2.60 but if I uninstalled and went back to 2.5x then it was ok. Unfortunately all the reboots eventually gave me a booting problem on my pc so it had gone back to be repaired. Another user tried my images and they exported correctly so it may have not been this exact issue. I am hoping the fix will be live by the time I get the desktop back so I can try it. Quote
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.