Windows 10: BSOD - NTOSKRNL.exe

  1.    10 Dec 2015 #1

    BSOD - NTOSKRNL.exe


    Attachment 53020

    Hi all I've been getting BSOD since playing Fallout 4. Initially I saw it was Nvidia related so I update my graphics and it seems to have cured that one, however now I've been getting a different error. I ran a memtest and all seemed good, I think it may be one of my drives. I'm guessing the steam SSD fallout is on. I downloaded a corsair toolbox to test the drive however when I opened it it BSOD'd again. I'm currently backing up my drives. Can anyone read by dumps and see where the issue is? I would have thought a problem with my drive would have triggered a SMART failure.

    Thanks,
    Chris
      My ComputerSystem Spec


  2. Posts : 8,183
    Windows 10 Enterprise and Pro/Windows 7 Enterprise/Linux Mint
       11 Dec 2015 #2

    Hello Chrisred and welcome to the forums. I will show you what I found

    Code:
    Use !analyze -v to get detailed debugging information.
    BugCheck 3D, {fffff803cc1ffbd8, fffff803cc1ff3f0, 0, 0}
    *** WARNING: Unable to verify timestamp for mv91xx.sys
    *** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
    Probably caused by : mv91xx.sys ( mv91xx+32276 )
    Followup:     MachineOwner
    That is your Marvell Raid/AHCI driver. This is your current driver

    Code:
     mv91xx
    Browse full module list
    start             end                 module name
    fffff800`f8540000 fffff800`f85cc000   mv91xx   T (no symbols)           
        Loaded symbol image file: mv91xx.sys
        Image path: \SystemRoot\System32\drivers\mv91xx.sys
        Image name: mv91xx.sys
        Browse all global symbols  functions  data
        Timestamp:        Fri Dec 25 00:45:39 2009 (4B345F93)
        CheckSum:         0004E351
        ImageSize:        0008C000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e
    As you can tell the driver needs updating. In 2009, Windows 10 was not even on the radar. When you installed Windows 10 did you update the drivers from your Motherboard web site or did you let Windows install the driver? You have an older chipset and I would suspect that your motherboard drivers do not include Windows 10 drivers.

    Also, please check and make sure your SSD is not connected to a Marvell port. I realize your motherboard does not have native sata 3 ports, but has the Marvell add on ports. But, I would suspect you will get about the same performance from a native sata 2 port that you are getting from a Marvell sata 3 port. Also, Marvell has a history of not liking to 'play nice' with SSDs.

    Please see if you can update that driver and swap your SSD from the Marvell port to an Intel port (usually ports 0-3) and see if you get any improvements with your BSOD problem. I would suggest you connecting the SSD to port 0 or 1, whichever is the first Intel controlled sata port. After making the switch you may need to go into BIOS and set your boot order again. Sometimes switching ports and controllers will cause BIOS to not find your boot drive.

    You may also want to check your Corsair Link drivers and make sure you have Windows 10 compatible drivers for that. It was pointed out in one of the dumps, but it could have been from the problems with the SSD/Controller causing it. It wouldn't hurt just to be sure.

    Please let me know how this works.
      My ComputersSystem Spec

  3.    11 Dec 2015 #3

    essenbe said: View Post
    Hello Chrisred and welcome to the forums. I will show you what I found

    Code:
    Use !analyze -v to get detailed debugging information.
    BugCheck 3D, {fffff803cc1ffbd8, fffff803cc1ff3f0, 0, 0}
    *** WARNING: Unable to verify timestamp for mv91xx.sys
    *** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
    Probably caused by : mv91xx.sys ( mv91xx+32276 )
    Followup:     MachineOwner
    That is your Marvell Raid/AHCI driver. This is your current driver

    Code:
     mv91xx
    Browse full module list
    start             end                 module name
    fffff800`f8540000 fffff800`f85cc000   mv91xx   T (no symbols)           
        Loaded symbol image file: mv91xx.sys
        Image path: \SystemRoot\System32\drivers\mv91xx.sys
        Image name: mv91xx.sys
        Browse all global symbols  functions  data
        Timestamp:        Fri Dec 25 00:45:39 2009 (4B345F93)
        CheckSum:         0004E351
        ImageSize:        0008C000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e
    As you can tell the driver needs updating. In 2009, Windows 10 was not even on the radar. When you installed Windows 10 did you update the drivers from your Motherboard web site or did you let Windows install the driver? You have an older chipset and I would suspect that your motherboard drivers do not include Windows 10 drivers.

    Also, please check and make sure your SSD is not connected to a Marvell port. I realize your motherboard does not have native sata 3 ports, but has the Marvell add on ports. But, I would suspect you will get about the same performance from a native sata 2 port that you are getting from a Marvell sata 3 port. Also, Marvell has a history of not liking to 'play nice' with SSDs.

    Please see if you can update that driver and swap your SSD from the Marvell port to an Intel port (usually ports 0-3) and see if you get any improvements with your BSOD problem. I would suggest you connecting the SSD to port 0 or 1, whichever is the first Intel controlled sata port. After making the switch you may need to go into BIOS and set your boot order again. Sometimes switching ports and controllers will cause BIOS to not find your boot drive.

    You may also want to check your Corsair Link drivers and make sure you have Windows 10 compatible drivers for that. It was pointed out in one of the dumps, but it could have been from the problems with the SSD/Controller causing it. It wouldn't hurt just to be sure.

    Please let me know how this works.

    Thank you very much for this. I did actually start looking in this direction, after searching for causes of Blue Screening in relation to the Corsair SSD toolbox, I briefly searched for the drivers but there was nothing I found, I'll have a better look.

    It's strange though I have had this setup for for years and I installed windows 10 on release, it's only since Fallout 4 that it appears to have caused blue screens.

    I was planning on Upgrading to skylake after the first price drop anyway.

    I'll see if i can get better drivers, failing that I'll disable the Marvel controller.

    Thanks again.

    Chris
      My ComputerSystem Spec

  4.    11 Dec 2015 #4

    Update:- Found some by looking at other x58 boards, I'll let you know how it goes. Updated Corsair link too.

    Thanks
    Chris
      My ComputerSystem Spec


  5. Posts : 8,183
    Windows 10 Enterprise and Pro/Windows 7 Enterprise/Linux Mint
       11 Dec 2015 #5

    Be sure and create a restore point before installing them. Also look for a firmware update for your Corsair SSD.
    https://www.tenforums.com/tutorials/4...dows-10-a.html and make sure system protection is turned on for your 'C' drive. https://www.tenforums.com/tutorials/4...dows-10-a.html
      My ComputersSystem Spec

  6.    11 Dec 2015 #6

    I have scheduled Image backups to my home server so I should be OK.

    I have updated Corsair Link, and Marvel Drivers, annoyingly they were not listed on the Asus website, however I found some on the Gigabyte website that seem to have worked. After restarting I can now open the SSD tool kit. I checked the Drives firmware, my M4 (Steam Drive) is up to date, the M550 (Windows Drive) is a version behind. I'm at work at the moment and doing this all remotely so I cannot update the firmware from here.

    I'll update tonight and if I can have an evening of Fallout 4 with no issue, I'd think it resolved if I can.

    Thanks again,

    Chris
      My ComputerSystem Spec


  7. Posts : 8,183
    Windows 10 Enterprise and Pro/Windows 7 Enterprise/Linux Mint
       11 Dec 2015 #7

    Sounds good so far. Just let me know and we'll see from there. Thanks for keeping me posted. Good luck.
      My ComputersSystem Spec

  8.    13 Dec 2015 #8

    I can't reply to your PM, but thought I'd let you know this fix sorted it, everything has been stable since. Many thanks

    Chris
      My ComputerSystem Spec


  9. Posts : 8,183
    Windows 10 Enterprise and Pro/Windows 7 Enterprise/Linux Mint
       14 Dec 2015 #9

    Great, I'm glad you have it running right again. If you have any other problems, please let us know.
      My ComputersSystem Spec


 

