BSOD or restart

[anstro]

Hy, I have a PC for three months and it crashes mostly when I play games, but sometimes just doing nothing. When it crashes I receive a message error who contains mostly this three error codes with different parameters:

BCCode : 1000008e BCP1 : C000001D BCP2 : 805A6D5B BCP3 : B689F958
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

BCCode : 10000050 BCP1 : FFFFFE64 BCP2 : 00000001 BCP3 : 805A7D64
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

BCCode : c2 BCP1 : 00000007 BCP2 : 00000CD4 BCP3 : 1A060002
BCP4 : 89602978 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

My PC specifications are:
CPU Intel Core 2 Duo E6600, 2.40 GHz
MB DFI Infinity 975 X/G
HDD Western Digital 250GB SATA2
RAM 2 GB Corsair XMS2 CM2X 1024-6400 (Dual Channel) 800MHz, a pair of two 1GB modules
GPU Leadtek Extreme PX7600, 256MB DDR3
Power source 550W
Windows XP Proffesional with SP2

The system have this crashes since begining. I have reinstall the OS many times, from the same CD I used for my older PC wich is running fine, I have changed my GPU, power source and motherboard with new ones from the same type, BIOS and drivers has the latest updates from the manufacturer sites, I have tested the system with new memory modules and hard discs, but still crashes.
Also on the BSOD I have one of the following messages:
PAGE_FAULT_IN_NON_PAGED_AREA
DRIVER_IRQL_NOT_LESS_OR_EQUAL
BAD_POOL_CALLER

If you can help me, please do, 'cause I am desperate, can't work or play on this new PC and the old one don't have the resources I need.
If you want additional informations please tell
Thank you for support me

 

[darel001]

I had a somewhat similar experience just a few weeks ago. I built a comp for my uncle and the whole thing just kept rebooting various times. I tried EVERYTHING!!!!!!!!!!!!. Including xchanging pieces (mobo and ram) for same ones . reinstalled os numerous times, PSU,etc.. ANYTHING YOU HAVE ALREADY DONE OR PLAN TO DO. MY ADVICE AND SOLUTION: get a different motherboard. chances are there must besome incompatibility between the ram and mobo. here is the link to my experience.

https://www.techspot.com/vb/topic65297.html

DIFFERENT MOBO !!!!(not same model) and dontget the ecs p4m800 cause it suks.

 

[anstro]

Hy darel001, the MB and ram works fine together, another person has built a PC with the same MB and ram and has no complains, also the options for a MB who works with Conroe processors are limited and DFI Infinity 975 X/G is the best rated for this in my country.
I will attach some of minidumps, maybe someone can tell what the problem really is.
I cheked the temp on system, and have no problems, CPU is not heating up over 41 degrees Celsius in any situation, and the dust not exist because the comp is new and the problems with restarting and BSODs are from begining.

 

[darel001]

THIS IS WHAT THE MINIDUMPS SHOWED ON THE DEBBUGGER< BUT I KNOW NOTHING ELSE SORRY

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\David\Desktop\Mini112006-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Nov 20 05:12:30.250 2006 (GMT-8)
System Uptime: 0 days 0:14:30.960
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.........................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {80abbbbc, 0, 8054aa0e, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for dxg.sys
*** ERROR: Module load completed but symbols could not be loaded for dxg.sys
Probably caused by : dxg.sys ( dxg+8058 )

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

 

[peterdiva]

The dumps are citing memory corruption as the probable cause. Try running with only 1 stick at a time.

BugCheck 10000050, {80abbbbc, 0, 8054aa0e, 0}
Probably caused by : memory_corruption

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
8054a97c - nt!ExAllocatePoolWithTag+14
[ 8b:9b ]
1 error : !nt (8054a97c)
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

BugCheck 1A, {41284, 11073001, 139e3, c0883000} <-- Memory management bugcheck.
Probably caused by : memory_corruption ( nt!MiLocateWsle+c1 )

BugCheck C2, {7, cd4, 1a060002, 89602978}
*** WARNING: Unable to verify timestamp for RtkHDAud.sys
*** ERROR: Module load completed but symbols could not be loaded for RtkHDAud.sys
Probably caused by : portcls.sys ( portcls!CPortPinWaveCyclic:eviceIoControl+1fa )

 

[anstro]

I have run memtest 86+ for 27 times and he has reported 0 errors. Is it possibile to have bad RAM or the sticks not working good in dual channel mode even they came in pair from the producer? Because I don't know what else could be. Is any chance to have bad CPU?

 

[anstro]

I have opened my latest minidump with Windows Debugger and analysed it, but don't know to manage it, about what system memory is refered to?
maybe someone can help me:


1: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffe64, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 805a7d64, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 41107b0d

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
fffffe64

FAULTING_IP:
nt+d0d64
805a7d64 897d88 mov dword ptr [ebp-78h],edi

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from b53d7d64 to 805a7d64

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b53d7c0c b53d7d64 0022e4e0 805a74de bc6a9678 nt+0xd0d64
b53d7c10 0022e4e0 805a74de bc6a9678 00000000 0xb53d7d64
b53d7d64 7c90eb94 badb0d00 0022e4c8 805d109a 0x22e4e0
b53d7d68 badb0d00 0022e4c8 805d109a 00000000 0x7c90eb94
b53d7d6c 0022e4c8 805d109a 00000000 00000000 0xbadb0d00
b53d7d70 805d109a 00000000 00000000 00000000 0x22e4c8
b53d7d74 00000000 00000000 00000000 00000000 nt+0xfa09a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+d0d64
805a7d64 897d88 mov dword ptr [ebp-78h],edi

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

SYMBOL_NAME: nt+d0d64

BUCKET_ID: WRONG_SYMBOLS

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

1: kd> referenced: nt!_KPRCB
^ Bad register error in 'referenced: nt!_KPRCB'
1: kd> nt!_KPRCB
^ Syntax error in 'nt!_KPRCB'

And from this I have my attention to this phrase:
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffe64, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 805a7d64, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

 

[anstro]

Thank you for the advice, seems to be one stick of RAM bad, when I run with other stick only, my computer work fine, when I use the bad stick, PC crashes in few minutes after I start a game. So I will go to my vendor and ask for another pair of memory sticks. Hope someone with the same problem read this and avoid the hell I've been through this months.