IRQL_NOT_LESS_OR_EQUAL (crash dump)

I'm a new Windows BBS participant, desperate for help with crash problem. My Windows XP system has been crashing at random intervals, 2-3 times a day or more, since it was new. I purchased it last summer. I haven't been able to correlate the crashing with anything I'm doing on the computer, but the problem does seem to occur more often as the room gets warmer.

I recently started collecting complete crash dumps and analyzing them. Every crash seems to be identical. I've included a dump analysis at the end of this post. Can someone with experience interpreting a dump analysis give me any insight into what is happening? I'm ready to start re-installing SW or replacing HW components, if I can get some idea where the problem might be.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {86891078, 2, 1, 804e5108}

Probably caused by : hardware ( nt!KeRemoveQueue+262 )

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

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: 86891078, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804e5108, address which referenced memory

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


WRITE_ADDRESS: 86891078 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
nt!KeRemoveQueue+262
804e5108 108978108986 adc [ecx+0x86891078],cl

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 80556fa6 to 804e5108

MISALIGNED_IP:
nt!KeRemoveQueue+262
804e5108 108978108986 adc [ecx+0x86891078],cl

TRAP_FRAME: ee5b9c28 -- (.trap ffffffffee5b9c28)
ErrCode = 00000002
eax=89000000 ebx=8645b8f8 ecx=00000000 edx=00000001 esi=85f74800 edi=85f74871
eip=804e5108 esp=ee5b9c9c ebp=ee5b9cc0 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!KeRemoveQueue+0x262:
804e5108 108978108986 adc [ecx+0x86891078],cl ds:0023:86891078=??
Resetting default scope

STACK_TEXT:
ee5b9cc0 80556fa6 00000001 ee5b9d01 ee5b9ca8 nt!KeRemoveQueue+0x262
ee5b9d48 804db2b1 000001b4 00c3ff14 00c3ff04 nt!NtRemoveIoCompletion+0xdf
ee5b9d48 7ffe0304 000001b4 00c3ff14 00c3ff04 nt!KiSystemService+0xc4
00c3febc 77f5c024 77e75975 000001b4 00c3ff14 SharedUserData!SystemCallStub+0x4
00c3fec0 77e75975 000001b4 00c3ff14 00c3ff04 ntdll!NtRemoveIoCompletion+0xc
00c3feec 780018b9 000001b4 00c3ff24 00c3ff14 kernel32!GetQueuedCompletionStatus+0x27
00c3ff28 780017e5 00007530 00c3ff78 00c3ff7c RPCRT4!COMMON_ProcessCalls+0x9f
00c3ff90 78001a74 780019d4 0009c948 00000000 RPCRT4!LOADABLE_TRANSPORT:rocessIOEvents+0xfb
00c3ff94 780019d4 0009c948 00000000 00080178 RPCRT4!ProcessIOEventsWrapper+0x9
00c3ffac 780015f3 00007530 77e7d28e 000ce6d0 RPCRT4!BaseCachedThreadRoutine+0x64
00c3ffb4 77e7d28e 000ce6d0 00000000 00080178 RPCRT4!ThreadStartRoutine+0x16
00c3ffec 00000000 780015dd 000ce6d0 00000000 kernel32!BaseThreadStart+0x37


FOLLOWUP_IP:
nt!KeRemoveQueue+262
804e5108 108978108986 adc [ecx+0x86891078],cl

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KeRemoveQueue+262

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .trap ffffffffee5b9c28 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

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

 

FOLLOWUP_IP:
nt!KeRemoveQueue+262
804e5108 108978108986 adc [ecx+0x86891078],cl

MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED

--------------

thats the important bits for this dump. Do they all fall into the ip_misaligned bucket? this is extremely likey to be caused by hardware. get the very latest bios updates. if that doesnt fix it, ram, cpu and motherboard will need to be swapped for testing

 

Thank you very much for your help, Joe.

Yes, they all fall into the ip_misaligned bucket. I'm not surprised that I may have a CPU/RAM/MB problem. I put this system together with parts I bought at Fry's Electronics. Never again! I went through 2 motherboards and 3 CPUs before I found a combination that worked as well as it does now (crashing several times a day).

Do you know of any way I can do additional testing that might narrow down the cause of the problem a bit more?

 

not really, once the cpu subsystem become "unreliable ", not much u can do but swap n test

 

Thanks

Thanks Joe. I'll start swapping.