IRQL_NOT_LESS_OR_EQUAL

[dev]

Typhoid said:

This BSOD comes up every day or so when I strike certain
keys on my keyboard (caps lock, tab, down arrow, etc),
independent of which applications are running.

I have a Toshiba Satellite 2410 running under XP-Pro.

Running WinDbg on the memory dump gives the following
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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write
operation
Arg4: 804f819c, address which referenced memory

My PCI bus memory range includes 804f819c. The PCI bus
driver appears up to date:
Microsoft
1/07/2001
5.1.2600.0
Microsoft Windows Publisher

I am thinking that it may be a hardware problem.

Could be. Look here for more clues...
http://aumha.org/win5/kbestop.htm

 

[Typhoid]

This BSOD comes up every day or so when I strike certain
keys on my keyboard (caps lock, tab, down arrow, etc),
independent of which applications are running.

I have a Toshiba Satellite 2410 running under XP-Pro.

Running WinDbg on the memory dump gives the following
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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write
operation
Arg4: 804f819c, address which referenced memory

My PCI bus memory range includes 804f819c. The PCI bus
driver appears up to date:
Microsoft
1/07/2001
5.1.2600.0
Microsoft Windows Publisher

I am thinking that it may be a hardware problem.

Help!

 

[James Martin]

Hmm, you could try not using those keys

Most likely bad RAM, but it could be something else. Check out this link:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn
ol/winxppro/reskit/prmd_stp_hwpg.asp

Run down to best buy and buy some ram, test it out, and if that's the
problem order some ram from pricewatch.com and return the Best Buy
overpriced crap. (In a pinch I had to by a firewire cable there--$30,
pricewatch--$5...)

-James

 

[Typhoid]

Hmm, you could try not using those keys

Most likely bad RAM, but it could be something else. Check out this link:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn
ol/winxppro/reskit/prmd_stp_hwpg.asp

Run down to best buy and buy some ram, test it out, and if that's the
problem order some ram from pricewatch.com and return the Best Buy
overpriced crap. (In a pinch I had to by a firewire cable there--$30,
pricewatch--$5...)

New RAM is a good idea. Even if that's not the problem, you can never
have too much RAM (much like many other things in life)!

Thanks mate.