Windows 10: Bsod: Interrupt_exception_not_handled

I've been having this BSOD lately. It first started when I initially upgraded to Windows 10, but stopped after a while. Now it's back after I wiped my SSD and reinstalled 10. If I could get some help fixing this I would be very happy if there is any more info that is needed I'll get it for you.

EDIT: I'm able to log in to my computer. The BSODs occur about 10-20 minutes after log in. Also, this is my hardware:

Motherboard: Asus Rampage Formula III
CPU: i7-950, 3.2 Ghz
Graphics: 2x EVGA GeForce GTX 660
HDD: Kingston HyperX SSD, 120GB


Attachment 61486

:)

 

BSOD dxgmms2.sys

Hey, I updated my gpu driver, but now I got a different BSOD error "INTERRUPT_EXCEPTION_NOT_HANDLED" This is the link for the minidump file: https://onedrive.live.com/redir?resid=4EBA5745EEA85D01!823&authkey=!AGKy1AlXZrrKzFY&ithint=file,zip

 

interrupt_exception_not_handled windows 10 BSOD

David your in the same boat as I am they are trying to blame it on the hardware and not the software. I have the exact same crash and have been all over the net and still got no answers..

 

Most of the crashes are caused by the Marvell Sata controller drivers, unfortunately there aren't Windows 10 compatible updates for your motherboard.
The best you can try is to install the most recent updates and see if that helps, else you have to revert back to a previous Windows.
Code: *** WARNING: Unable to verify timestamp for mv91xx.sys *** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys 0: kd> lmvm mv91xx start end module name fffff800`ff950000 fffff800`ff9dc000 mv91xx T (no symbols) Loaded symbol image file: mv91xx.sys Image path: \SystemRoot\System32\drivers\mv91xx.sys Image name: mv91xx.sys Timestamp: Fri Dec 25 07:45:39 2009 (4B345F93) CheckSum: 0004E351 ImageSize: 0008C000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Thank you for your reply. I attempted to update the driver to see if that would work, but I guess the driver was already current. I decided to downgrade back to 7.

Bummer. I was really starting to like 10. Maybe when I upgrade some of my hardware I might go back to 10.

Thank you for your help!