Page 1 of 1

Windows blue screen on exit when project is stored on an encrypted partition

Posted: Sun Nov 29, 2020 2:31 am
by Jacek
Hi!
Dear Scrivener Team, did you change the way Scrivener treats encrypted partitions in the last Beta? I have my project on the encrypted partition and till now there was no problem with that. But after installing the last Beta everytime I close my project Windows blue screen is showed with this code:
PAGE_FAULT_IN_NONPAGED_AREA
When I open my project from a non-encrypted partition, everything is OK, so it looks like enryption is the problem here. But it wasn't in earlier Betas... :(
Is it possible to do something with that?
Regards!

Re: Windows blue screen on exit when project is stored on an encrypted partition

Posted: Sun Nov 29, 2020 5:44 am
by devinganger
Jacek wrote:I have my project on the encrypted partition and till now there was no problem with that. But after installing the last Beta everytime I close my project Windows blue screen is showed with this code:
PAGE_FAULT_IN_NONPAGED_AREA
When I open my project from a non-encrypted partition, everything is OK, so it looks like enryption is the problem here. But it wasn't in earlier Betas... :(


Applications like Scrivener aren't supposed to even know whether the partition is encrypted or not -- the encryption happens below the file system layer.

What kind of encryption are you using? Native Bitlocker, or some other third-party system?

If it's Bitlocker, something may be out-of-whack. One of the things I have done in the past is decrypt the partition in question, reboot, then re-encrypt it from scratch. It takes a little while and forces updates of the recovery keys, but usually helps sort out if there are issues.

Otherwise, I'd be looking to see if you had any relevant Windows or driver updates that happened right around the same time you updated Scrivener.

Re: Windows blue screen on exit when project is stored on an encrypted partition

Posted: Fri Jan 15, 2021 11:12 pm
by Jacek
Thank you very much for your answer and excuse me my delayed response :) My problem disappeared with the next (quite quick ;) ) beta.