IRQL_NOT_LESS_OR_EQUAL possibly ntkrnlmp.exe ( nt!KiRetireDpcList+4bb


  1. Posts : 5
    Windows 10
       #1

    IRQL_NOT_LESS_OR_EQUAL possibly ntkrnlmp.exe ( nt!KiRetireDpcList+4bb


    I've had BSOD problems on two separate laptops of the same model and make, I shipped and returned the first one and got a replacement.

    The BSODs still kept happening even on a newly shipped laptop.

    Please help. :/
      My Computer


  2. Posts : 654
    windows 10 Pro
       #2

    The latest dumpfiles are all
    Code:
      *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {ffffe000fd88c788, 2, 0, fffff802dc6c764b}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiRetireDpcList+4bb )
    Sadly the dumpfile does not point to something specific.

    Usual causes:
    This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

    The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

    If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

    Looking through your drivers module, there are some older drivers.
    ETD.sys Tue Jul 28 04:01:31 2015
    Driver Description: ELAN PS/2 Port Smart Pad
    Driver Update Site: OEM

    evolve.sys Sat Aug 07 06:47:00 2010
    Driver Description: Echobit Evolve Virtual Miniport (Ethernet) driver
    Driver Update Site: Social Gaming Platform Evolve

    NTIOLib_X64 Thu Oct 25 12:27:58 2012
    winio64 Fri Jun 04 06:08:03 2010 (Part of MSI Dragoon Gaming Center also)
    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: Afterburner - MSI Gaming Series

    RtsPer Fri May 29 08:32:34 2015
    Driver Description: RealTek RTS PCIE READER Driver
    Driver Update Site: Realtek
    or from OEM

    SAlphaPS264 Wed Mar 05 16:00:39 2014
    SteelBus64 Tue Jun 02 22:00:55 2015
    Driver Description: SteelSeries Engine HID Driver
    Driver Update Site: Support(FAQ): Frequently Asked Questions
    Downloads: SteelSeries Engine Downloads Drivers | SteelSeries

    semav6msr64 Fri Jan 24 20:22:40 2014
    Driver Description: SEMA Software Driver
    Driver Update Site: Download () - http://sema-soft.com/en/start.php

    Because you have a MSI laptop first look for newer drivers versions on your supportpage Support For GS60 6QE Ghost Pro(4K) | MSI Global | Laptops - The best gaming laptop provider

    Also look if there is a newer BIOS version.
      My Computer


  3. Posts : 5
    Windows 10
    Thread Starter
       #3

    Hi lifetec, sorry for answering so late, but I have downloaded and installed the updated bios from the MSI website you provided. So far I haven't ran into any problems yet, but I will be keeping an eye out for any more bluescreens.

    In the meantime, can you help me with uninstalling the afterburner drivers? I can't seem to find it anywhere to get rid of it.

    Thanks so much for helping me with this.
      My Computer


  4. Posts : 654
    windows 10 Pro
       #4

    it looks that the afterburner drivers in your system are part of MSI supercharger.

    NTIOLib_1_0_ NTIOLib_1_0_3 NTIOLib_1_0_3 Kernel Manual Running OK TRUE FALSE 0 4,096 0 2012-10-25 3:27:58 AM \??\C:\Program Files (x86)\MSI\SUPER CHARGER\NTI 4,096
    WINIO WINIO WINIO Kernel Manual Running OK TRUE FALSE 0 4,096 0 2010-06-03 9:08:03 PM \??\C:\Program Files (x86)\MSI\Dragon Gaming Cen 4,096
      My Computer


  5. Posts : 5
    Windows 10
    Thread Starter
       #5

    Well after a week or so, the BSODs have definitely happened a lot less. (3 so far) but still happens. I've updated all the drivers from the MSI website, and uninstalled dragoon gaming center. So now I'm wondering what else could be causing more BSODs. Here're my new logs.
    Attachment 80872
      My Computer


  6. Posts : 654
    windows 10 Pro
       #6

    In all 3 dumpfiles the processname is Chrome.exe.
    And two are related to tcpip.sys
    This all could point to networking related.


    I see you have still the old driver from evolve installed.(does this use chrome browser to connect)
    See if there is a windows 10 compatible drivers/version.
    Or complete uninstall/remove it.

    Also check if there are newer version avaliable of you networking drivers from the supportpage (lan/bluetooth/wifi etc.)
      My Computer


  7. Posts : 5
    Windows 10
    Thread Starter
       #7

    Alright. So by now I have uninstalled evolve completely. I might even start considering uninstalling chrome at this rate.
    Here are two more dump files from just today.

    I believe I've gotten all the updates from the msi support page that you linked me in your first response, so I should have the most recent drivers unless the support page itself is outdated.
      My Computer


  8. Posts : 654
    windows 10 Pro
       #8

    Are the 2 latest dumpfiles before you removed Evolve?
    Because in the dumpfiles still evolve.sys is mentioned.
    In the procesname now no more chrome.exe is named but aidiodbg.exe and agent.exe(battle.net Diablo).

    In the unloaded module 7 times SAlpham64.sys is named. and the driver is still from 2014.
    What devices of steelseries do you have and how old are these devices, are they compatible with windows 10?
    Are they compatible with steel engine 3?

    Also there is still 1x Ntiolibx64.sys driver in the modulelist, please uninstall MSI supercharger.
    Do you already updated the Realtek PCIE CardReader?, because this device is named in the windows error report.
    My advice is to install/update all the windows 10 drivers from the supportpage( not only drivers we mentioned in earlier post)
      My Computer


  9. Posts : 5
    Windows 10
    Thread Starter
       #9

    Hmm, I guess not. I have uninstalled evolve and steelseries engine 2, I was hesitant on doing that because none of my steelseries devices(kana & built in keyboard) are detected on SE 3. Plus the installer I got from the website said I was already using the latest update.

    As for the cardreader, I did go through every single driver installer that was listed on the MSI support page. So if that's still a problem I'm not sure how I could fix it.
      My Computer


  10. Posts : 654
    windows 10 Pro
       #10

    Could you check if your specific steel series devices are compatible with windows 10 at all.
    If you have other keyboard/mouse avaliable/borrow could you use these temporarily and see if the BSODs keep happening.
    Could you if get a new BSod (hopefully not) upload a new zip.

    If these new dumpfile also have/give no specific clues/solution for the problem.
    The next step is using Driver Verifier.
    You can enable "Driver Verifier" according to instructions from the below link.
    Driver Verifier - Enable and Disable in Windows 10 - Windows 10 Forums
    "Verifier" is a Microsoft's own tool to stress test third party drivers and find the buggy one. If it detects a violation, a blue screen will be created immediately and the dump will give us the name of offending driver straight forward. After enabling "Verifier" , system will be a bit slow and laggy during to the background verification process. After you got two or more blue screens, please upload the new crash dumps and we will know whether the issue is caused by third party drivers or low level hardware (a verifier enabled dump which blames Windows system files is a clear confirmation of hardware problem).
    "Verifier" should be only used to monitor third party drivers. Selecting Microsoft system drivers is totally unnecessary and doing so may make the system non bootable.
      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 01:15.
Find Us




Windows 10 Forums