Since 2 months now i've getting a BSOD very often. Most of the time i get the errors IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA.
From cpc2004's other posts i understand this because of faulty hardware or a faulty device driver.

I uploaded 3 of the dumps to this location Minidumps.

And wil post some of the errors here:

Error 1003
Foutcode; 10000050, parameter1: fffffff4, parameter2: 00000000, parameter3: 8057ec15, parameter4: 00000000.

Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp voor meer informatie.

Error 1001
De computer is opnieuw gestart na een foutencontrole. Foutencontrole: 0x10000050 (0xfffffff4, 0x00000000, 0x8057ec15, 0x00000000). Er is een dump opgeslagen in: C:\WINDOWS\Minidump\Mini091105-01.dmp.

Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp voor meer informatie.

Error 1003
Foutcode; 1000008e, parameter1: 80000003, parameter2: 805103f4, parameter3: f418a6b0, parameter4: 00000000.

Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp voor meer informatie.

Error 1001
De computer is opnieuw gestart na een foutencontrole. Foutencontrole: 0x1000008e (0x80000003, 0x805103f4, 0xf418a6b0, 0x00000000). Er is een dump opgeslagen in: C:\WINDOWS\Minidump\Mini090905-01.dmp.

Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp voor meer informatie.

Can someone please look at this and tell me if it is a faulty memory stick or something else?

Greets,
Jimmy

Hello Jimmy

Did you post your question on www.Helpmij.nl.

If not do so, than I can reply in dutch.

Wisperbird.

do a memtest

www.memtest.org

its free

my advice do a couple of passes

it there is errors. remove all sticks and then do one stick at a time to limit it down to which stick is junk. If you dont get errors report back and ill tell you how to PRIME95

Good luck

Hi Jimmy,

I've investigated your minidumps. One of the minidumps crashes with memory corruption which is caused faulty ram.

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

Debugging Details:
------------------
WRITE_ADDRESS: 0d34d300
CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRemoveWsle+88
804f0009 008100d30000 add [ecx+0xd300],al

CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from 804f9bb4 to 804f0009

TRAP_FRAME: f3858ae4 -- (.trap fffffffff3858ae4)
ErrCode = 00000002
eax=c050fb70 ebx=0d340209 ecx=0d340000 edx=c0503000 esi=00003135 edi=000149a0
eip=804f0009 esp=f3858b58 ebp=f3858b88 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!MiRemoveWsle+0x88:
804f0009 008100d30000 add [ecx+0xd300],al ds:0023:0d34d300=??
Resetting default scope

STACK_TEXT:
f3858b5c 804f9bb4 0d340000 c03000d0 ffa81560 nt!MiRemoveWsle+0x88
f3858b88 804f9d38 c0034d00 0d340000 00000000 nt!MiDeletePte+0x1d6
f3858c48 804f7067 e3833b30 0d340fff 00000000 nt!MiDeleteVirtualAddresses+0x149
f3858cf4 80587e82 814b8020 ffa81560 f3858d64 nt!MiRemoveMappedView+0x212
f3858d38 80587f36 81ebd5d0 814d28d0 00000000 nt!MiUnmapViewOfSection+0x12a
f3858d54 804da140 ffffffff 814b8020 00000000 nt!NtUnmapViewOfSection+0x52
f3858d54 7ffe0304 ffffffff 814b8020 00000000 nt!KiSystemService+0xc4
04aafef8 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
804f0000 - nt!MiRemoveWsle+2f
[ 00:02 ]
804f0002-804f0003 2 bytes - nt!MiRemoveWsle+81 (+0x02)
[ 83 20:88 00 ]
804f0008-804f000b 4 bytes - nt!MiRemoveWsle+87 (+0x06)
[ 02 0f 84 dc:00 00 81 00 ]
7 errors : !nt (804f0000-804f000b)

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

Followup: memory_corruption