Windows 10: Bsod irql_not_less_or_equal

Page 1 of 2 12 LastLast
  1.    30 Jul 2015 #1

    Bsod irql_not_less_or_equal


    Upgrade to Windows 10 yesterday, from Windows 7 Pro. After a couple of hours of usage, I started getting BSODs, more specifically IRQL_NOT_LESS_OR_EQUAL.

    I decided to reset the system, but the same problem keeps occurring. I'm thinking it's a driver issue, but I am not sure.

    Blue screen view says "caused by driver ntoskrnl.exe+14cc20.

    These BSODs were also occurring when I used the Windows 10 technical preview builds. I reverted back to Windows 7, and the PC ran BSOD-free.

    I can barely get anything done before the BSOD occurs. I have attached the minidump file.
      My ComputerSystem Spec

  2.    30 Jul 2015 #2

    I just received the same thing a few minutes ago, IRQL_NOT_LESS_OR_EQUAL. What did you use to generate the minidump information? I'm wondering if I could use it to figure out what driver is bad ...

    Never mind - I see the instructions thread now
      My ComputerSystem Spec

  3.    30 Jul 2015 #3

    GatsbyGlen said: View Post
    I just received the same thing a few minutes ago, IRQL_NOT_LESS_OR_EQUAL. What did you use to generate the minidump information? I'm wondering if I could use it to figure out what driver is bad ...

    Never mind - I see the instructions thread now
    Have you tried using blue screen view for additional details?

    Anyways, I decided to do some debugging myself, and found the culprit to be an AMD driver. AMD released their Win 10 driver yesterday, but Win 10 automatic update was installing the previous Win 8.1 iteration of the drivers. I noticed this after I wiped all AMD drivers from my PC, but noticed that after 20-30 seconds, they were being re-installed via Windows Update. For those who may be less tech savvy, this could be an issue for them. Luckily, I have Win 10 Pro, which means I can defer the upgrades if I wish. That's what I did end up doing, and then manually installing the Win 10 AMD drivers. PC has worked fine for a little more than an hour so far.

    I'm curious, could you perhaps upload your dump files here? I'd like to check them out. I can't guarantee I'll solve your particular issue, but maybe I could help.
      My ComputerSystem Spec

  4.    30 Jul 2015 #4

    Sure thing, see attached. With Windows 8.1 I always added updates manually, but elected to receive them automatically with 10. Maybe I need to rethink that. I do have Win 10 Pro so I guess I could defer them.

    Blue Screen says something about a mailslot driver. Not sure what that is.

    Lenovo W541
      My ComputerSystem Spec

  5.    30 Jul 2015 #5

    BugCheck D1, {32, 2, 0, fffff80086bac89a}

    *** WARNING: Unable to verify timestamp for Netwbw02.sys
    *** ERROR: Module load completed but symbols could not be loaded for Netwbw02.sys
    Probably caused by : Netwbw02.sys ( Netwbw02+21ceb )
    Netwbw02.sys is an Intel WiFi Driver. Seems like the driver is for Windows 8.1. Try uninstalling the driver, and then see if Intel has WiFi drivers for Windows 10.
      My ComputerSystem Spec

  6.    30 Jul 2015 #6

    MrTryfe said: View Post
    Netwbw02.sys is an Intel WiFi Driver. Seems like the driver is for Windows 8.1. Try uninstalling the driver, and then see if Intel has WiFi drivers for Windows 10.
    Thanks - are you using WinDBG to get that info?
      My ComputerSystem Spec

  7.    30 Jul 2015 #7

    GatsbyGlen said: View Post
    Thanks - are you using WinDBG to get that info?
    Yeah.
      My ComputerSystem Spec

  8.    30 Jul 2015 #8

    MrTryfe said: View Post
    Yeah.
    I'll have to try that sometime Thanks for the quick response. Lenovo had a newer WiFi driver, so I installed that.
      My ComputerSystem Spec


  9. Posts : 8,166
    Windows 10 Enterprise and Pro/Windows 7 Enterprise/Linux Mint
       30 Jul 2015 #9

    MrTryfe I looked at your dump file and it says

    Code:
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {ffffffffffffffff, 2, 0, fffff802b804db7b}
    
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : atikmdag.sys ( atikmdag+28707 )
    
    Followup:     MachineOwner
    I'm sure you know that is your AMD graphics driver and this is your current version

    Code:
    start             end                 module name
    fffff800`a8070000 fffff800`a957a000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Browse all global symbols  functions  data
        Timestamp:        Wed Jul 15 20:37:09 2015 (55A70AC5)
        CheckSum:         014A8B0F
        ImageSize:        0150A000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    If I may, I would like to try to give you some suggestions on reinstalling your graphics driver, but at this point I am not sure what works with windows 10. I would give it a try anyway. I assume you also know that AMD has had a lot of driver problems with Windows 10 so far.

    I am going to give you some links that will help you get a good clean install and not have any drivers you don't need that will conflict with other drivers. Download a WHQL driver from https://www.tenforums.com/drivers-har...dows-10-a.html . Once you have them downloaded, uninstall you current driver from control panel. next clean up any left over drivers from following this tutorial http://www.sevenforums.com/tutorials...nstalling.html and select only ATI Display Drivers. After you have done that and rebooted, install the new driver, only select custom install and install only what you have to. Very few people need most of what they include. You do not need the audio/HDMI drivers as you already have that in your Motherboard drivers. Unless there is some reason you need them, the only thing you really need is the Display Driver. These links are for Windows 7 and they work with that, but it's worth a try. Maybe we both can learn something.

    If everyone else would start their own thread it would cut down on the confusion.
      My ComputersSystem Spec

  10.    30 Jul 2015 #10

    Thanks for the info, essenbe. If my issue persists, I'll create a new thread. Sorry to hijack.
      My ComputerSystem Spec


 
Page 1 of 2 12 LastLast

Related Threads
Solved My first BSOD in ten. in BSOD Crashes and Debugging
It happened after I just have installed Speccy and let it run for the first time. When it is "Analyzing", the BSOD happened. The screen says it is cpuz138_x64.sys that caused the BSOD. I dont have CPUz Installed. The later runs of Speccy...
Solved BSOD: Can Some Please Take A Look in BSOD Crashes and Debugging
My computer blue screened upon updating, can someone have a look and see what needs to be done, please?
My First Win 10 BSOD in BSOD Crashes and Debugging
Throwing it out here for everyone. A lot of symbols can't be found. Seems to blame my graphics driver and the stack indicates the driver got caught up in some type of loop. A few minutes before that, Facebook was open and a video played,...
Bsod help please in BSOD Crashes and Debugging
Hey all getting bsod on windows 10 tech preview here is my debug info 12754 help much appreciated. I have run mem test overnight no ram errors. cheers Just a bit more info the error bcc is 0xc000021a and the cause is "ntoskrnl.exe" address...
Solved BSOD - usbehci.sys - IRQL_NOT_LESS_OR_EQUAL in BSOD Crashes and Debugging
I have already had 7 of them, just got one when trying to post this. I suspect my USB sound card. So far they have happened only in Windows, not in games, when listening to the music on youtube or via Radiosure, sometimes I was not even at PC, so I...
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 22:30.
Find Us