Windows 10: Multiple crashes with multiple error codes & modules

DM Log from Verifier BSODs -


Thank you so much for your help so far, Axe.

EDIT: Had 2 more crashes today, updated .zip

 

One dumpfile blames
Code: BugCheck C9, {21f, fffff802b7ddb174, ffff940b9e2328c0, 0} Unable to load image \SystemRoot\System32\drivers\ScpVBus.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ScpVBus.sys *** ERROR: Module load completed but symbols could not be loaded for ScpVBus.sys Probably caused by : memory_corruption[/quote] ScpVBus Sun May 05 23:31:26 2013
Driver Description: Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver
Driver Update Site: XInput Wrapper for DS3 and Play.com USB Dual DS2 Controller

This driver is from 2013 and is probably not compatible with windows 10.
See if there is anewer version avaliable or uninstall it and see if this stops the BSOD.

Also the drivers for your Logitech Wingman device are from 2010, also see if there are windows 10 compatible drivers avaliable.
WmBEnum Tue Apr 27 22:10:19 2010
WmXlCore Tue Apr 27 22:09:26 2010
Driver Description: Logitech WingMan Virtual Bus Enumerator Driver
Driver Update Site: Logitech Support

 

I actually uninstalled what I believe was causing the Logitech issues last night - it was the program responsible for a steering wheel input. Since then, I haven't crashed. I also just uninstalled the Scp driver from XInput so hopefully these 2 combined fix things. I'll run another driver verifier tonight and hopefully it'll all go well.

Thank you lifetec.

 

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver, you can use this tutorial for the installation part *Arrow NVIDIA Drivers - Avoid Problems - Windows 7 Help Forums



Code: 1: kd> lmvm nvlddmkm Browse full module list start end module name fffff80a`6f340000 fffff80a`70176000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f37f8f12da8b10d7\nvlddmkm.sys Image name: nvlddmkm.sys Browse all global symbols functions data Timestamp: Thu Mar 16 23:38:26 2017 (58CB13E2) CheckSum: 00DF2317 ImageSize: 00E36000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Was away for a few days, but I've used DDU and reinstalled the Nvidia drivers as instructed, as well as clearing out a bunch of old Logitech drivers. Hopefully this fixes things but if anything happens, I'll upload future DM logs.

Thank you both for your help.

 

Okay, so I'm still getting sporadic Blue Screens, albeit significantly less than before. I've uploaded a new .zip file.

I've reinstalled all Nvidia Drivers in response to the recent dxgmms2.sys BSOD.

EDIT: Just realised Windows was set to automatically update my drivers, I've now disabled this.

EDIT2: Updated zip after another crash.

 

In the last dumpfile there are still drivers related to the Logitech device
WmBEnum Tue Apr 27 22:10:19 2010
WmXlCore Tue Apr 27 22:09:26 2010

Also i found this driver
NTIOLib_X64 Mon Nov 26 11:11:53 2012
Driver Description: MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5, MSI Super Charger & MSI Smart Utilities.

Recently (Nov 2014) there have been numerous instances of this driver in memory dumps. Analysis reveals that they are scattered throughout the filesystem by the installed MSI command utilities. For now I suggest uninstalling them all.
Driver Update Site: MSI Global
And in your unloaded module this one amifldrv64.sys
Driver Description: MSI DPC Latency Tuner
Driver Update Site: MSI Global

I would uninstall/remove all MSI Utiliites from your system.

 

In the last dumpfile there are still drivers related to the Logitech device
WmBEnum Tue Apr 27 22:10:19 2010
WmXlCore Tue Apr 27 22:09:26 2010

Also i found this driver
NTIOLib_X64 Mon Nov 26 11:11:53 2012
Driver Description: MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5, MSI Super Charger & MSI Smart Utilities.

Recently (Nov 2014) there have been numerous instances of this driver in memory dumps. Analysis reveals that they are scattered throughout the filesystem by the installed MSI command utilities. For now I suggest uninstalling them all.
Driver Update Site: MSI Global
And in your unloaded module this one amifldrv64.sys
Driver Description: MSI DPC Latency Tuner
Driver Update Site: MSI Global

I would uninstall/remove all MSI Utiliites from your system.

 

Hm, I was sure I had uninstalled all the wingman devices. The only thing I can think of is that they're installed with the Logitech Gaming Software, which unfortunately I need to have installed as I have a G600 Mouse that doesn't work without the software.

I did have MSI Command Center & Afterburner installed, so I've uninstalled them.


What's the best way for me to get rid of the Wingman drivers? Would I have to find them in System 32 and remove/rename the .sys file?

EDIT: There are no more unused Logitech devices shown in my Device Manager. There are two used ones, "Logitech Gaming Virtual Bus Enumerator" and "Logitech Virtual Bus Enumerator" but I would assume these are from/for the G600 mouse?

EDIT2: When searching sys32 fo rWmBEnum & WmXlCore, it brings up two .sys files for each. I'm able to rename one but not the other and I can't delete any.

 

Reinstall the Logitech drivers/software for your mouse.


Please (re)move some files to increase the free space to at least 15%.
Every partition needs at least 10-15% free space so Windows can do its thing in the background, 15% is to be on the safe side.


Warning Less free space could cause BSODs or other problems, because Windows cannot perform the tasks it needs to do in the background!


Download Intel Rapid drivers from MSI and install them, they are an older version but chances are they are more compatible with your system.


Don't rename driver files out of nowhere, especially if you have software/hardware that may still use them!

 

I booted into Safe Mode and was able to remove the two Wingman drivers aforementioned, and the Logitech mouse is still working. Doing a search for either driver comes up with no results, so it seems to have worked this time round.

I've installed ver. 14.5.0.1081 of the Intel Rapid drivers from the drivers listed under my motherboard on MSI's website. I will go ahead and reinstall the mouse software though.

EDIT: Reinstalled the mouse software, neither of the old drivers that were causing issues have returned.

 

So I installed InputMapper to play Dark Souls, as I only have a DS4 controller. Today I had a BSOD in hidclass.sys and I found the ScP drivers that were causing me a BSOD before I removed them This leads me to believe that the Xinput wrapper is an issue, but I'm not aware of another way to use a DS4 controller on Windows unless a game natively supports it, which Dark Souls 3 does not.

I've uploaded the log with the recent crash in it, just in case I'm wrong in thinking it's caused by InputMapper's drivers.

Is there a better way to emulate an Xbox controller for the DS4 other than InputMapper that doesn't use the ScP drivers that give me blue screens?

EDIT: Updated log, another crash - again with the DS4 controller plugged in.

 

Tip, don't edit your posts after a few hours except for typos. We aren't notified of edits and will miss them if you don't make us aware of them.

 

We'll need more information of your system, stuff like the PSU and cooler cannot be retrieve from the logs.

Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.
In the left corner below in your post you find 'My System Specs'. After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.

 

Updated my system specs.