IRQL_NOT_LESS_OR_EQUAL

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all,

suddenly my Windows Xp Sp2 restart saving a dump.
The error is IRQL_NOT_LESS_OR_EQUAL
Anybody have an idea on how to solve this problem? or suggest me what I can
do to investigate? i suppose it's something hardware but i can't see any
conflict in the Device Manager!
Thanks
 
Thanks Rich,

My motherboard is Asus P5AGD2 Deluxe and my graphic card is Asus N6600
Extreme and I downloaded the last driver by Asus.
I guess I should anylize the minidump windows saves when it restart...but I
don't know how!
 
Thanks Mary,

I read it but maybe it's too difficult for me...and i don't know how to open
a debugging software :)
 
Anyway I tried to upgrade any driver...video...audio...chipset...
But the pc do not restart at fixed intervals....it's totally random!!! it
may happen twice a day....and then it's not going to happen for 2 days....
 
Guess I didn't sove the problem...since the pc just restarted on it's own!
Anybody would be able to analyze my minidump for an advice?
Thanks
 
Kuki, try downloading and installing Motherboard Monitor. It's free and
it will give you a readout of your Power Supply
Voltages 3.3, 5 and 12v rails. They shouldnt dip below 5% of the
Voltage values.
 
Kuki said:
Guess I didn't sove the problem...since the pc just restarted on it's own!
Anybody would be able to analyze my minidump for an advice?
Thanks
Click to expand...

Sounds like it could possibly be a memory problem.
(Usually it *is* a driver problem though.). Try downloading
Memtest86+ from http://www.memtest.org and running it
for a few cycles. Zero errors is the only acceptable result.

-- Bob Day
http://bobday.vze.com
 
Thanks for the advice Bob...i just ran the memory test and always got 0 errors.
Now i'm trying to use verifier.exe but the performance are really slow.
I tried the debugger also but i'm able to use it at all.
Guess it's a driver problem but i can't identify which one!
 
That's what I got from WinDbg....anybody is able to understand what dows it
mean?

Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\Prova*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Oct 16 23:38:24.281 2005 (GMT+2)
System Uptime: 0 days 0:10:25.991
Loading Kernel Symbols
..........................................................................................................................................
Loading unloaded module list
............
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {820, 1e, 1, 804d9e0e}

Probably caused by : NDIS.sys ( NDIS!ndisMIsr+54 )

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: 00000820, memory referenced
Arg2: 0000001e, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804d9e0e, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: 00000820

CURRENT_IRQL: 1e

FAULTING_IP:
nt!KiIpiSend+10
804d9e0e f0099020080000 lock or [eax+0x820],edx

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804e6173 to 804d9e0e

TRAP_FRAME: 805562e8 -- (.trap ffffffff805562e8)
ErrCode = 00000002
eax=00000000 ebx=89089254 ecx=00000000 edx=00000002 esi=00100000 edi=805613f0
eip=804d9e0e esp=8055635c ebp=8055637c iopl=0 nv up ei pl zr na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010247
nt!KiIpiSend+0x10:
804d9e0e f0099020080000 lock or [eax+0x820],edx ds:0023:00000820=????????
Resetting default scope

STACK_TEXT:
80556360 804e6173 89089278 89089254 80556450 nt!KiIpiSend+0x10
8055637c f7972ec8 ffdff9c0 00000000 00000000 nt!KeInsertQueueDpc+0xe8
8055639c 804db90f 8903a008 01089240 00010008 NDIS!ndisMIsr+0x54
8055639c f76b9062 8903a008 01089240 00010008 nt!KiInterruptDispatch+0x45
80556450 804dcbef 00000000 0000000e 00000000 intelppm!AcpiC1Idle+0x12
80556454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10


FOLLOWUP_IP:
NDIS!ndisMIsr+54
f7972ec8 84c0 test al,al

SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: NDIS!ndisMIsr+54

MODULE_NAME: NDIS

IMAGE_NAME: NDIS.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107ec3

STACK_COMMAND: .trap ffffffff805562e8 ; kb

FAILURE_BUCKET_ID: 0xA_W_NDIS!ndisMIsr+54

BUCKET_ID: 0xA_W_NDIS!ndisMIsr+54

Followup: MachineOwner
 
that suggests a network driver problem (NDIS).

Kuki said:
That's what I got from WinDbg....anybody is able to understand what dows
it
mean?

Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is:
SRV*c:\Prova*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Oct 16 23:38:24.281 2005 (GMT+2)
System Uptime: 0 days 0:10:25.991
Loading Kernel Symbols
.........................................................................................................................................
Loading unloaded module list
...........
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {820, 1e, 1, 804d9e0e}

Probably caused by : NDIS.sys ( NDIS!ndisMIsr+54 )

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: 00000820, memory referenced
Arg2: 0000001e, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804d9e0e, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: 00000820

