BSOD Problem, cpc2004 please help

Status
Not open for further replies.

IcebladeXI

Posts: 7   +0
Hi, like many other people I am getting a BSOD problem saying IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGE_AREA. I have seen you solve some of these problems, and am hoping you can diagnose mine.

My computer setup:
AMD Athlon 2500+
Ati Radeon 9600XT
512 Ram Corsair value Select
M7NCD Pro Biostar Motherboard Nforce2

At first, I thought it was a ram problem, but through switching slots, switching ram, etc. I am almost 100% sure it is NOT a ram problem.
I now think it is either a Motherboard or a CPU problem, i was hoping you could find out which one it is.
It also may be a PSU problem, but I have been using this same stuff for over a year, and I dont understand why my PSU wouldnt be enough to power my system now.

From reading other threads, I assume you need my dumps, I dont know where to find these and since I am on another computer, I will get on the nonworking one and try to find out where the dumps are, ill post them in a few.
Thanks
 

IcebladeXI

Posts: 7   +0
Hey, I cannot even access my other computer. After windows starts, I either get BSOD and it restarts, or the monitor just goes dead.
 

IcebladeXI

Posts: 7   +0
Ok, I am on the faulty computer and I some of the files from Windows/minidump and put them in a few zips. There are quite a few of those files in the minidump folder, I uploaded 10 minidumps in total, some old some new.

Thanks
 

cpc2004

Posts: 1,994   +0
I believe that it is memory issue. One minidump is inaccessible and one minidump with one bit corruption.

Suggestion
1 Downclock the RAM
2 Check BIOS setting and make sure that your RAM is compatible to the motherboard

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000008f, The free or zeroed page listhead is corrupt
Arg2: 0001a0d7, new page
Arg3: 0000a0d7, old page
Arg4: 00000000, 0

Debugging Details:
------------------
PFN_PAGE_SINGLE_BIT_ERROR: Bugcheck args 2 and 3 differ by a bit, its hardware error.
MEMORY_CORRUPTOR: ONE_BIT
CUSTOMER_CRASH_COUNT: 13
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x4E

LAST_CONTROL_TRANSFER: from 8051bf6b to 805266db

STACK_TEXT:
f8951814 8051bf6b 0000004e 0000008f 0001a0d7 nt!KeBugCheckEx+0x19
f895184c 8068cf80 823ce790 00000000 00000000 nt!MmZeroPageThread+0x124
f8951dac 8057c73a 80087000 00000000 00000000 nt!Phase1Initialization+0xe35
f8951ddc 805124c1 8068ad55 80087000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

FOLLOWUP_NAME: memory_corruption
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
 

IcebladeXI

Posts: 7   +0
Could it be the actual ram slots on the motherboard causing the problem? I know the ram works because I am using it right now posting from a different computer.
 

IcebladeXI

Posts: 7   +0
I double checked to see if the ram was compatible, it was.

Right now I have 2 sticks of 256mb ram. If I stick 1 stick in, it works fine. If I stick both in, it goes to BSOD. So it has led me to believe that the actual slot ON the motherboard is causing this problem. Do you agree or no??


I also tested with 1 stick of 512mb ram which is also compatible, and it goes to BSOD too..
 
Status
Not open for further replies.