Windows 10: irql not less or equal BSOD

  1.    26 Oct 2015 #1

    irql not less or equal BSOD


    I've been having this problem for a while now, random BSODs giving the IRQL not less or equal message. It happens at random times, and doesn't seem to be tied to any particular action.
      My ComputerSystem Spec


  2. Posts : 11,830
    Windows 10 Pro
       26 Oct 2015 #2

    Hi abccormac,

    Welcome to the 10forums.

    Please disconnect every USB device, except for mouse and keyboard.
    Please uninstall Google Chrome while troubleshooting.
    Please remove / disable items from the startup in taskmanager
    These programs could interfere with the boot process giving you trouble and increase the boot time.

    The 0xA, 0xD1 and some 0x3B are speaking of memory corruption.
    This has 2 sides
    • A driver tried to access corrupted data from the memory
    • A driver tried to access a wrong/invalid address from the memory

    Please test your memory using MemTest86+
    If MemTest86+ gives a final result of zero errors, run driver verifier



    irql not less or equal BSOD Diagnostic Test irql not less or equal BSOD
     RAM TEST

    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note


    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.




    irql not less or equal BSOD Diagnostic Test irql not less or equal BSOD
     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 follow this tutorial to run driver verifier.

    Some windows drivers are blamed in a few crashes, 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: fffff68001301658, 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: fffff80145e10670, address which referenced memory
    Code:
    BugCheck 3B, {c0000005, fffff80114090e8d, ffffd000266158a0, 0}
    
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    ---------
    
    Processing initial command '!analyze -v; !
    2: kd> !analyze -v; !
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff80114090e8d, Address of the instruction which caused the bugcheck
    Arg3: ffffd000266158a0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    Code:
    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: 0000000000000002, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff801aeb40e58, address which referenced memory
      My ComputersSystem Spec

  3.    28 Oct 2015 #3

    Thanks very much, sorry for the delay in responding, been a bit busy here. I've run memtest, and it comes back clear. I've got driver verifier running now, I'm just wondering what I should do now? Just leave it running and use the computer normally until I experience a bluescreen?
      My ComputerSystem Spec


  4. Posts : 11,830
    Windows 10 Pro
       28 Oct 2015 #4

    Use the computer less then normal as the performance could be horrible bad.
      My ComputersSystem Spec

  5.    29 Oct 2015 #5

    I've had driver verifier running for 24 hours now without any crashes. The computer also seems to be running normally with no noticable slowdown. I've checked to make sure verifier is actually running by launching it and checking display existing settings and it appears to be running correctly. The stupid machine won't crash now that I want it to!
      My ComputerSystem Spec


  6. Posts : 11,830
    Windows 10 Pro
       29 Oct 2015 #6

    Give it another 24h as instructed.
      My ComputersSystem Spec


 

Related Threads
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...
I am getting a BSOD with 2 different errors (what it's shown me so far): "IRQL not less or equal to" and also "Driver_Irql not less or equal to". I am using Windows 10. My upgrade was about a month ago. I use this Alienware M17XR3 laptop to mostly...
BSOD irql not less or equal in BSOD Crashes and Debugging
Upgraded Win 7 Pro Dell laptop to Win 10 Pro. Screen resolution changed on first win 10 boot and other resolutions greyed out. Windows update says unable to update Intel HD graphics drivers. Downloaded win 10 drivers from Intel site and...
Hi, I am sorry, but I couldn't post a debug-YourComputerName-xxxx.zip file because I am currently unable to use my computer. But anyway, I originally posted this question on another answer website, and somebody started helping me and then...
BSOD IRQL less than or equal to error in BSOD Crashes and Debugging
HI, Since upgrading from 8.1 to 10 my PC often blue screens with the IRQL less than or equal to error. It appears to happen more often that not if i have sound playing at the time. I have upgraded all of my drivers to the latest ones and even on...
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 00:42.
Find Us