CURRENT_IRQL: 1e

FAULTING_IP:
nt!KiIpiSend+10
804d9e0e f0099020080000 lock or [eax+0x820],edx

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804e6173 to 804d9e0e

TRAP_FRAME: 805562e8 -- (.trap ffffffff805562e8)
ErrCode = 00000002
eax=00000000 ebx=89089254 ecx=00000000 edx=00000002 esi=00100000
edi=805613f0
eip=804d9e0e esp=8055635c ebp=8055637c iopl=0 nv up ei pl zr na po
cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010247
nt!KiIpiSend+0x10:
804d9e0e f0099020080000 lock or [eax+0x820],edx
ds:0023:00000820=????????
Resetting default scope

STACK_TEXT:
80556360 804e6173 89089278 89089254 80556450 nt!KiIpiSend+0x10
8055637c f7972ec8 ffdff9c0 00000000 00000000 nt!KeInsertQueueDpc+0xe8
8055639c 804db90f 8903a008 01089240 00010008 NDIS!ndisMIsr+0x54
8055639c f76b9062 8903a008 01089240 00010008 nt!KiInterruptDispatch+0x45
80556450 804dcbef 00000000 0000000e 00000000 intelppm!AcpiC1Idle+0x12
80556454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10


FOLLOWUP_IP:
NDIS!ndisMIsr+54
f7972ec8 84c0 test al,al

SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: NDIS!ndisMIsr+54

MODULE_NAME: NDIS

IMAGE_NAME: NDIS.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107ec3

STACK_COMMAND: .trap ffffffff805562e8 ; kb

FAILURE_BUCKET_ID: 0xA_W_NDIS!ndisMIsr+54

BUCKET_ID: 0xA_W_NDIS!ndisMIsr+54

Followup: MachineOwner
Click to expand...
 
Does this only happen at start-up or can it happen when you insert or remove
a USB.
What virus/spyware software do you have installed?
 
IMHO this means a buggy driver (not nesessarily netcard or hardware at all)
that causes system failure.
Without knowing what h/w you have it's hard to tell more.

Regards,
--PA

Kuki said:
That's what I got from WinDbg....anybody is able to understand what dows it
mean?

Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\Prova*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Oct 16 23:38:24.281 2005 (GMT+2)
System Uptime: 0 days 0:10:25.991
Loading Kernel Symbols
........................................................................................................................................
Loading unloaded module list
...........
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {820, 1e, 1, 804d9e0e}

Probably caused by : NDIS.sys ( NDIS!ndisMIsr+54 )

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: 00000820, memory referenced
Arg2: 0000001e, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804d9e0e, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: 00000820

CURRENT_IRQL: 1e

FAULTING_IP:
nt!KiIpiSend+10
804d9e0e f0099020080000 lock or [eax+0x820],edx

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804e6173 to 804d9e0e

TRAP_FRAME: 805562e8 -- (.trap ffffffff805562e8)
ErrCode = 00000002
eax=00000000 ebx=89089254 ecx=00000000 edx=00000002 esi=00100000 edi=805613f0
eip=804d9e0e esp=8055635c ebp=8055637c iopl=0 nv up ei pl zr na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010247
nt!KiIpiSend+0x10:
804d9e0e f0099020080000 lock or [eax+0x820],edx ds:0023:00000820=????????
Resetting default scope

STACK_TEXT:
80556360 804e6173 89089278 89089254 80556450 nt!KiIpiSend+0x10
8055637c f7972ec8 ffdff9c0 00000000 00000000 nt!KeInsertQueueDpc+0xe8
8055639c 804db90f 8903a008 01089240 00010008 NDIS!ndisMIsr+0x54
8055639c f76b9062 8903a008 01089240 00010008 nt!KiInterruptDispatch+0x45
80556450 804dcbef 00000000 0000000e 00000000 intelppm!AcpiC1Idle+0x12
80556454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10


FOLLOWUP_IP:
NDIS!ndisMIsr+54
f7972ec8 84c0 test al,al

SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: NDIS!ndisMIsr+54

MODULE_NAME: NDIS

IMAGE_NAME: NDIS.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107ec3

STACK_COMMAND: .trap ffffffff805562e8 ; kb

FAILURE_BUCKET_ID: 0xA_W_NDIS!ndisMIsr+54

BUCKET_ID: 0xA_W_NDIS!ndisMIsr+54

Followup: MachineOwner
Click to expand...
 
Kuki said:
Thanks for the advice Bob...i just ran the memory test and always got 0 errors.
Now i'm trying to use verifier.exe but the performance are really slow.
I tried the debugger also but i'm able to use it at all.
Guess it's a driver problem but i can't identify which one!
Click to expand...

Try moving USB devices to another port or unplug them.

do you use a USB modem?
 
Back
Top