Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Richard\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\V3VHT2MD\mikelamar111412\mikelamar111412.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 9200 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16424.amd64fre.win8_gdr.120926-1855
Machine Name:
Kernel base = 0xfffff803`07678000 PsLoadedModuleList = 0xfffff803`07942a60
Debug session time: Wed Nov 14 12:50:22.575 2012 (UTC - 5:00)
System Uptime: 5 days 17:49:18.223
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.................................................
Unable to load image \SystemRoot\system32\DRIVERS\RT2500.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RT2500.sys
*** ERROR: Module load completed but symbols could not be loaded for RT2500.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88004f81828, fffff880197888e8, fffff88019788120}
[B]Probably caused by : RT2500.sys ( RT2500+1828 )[/B]Followup: MachineOwner
---------
0: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004f81828, The address that the exception occurred at
Arg3: fffff880197888e8, Exception Record Address
Arg4: fffff88019788120, 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:
RT2500+1828
fffff880`04f81828 c70004000000 mov dword ptr [rax],4
EXCEPTION_RECORD: fffff880197888e8 -- (.exr 0xfffff880197888e8)
ExceptionAddress: fffff88004f81828 (RT2500+0x0000000000001828)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000060001
Attempt to write to address 0000000000060001
CONTEXT: fffff88019788120 -- (.cxr 0xfffff88019788120)
rax=0000000000060001 rbx=0000000000000006 rcx=fffffa8010f92000
rdx=000000008c412000 rsi=fffffa8006fd6ca0 rdi=fffffa8010aeb1a0
rip=fffff88004f81828 rsp=fffff88019788b20 rbp=0000000000000000
r8=0000000000000006 r9=fffff88019788bd0 r10=0000000000000000
r11=0000000000000000 r12=0000000000000001 r13=fffff88001918d50
r14=0000000000000006 r15=fffffa8006fd6db8
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
RT2500+0x1828:
fffff880`04f81828 c70004000000 mov dword ptr [rax],4 ds:002b:00000000`00060001=????????
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
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: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000060001
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff803079ce168
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
0000000000060001
FOLLOWUP_IP:
RT2500+1828
fffff880`04f81828 c70004000000 mov dword ptr [rax],4
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 000000000000000b to fffff88004f81828
STACK_TEXT:
fffff880`19788b20 00000000`0000000b : fffff880`188f4080 fffffa80`10aeb1a0 fffff880`018c3a57 00000000`00000006 : RT2500+0x1828
fffff880`19788b28 fffff880`188f4080 : fffffa80`10aeb1a0 fffff880`018c3a57 00000000`00000006 fffff880`019794ca : 0xb
fffff880`19788b30 fffffa80`10aeb1a0 : fffff880`018c3a57 00000000`00000006 fffff880`019794ca ffff9aeb`f4974812 : HIDCLASS! ?? ::FNODOBFM::`string'
fffff880`19788b38 fffff880`018c3a57 : 00000000`00000006 fffff880`019794ca ffff9aeb`f4974812 fffff803`0779280a : 0xfffffa80`10aeb1a0
fffff880`19788b40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisCancelWaitWake+0x5f
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: RT2500+1828
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RT2500
IMAGE_NAME: RT2500.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 447efc0a
STACK_COMMAND: .cxr 0xfffff88019788120 ; kb
FAILURE_BUCKET_ID: X64_0x7E_RT2500+1828
BUCKET_ID: X64_0x7E_RT2500+1828
Followup: MachineOwner