Windows 10: Multiple crashes with multiple error codes & modules Solved

Page 2 of 4 FirstFirst 1234 LastLast

  1. Posts : 21
    Microsoft Windows 10 Pro 64-bit 14393 Multiprocessor Free
    Thread Starter
       27 Mar 2017 #11

    Well so far so good - I've yet to crash again. If I get another crash I'll post an update in here with an updated DM Log zip file.

    Thank you for your help Axe!
      My ComputerSystem Spec

  2. Posts : 21
    Microsoft Windows 10 Pro 64-bit 14393 Multiprocessor Free
    Thread Starter
       29 Mar 2017 #12

    Unfortunately it didn't last too long. Had another crash this afternoon, I've attached the log zip.
      My ComputerSystem Spec

  3. Posts : 13,319
    Windows 10 Pro
       29 Mar 2017 #13

    Multiple crashes with multiple error codes & modules Diagnostic Test Multiple crashes with multiple error codes & modules

    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My ComputersSystem Spec

  4. Posts : 21
    Microsoft Windows 10 Pro 64-bit 14393 Multiprocessor Free
    Thread Starter
       29 Mar 2017 #14

    DM Log from Verifier BSODs -

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

    EDIT: Had 2 more crashes today, updated .zip
    Last edited by Veilyn; 30 Mar 2017 at 11:23.
      My ComputerSystem Spec

  5.    31 Mar 2017 #15

    One dumpfile blames
      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
    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 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
      My ComputerSystem Spec

  6. Posts : 21
    Microsoft Windows 10 Pro 64-bit 14393 Multiprocessor Free
    Thread Starter
       31 Mar 2017 #16

    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.
      My ComputerSystem Spec

  7. Posts : 13,319
    Windows 10 Pro
       31 Mar 2017 #17

    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 NVIDIA Drivers - Avoid Problems - Windows 7 Help Forums

    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
      My ComputersSystem Spec

  • Posts : 21
    Microsoft Windows 10 Pro 64-bit 14393 Multiprocessor Free
    Thread Starter
       03 Apr 2017 #18

    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.
      My ComputerSystem Spec

  • Posts : 21
    Microsoft Windows 10 Pro 64-bit 14393 Multiprocessor Free
    Thread Starter
       07 Apr 2017 #19

    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.
    Last edited by Veilyn; 07 Apr 2017 at 21:16.
      My ComputerSystem Spec

  •    08 Apr 2017 #20

    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:
    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.
      My ComputerSystem Spec

    Page 2 of 4 FirstFirst 1234 LastLast

    Related Threads
    Built a new computer around the start of this month (feb) and have been having intermittent BSOD's, ranging between 1 day and 1 week or so between. They don't seem to happen at any specific time or usage; having occured when the pc was idle...
    I completed a new PC build a couple weeks ago. Every time I turn the PC off for a few hours and come back and power it on 1 of 2 things happens. 1. The PC BSOD during the windows load before the log on screen 2. The PC BSOD at the log on or...
    Crashes mostly occur when gaming, but not a rule Hello guys, Here's a quick preview of the issues: 89238 First time here, I saw you are an active and helpful community so I decided to try my luck. I first ingored the BSODs, but it's...
    BSOD - Multiple error codes/bug checks in BSOD Crashes and Debugging
    Attached is my dmp file. This has been happening for months. I reformatted/upgraded my PC recently to Windows 10, which leads me to believe that it shouldn't be a driver issue (I assume it's probably a hardware issue) But I was hoping you guys could...
    Multiple BSOD error codes in BSOD Crashes and Debugging
    I updated from windows 7 the day that 10 launched and for a few days everything worked perfectly, then I crashed a few times, and today I crashed three times, all for different reasons. The first crash was a kernell_data_inpage_error. I did...
    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 17:24.
    Find Us