Windows 10: BitLocker Kmode exception not handled. fvevol.sys

Hi I have been trying to find a solution to this problem and have gotten nowhere on the windows community. I'm hoping someone here might have some kind of solution. I get this BSOD while unlocking storage drives. My OS is on a Vertex 4 SSD My storage drives are on HDD. I would say I have 50% chance of a BSOD unlocking drives.

:)

 

BitLocker Kmode exception not handled. fvevol.sys (Still unresolved)

Actually the event viewer logs were more informative than the full memory DMP.

1-Many, many, many disk errors. I suspect this is why bitlocker crashes the system

2-You never specified that you have a RAID.

3-What is actually happening is that bitlocker is requesting the unlock but the HD is either taking to long or erroring out hence the crash.

4-You have a storahci driver error.

5-Readyboot (prefetech) is erroring out

Session "ReadyBoot" stopped due to the following error: 0xC0000188

I would run CHKDSK, and go to the HD maker find, download, and run their disk checking utility and disable readyboot

 

BitLocker Kmode exception not handled. fvevol.sys (Still unresolved)

All files uploaded

 

Hi Marcus Agrippa,

Welcome to the 10forums.



Note Before we proceed in troubleshooting, I strongly recommend to create multiple backups of your data as some of the suggestions may cause data loss with Bitlocker.

Are all your storage devices used by Bitlocker?

As it is a 0x1E(KMODE_EXCEPTION_NOT_HANDLED) with Bitlocker, in this thread pretty much the same problem occurs and the activity in the dumps are leading to the system itself there are a few possibilities:

• hardware (hard drive),
• compatibility (issue in Windows),
• memory.

Please follow instructions below.
With SSD, only run chkdsk.
With HDD and SeaTools in windows, run SMART, short generic and long generic tests.





Diagnostics Test

HDD & SSD TEST


Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums



Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk Disk Check - Windows 7 Help Forums






Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.






Diagnostics Test

System File Check
Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

 

Hello axe0. Thanks for taking the time to help.My storage drives are locked by bit locker. Currently my OS drive is not encrypted.Yes that thread is what brought me here,but i don't believe I have Intel rapid storage. So i ran all of these tests. My 3 day old WD drive failed with bad sectors,but it couldn't be the problem because this began in January when I downloaded windows 10 preview. All other drives passed all tests After switching to IDE I ran memtest all night. 7 passes with 0 errors.I have been running the same setup since windows 8 release and never had a BSOD unlocking a drive until windows 10

 

It looks like you are having the same problem.
What this means: there is a bug with Bitlocker, when you unlock your drives a kernel-mode exception occurs which cannot be handled.
It is just like you get a request which you cannot perform for whatever reason, usually is this because you're not expecting it.
I am not sure where it goes wrong, but the action of Bitlocker is not expected by whatever needs to handle it.

EDIT: why this is happening only at 50% of the times I don't know, there are many variables involved with this.