Kmode exception not handled. fvevol.sys

Page 8 of 10 FirstFirst ... 678910 LastLast

  1. Posts : 12,726
    Windows 11 Pro
       #71

    Under boot mode you have UEFI. What options are there? Do you have one for MBR or Legacy? If you do, try that.
      My Computer


  2. Posts : 48
    Win10Pro
    Thread Starter
       #72

    essenbe said:
    Under boot mode you have UEFI. What options are there? Do you have one for MBR or Legacy? If you do, try that.
    Only one more option: Legacy
    Can I change that without risk? What is the difference, anyway?

    Thank you
      My Computer


  3. Posts : 11
    Windows 10
       #73

    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 with Win 7 Home without any issues.

    He recently upgraded to Win 10 Home, and since then has had all manner of issues, mostly relating to getting an internet connection. We tried all manner of fixes including getting a new router from his provider, then changing providers. Other laptops and devices were able to get connected.

    Last week my parents made the long trip to visit us and my father bought his pc with them and we did a clean install of Win 10 Home onto a new Samsung EVO 500 Gb SSD. Everything installed just fine, and he had no issues connecting to my network for the whole week they were here.

    However, less than a week after returning home, he has had 3 BSOD's in a day with the above error, and can no longer connect to the internet (yellow warning triangle - no io nternet access). We have a reasonable working knowledge of Windows, but this network issue has us both pulling our hair out.

    I have had my father make a debug log as per the sticky BSOD Posting Insructions, which I have attached. Hopefully somebody with more experience than us can get something out of it for us!
      My Computer


  4. Posts : 14,894
    Windows 10 Pro
       #74

    Camberwell said:
    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 with Win 7 Home without any issues.

    He recently upgraded to Win 10 Home, and since then has had all manner of issues, mostly relating to getting an internet connection. We tried all manner of fixes including getting a new router from his provider, then changing providers. Other laptops and devices were able to get connected.

    Last week my parents made the long trip to visit us and my father bought his pc with them and we did a clean install of Win 10 Home onto a new Samsung EVO 500 Gb SSD. Everything installed just fine, and he had no issues connecting to my network for the whole week they were here.

    However, less than a week after returning home, he has had 3 BSOD's in a day with the above error, and can no longer connect to the internet (yellow warning triangle - no io nternet access). We have a reasonable working knowledge of Windows, but this network issue has us both pulling our hair out.

    I have had my father make a debug log as per the sticky BSOD Posting Insructions, which I have attached. Hopefully somebody with more experience than us can get something out of it for us!
    Please create a new thread for your problem, this makes it easier for us to help you.
      My Computers


  5. Posts : 12,726
    Windows 11 Pro
       #75

    Ron99 said:
    Only one more option: Legacy
    Can I change that without risk? What is the difference, anyway?

    Thank you
    I don't really think there is a risk. The only thing that could happen is you may have trouble booting into your OS, but I don't think so. You can change it back when you finish running memtest86+. It's difficult to tell. All the OEM Manufacturers lock down their BIOS's so much, you have limited options. You have many more options on a Retail Motherboard. When you are in UEFI mode, Windows will only boot from a Windows Boot Manager partition. Changing it should make your USB drive with Memtest86+ show up as a boot option. If your OS won't boot with those options, you should be able to just change it back to UEFI mode. Try these instructions

    Please Run Memtest86+

    information   Information
    Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip
    Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask
      My Computer


  6. Posts : 11
    Windows 10
       #76

    axe0 said:
    Please create a new thread for your problem, this makes it easier for us to help you.
    Sorry, we were having multiple BSOD's with kmode exception not handled, and in the BSOD Posting Instructions sticky it says:

    NOTE: Please do not create duplicate threads and posts on the same issue.

    Should I still make a new thread?
      My Computer


  7. Posts : 14,894
    Windows 10 Pro
       #77

    I bet a lot of people are getting multiple BSOD's with kmode exception not handled, but the core issue is different.
      My Computers


  8. Posts : 11
    Windows 10
       #78

    axe0 said:
    I bet a lot of people are getting multiple BSOD's with kmode exception not handled, but the core issue is different.
    OK no problem, I will make a new thread. Thanks!
      My Computer


  9. Posts : 48
    Win10Pro
    Thread Starter
       #79

    QUOTE
    I don't really think there is a risk. The only thing that could happen is you may have trouble booting into your OS, but I don't think so. You can change it back when you finish running memtest86+. It's difficult to tell.
    UNQUOTE

    Ok. will try this weekend. In case I have some trouble that is when I don't bother too much not having the pc.

    Thank you.


    BTW: I have been free of bsod for 48h now!!??
    Perhaps, after having uninstalled most old (2012, 2013) software.??
    Will see....
      My Computer


  10. Posts : 12,726
    Windows 11 Pro
       #80

    By 'having trouble', if you mean your computer won't boot into your OS, then change that bios setting back and you should be fine.

    Great news about being BSOD free. Whatever you and @axe0 decide is fine with me. I would think you may want to wait a few days to see if your problem is resolved.
      My Computer


 

  Related Discussions
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 16:16.
Find Us




Windows 10 Forums