After the update a few weeks ago I began getting BSOD's in Windows 10. At first the issues were happening with an Exception in my video drivers. They got corrected by Intel but the BSOD's (while different) continued. Intel said they corrected the issues so my next step was to Google Win 10 BSODs. It turns out that Avast! was generating them but my version had been corrected. The BSOsS have stopped but it was after decrypting the hard drive completely. It appears that the exceptions (ATTEMPTED WRITE TO READ ONLY MEMORY) were happening at the time that the "screen saver" window was going to be thrown up. If you want I can include a memory dump or a minidump of the BSOD happening. But it truely appears that Veracrypt is the cause of the exception. I was running 1.18.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
HIi Michael. I realise this is an old post. I was wondering if you woudl be so kind to look at the post i made on my problem to see if the issue you found could be the cause of my problem. I do not know to find let alone resolve the issue you state. https://sourceforge.net/p/veracrypt/discussion/general/thread/2475529dad/
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After the update a few weeks ago I began getting BSOD's in Windows 10. At first the issues were happening with an Exception in my video drivers. They got corrected by Intel but the BSOD's (while different) continued. Intel said they corrected the issues so my next step was to Google Win 10 BSODs. It turns out that Avast! was generating them but my version had been corrected. The BSOsS have stopped but it was after decrypting the hard drive completely. It appears that the exceptions (ATTEMPTED WRITE TO READ ONLY MEMORY) were happening at the time that the "screen saver" window was going to be thrown up. If you want I can include a memory dump or a minidump of the BSOD happening. But it truely appears that Veracrypt is the cause of the exception. I was running 1.18.
HIi Michael. I realise this is an old post. I was wondering if you woudl be so kind to look at the post i made on my problem to see if the issue you found could be the cause of my problem. I do not know to find let alone resolve the issue you state. https://sourceforge.net/p/veracrypt/discussion/general/thread/2475529dad/