Multiple differernt BSODS while gaming on multiple games

Page 2 of 4 FirstFirst 1234 LastLast

  1. Posts : 14,894
    Windows 10 Pro
       #11

    What you should do is check your USB devices for driver updates from their manufacturer.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {ffffdfffe06deb30, 2, 1, fffff8013c080549}
    
    Probably caused by : hardware ( ucx01000!Urb_LegacyTransferUrbCompletion+129 )
      My Computers


  2. Posts : 21
    Windows 10 64 bit
    Thread Starter
       #12

    Okay updated everything USB that I could think of and just got another BSOD.
      My Computer


  3. Posts : 14,894
    Windows 10 Pro
       #13

    See if a BIOS update helps something, you are currently using version F2 while F5 is available.
    GIGABYTE - Motherboard - Socket 1151 - GA-Z170XP-SLI (rev. 1.0)
      My Computers


  4. Posts : 21
    Windows 10 64 bit
    Thread Starter
       #14

    Updated BIOS this morning to F5, all was well for a while and just got another BSOD...
      My Computer


  5. Posts : 14,894
    Windows 10 Pro
       #15

    The crash seems to be caused by the Nvidia display driver, but for some reason I couldn't believe it which is why I checked the unloaded drivers.
    Most of them are from Windows, but there are 2 that caught my eye which are Xbox USB drivers and drivers from MSI Afterburner which is the active process when the crash occured.
    My suggestion is to update or reinstall the Xbox drivers and remove MSI Afterburner.
    Driver Reference Table - xusb22.sys
    Driver Reference Table - RTCore64.sys
    Code:
    PROCESS_NAME:  MSIAfterburner
    
    Unloaded modules:
    fffff800`e3b50000 fffff800`e3b6f000   xusb22.sys
    fffff800`e3b40000 fffff800`e3b47000   WinRing0x64.
    fffff800`e3b00000 fffff800`e3b06000   RTCore64.sys
    fffff800`e34f0000 fffff800`e3ac4000   iqvw64e.sys
    fffff800`e3b10000 fffff800`e3b17000   WinRing0x64.
    fffff800`e1c20000 fffff800`e1c44000   USBSTOR.SYS
    fffff800`e0140000 fffff800`e014e000   WpdUpFltr.sy
    fffff800`e0100000 fffff800`e013b000   WUDFRd.sys
    fffff800`e00a0000 fffff800`e00db000   WUDFRd.sys
    fffff800`def30000 fffff800`def3f000   dump_storpor
    fffff800`de7d0000 fffff800`de7f5000   dump_storahc
    fffff800`de800000 fffff800`de81c000   dump_dumpfve
    fffff800`de160000 fffff800`de17c000   EhStorClass.
    fffff800`e1370000 fffff800`e1392000   i8042prt.sys
    fffff800`df8f0000 fffff800`df903000   dam.sys 
    fffff800`de820000 fffff800`de851000   cdrom.sys
    fffff800`dde20000 fffff800`dde30000   WdBoot.sys
    fffff800`dee50000 fffff800`dee5e000   hwpolicy.sys
    
    
    1: kd> lmvm xusb22
    start             end                 module name
    fffff800`e3b80000 fffff800`e3b9f000   xusb22     (deferred)             
        Mapped memory image file: d:\symbols\xusb22.sys\5632D8C61f000\xusb22.sys
        Image path: \SystemRoot\System32\drivers\xusb22.sys
        Image name: xusb22.sys
        Timestamp:        Fri Oct 30 03:41:10 2015 (5632D8C6)
        CheckSum:         0001E8F5
        ImageSize:        0001F000
        File version:     10.0.10586.0
        Product version:  10.0.10586.0
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.0 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     XUSB21
        OriginalFilename: XUSB21.sys
        ProductVersion:   10.0.10586.0
        FileVersion:      10.0.10586.0 (th2_release.151029-1700)
        FileDescription:  Xbox 360 Common Controller for Windows Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    
    1: kd> lmvm RTCore64
    start             end                 module name
    fffff800`e3b70000 fffff800`e3b76000   RTCore64   (deferred)             
        Image path: \??\C:\Program Files (x86)\MSI Afterburner\RTCore64.sys
        Image name: RTCore64.sys
        Timestamp:        Fri Apr 24 09:01:47 2015 (5539EA5B)
        CheckSum:         0000F888
        ImageSize:        00006000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computers


  6. Posts : 21
    Windows 10 64 bit
    Thread Starter
       #16

    Okay well I didn't even know that I have an xbox driver? How do I find out were it is or what to update? And are there any other good programs that do on screen displays for computer information while gaming? As afterburner is the only program I have had good luck with.
      My Computer


  7. Posts : 14,894
    Windows 10 Pro
       #17

    In the system root directory is a folder in a folder where you can find the driver.
    The path to the file is in the code below.
    Code:
    %systemroot%\system32\drivers\
    Have you ever connected an Xbox device to the PC?

    Honestly I wouldn't know, I have never done anything close to it I believe.
      My Computers


  8. Posts : 21
    Windows 10 64 bit
    Thread Starter
       #18

    Ive never connected anything xbox related just a Playstation 4 controller. Is it the windows 10 xbox app that needs to be updated? Shouldnt that auto update with windows update? I ran this on admin command prompt "sfc /scannow", I dont know if it helps you any but it says it found corrupt files and that it repaired/replaced them. I would attach the CBS file but the forum says the file is to large.
      My Computer


  9. Posts : 21
    Windows 10 64 bit
    Thread Starter
       #19

    I think I made it a zip file correctly I am not sure, let me know if it helps. Thanks again.
      My Computer


  10. Posts : 21
    Windows 10 64 bit
    Thread Starter
       #20

    Another lovely BSOD for ya, this time I was not using MSI Afterburner so maybe that will eliminate that as a problem? I'm hoping. Thanks again for all the time you have in helping me.
      My Computer


 

  Related Discussions
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 09:51.
Find Us




Windows 10 Forums