Related Threads
Random BSOD ntoskrnl.exe in BSOD Crashes and Debugging
Hi. I revamped an old X58 build some months ago. It was an inherited computer with several problems. I have been changing most of it (CPU, MOBO, RAM, HDD) but random BSODs keep happening. I'm running a fresh install of Windows 10 Home x64,...
BSOD because of ntoskrnl.exe in BSOD Crashes and Debugging
Hello guys, I had trouble with my windows 7 : bosd because of ntoskrnl.exe so i decided to do a clean install windows 10 for a new fresh start. But the bsod is still here so i think its probably Hardware problems but wich one ? I've only...
BSOD ntoskrnl.exe fix? in BSOD Crashes and Debugging
Computer has been crashing a ton recently and I am looking for a fix, please respond if you know any anything.
Ntoskrnl.exe Bsod in BSOD Crashes and Debugging
Hello, i have costume build pc for a years now , i think last year i had to change cooler and its probably when my problems started , or could be later im not sure , basicly now everyday when i first start up pc its getting freezed , if i restart...
Solved BSOD in ntoskrnl.exe in BSOD Crashes and Debugging
This is the most recent BSOD. I have no idea on what is causing the problem. I dont know if it's a chipset driver, graphics card issue, sound card issue, or an on the mainboard component that is causing the issue. This morning I was rendering a...
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 18:43.
Find Us