Windows 10: 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

:)

 

Lots of BSOD's

PS: after my previous/last replie i had 3 more BSOD's:

seems like there are a lot of random once...

MEMORY_MANAGEMENT win32kbase.sys

MEMORY_MANAGEMENT ntoskrnl.exe

ntoskrnl.exe

 

BSOD APC_INDEX_MISMATCH ntoskrnl.exe+142940

I had a BSOD. Bug Check String APC_INDEX_MISMATCH , cause by driver ntoskrnl.exe caused by address ntoskrnl.exe+142940. Adive on the fix for this. XPS 15 9950 RUNNING Windows 10 Pro.

 

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[/quote] 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[/quote] 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.

 

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[/quote] 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.[/quote]
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

 

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

Thanks
Chris

 

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

 

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

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

 

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

 

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

 

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