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


Loading Dump File [C:\WINDOWS\Minidump\Mini083010-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:/Symbole*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.100216-1514
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Aug 30 09:15:16.078 2010 (GMT+2)
System Uptime: 0 days 0:00:14.781
Loading Kernel Symbols
...............................................................
..............................................
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {80bafd1c, 1, b5fd9640, 0}


Could not read faulting driver name
Probably caused by : tcpip.sys ( tcpip!CopyToNdisSafe+4e )

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

1: 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: 80bafd1c, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: b5fd9640, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS:  80bafd1c 

FAULTING_IP: 
tcpip!CopyToNdisSafe+4e
b5fd9640 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  svchost.exe

LAST_CONTROL_TRANSFER:  from b5fd8e85 to b5fd9640

STACK_TEXT:  
b5a2e5c8 b5fd8e85 8a297360 b5a2e634 b5a2e640 tcpip!CopyToNdisSafe+0x4e
b5a2e6a4 b5fd9598 8a392008 8a47871c 8a297360 tcpip!ARPQueryInfo+0x52a
b5a2e800 b5fd931a 00000000 00000038 b5adbe90 tcpip!IPQueryInfo+0xad
00000000 00000000 00000000 00000000 00000000 tcpip!TdiQueryInformationEx+0x2d4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!CopyToNdisSafe+4e
b5fd9640 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  tcpip!CopyToNdisSafe+4e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  485b99ad

FAILURE_BUCKET_ID:  0x50_tcpip!CopyToNdisSafe+4e

BUCKET_ID:  0x50_tcpip!CopyToNdisSafe+4e

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