Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\050911-25459-01.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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a58000 PsLoadedModuleList = 0xfffff800`02c95e50
Debug session time: Tue May 10 01:12:45.469 2011 (GMT-4)
System Uptime: 0 days 0:07:40.045
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a009953000, 1, fffff80002abf494, 0}
Unable to load image \SystemRoot\System32\Drivers\N360x64\0403000.005\SRTSP64.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SRTSP64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS
Could not read faulting driver name
Probably caused by : SRTSP64.SYS ( SRTSP64+36fcc )
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: fffff8a009953000, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002abf494, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d000e0
fffff8a009953000
FAULTING_IP:
nt!memmove+64
fffff800`02abf494 488901 mov qword ptr [rcx],rax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: wlanext.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800697f560 -- (.trap 0xfffff8800697f560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8a009953000
rdx=000000e00aa45be0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002abf494 rsp=fffff8800697f6f8 rbp=fffffa8001e3ff20
r8=0000000000000000 r9=ffffffffffffdc84 r10=000008d202040103
r11=fffff8a009940420 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!memmove+0x64:
fffff800`02abf494 488901 mov qword ptr [rcx],rax ds:a600:fffff8a0`09953000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b48f14 to fffff80002ac8740
STACK_TEXT:
fffff880`0697f3f8 fffff800`02b48f14 : 00000000`00000050 fffff8a0`09953000 00000000`00000001 fffff880`0697f560 : nt!KeBugCheckEx
fffff880`0697f400 fffff800`02ac682e : 00000000`00000001 00000000`00001000 00000000`00001000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`0697f560 fffff800`02abf494 : fffff800`02de3c51 00000000`00001000 00000000`00000000 fffffa80`01e48390 : nt!KiPageFault+0x16e
fffff880`0697f6f8 fffff800`02de3c51 : 00000000`00001000 00000000`00000000 fffffa80`01e48390 00000000`00001000 : nt!memmove+0x64
fffff880`0697f700 fffff800`02de37d2 : 00000000`00040000 fffff8a0`09940420 00000000`00001000 00000000`00001000 : nt!CcCopyBytesToUserBuffer+0x41
fffff880`0697f740 fffff880`012b2d28 : fffff880`00000000 00000000`00000005 fffffa80`00001000 fffffa80`00001001 : nt!CcCopyRead+0x1a2
fffff880`0697f800 fffff880`010c40c8 : fffffa80`01e3ff20 fffffa80`01e48328 00000000`00001000 00000000`00000001 : Ntfs!NtfsCopyReadA+0x1a8
fffff880`0697f9d0 fffff880`010c7c2a : fffff880`0697fac8 fffffa80`05eebc03 fffff880`0697fb00 00000000`00000000 : fltmgr!FltpPerformFastIoCall+0x88
fffff880`0697fa30 fffff880`010d5130 : 00000000`00000004 00000000`00000000 fffffa80`01e3ff20 00000000`00000000 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`0697fa70 fffff880`04762fcc : fffffa80`01e48260 fffff880`010c7af5 00000000`00000001 fffff8a0`08c40360 : fltmgr!FltReadFile+0x260
fffff880`0697fb50 fffffa80`01e48260 : fffff880`010c7af5 00000000`00000001 fffff8a0`08c40360 fffff8a0`09940420 : SRTSP64+0x36fcc
fffff880`0697fb58 fffff880`010c7af5 : 00000000`00000001 fffff8a0`08c40360 fffff8a0`09940420 fffff880`00000004 : 0xfffffa80`01e48260
fffff880`0697fb60 fffff880`0477a1c5 : 00000000`00000000 00000000`00000000 00000000`00006000 fffff880`066a41ec : fltmgr!FltpFreeIrpCtrl+0x145
fffff880`0697fbb0 00000000`00000000 : 00000000`00000000 00000000`00006000 fffff880`066a41ec fffff8a0`098eb010 : SRTSP64+0x4e1c5
STACK_COMMAND: kb
FOLLOWUP_IP:
SRTSP64+36fcc
fffff880`04762fcc ?? ???
SYMBOL_STACK_INDEX: a
SYMBOL_NAME: SRTSP64+36fcc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SRTSP64
IMAGE_NAME: SRTSP64.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4b85bd61
FAILURE_BUCKET_ID: X64_0x50_SRTSP64+36fcc
BUCKET_ID: X64_0x50_SRTSP64+36fcc
Followup: MachineOwner
---------
