Random BSOD , IRQL_NOT_LESS_OR_EQUAL (a)


  1. zigzag441104
    Posts : 1
    Windows 7 64 bit
       New #1

    Random BSOD , IRQL_NOT_LESS_OR_EQUAL (a)


    Hi! I got some BSOD now every day when i play or just watching movies or internet. I have 2 ssd hardrives in raid 0 mode .I need help and i have trayed to read the minidump files.

    HERE IS THE FIRST ONE:

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 1000000A, {f0e4dff0, 2, 1, 80514490}
    Probably caused by : memory_corruption ( nt!MiCompleteProtoPteFault+30 )
    Followup: MachineOwner
    ---------
    2: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    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: f0e4dff0, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, 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: 80514490, address which referenced memory
    Debugging Details:
    ------------------

    WRITE_ADDRESS: f0e4dff0
    CURRENT_IRQL: 2
    FAULTING_IP:
    nt!MiCompleteProtoPteFault+30
    80514490 834e0c08 or dword ptr [esi+0Ch],8
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: DRIVER_FAULT
    BUGCHECK_STR: 0xA
    PROCESS_NAME: RpcSandraSrv.ex
    LAST_CONTROL_TRANSFER: from 80515dc6 to 80514490
    STACK_TEXT:
    b325ec68 80515dc6 00000000 00435080 c00021a8 nt!MiCompleteProtoPteFault+0x30
    b325ece0 8051fdf6 e132c1f0 00435080 c00021a8 nt!MiDispatchFault+0x636
    b325ed4c 80543810 00000008 00435080 00000001 nt!MmAccessFault+0x111c
    b325ed4c 00435080 00000008 00435080 00000001 nt!KiTrap0E+0xd0
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0231f7dc 00000000 00000000 00000000 00000000 0x435080

    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nt!MiCompleteProtoPteFault+30
    80514490 834e0c08 or dword ptr [esi+0Ch],8
    SYMBOL_STACK_INDEX: 0
    SYMBOL_NAME: nt!MiCompleteProtoPteFault+30
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    DEBUG_FLR_IMAGE_TIMESTAMP: 4b7a91dc
    IMAGE_NAME: memory_corruption
    FAILURE_BUCKET_ID: 0xA_nt!MiCompleteProtoPteFault+30
    BUCKET_ID: 0xA_nt!MiCompleteProtoPteFault+30
    Followup: MachineOwner
    ---------

    HERE IS THE OTHER:
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 1000000A, {0, 2, 1, 805219f0}
    Probably caused by : memory_corruption ( nt!MiRemovePageByColor+66 )
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    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: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, 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: 805219f0, address which referenced memory
    Debugging Details:
    ------------------

    WRITE_ADDRESS: 00000000
    CURRENT_IRQL: 2
    FAULTING_IP:
    nt!MiRemovePageByColor+66
    805219f0 ff08 dec dword ptr [eax]
    CUSTOMER_CRASH_COUNT: 2
    DEFAULT_BUCKET_ID: DRIVER_FAULT
    BUGCHECK_STR: 0xA
    PROCESS_NAME: System
    LAST_CONTROL_TRANSFER: from 80521f1a to 805219f0
    STACK_TEXT:
    b84c37f4 80521f1a 0005f05c 00000000 00000000 nt!MiRemovePageByColor+0x66
    b84c380c 8051be1f 00000000 00008000 00000000 nt!MiRemoveAnyPage+0xbc
    b84c3840 80696b94 8a32a680 00000000 00000044 nt!MmZeroPageThread+0x153
    b84c3dac 805ce85c 80087000 00000000 00000000 nt!Phase1Initialization+0x1288
    b84c3ddc 8054537e 8069590c 80087000 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nt!MiRemovePageByColor+66
    805219f0 ff08 dec dword ptr [eax]
    SYMBOL_STACK_INDEX: 0
    SYMBOL_NAME: nt!MiRemovePageByColor+66
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    DEBUG_FLR_IMAGE_TIMESTAMP: 4b7a91dc
    IMAGE_NAME: memory_corruption
    FAILURE_BUCKET_ID: 0xA_nt!MiRemovePageByColor+66
    BUCKET_ID: 0xA_nt!MiRemovePageByColor+66
    Followup: MachineOwner
    ---------
    I hope somebody can help me!



    I have done the memtest 100% OK! I run the ccleaner and antivirus check on every hdd nothing. I have upgrade all drivers to the latest new, and still nothing. The screen crash random with the attached picture.I tray to find the dump files to read, but i cant find them. I check the derictory where is they and everyting is ok they must be in the C/windows/minidump. I dont have any minidumps after crash!
    Last edited by zigzag441104; 19 Feb 2012 at 14:56. Reason: still crashing random and no have dump files
      My Computer
    Quote Quote

  3. zigzag3143
    Posts : 28,845
    Win 8 Release candidate 8400
       New #2

    Nice User name



    These crashes were caused by memory corruption/exception (probably a driver).
    Please run these two tests to verify your memory and find which driver is causing the problem.

    * If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!

    * If you have raid update its Driver.



    Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    RAM - Test with Memtest86+



    Driver verifier

    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen.
    Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
    The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
    If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
      My Computer
    Quote Quote

 

  Related Discussions
Irql_Not_Less_or_Equal bsod? Random
in BSOD Help and Support

So I have had this issue for a couple of months now but I rarely use windows. This bsod first started when clicking on things before the system had completely gotten up and running but now I can just let it sit and it will go. It's very random sometimes it will go through stress tests and not doing...
Having trouble with random BSOD and shut downs, please help. Thanks in advance.
Random BSOD (IRQL_NOT_LESS_OR_EQUAL)
in BSOD Help and Support

I've been getting random BSOD all the time, but it only happens every month or so, so I ignored it. But these few BSOD happened often and recently when I was gaming with Skype on. It doesn't happen when I don't have Skype on. But I don't think that's the case. I'm wondering how to fix this. My...
Just got this PC custom built around the end february. BSoD appears after I run the pc for a while. Replacing RAM didnt fix the problem so Im kinda leaning towards a driver problem. Downloaded a few driver checkers and downloaded updates(in safe mode) for drivers but when I go to install (back in...
Hello i have noticed Recently that i have been Getting a BSOD i had about 3 Today i have a program called Who Crashed to analyze my Dump Files i will also include BSOD Dump & System File Collection app Files etc PC is about 3 years old (so is all the hardware except the GFX card is like 1 year...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 09:41.
Find Us