 |  |
| |
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows 7. The Windows 7 forum also covers news and updates and has an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.
Windows 7 - IRQL Not Less Or Equal
| |
| 10-30-2010 | #1 |
| | IRQL Not Less Or Equal In different ocaciones it has given me this problem. Bluescreen: - 0x0000000A - 0xFFFF7FFFFFFFE0, 0x0 ... 2, 0x0 ... 1 - 0xFFFFF80002b1c8349 Please, help. Intel Core2Quad Q9400 4Gb RAM (2x2Gb) 1333Mhz DDR3 Kingston M/B Gigabyte G41M-Combo |
My System Specs |
| 10-30-2010 | #2 |
| | 
Quote: Originally Posted by infrn  In different ocaciones it has given me this problem. Bluescreen: - 0x0000000A - 0xFFFF7FFFFFFFE0, 0x0 ... 2, 0x0 ... 1 - 0xFFFFF80002b1c8349 Please, help. Intel Core2Quad Q9400 4Gb RAM (2x2Gb) 1333Mhz DDR3 Kingston M/B Gigabyte G41M-Combo Memory corruption probably caused by a driver. Test the memory with memtest. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. 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. Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\103010-20061-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a65000 PsLoadedModuleList = 0xfffff800`02ca2e50
Debug session time: Sat Oct 30 19:30:08.115 2010 (GMT-4)
System Uptime: 0 days 0:10:28.722
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffee7fffffffe0, 2, 1, fffff80002b1c349}
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )
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: ffffee7fffffffe0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002b1c349, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0d0e0
ffffee7fffffffe0
CURRENT_IRQL: 2
FAULTING_IP:
nt!MmZeroPageThread+3d4
fffff800`02b1c349 f0410fba6d1000 lock bts dword ptr [r13+10h],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880009a9a40 -- (.trap 0xfffff880009a9a40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000004a rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b1c349 rsp=fffff880009a9bd0 rbp=00000000000000ff
r8=0000000000000000 r9=0000058000000000 r10=0000000000000002
r11=0000000000000009 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!MmZeroPageThread+0x3d4:
fffff800`02b1c349 f0410fba6d1000 lock bts dword ptr [r13+10h],0 ds:c040:00000000`00000010=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ad4ca9 to fffff80002ad5740
STACK_TEXT:
fffff880`009a98f8 fffff800`02ad4ca9 : 00000000`0000000a ffffee7f`ffffffe0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009a9900 fffff800`02ad3920 : 00000000`00000000 ffffffbf`ffffffff 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009a9a40 fffff800`02b1c349 : fffffa80`03902800 00000000`00000008 00000000`000000ff 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009a9bd0 fffff800`02d79c06 : fffffa80`039ec040 00000000`00000080 fffffa80`03973890 fffff800`02ab3c19 : nt!MmZeroPageThread+0x3d4
fffff880`009a9d00 fffff800`02ab3c26 : fffff800`02c4fe80 fffffa80`039ec040 fffff800`02c5dc40 0003b519`0003b498 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9970 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MmZeroPageThread+3d4
fffff800`02b1c349 f0410fba6d1000 lock bts dword ptr [r13+10h],0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MmZeroPageThread+3d4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MmZeroPageThread+3d4
BUCKET_ID: X64_0xA_nt!MmZeroPageThread+3d4
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: ffffee7fffffffe0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002b1c349, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: ffffee7fffffffe0
CURRENT_IRQL: 2
FAULTING_IP:
nt!MmZeroPageThread+3d4
fffff800`02b1c349 f0410fba6d1000 lock bts dword ptr [r13+10h],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880009a9a40 -- (.trap 0xfffff880009a9a40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000004a rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b1c349 rsp=fffff880009a9bd0 rbp=00000000000000ff
r8=0000000000000000 r9=0000058000000000 r10=0000000000000002
r11=0000000000000009 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!MmZeroPageThread+0x3d4:
fffff800`02b1c349 f0410fba6d1000 lock bts dword ptr [r13+10h],0 ds:c040:00000000`00000010=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ad4ca9 to fffff80002ad5740
STACK_TEXT:
fffff880`009a98f8 fffff800`02ad4ca9 : 00000000`0000000a ffffee7f`ffffffe0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009a9900 fffff800`02ad3920 : 00000000`00000000 ffffffbf`ffffffff 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009a9a40 fffff800`02b1c349 : fffffa80`03902800 00000000`00000008 00000000`000000ff 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009a9bd0 fffff800`02d79c06 : fffffa80`039ec040 00000000`00000080 fffffa80`03973890 fffff800`02ab3c19 : nt!MmZeroPageThread+0x3d4
fffff880`009a9d00 fffff800`02ab3c26 : fffff800`02c4fe80 fffffa80`039ec040 fffff800`02c5dc40 0003b519`0003b498 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9970 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MmZeroPageThread+3d4
fffff800`02b1c349 f0410fba6d1000 lock bts dword ptr [r13+10h],0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MmZeroPageThread+3d4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MmZeroPageThread+3d4
BUCKET_ID: X64_0xA_nt!MmZeroPageThread+3d4
Followup: MachineOwner
--------- |
| My System Specs |
 |
IRQL Not Less Or Equal problems?
| Thread Tools | |
| Similar Threads for: IRQL Not Less Or Equal | ||||
| Thread | Forum | |||
| IRQL not less or Equal | Crashes and Debugging | |||
| IRQL is less than or not equal | Crashes and Debugging | |||
| Irql not less or equal! Help! | Crashes and Debugging | |||
| IRQL Less than Equal | Crashes and Debugging | |||
| irql not less or equal | Crashes and Debugging | |||
All times are GMT -5. The time now is 03:50 PM.
