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

  1.    29 Oct 2015 #1

    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.
    Last edited by Marcus Agrippa; 20 Nov 2015 at 17:17.
      My ComputerSystem Spec


  2. Posts : 12,055
    Windows 10 Pro
       30 Oct 2015 #2

    Hi Marcus Agrippa,

    Welcome to the 10forums.

    Note   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.



    BitLocker Kmode exception not handled. fvevol.sys Diagnostics Test BitLocker Kmode exception not handled. fvevol.sys
     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   Note
    Do not run SeaTools on an SSD as the results will be invalid.


    Run chkdsk Disk Check - Windows 7 Help Forums




    BitLocker Kmode exception not handled. fvevol.sys Diagnostic Test BitLocker Kmode exception not handled. fvevol.sys
     RAM TEST

    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   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.





    BitLocker Kmode exception not handled. fvevol.sys Diagnostics Test BitLocker Kmode exception not handled. fvevol.sys
     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.
      My ComputersSystem Spec

  3.    31 Oct 2015 #3

    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
      My ComputerSystem Spec


  4. Posts : 12,055
    Windows 10 Pro
       31 Oct 2015 #4

    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.
    Last edited by axe0; 31 Oct 2015 at 08:43.
      My ComputersSystem Spec


 

Related Threads
Kmode exception not handled. fvevol.sys in BSOD Crashes and Debugging
Hi, Thank you for looking at my problema! I migrated to W10pro about a week ago and I must say all went perfectly smooth and well! Nothing special until this morning. Using Bitlocker on both partitions, startup and data. I started up...
Hi all, I was advised to make my own thread for this issue, so here goes: My father is also having BSOD's with this same error message KMODE exception not handled. I built him a pc a few years back based on an Asrock Z77 Pro4-M, and it has run...
I updated to Windows 10 last week from 8.1 on my Samsung laptop. The update went fine but the restart left me with the message "System THread Exception Not Handled". The only way to get my computer to reboot was to restore it to the original 8.1...
Upgraded to Win 10 from 8.1 recently and it was working fine. This morning when I tried to boot it won't. Stays stuck in a 'your PC ran into a problem' loop and shows a 'system thread exception not handled' error. I hadn't got a chance to create...
BSOD, System Thread exception not handled in BSOD Crashes and Debugging
Hey, tried several times to upgrade from Win7 64bit to Win 10. After upgrade i mostly could login and then get BSOD sometimes after a few seconds, other times i could use edge and chrome for several minutes. The weird thing was that starting task...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 09:49.
Find Us