Цитата:
очень было бы хорошо, если бы вы выложили полную ошибку, с 4мя поарметрами и названием драйвера.
а так же не полохо было бы узнать - бывают ли какие-нибудь другие ошибки
|
Выкладываю расшифровку дампа программой
WinDbg.
Код:
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
---------
Других ошибок пока не было.
Про память в DUAL режиме я знаю. Сейчас у меня одна планка в одноканальном режиме естественно. Пока не добьюсь стабильности, думать о DUAL режиме боюсь. Сложнее будет определить причину.
