Only able to run Athlon X2 3800 at 1ghz or 800mhz, can anyone analyse this dump file?
-
Only able to run Athlon X2 3800 at 1ghz or 800mhz, can anyone analyse this dump file?
I had an MSI PT880 Neo board with a P4 Prescott which worked great for years, and now I decided to upgrade to an Asrock 939Dual-Sata 2 board with a Athlon x2 3800 Manchester stepping 1 Revision BH-E4. Big problems!
First of all, it seems that I can only load windows when I downclock the X2 3800 to 1ghz, or 800mhz. Anything higher than that gives me an IRQL NOT LESS OR EQUAL, Stop: 0x0000000A, although sometimes I get other errors as well such as PFN LIST CORRUPT, and Stop: 0x0000007F.
Here's a recent minidump for an IRQL NOT LESS OR Equal, please can someone analyze this? :
************************************************** *****************************
* *
* 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: ea05ba28, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804d8a22, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: ea05ba28
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiRemovePageByColor+90
804d8a22 8954dd08 mov dword ptr [ebp+ebx*8+8],edx
CUSTOMER_CRASH_COUNT: 9
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: f894d790 -- (.trap fffffffff894d790)
ErrCode = 00000002
eax=8053f8e0 ebx=ad281544 ecx=8f0d5c6c edx=ffffffff esi=80cf7200 edi=00000005
eip=804d8a22 esp=f894d804 ebp=80c51000 iopl=0 vif nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00090293
nt!MiRemovePageByColor+0x90:
804d8a22 8954dd08 mov dword ptr [ebp+ebx*8+8],edx ss:0010:ea05ba28=??
??????
Resetting default scope
LAST_CONTROL_TRANSFER: from 804fd12e to 80517ee6
STACK_TEXT:
f894d774 804fd12e 0000000a ea05ba28 00000002 nt!KeBugCheckEx+0x19
f894d774 804d8a22 0000000a ea05ba28 00000002 nt!KiTrap0E+0x2b5
f894d81c 804dc2cb 00000000 00008000 00000000 nt!MiRemovePageByColor+0x90
f894d848 8067419a 81fcc790 00000000 05664f1d nt!MmZeroPageThread+0x9d
f894ddac 8055e764 80087000 00000000 00000000 nt!Phase1Initialization+0xf56
f894dddc 804fdf4d 80673243 80087000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiRemovePageByColor+90
804d8a22 8954dd08 mov dword ptr [ebp+ebx*8+8],edx
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 3b7dc674
SYMBOL_NAME: nt!MiRemovePageByColor+90
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xA_W_nt!MiRemovePageByColor+90
BUCKET_ID: 0xA_W_nt!MiRemovePageByColor+90
Followup: MachineOwner
-
Is this a totally new build or did you use some old parts? How about the RAM?
Are you sure that all the hardware is compatible?
Your errors indicate memory issues.
Are you using a SATA drive? Is this a new drive?
Assuming that you did a Clean Install of XP on the new board? (This is essential).