irq not less than equal, blue screen reboots, frequent problems

Hi,

I am having computer reboots/crashes every day now, details as follows:

using-

intel p4 2.8ghz ht
gigabyte 8knxp ultra rev 1.0 motherboard latest bios
integrated devices on mboard-
-5.1 soundcard realtek/gigabyte
-10/1000mbps intel lan

ati all in wonder 9700 pro 128mb ram 8x agp
-dvi output used
1024mb ddr ram kingston (4 sticks x256)
sata 120gb hd smart enabled
pide 250gb hd smart enabled

power supply 600watts (calculator states usage = 345watts)

usb keyboard connected via ps/2 kvm switch to computer
(using usb to ps/2 adapter)

software- norton internet sec 2005

Cpu temp runs at 40 deg celcius normal, but upon reaching 60 deg cel (cpu intensive applications used) crashing occurs,

tested ram with 9 passes no errors

xp pro (clean install) service pack 1 (tried service pack 2 before)

Computer crashed whilst clean install of xp also, never happened before.

also crashed using prime 95 on torture test 2 (passed 1st test) temp was over 60

I get irq not less than equal, stop 0x000007...
computer rebooted because of a bug check:

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000c, 0x00000002, 0x00000000, 0xbafa6f65).

I have checked the minidumps and suspected a new sound card (cm media) which I uninstalled and removed, after installing old sound card again. still crashing.

recently upgraded ram from 512mb to 1024 (added 2 stick of 256)
replaced power supply from 350w to 600w
added pide 250 gb hd

Please note that the crashing occurred even before the above upgrades, which is why I clean installed xp pro, however problems still occur.

Please could someone look at the minidumps and advise, any help would be appreciated.

thanks.

Hi imed,

Your windows is memory corruption which is related to faulty memory. 16 bytes is overlaid at windows system service table.

BugCheck 1000007E, {c0000005, 804fee17, f7c61b84, f7c61884}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
1: kd> !analyze -v
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804fee17, The address that the exception occurred at
Arg3: f7c61b84, Exception Record Address
Arg4: f7c61884, Context Record Address

Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"

FAULTING_IP:
nt!MiUpdateWsle+11
804fee17 8b4b14 mov ecx,[ebx+0x14]

EXCEPTION_RECORD: f7c61b84 -- (.exr fffffffff7c61b84)
.exr fffffffff7c61b84
ExceptionAddress: 804fee17 (nt!MiUpdateWsle+0x00000011)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000014
Attempt to read from address 00000014

CONTEXT: f7c61884 -- (.cxr fffffffff7c61884)
.cxr fffffffff7c61884
eax=f7c61c84 ebx=00000000 ecx=0002df95 edx=000299c9 esi=8163d190 edi=8054a5a0
eip=804fee17 esp=f7c61c4c ebp=f7c61c54 iopl=0 nv up ei pl nz na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010207
nt!MiUpdateWsle+0x11:
804fee17 8b4b14 mov ecx,[ebx+0x14] ds:0023:00000014=????????
.cxr
Resetting default scope

DEFAULT_BUCKET_ID: CODE_CORRUPTION

ERROR_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"

READ_ADDRESS: 00000014

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 80510656 to 804fee17

STACK_TEXT:
f7c61c54 80510656 f7c61c84 d8095000 00000000 nt!MiUpdateWsle+0x11
f7c61c8c 804de725 d8095000 00000000 80546598 nt!MmCheckCachedPageState+0x2d8
f7c61d3c 804e39b0 867c3298 8054d0a0 867cb020 nt!CcPerformReadAhead+0x213
f7c61d7c 80528267 867c3298 00000000 867cb020 nt!CcWorkerThread+0x130
f7c61dac 805b046c 867c3298 00000000 00000000 nt!ExpWorkerThread+0xed
f7c61ddc 80534ad6 8052817a 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
!chkimg -lo 50 -d !nt
804fe054-804fe057 4 bytes - nt!KiServiceTable+7c

[ 74 72 58 80:48 93 31 86 ]
804fe0e8-804fe0eb 4 bytes - nt!KiServiceTable+110 (+0x94)

[ 94 fc 59 80:f8 04 16 86 ]
804fe1c0-804fe1c3 4 bytes - nt!KiServiceTable+1e8 (+0xd8)

[ 7a bd 5a 80:28 92 16 86 ]
804fe1d8-804fe1db 4 bytes - nt!KiServiceTable+200 (+0x18)

[ 28 c0 5a 80:f0 91 16 86 ]
16 errors : !nt (804fe054-804fe1db)

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
STACK_COMMAND: .cxr fffffffff7c61884 ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE

Followup: memory_corruption

Hey all,
I have revently started to have an error that goes something like this
DRIVER_IRQL_NOT_LESS_OR_EQUAL
...
...
...
STOP: 0x000000D1
Im not a computer techy like some of you are but I do know that someone here may be able to interpret my mini dump files and possibly tell me what is causing this error. The error usually accurs when I attempt to play a game such as Americas Army or Battlefield 1942, there has also been some random restarts but only about 2 or 3 since this error has occured. Attached is my minidump files, if anyone can help please do it would be of great assistance.


Thankyou
Dan