Windows 10: BSOD while playing Overwatch, error 0x000000d1 IRQL_NOT_LESS_OR_EQUAL

  1.    26 Dec 2016 #1

    BSOD while playing Overwatch, error 0x000000d1 IRQL_NOT_LESS_OR_EQUAL


    As the title says I'm getting a BSOD on my wife's computer when running overwatch. Not sure if it's related but the BSOD only occurs when playing a match with other human players, bot matches don't cause a crash.

    I've done what little diagnostics i know how to do, i've pulled the minidump files and ran windows system check and memory diagnostics and both came up with no errors. I'm at a loss.

    DESKTOP-1D96NNJ-Mon_12_26_2016_145108_25.zip

    System specs:
    WIndows 10 pro
    CPU: AMD Phenom II x4 965
    MB: MSI 870A-G55 AM3
    GPU: GeForce GTX 460
    4GB Ram
      My ComputerSystem Spec

  2.    26 Dec 2016 #2

    First you running a system with the absolute minimum specs for playing Overwatch.

    But Your MSI Afterburner drivers/version has drivers from 2012.
    Update it to the latest version.

    Also your Razer deviceses have drivers from 2015 see if there are newer drivers.
      My ComputerSystem Spec

  3.    26 Dec 2016 #3

    Ahh perfect, thanks for the reply i'll check on those drivers and get those updated.

    i know its bare minimum specs, but the game runs at 80 or so fps at lowest settings, would the outdated hardware still cause a crash like that?
      My ComputerSystem Spec

  4.    26 Dec 2016 #4

    lifetec said: View Post
    First you running a system with the absolute minimum specs for playing Overwatch.

    But Your MSI Afterburner drivers/version has drivers from 2012.
    Update it to the latest version.

    Also your Razer deviceses have drivers from 2015 see if there are newer drivers.
    So i checked and i've got the most up to date versions of the Razer drivers.
    Not using afterburner on this PC so i just uninstalled/removed afterburner.

    On a related note, i had an SSD that i was planning on installing in this computer as well, so after checking the drivers and the game still crashing i went ahead and just threw that in and did a fresh win 10 install on the new drive. double checked all the drivers when it was up and running again.

    This time i was able to play for about 20-30 minutes before the game crashed. I Attached another dump file from the latest crash.

    I'm assuming this box is just too old to run the game now?
    DESKTOP-VI2SCEQ-Mon_12_26_2016_214714_66.zip
      My ComputerSystem Spec

  5.    27 Dec 2016 #5

    Again the same bugcheck
    Code:
      BugCheck D1, {0, 2, 8, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+247 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: 0000000000000000, address which referenced memory
    Usual causes:* Device driver

    Your Intel(R) PRO/1000 GT Desktop Adapter has drivers from 2010.
    Searching on the intel site there are no windows 10 drivers for this device, the latest are from 2013.
    You could try these 2013 drivers, else i would remove/uninstall this device and see if this stops the BSOD.
    Downloads for Intel(R) PRO/1000 GT Desktop Adapter
      My ComputerSystem Spec

  6.    27 Dec 2016 #6

    Thanks for the help, uninstalling the driver and removing the network card didn't fix the issue either. Same blue screen, same bugcheck
      My ComputerSystem Spec

  7.    28 Dec 2016 #7

    Please post an updated collection of logs.

    Also, use Driver Verifier to help pinpoint the problematic driver(s).
      My ComputerSystem Spec


 

Related Threads
BSOD playing Overwatch, error L1C63x64.sys in BSOD Crashes and Debugging
Hi all, I have been experiencing this BSOD: Driver IRQL Not Less or Equal, L1C63x64.sys for a few months now. When it happens, it is only when I am in the middle of gaming (Overwatch). After some research, I see that there are many of the same...
Hi all, Hoping you can shed some light on this, as I'm at the end of my tether with my machine at the minute. Built it myself a little over two years, and has been absolutely spot on fine until around 3 months ago. Started getting some severe...
BSOD playing League of Legends / Overwatch in BSOD Crashes and Debugging
I keep getting blue screens and I did my own basic research on the errors and have had no luck. If I could get some help on this it would be much appreciated.
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...
My system is overclocked but I ran a stress test with OCCT for ~24 hours when I first set it up and there were no issues. The crashes have only ever happened while playing Overwatch. They are definitely not heat related unless CAM is reading the...
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 13:35.
Find Us