1. #1

    BSOD Memory Management/irql_not_less_or_equal

    Running 64bit Win7 Ultimate, fresh install yet I get these errors :|DriverList.txtEventApp.txtHosts.txtSystemInfo.txtDriverList.txtEventApp.txtHosts.txt
    Unsure of which .txt or .dmp documents you guys need :/

    • Ad Bot



  2. #2

    Re: BSOD Memory Management/irql_not_less_or_equal


    Please refer to the following and reply back accordingly with the required information - http://www.sysnative.com/forums/bsod...ows-vista.html



  3. #3

    Re: BSOD Memory Management/irql_not_less_or_equal

    Quote Originally Posted by Patrick View Post

    Please refer to the following and reply back accordingly with the required information - http://www.sysnative.com/forums/bsod...ows-vista.html


    Hope the following is correct. Sorry about the previous postreports.zip

  4. #4

    Re: BSOD Memory Management/irql_not_less_or_equal

    It's not a problem.

    Did you run the app? It didn't appear to put the crash dumps in the folder.

    Navigate to C:\Windows\Minidump and zip up and manually attach any there.



  5. #5

    Re: BSOD Memory Management/irql_not_less_or_equal

    Yeah I ran the app, strange how they wasn't included.

    I had some issues with file permissions in C:\Windows\Minidump so I had to turn off UAC.

    Attached is the .zip of all my .dmp files in the above folder.




  6. #6

    Re: BSOD Memory Management/irql_not_less_or_equal

    Thanks a lot, Jamie!

    We have two consistent bug checks:


    This indicates that a severe memory management error occurred.

    BugCheck 1A, {41287, 18, 0, 0}

    - The 1st parameter of the bug check is 41287 which indicates an illegal page fault occurred while holding working set synchronization.


    This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

    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.

    1. Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes as it may be causing conflicts:

    avast! removal - avast! Uninstall Utility | Download aswClear for avast! Removal

    MSE - Microsoft Security Essentials - Microsoft Windows

    2. If you're still crashing after the above, please run Memtest for NO LESS than ~8 passes (several hours):


    Download Memtest86+ here:

    Memtest86+ - Advanced Memory Diagnostic Tool

    Which should I download?

    You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

    Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

    How Memtest works:

    Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

    The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

    Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

    Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

    This information, if available to the program, can be displayed via a menu option.

    Any other questions, they can most likely be answered by reading this great guide here:

    FAQ : please read before posting



Similar Threads

  1. Attempted Execute of noexecute memory BSOD
    By JDH2334 in forum BSOD, Crashes, Kernel Debugging
    Replies: 6
    Last Post: 10-28-2013, 04:41 PM
  2. BSOD - IRQL_Not_less_or_equal - SFC stopping
    By RodgerE1 in forum BSOD, Crashes, Kernel Debugging
    Replies: 3
    Last Post: 06-18-2013, 12:57 PM
    By Nobodies in forum BSOD, Crashes, Kernel Debugging
    Replies: 1
    Last Post: 06-03-2013, 04:12 PM
  4. BSOD acer V3 571G irql_not_less_or_equal
    By Petdunmor in forum BSOD, Crashes, Kernel Debugging
    Replies: 4
    Last Post: 02-13-2013, 09:48 AM
  5. Several BSOD's, memory problem? 0x109 - Windows 7 x64
    By Draggoth in forum BSOD, Crashes, Kernel Debugging
    Replies: 7
    Last Post: 01-22-2013, 03:17 PM

Log in

Log in