IRQL not less or equal to BSOD in Windows 10 after after startup


  1. Posts : 12
    Microsoft Windows 10 Home Single Language 64-bit 10586 Multiprocessor Free
       #1

    IRQL not less or equal to BSOD in Windows 10 after after startup


    Hi, i've been having several BSODs related to "IRQL not less or equal" and "driver irql not less or equal too" after upgrading to windows 10. It happens only once, during start up and it will be fine again after windows restarts itself.

    Attached is the log
      My Computer


  2. Posts : 14,903
    Windows 10 Pro
       #2

    Hi karljchan,

    Welcome to the 10forums.

    Please fill in your system specs
    Please go to this site and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.
    How to fill in your system specs:





    Diagnostic Test

     DRIVER VERIFIER


    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please read and run driver verifier.

    A windows driver is blamed in the crash, but that usually means that a 3rd party driver is actually the cause.
    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.



    Code:
    IRQL_NOT_LESS_OR_EQUAL (a)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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000000008, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff801b50bdba1, address which referenced memory
    Please Run Memtest86+

    information   Information
    Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip
    Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes in the same session to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask.
      My Computers


  3. Posts : 12
    Microsoft Windows 10 Home Single Language 64-bit 10586 Multiprocessor Free
    Thread Starter
       #3

    Hi axe0,

    Thank you for your assistance. I've updated my system specs as per request.

    I have a question, after running the driver verifier and in the event that a BSOD occurs, what will happen after that? How do I know which driver is causing the crash?

    Also my BSOD's only occur on start up after a shutting down/sleep mode, it is fine on restarts. Should I shut down my pc after running the driver verifier?

    Thank you once again.
      My Computer


  4. Posts : 14,903
    Windows 10 Pro
       #4

    When there is a bluescreen when driver verifier is enabled, there will be a minidump generated automatically and windows will restart.
    When you're back in windows and have disabled driver verifier I need you to use the tool again and upload the zip file.
    In the minidump is most likely the information needed to solve the problem.

    The minidump is located at {windows partition}\Windows\Minidump\, but you can't properly open it without the right software.
      My Computers


  5. Posts : 12
    Microsoft Windows 10 Home Single Language 64-bit 10586 Multiprocessor Free
    Thread Starter
       #5

    I've done as you've said, and uploaded the zip file.

    Cheers!
      My Computer


  6. Posts : 14,903
    Windows 10 Pro
       #6

    The cause of the crash is your network driver: Qualcomm Atheros Extensible Wireless LAN device driver
    Please check your manufacturers site for windows 10 compatible driver updates

    Code:
    3: kd> lmvm athw10xstart             end                 module name
    fffff800`b1710000 fffff800`b1b42000   athw10x  T (no symbols)           
        Loaded symbol image file: athw10x.sys
        Image path: \SystemRoot\System32\drivers\athw10x.sys
        Image name: athw10x.sys
        Timestamp:        Mon May 18 08:33:25 2015 (555987B5)
        CheckSum:         0042668C
        ImageSize:        00432000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computers


 

  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 12:46.
Find Us




Windows 10 Forums