![]() ![]() Please tell us more about your environmentÄell Vostro 230, 8GB RAM, Intel(R) Core(TM)2 Quad CPU Q9500 2.83GHz 2. Only information on BSOD was single line of text that read: "IRQ NOT LESS OR EQUAL" Your Environment Delete Symantec software to restore normalcy.Reboot repeatedly until able to attempt 5 again.In the modern world, automation is being introduced into every facet of. After boot launch Veracrypt and attempt to mount volume of step 3 above, results in BSOD The product marketing team has created new overview video for Symantec Encryption.Install Symantec Desktop V 10.5.1 (forces reboot).AES256 (primary key), XTS mode, HMAC-SHA-512 Recovery is to persist with attempting reboots until successful (may take as many as 8 attempts at to power-on reboot.) Steps to reproduce Once the BSOD happens, successive attempts to boot the WinPC result in PC power cycling repeatedly. The file volume being mounted is AES256 (primary key), XTS mode, HMAC-SHA-512. The boot volume is also not encrypted by Symantec nor Veracrypt. ![]() Symantec disk encryption is installed but not used (i.e., there are no PGM encrypted volumes mounted nor attempting to mount. 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. 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. 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. ![]()
0 Comments
Leave a Reply. |