Search the Community

Hi Rudolphus, According to development (see here) it is not actually possible for Affinity to cause a BSoD, it will only be a driver or hardware error as narrationsd has suggested above. I would be interested if you could reproduce the sluggishness you were getting however - if so please try and get a video! Thanks

It would also help to know what was happening when the system crashed, whether the BSOD advice was followed, and what happened if it was.

After a BSOD-crash of my computer, i can't close "Photo" normaly. Only the hard way with the taskmanager. "Photo" was opening a file at the time of the crash. Now every time i try to close the programm, i get the message that a file is currently loading and the progrann can't close because of that. Any Idea to fix this?

He's just venting, I think if he'd come to this forum before he got so wound up things could have been different. I'm guessing he's a Windows user on a average spec system. Adobe have a 30 year head start on Affinity so I think Adobe should have got it right by now, having said that looking at the adobe forums would suggest adobe is anything but stable lol! I've used Adobe products for more years than I care to remember and there have been many crashes, incompatibilities, even BSOD when I was a Windows user. Aah! the memories, playing Ghost Recon "if you can see me you're already dead" or SplinterCell 'sneaky sneaky' Sat there with Bandana on and camo'ed up and thinking Rambo thoughts hahaha! Maybe when he's calmed down we could help him, if he wants that help. I think he needs a hug so I'm sending him a hug there you go vexed man lol!

Well if any computer does not work due to a hardware failure you will need a technician to fix it as your ex wife did. If you can not access it due to hardware failure you would need to either have spare parts to replace them. Linux is a operating system as is mac os or windows. If you want to troubleshoot it yourself and have the technical experience then yes you will need to have a second machine to have the other running. As for your network card experienced my self a issue that windows updates just made my pc malfunction. On Linux everything was working fine. Dell has machines that come with Linux Installed out of the box as has the Dell XPS 13 Developer Edition . As for the warranty Usually computers that are targeted for business come with a on site repair. It is usually marketed that way and not all computers have that warranty. Ok the back up part made me laugh. I'm pretty sure you have no idea how Linux works on this point. Not only do you have graphical backups and strong terminal backup solutions that can take a backup from your hard drive bit by bit. You can reinstall the operating system while keeping your home directory intact. Which in other words means even if you screw up badly you can restore the operating system while keeping your files intact. Hardware issues are dealt with the same way as every other computer out there. Blue screens usually are a sign that your ram in failing and Linux gives you the option to run memtest upon boot in the grub menu. But in windows Viruses or "malfunctioning" software can also cause BSOD. P.S. Please respect my initial statement on not quoting me.

BSOD are caused by kernel level faults, which can only happen via drivers (user mode, i.e. application level, errors result in the applications crashing), so I suspect there is a bug in that driver, or firmware.

Error using NVIDIA GeForce 745M GPU with Driver version 381.65 note that this error doesnt happen if I use the integrated GPU which is an Intel HD4600. Only happens using Gunny Rewritten Font (Jan 14, 2014) at 72 pt, also seemed to cause the display driver nvlddmkm.sys to stop responding. (NVIDIA Kernel Mode Driver 22.21.13.8165) Faulting application name: Photo.exe, version: 1.5.2.63, time stamp: 0x58de6274 Faulting module name: ucrtbase.dll, version: 10.0.15063.0, time stamp: 0xaf2e320b Exception code: 0xc0000409 Fault offset: 0x00000000000734be Faulting process id: 0x3160 Faulting application start time: 0x01d2b7215d05039f Faulting application path: C:\Program Files\Affinity\Affinity Photo Customer Beta\Photo.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Eventually can cause a BSOD with VIDEO_SCHEDULER_INTERNAL_ERROR if repeated often enough. Repaired the NVIDIA drivers by doing a clean install and first-time start-up of Affinity Photo Beta caused the same crash but after that first-time crash it starts OK: Faulting application name: Photo.exe, version: 1.5.2.63, time stamp: 0x58de6274 Faulting module name: ucrtbase.dll, version: 10.0.15063.0, time stamp: 0xaf2e320b Exception code: 0xc0000409 Fault offset: 0x00000000000734be Faulting process id: 0xf6c Faulting application start time: 0x01d2b7282005adfb Faulting application path: C:\Program Files\Affinity\Affinity Photo Customer Beta\Photo.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Attached the WER report and a DMP file. The dump (DMP) can be downloaded from https://www.dropbox.com/s/pex5d9qa5fggi5j/APB%20Photo.exe.5752.dmp?dl=0 Note my system specs are: Win 10 x64 System with Intuos Pen & Touch * Sys :Intel i7-4700MQ @2.40Ghz x 4 core/8 thread, 16GB RAM * GPU 1: Intel HD4600, 1GB, OpenGL v4.3, OpenCL v1.2 * GPU 2: NVIDIA GT 745M, 4GB, OpenGL v4.5, OpenCL v1.2 APB BEX64.wer.txt