Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\122209-27003-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
[B]Built by: 7600.16385.x86fre.win7_rtm.090713-1255[/B]
Machine Name:
Kernel base = 0x82808000 PsLoadedModuleList = 0x82950810
Debug session time: Tue Dec 22 09:50:02.917 2009 (GMT-5)
System Uptime: 0 days 0:07:53.758
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\system32\DRIVERS\2WirePCP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for 2WirePCP.sys
*** ERROR: Module load completed but symbols could not be loaded for 2WirePCP.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 91b2b23e, 807cfb4c, 807cf730}
[B]
Probably caused by : 2WirePCP.sys ( 2WirePCP+223e )
Followup: MachineOwner[/B] [B]
---------
kd> !analyze -v[/B] [B]
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/B] [B]
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.[/B]
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 91b2b23e, The address that the exception occurred at
Arg3: 807cfb4c, Exception Record Address
Arg4: 807cf730, 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:
2WirePCP+223e
91b2b23e f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
EXCEPTION_RECORD: 807cfb4c -- (.exr 0xffffffff807cfb4c)
ExceptionAddress: 91b2b23e (2WirePCP+0x0000223e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000001
Attempt to read from address 00000001
CONTEXT: 807cf730 -- (.cxr 0xffffffff807cf730)
eax=00000042 ebx=85580f4c ecx=00000010 edx=00000042 esi=00000001 edi=864bf108
eip=91b2b23e esp=807cfc14 ebp=807cfc2c iopl=0 nv up ei pl nz na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010203
2WirePCP+0x223e:
91b2b23e f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 00000001
READ_ADDRESS: GetPointerFromAddress: unable to read from 82970718
Unable to read MiSystemVaType memory at 82950160
00000001
FOLLOWUP_IP:
2WirePCP+223e
91b2b23e f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 91b2c97b to 91b2b23e
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
807cfc2c 91b2c97b 004c0001 864bf108 807cfc6c 2WirePCP+0x223e
807cfc94 91b33b34 85580e64 00000042 00000000 2WirePCP+0x397b
807cfcb8 91b357b3 00000000 86442004 8493dbfc 2WirePCP+0xab34
807cfd00 82875f2b 8493dbec 00000000 848485e8 2WirePCP+0xc7b3
807cfd50 82a1666d 00000000 a1274ec1 00000000 nt!ExpWorkerThread+0x10d
807cfd90 828c80d9 82875e1e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: 2WirePCP+223e
FOLLOWUP_NAME: MachineOwner
[B]
MODULE_NAME: 2WirePCP
IMAGE_NAME: 2WirePCP.sys[/B] [B]
DEBUG_FLR_IMAGE_TIMESTAMP: 3d8f9a28[/B] [B]
STACK_COMMAND: .cxr 0xffffffff807cf730 ; kb[/B] [B]
FAILURE_BUCKET_ID: 0x7E_2WirePCP+223e[/B] [B]
BUCKET_ID: OLD_IMAGE_2WirePCP.sys[/B]
Followup: MachineOwner
---------
