עזרה בניתוח קובץ MINIDUMP

קיבלתי BSOD במחשב שלי (מן הראוי לציין שהוא עובד ללא בעיות מאז שקניתי אותו (כחודש)ולא נעשתה שום פעולה מיוחדת בזמן התקלה) התוכנות שרצו הן הFF שפעל ברקע אבל לא היה פעיל והEMULE ועוד כל מיני עזרים ותוכנות שרצות ברקע כל הזמן שעבדים אצלי כל הזמן.

להלן תוכן הקובץ:

Microsoft ® Windows Debugger Version 6.6.0007.5

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini101706-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/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: Tue Oct 17 16:34:00.562 2006 (GMT+2)

System Uptime: 0 days 21:27:21.264

Loading Kernel Symbols

...

Loading User Symbols

Loading unloaded module list

....................

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, f42c55c8, f7a3eb4c, f7a3e848}

Probably caused by : tcpip.sys ( tcpip!TcpipBufferVirtualAddress+8 )

Followup: MachineOwner

---------

1: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

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: f42c55c8, The address that the exception occurred at

Arg3: f7a3eb4c, Exception Record Address

Arg4: f7a3e848, Context Record Address

Debugging Details:

------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:

tcpip!TcpipBufferVirtualAddress+8

f42c55c8 f6400605 test byte ptr [eax+6],5

EXCEPTION_RECORD: f7a3eb4c -- (.exr fffffffff7a3eb4c)

ExceptionAddress: f42c55c8 (tcpip!TcpipBufferVirtualAddress+0x00000008)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 00000000

Parameter[1]: 01000006

Attempt to read from address 01000006

CONTEXT: f7a3e848 -- (.cxr fffffffff7a3e848)

eax=01000000 ebx=0000b9af ecx=e0ca62ef edx=00000000 esi=01000000 edi=00000000

eip=f42c55c8 esp=f7a3ec14 ebp=f7a3ec14 iopl=0 nv up ei pl nz na po nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202

tcpip!TcpipBufferVirtualAddress+0x8:

f42c55c8 f6400605 test byte ptr [eax+6],5 ds:0023:01000006=??

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

READ_ADDRESS: 01000006

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from f42c827f to f42c55c8

STACK_TEXT:

f7a3ec14 f42c827f 01000000 00000010 8639007f tcpip!TcpipBufferVirtualAddress+0x8

f7a3ec34 f42c9b32 000250bf 86393134 85b4f1f8 tcpip!XsumSendChain+0x44

f7a3ecb4 f42c994a 862708e8 85b4f1f8 85e880c0 tcpip!UDPSend+0x3ca

f7a3ecd8 f42c99b0 00a3ecfc 85e88008 86393174 tcpip!TdiSendDatagram+0xd5

f7a3ed10 f42c8308 85e880c0 85e88154 85e880c0 tcpip!UDPSendDatagram+0x4f

f7a3ed2c 804eeeb1 86785b20 85e880c0 860fae98 tcpip!TCPDispatchInternalDeviceControl+0xff

f7a3ed7c 80537757 85f8c6a8 00000000 86fc1da8 nt!IopfCallDriver+0x31

f7a3edac 805ce794 85f8c6a8 00000000 00000000 nt!ExpWorkerThread+0xef

f7a3eddc 805450ce 80537668 00000001 00000000 nt!PspSystemThreadStartup+0x34

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

FOLLOWUP_IP:

tcpip!TcpipBufferVirtualAddress+8

f42c55c8 f6400605 test byte ptr [eax+6],5

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME: tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 444775d3

SYMBOL_NAME: tcpip!TcpipBufferVirtualAddress+8

STACK_COMMAND: .cxr 0xfffffffff7a3e848 ; kb

FAILURE_BUCKET_ID: 0x7E_tcpip!TcpipBufferVirtualAddress+8

BUCKET_ID: 0x7E_tcpip!TcpipBufferVirtualAddress+8

Followup: MachineOwner

---------

לא הצלחתי להגיע לתשובה סופית מה גרם לבעיה, אודה למי שיוכל לעזור