Irql_not_less_or_equal

Hi asx,

The culprit is yk51x86.sys and it is the NDIS5.1 32-bit Miniport driver. This module is upgraded recently. Why do you upgrade this device driver. I also find you upgrade the following driver.

yk51x86 yk51x86.sys Wed Jul 20 20:19:18 2005 (42DE4146)
ati2mtag ati2mtag.sys Wed Aug 31 10:42:34 2005 (4315191A)
iteraid iteraid.sys Fri May 13 15:31:56 2005 (428457EC)
LHidKE LHidKE.Sys Sat May 21 06:01:30 2005 (428E5E3A)
LHidUsbK LHidUsbK.Sys Sat May 21 06:00:57 2005 (428E5E19)
LMouKE LMouKE.Sys Sat May 21 06:01:24 2005 (428E5E34)

The following modules are deleted
hidusb.sys, sr.sys, sfmanm.sys, redbook.sys, imapi.sys, gameenum.sys, Fastfat.SYS and emu10k1m.sys

Unable to load image yk51x86.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for yk51x86.sys
*** ERROR: Module load completed but symbols could not be loaded for yk51x86.sys
Probably caused by : yk51x86.sys ( yk51x86+c835 )

BugCheck 100000D1, {0, 2, 0, aa219e7b}
Unable to load image yk51x86.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for yk51x86.sys
*** ERROR: Module load completed but symbols could not be loaded for yk51x86.sys
Probably caused by : yk51x86.sys ( yk51x86+c835 )

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: aa219e7b, address which referenced memory

Debugging Details:
------------------
READ_ADDRESS: 00000000
CURRENT_IRQL: 2

FAULTING_IP:
tcpip!TCPSendComplete+92
aa219e7b 8b36 mov esi,[esi]

CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from aa21968e to aa219e7b

STACK_TEXT:
f7c5abe4 aa21968e 855da088 855da020 00000000 tcpip!TCPSendComplete+0x92
f7c5ac1c aa21981d 862d60d0 00592228 00000000 tcpip!IPSendComplete+0x126
f7c5ac40 f7668c1c 861a7008 85569364 00000000 tcpip!ARPSendComplete+0xf6
f7c5ac64 f711fb69 86218ad0 85592228 00000000 NDIS!ndisMSendCompleteX+0x8d
f7c5ac84 f7668c1c 86008310 01592228 00000000 psched!ClSendComplete+0x67
f7c5aca8 f71ca835 86333848 85592228 00000000 NDIS!ndisMSendCompleteX+0x8d
WARNING: Stack unwind information not available. Following frames may be wrong.
f7c5acc8 f71c5c11 860a1004 860a1004 00000000 yk51x86+0xc835
f7c5ad04 f71c71ea 680a1004 f7c5ad28 f766bf09 yk51x86+0x7c11
f7c5ad10 f766bf09 860a1004 80560f00 f7ac79c0 yk51x86+0x91ea
f7c5ad28 804dcd22 860a1088 860a1074 00000000 NDIS!ndisMDpcX+0x21
f7c5ad50 804dcc07 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
f7c5ad54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28

FOLLOWUP_IP:
yk51x86+c835
f71ca835 ?? ???

SYMBOL_STACK_INDEX: 6
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: yk51x86+c835
MODULE_NAME: yk51x86
IMAGE_NAME: yk51x86.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 42de4146
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0xD1_yk51x86+c835
BUCKET_ID: 0xD1_yk51x86+c835

Hi asx,

After you upgrade the logitech Usb driver, do you still get the blue screen?

I did update my Network Card driver (the yk bla bla .sys ) but i look for NDIS driver and i dint find anything on google :/

My laptop also crashes...

... but only when running in battery. When I boot on AC everything seems fine but when i unplug the cable I get a BSOD. The minidump is attached. I dont think it is a RAM problem cause when i boot in safe mode (battery) everything works fine. I someone can help me please drop a post...

Try "Last known Good Configuration"

Hi Alas,

One minidump is insufficient to diagnostic your problem. Zip 5 to 6 minidumps and attach them here.

I never had a LAst Know configuration...
Last time its work ok was 7 month ago.

Heres some new dump after i updated my drivers

Hi Asx,

Your original problem re-occurs again and it seems that Microsoft recommendation does not work. Do you install any new software at your windows?


Debug report
=========
Debug session time: Sat Oct 8 09:26:14.671 2005 (GMT+8)
System Uptime: 4 days 0:25:37.360
BugCheck 1000000A, {820, 1e, 1, 804d9e0e}
Probably caused by : NDIS.sys ( NDIS!ndisMIsr+54 )

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

CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from 804e6173 to 804d9e0e

STACK_TEXT:
f7c5ac60 804e6173 855180ac 85518088 f7c5ad50 nt!KiIpiSend+0x10
f7c5ac7c f7645ec8 f7ac79c0 00000000 00000000 nt!KeInsertQueueDpc+0xe8
f7c5ac9c 804db90f 861d1610 01518074 01010006 NDIS!ndisMIsr+0x54
f7c5ac9c f7a31062 861d1610 01518074 01010006 nt!KiInterruptDispatch+0x45
f7c5ad50 804dcbef 00000000 0000000e 00000000 intelppm!AcpiC1Idle+0x12
f7c5ad54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10

FOLLOWUP_IP:
NDIS!ndisMIsr+54
f7645ec8 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: kb
FAILURE_BUCKET_ID: 0xA_W_NDIS!ndisMIsr+54
BUCKET_ID: 0xA_W_NDIS!ndisMIsr+54

Hello and welcome to Techspot.

Your mindump crashes at amdk7.sys. This is part of the power throttling of your cpu.

The fact that you only get the problem when running from battery, would suggest that your battery is not providing enough power.

Try getting a new battery. If that doesn`t work, then maybe your charger isn`t charging the battery properly.

Regards Howard :wave: :wave:

sounds like a USB power problem - either over or undervoltage.

Tedster my problem or the guy with the laptop ?

cpc2004's problem

I got a different BOSD msg today...

Hi asx,

One minidump is crashed at ATI display driver and you installed ATI display card at this month. Your version of ATI display card driver is unstable and some forum recommend to omegadrive.

Another minidump is the old problem and you reported the problem to Microsoft. Microsoft's feedback is device driver error and you don't tell me what is the Microsoft's recommendation. Why the problem is still existed?

Microsoft doesnt recommend anything...

update your driver then

It could be an issue of overheating as well. Make sure that your CPU's heatsink isn't clogged. Processors do funny things when they get heat stroke..

IRQL_NOT_LESS_OR_EQUAL

http://www.tweaksforgeeks.com/IRQL_NOT_LESS_OR_EQUAL.html

Here a new bosd ,

your minidump couldn't be opened.