Perci
Did you solve your problem?
I have the same problem.
Here's my computer:
GigaByte GA-8I945P-G Socket775 <i945P> PCI-E+ GbLAN SATA RAID U133 ATX 4DDR-II <PC-5300>
CPU Intel Pentium D 820 2.8 ГГц/ 2Мб/ 800МГц 775-LGA
ZALMAN <CNPS7700-AlCu> Cooler for Socket 478/ 775/ 754/ 939/ 940 (Fan speed contr., 20-32дБ, 1000-2000об/ мин, Cu+ Al)
SVGA 256Mb <PCI-E> DDR Gigabyte GV-NX76G256D-RH (OEM) +DVI+TV Out+SLI <GeForce 7600 GS>
Kingmax DDR-II DIMM 1Gb <PC-5300>
HDD 300 Gb SATA-II 300 Maxtor DiamondMax 10 <6V300F0> 7200rpm 16Mb
Miditower Thermaltake <VB6430BNSE> Black Swing ATX 430W (24+ 6+ 4pin)
I get 8E, C2 and C5 stop codes when I play WOW. Also I sometimes get these stops when I restart or shutdown my computer.
Here're some examples:
Code:
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini101206-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\Symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Thu Oct 12 23:03:59.937 2006 (GMT+4)
System Uptime: 0 days 2:51:15.660
Loading Kernel Symbols
.................................................................................................... ...................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, cd4, 1f, 86432008}
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 0000001f, Memory contents of the pool block
Arg4: 86432008, Address of the block of pool being deallocated
Debugging Details:
------------------
GetUlongFromAddress: unable to read from 80564c50
POOL_ADDRESS: 86432008
BUGCHECK_STR: 0xc2_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 8054a583 to 804f9c37
STACK_TEXT:
f7a2ece8 8054a583 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
f7a2ed38 f46f885d 86432008 c5646641 f46f77a8 nt!ExFreePoolWithTag+0x2a3
f7a2ed4c f46f586a 864320b0 8653b130 860b5490 afd!AfdFreeEndpoint+0x2d
f7a2ed68 805758d9 860b5490 00000000 8056375c afd!AfdDoWork+0x51
f7a2ed7c 80537757 8653b130 00000000 865c2b30 nt!IopProcessWorkItem+0x13
f7a2edac 805ce794 8653b130 00000000 00000000 nt!ExpWorkerThread+0xef
f7a2eddc 805450ce 80537668 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
afd!AfdFreeEndpoint+2d
f46f885d 5e pop esi
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: afd!AfdFreeEndpoint+2d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: afd
IMAGE_NAME: afd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107eb5
FAILURE_BUCKET_ID: 0xc2_7_afd!AfdFreeEndpoint+2d
BUCKET_ID: 0xc2_7_afd!AfdFreeEndpoint+2d
Followup: MachineOwner
--------- Code:
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: 805af891, The address that the exception occurred at
Arg3: b9575bb4, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
FAULTING_IP:
nt!MiUnsecureVirtualMemory+69
805af891 8b0f mov ecx,dword ptr [edi]
TRAP_FRAME: b9575bb4 -- (.trap ffffffffb9575bb4)
ErrCode = 00000000
eax=00000000 ebx=86458008 ecx=00000000 edx=85c109bc esi=86458008 edi=00000024
eip=805af891 esp=b9575c28 ebp=b9575c34 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!MiUnsecureVirtualMemory+0x69:
805af891 8b0f mov ecx,dword ptr [edi] ds:0023:00000024=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: WoW.exe
LAST_CONTROL_TRANSFER: from 805b0779 to 805af891
STACK_TEXT:
b9575c34 805b0779 85c108a0 00000000 b9575d00 nt!MiUnsecureVirtualMemory+0x69
b9575c44 bf9cb389 86458008 e37a1828 e14f9714 nt!MmUnsecureVirtualMemory+0xf
b9575d00 bf9cd549 e14f9008 e54f1c58 b9575d34 dxg!vDdDisableSurfaceObject+0xed
b9575d48 bf9cd847 024016dd 00000000 b9575d64 dxg!bDdDeleteSurfaceObject+0xcd
b9575d58 8054060c 024016dd 0012fd18 7c90eb94 dxg!DxDdDeleteSurfaceObject+0xf
b9575d58 7c90eb94 024016dd 0012fd18 7c90eb94 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fd18 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
dxg!vDdDisableSurfaceObject+ed
bf9cb389 832700 and dword ptr [edi],0
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxg!vDdDisableSurfaceObject+ed
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxg
IMAGE_NAME: dxg.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107b93
FAILURE_BUCKET_ID: 0x8E_dxg!vDdDisableSurfaceObject+ed
BUCKET_ID: 0x8E_dxg!vDdDisableSurfaceObject+ed
Followup: MachineOwner
My hard drive was new. So I formatted it before installing WinXP Pro.
That's why I don't believe that reformatting can help me.
I've checked and even replaced my RAM.
I've checked my motherboard at service centre.
Still get BSODs. 
Any suggestions?
Newbie
