Windows Auto Reboot IRQL_NOT_LESS_OR_EQUAL

G

Guest

Hi all,
my windows xp Pro Sp2 keep restarting at random intervals with the error
IRQL_NOT_LESS_OR_EQUAL.
I tried to analyze my MEMORY.DMP file with Windows Debugger but I can't
understand the results at all...anybody can help please? Thanks!
Here it's the results from debugger:

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
 
R

Rick \Nutcase\ Rogers

Hi,

Troubleshooting a Stop 0x0000000A Error in Windows XP [Q314063]
http://support.microsoft.com/?kbid=314063

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

Kuki said:
Hi all,
my windows xp Pro Sp2 keep restarting at random intervals with the error
IRQL_NOT_LESS_OR_EQUAL.
I tried to analyze my MEMORY.DMP file with Windows Debugger but I can't
understand the results at all...anybody can help please? Thanks!
Here it's the results from debugger:

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...
 
G

Guest

Thanks Rick,

but i can't find anything interesting on this link.
I think I should find which is the driver causing the problem...do you think
it's possible from those information?
I tried to upload any driver on my computer already!...could be related to
bad DDR modules?
Thanks

Rick "Nutcase" Rogers said:
Hi,

Troubleshooting a Stop 0x0000000A Error in Windows XP [Q314063]
http://support.microsoft.com/?kbid=314063

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

Kuki said:
Hi all,
my windows xp Pro Sp2 keep restarting at random intervals with the error
IRQL_NOT_LESS_OR_EQUAL.
I tried to analyze my MEMORY.DMP file with Windows Debugger but I can't
understand the results at all...anybody can help please? Thanks!
Here it's the results from debugger:

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...
Click to expand...
 
R

Rick \Nutcase\ Rogers

You need to follow the troubleshooting steps in the article: Removing
peripherals, changing CMOS settings, testing simms, etc. All the arguments
tell us is the memory location that was holding the instructions that were
bad. They don't tell us what device driver made the bad call.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

Kuki said:
Thanks Rick,

but i can't find anything interesting on this link.
I think I should find which is the driver causing the problem...do you
think
it's possible from those information?
I tried to upload any driver on my computer already!...could be related to
bad DDR modules?
Thanks

Rick "Nutcase" Rogers said:
Hi,

Troubleshooting a Stop 0x0000000A Error in Windows XP [Q314063]
http://support.microsoft.com/?kbid=314063

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

Kuki said:
Hi all,
my windows xp Pro Sp2 keep restarting at random intervals with the
error
IRQL_NOT_LESS_OR_EQUAL.
I tried to analyze my MEMORY.DMP file with Windows Debugger but I can't
understand the results at all...anybody can help please? Thanks!
Here it's the results from debugger:

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...
Click to expand...
Click to expand...
 
G

Guest

Probelm solved.
I guess it was the PCI Ethernet card I added...or something wrong with it's
IRQ, because I just tried to use the built in network card of my motherboard
and everything is fine!
:)

Rick "Nutcase" Rogers said:
You need to follow the troubleshooting steps in the article: Removing
peripherals, changing CMOS settings, testing simms, etc. All the arguments
tell us is the memory location that was holding the instructions that were
bad. They don't tell us what device driver made the bad call.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

Kuki said:
Thanks Rick,

but i can't find anything interesting on this link.
I think I should find which is the driver causing the problem...do you
think
it's possible from those information?
Arg1: 00000820, memory referenced
Arg2: 0000001e, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804d9e0e, address which referenced memory
Click to expand...

I tried to upload any driver on my computer already!...could be related to
bad DDR modules?
Thanks

Rick "Nutcase" Rogers said:
Hi,

Troubleshooting a Stop 0x0000000A Error in Windows XP [Q314063]
http://support.microsoft.com/?kbid=314063

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

Hi all,
my windows xp Pro Sp2 keep restarting at random intervals with the
error
IRQL_NOT_LESS_OR_EQUAL.
I tried to analyze my MEMORY.DMP file with Windows Debugger but I can't
understand the results at all...anybody can help please? Thanks!
Here it's the results from debugger:

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...
Click to expand...
Click to expand...
 
E

Enkidu

Kuki said:
Probelm solved.
I guess it was the PCI Ethernet card I added...or something wrong with it's
IRQ, because I just tried to use the built in network card of my motherboard
and everything is fine!
:)
Click to expand...
Great! Incidentally, whenever one of these
IRQL_NOT_LESS_OR_EQUAL things comes up, I've often wanted to
reply "Well, set your IRQL to LESS_OR_EQUAL then!", but I
don't think that the (tiny amount of) humour would be
appreciated......

Cheers,

Cliff
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

dump file any thoughts on this? 8
BSOD and random restarts 1
Bug Check - Reboot 4
Windows XP Win2k3 stop error 0xa 1
Weird Blue Screens -- Need Advice on Next Step 0
Server Restarted with Mini dump 3
Can not boot to SAFE MODE, STOP ERROR 10
STOP 0XD1 Error on XP SP2 2

Top