Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BSOD: IRQL_NOT_LESS_OR_EQUAL

Status
Not open for further replies.

bdoub1eu

IS-IT--Management
Dec 10, 2003
440
0
0
US
We have a dell optiplex 270...Fairly new and the last three tuesday's between 11am - 1pm, the machine has blue screened with this blue screen error...I performed an analysis of the dumb and here are the results...I have no idea what it's referring to and I haven't had much experience debugging dumps...Any help would be much appreciated!

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: 00000000, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804f63e1, address which referenced memory

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


READ_ADDRESS: 00000000

CURRENT_IRQL: 1c

FAULTING_IP:
nt!MmPurgeSection+d5
804f63e1 803b02 cmp byte ptr [ebx],0x2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 805334b1 to 804f5471

STACK_TEXT:
effe7c2c 805334b1 0000000a 00000000 0000001c nt!MiUpdateWsle+0x64
effe7c48 806bb2cc 00000000 effe7c9c 00000000 nt!_vsnwprintf+0x69
00000000 00000000 00000000 00000000 00000000 hal!HalpWhackICHUsbSmi+0x10


FOLLOWUP_IP:
nt!MmPurgeSection+d5
804f63e1 803b02 cmp byte ptr [ebx],0x2

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MmPurgeSection+d5

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 3ea80977

STACK_COMMAND: kb

IMAGE_NAME: memory_corruption

BUCKET_ID: 0xA_nt!MmPurgeSection+d5

Followup: MachineOwner
---------


 
I have seen this before. You might try plugging whatever PCI devices you have into different slots.

... also, in the BIOS Setup, make sure that it's set to "Reset configuration data" in the PCI/IRQ section, as well as "Plug and Play OS" = Yes.

Hope this helps!

--Greg
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top