Код:
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\Koko\Desktop\Mini120206-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sat Dec 2 16:44:30.531 2006 (GMT+2)
System Uptime: 0 days 0:48:34.086
Loading Kernel Symbols
...
Loading unloaded module list
..........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {e7fffff8, 0, 8054a832, 2}
Could not read faulting driver name
Unable to load image a347bus.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for a347bus.sys
*** ERROR: Module load completed but symbols could not be loaded for a347bus.sys
Probably caused by : a347bus.sys ( a347bus+e072 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* 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: e7fffff8, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8054a832, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: e7fffff8
FAULTING_IP:
nt!ExFreePoolWithTag+237
8054a832 668b4efa mov cx,[esi-0x6]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
LAST_CONTROL_TRANSFER: from 8058cbc1 to 8054a832
STACK_TEXT:
f7757c08 8058cbc1 e7fffffe 00000000 e125a908 nt!ExFreePoolWithTag+0x237
f7757c24 8058b377 e125a908 e106a5a8 e1011314 nt!CmpCleanUpKcbValueCache+0x51
f7757c38 80589fe1 e262a4d0 e1fb6388 80567ca8 nt!CmpCleanUpKcbCacheWithLock+0x1a
f7757c44 80567ca8 f7757c58 80567c5f e106a5a8 nt!CmpGetDelayedCloseIndex+0x16
f7757c4c 80567c5f e106a5a8 f7757c64 80567aed nt!CmpAddToDelayedClose+0xa
f7757c58 80567aed e106a5a8 f7757c7c 8056b7f2 nt!CmpDereferenceKeyControlBlockWithLock+0x38
f7757c64 8056b7f2 e106a5a8 00000000 e1a02100 nt!CmpDereferenceKeyControlBlock+0x12
f7757c7c 805638f7 e1a02118 e1a02100 00000000 nt!CmpDeleteKeyObject+0x92
f7757c98 804e36d5 e1a02118 00000000 00000178 nt!ObpRemoveObjectRoutine+0xdf
f7757cbc 80566ab3 8532cb98 e11f4300 84fb06e0 nt!ObfDereferenceObject+0x5f
f7757cd4 80566b1c e11f4300 e1a02118 00000178 nt!ObpCloseHandleTableEntry+0x155
f7757d1c 80566b66 00000178 00000001 00000000 nt!ObpCloseHandle+0x87
f7757d30 f750d072 00000178 f750cfcc 0103fd64 nt!NtClose+0x1d
WARNING: Stack unwind information not available. Following frames may be wrong.
f7757d58 804de7ec 00000178 0103fd1c 7c90eb94 a347bus+0xe072
f7757d58 7c90eb94 00000178 0103fd1c 7c90eb94 nt!KiFastCallEntry+0xf8
0103fd1c 00000000 00000000 00000000 00000000 0x7c90eb94
FOLLOWUP_IP:
a347bus+e072
f750d072 ?? ???
SYMBOL_STACK_INDEX: d
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: a347bus+e072
MODULE_NAME: a347bus
IMAGE_NAME: a347bus.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4091f40d
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0x50_a347bus+e072
BUCKET_ID: 0x50_a347bus+e072
Followup: MachineOwner
---------
Probably caused by : a347bus.sys ( a347bus+e072 )
Alcohol 120%. Нищо ново под слънцето. Деинсталирай го, рестартирай и пробвай пак.