VeraCrypt 1.26.29 BSOD "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x7E)"
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- operating-systems, security
Research direction
The report names VeraCrypt 1.26.29, Windows 11 IoT Enterprise 25H2, and a Movespeed 4 TB SSD, but no source files or tests. Start by reproducing the BSOD while opening the encrypted drive and collecting diagnostic details; compare behavior across the affected drive and the other drives mentioned. Done means identifying a reproducible cause and verifying a fix prevents the crash.
Written by the indexing model from the issue text.
Description
I am experiencing a recurring issue when trying to open a fully encrypted drive. It is a 4 TB Movespeed SSD (model YSSDHB-4TN7000).
Until last month, I would turn on the computer and immediately open the drive to start working. This September, however, whenever I do this, the computer triggers a BSOD.
As shown in the following image: https://imgur.com/biJ1qNL
What I don't understand is that I have other drives encrypted in the same way (NVMe SSDs and HDDs), yet this problem seems to occur only with this specific drive. In fact, one of the other NVMe SSDs is also a Movespeed model.
I used the Hiren’s BootCD tool on a USB drive on the same computer and attempted to decrypt it; it worked fine.
It might be due to a Windows update from the last few months. I can't say for sure.
Windows 11 IoT Enterprise 25H2 26200.6550
VeraCrypt 1.26.29
If you need more details, please let me know.
Note: It does happen with the other drives sometimes, but very rarely.
- Dominant language
- C
- Stars
- 11.7k
- Forks
- 1.4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 28
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from veracrypt/VeraCrypt
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug
Difficulty 5/5 Over a week Newbie friendliness 32/100
veracrypt/VeraCrypt#1995 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
veracrypt/VeraCrypt#1993 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
veracrypt/VeraCrypt#1991 · 1 comment ·
Maintainers usually reply within 1 day
All issues in veracrypt/VeraCrypt
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area: recompiler area: runtime kind: bug preview-effort: small priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug game: 01008BA02525A000 ios
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day