VeraCrypt icon indicating copy to clipboard operation
VeraCrypt copied to clipboard
verified publisher icon veracrypt

Veracrypt 1.25.9 BSOD With Symantec Desktop Encryption 10.5.1

Open jbarrieb opened this issue 3 years ago • 1 comments

Veracrypt 1.25.9 BSOD when run on same Win10 Pro machine as Symantec Desktop Symantec 10.5.1 when attempting to mount previously encrypted file-based volumes.

Expected behavior

Veracrypt 1.25.9 (64-bit on Win10Pro 21H2) runs happily when installed with earlier versions of Symantec Desktop (e.g., 10.3.1) Upgrade to Symantec 10.5.1 causes Veracrypt to BSOD.

Observed behavior

Veracrypt 1.25.9 (64-bit on Win10Pro 21H2) BSODs when runs against Symantec Desktop 10.5.1 when attempting to mount previously encrypted file-based volumes. Symantec disk encryption is installed but not used (i.e., there are no PGM encrypted volumes mounted nor attempting to mount. The boot volume is also not encrypted by Symantec nor Veracrypt. The file volume being mounted is AES256 (primary key), XTS mode, HMAC-SHA-512. Once the BSOD happens, successive attempts to boot the WinPC result in PC power cycling repeatedly. Recovery is to persist with attempting reboots until successful (may take as many as 8 attempts at to power-on reboot.)

Steps to reproduce

  1. Install Symantec Desktop V 10.3.1
  2. Install VeraCrypt 1.25.9 64 bit
  3. Create encrypted volume w. AES256 (primary key), XTS mode, HMAC-SHA-512
  4. Install Symantec Desktop V 10.5.1 (forces reboot)
  5. After boot launch Veracrypt and attempt to mount volume of step 3 above, results in BSOD
  6. Reboot repeatedly until able to attempt 5 again.
  7. Delete Symantec software to restore normalcy

Screenshots

Only information on BSOD was single line of text that read: "IRQ NOT LESS OR EQUAL"

Your Environment

Please tell us more about your environment

VeraCrypt version: 1.25.9 64 bit Operating system and version: Win10Pro 64 bit 21H2 Build 19044.1586 System type: Dell Vostro 230, 8GB RAM, Intel(R) Core(TM)2 Quad CPU Q9500 @ 2.83GHz 2.83 GHz 64-bit operating system, x64-based processor

jbarrieb avatar May 19 '22 14:05 jbarrieb

Shouldn't this be filed with Symantec rather than Veracrypt?

Your solution to remove Symantec seems like the reasonable thing to do.

peteh avatar Aug 20 '22 11:08 peteh

I use Symantec Encryption Desktop 10.5.0 and I also have a BSOD when launching veracrypt 1.25.9. The BSOS also appears with Veracrypt 1.21.

bernouilli avatar Dec 05 '22 12:12 bernouilli