Windows 10: BSODs playing Overwatch, multiple codes

Page 1 of 3 123 LastLast

  1. Posts : 18
    Windows 10/Arch Linux
       07 Sep 2016 #1

    BSODs playing Overwatch, multiple codes

    Hi all,

    I've recently started playing Overwatch, and it's been resulting in BSODs and crashes every so often, making the game pretty difficult to play (it's also happened once during Far Cry 3 recently, which is strange, since I had been running that game fine for the most part). The BSODs have been several different codes, but the ones I remember happening most are IRQL_NOT_LESS_OR_EQUAL and MEMORY MANAGEMENT. I've tried to open the minidumps in WinDbg myself, but I'm afraid I'm a bit lost trying to interpret what I see. I've attached the zip of my system information and dumps compiled by the program under the posting guidelines here.

    Incidentally, I had similar problems with other games back when I was running Windows 7, which I posted about here: BSOD from nvlddmkm (running verifier) when trying to open GeForce Exp Solved - Windows 7 Help Forums

    Looking back at it, it seems like it wasn't really resolved fully, but I haven't had much problem with it since then until now. Any help would be appreciated!
      My ComputerSystem Spec

  2. Ztruker's Avatar
    Posts : 6,275
    Windows 10 Pro X64 17134.191
       08 Sep 2016 #2

    I don't see much useful info in any of the dumps though 3 or 4 indicate memory_corruption_large.

    It would be a good idea to test your RAM as follows:


    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    information   Information

    MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses

    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.
      My ComputersSystem Spec

  3. Posts : 18
    Windows 10/Arch Linux
    Thread Starter
       09 Sep 2016 #3

    Thanks for taking a look! I just ran Memtest86+ over night last night, and I woke up to 8 passes with 0 errors this morning. Should I run a longer test, or do you think it may be something else, like the CPU?
      My ComputerSystem Spec

  4. Ztruker's Avatar
    Posts : 6,275
    Windows 10 Pro X64 17134.191
       10 Sep 2016 #4

    That is enough for memory, looks good.

    Let's try runninv with Driver Verifier enabled, see if that gives us any more information.
    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to
    and make sure the correct boxes are checked.

    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.
      My ComputersSystem Spec

  5. Posts : 18
    Windows 10/Arch Linux
    Thread Starter
       11 Sep 2016 #5

    Sorry for the delayed response; I was out of town for the weekend.

    I just tried the driver verifier and it gave me a BSOD during boot up. I've recreated the zip file with the new crash dump information and attached it here (I guess you should only pay attention to the new one on 9/11/16). What would runninv have done if I had been able to boot up?
      My ComputerSystem Spec

  6. Ztruker's Avatar
    Posts : 6,275
    Windows 10 Pro X64 17134.191
       12 Sep 2016 #6

    The latest dump indicates a problem with ScpVBus.sys
    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
    This belongs to Scarlet.Crush Productions Scp Dual Shock Virtual Bus Driver. I think it's SCPToolkit on your computer and has to do with Game controllers. Uninstall it and see if that fixes the problem.
      My ComputersSystem Spec

  7. Posts : 18
    Windows 10/Arch Linux
    Thread Starter
       12 Sep 2016 #7

    Ah, okay, I uninstalled it. Should I try the driver verifier again, or just try playing games and look for blue screens?
      My ComputerSystem Spec

  8. Posts : 18
    Windows 10/Arch Linux
    Thread Starter
       12 Sep 2016 #8

    I was just playing some Overwatch to test my computer and I had another BSOD, though I feel like it took longer than usual this time to crash. It was another "MEMORY MANAGEMENT" error, crash dump attached here.

    Should I try the driver verifier again?
      My ComputerSystem Spec

  9. Ztruker's Avatar
    Posts : 6,275
    Windows 10 Pro X64 17134.191
       13 Sep 2016 #9

    Nothing useful in that dump unfortunately. Give Driver Verifier another try. Maybe it will show us something useful.
      My ComputersSystem Spec

  10. Posts : 18
    Windows 10/Arch Linux
    Thread Starter
       14 Sep 2016 #10

    The latest BSOD, running driver verifier, is attached. This time, it was something like "Kernel Security Check".
      My ComputerSystem Spec

Page 1 of 3 123 LastLast

Related Threads
Hi, This issue has occurred whenever I play Overwatch. It can occur when I have only played for 10 minutes or it may not appear until after many hours of playing. I have 8GB of RAM and the most I have seen Overwatch use via task manager is...
Constant BSODs in Windows 10. Multiple codes in BSOD Crashes and Debugging
Haven't been using my desktop much lately, so not quite sure if this happened after recent Windows 10 updates or not, but I have been having constant BSODs lately. There doesn't seem to be immediate rhyme or reason to when: sometimes it happens...
Hi! I've been having numerous crashes of Overwatch and Google Chrome for the past several weeks. I've been trying to troubleshoot the crashes but haven't been successful so far. I've attached the minidump files to this thread. If anyone can point me...
BSOD while playing Overwatch: error 0x00000124 in BSOD Crashes and Debugging
Hey guys, I just recently downloaded Overwatch and started playing a few hours ago when I suddenly got a BSOD that stated "Whea Uncorrectable Error" as a code. This is a fairly new laptop that I've had for less than 6 months. I've gotten a handful...
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 08:20.
Find Us