Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\TManTM\022712-28033-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
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e5c000 PsLoadedModuleList = 0xfffff800`030a1e90
Debug session time: Mon Feb 27 05:19:28.919 2012 (UTC - 7:00)
System Uptime: 0 days 0:01:42.090
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\system32\DRIVERS\RTL8192u.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTL8192u.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL8192u.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880068c7b73, fffff880033617d8, fffff88003361030}
Probably caused by : RTL8192u.sys ( RTL8192u+56b73 )
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880068c7b73, The address that the exception occurred at
Arg3: fffff880033617d8, Exception Record Address
Arg4: fffff88003361030, 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:
RTL8192u+56b73
fffff880`068c7b73 8801 mov byte ptr [rcx],al
EXCEPTION_RECORD: fffff880033617d8 -- (.exr 0xfffff880033617d8)
ExceptionAddress: fffff880068c7b73 (RTL8192u+0x0000000000056b73)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 00000000004d5d28
Attempt to write to address 00000000004d5d28
CONTEXT: fffff88003361030 -- (.cxr 0xfffff88003361030)
rax=fffffa8007f80000 rbx=0000000000000000 rcx=00000000004d5d28
rdx=fffff88002e8bd28 rsi=fffffa8009075000 rdi=0000000000000001
rip=fffff880068c7b73 rsp=fffff88003361a18 rbp=fffffa800a9aef48
r8=0000000000000004 r9=fffff88003361a50 r10=0000000000000000
r11=00000000004d5d28 r12=00000000004d5d28 r13=0000000000000004
r14=fffffa800a9aef44 r15=0000000000000004
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
RTL8192u+0x56b73:
fffff880`068c7b73 8801 mov byte ptr [rcx],al ds:002b:00000000`004d5d28=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
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: 00000000004d5d28
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310d0e8
00000000004d5d28
FOLLOWUP_IP:
RTL8192u+56b73
fffff880`068c7b73 8801 mov byte ptr [rcx],al
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff8800687660f to fffff880068c7b73
STACK_TEXT:
fffff880`03361a18 fffff880`0687660f : 00000000`00000000 00000000`c0000001 fffffa80`09b88b70 00000000`c0000001 : RTL8192u+0x56b73
fffff880`03361a20 00000000`00000000 : 00000000`c0000001 fffffa80`09b88b70 00000000`c0000001 fffff800`03061c00 : RTL8192u+0x560f
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: RTL8192u+56b73
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RTL8192u
IMAGE_NAME: RTL8192u.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48c9e423
STACK_COMMAND: .cxr 0xfffff88003361030 ; kb
FAILURE_BUCKET_ID: X64_0x7E_RTL8192u+56b73
BUCKET_ID: X64_0x7E_RTL8192u+56b73
Followup: MachineOwner
---------
1: kd> lmvm RTL8192u
start end module name
fffff880`06871000 fffff880`068fb000 RTL8192u T (no symbols)
Loaded symbol image file: RTL8192u.sys
Image path: \SystemRoot\system32\DRIVERS\RTL8192u.sys
Image name: RTL8192u.sys
Timestamp: Thu Sep 11 21:38:11 2008 (48C9E423)
CheckSum: 0007A341
ImageSize: 0008A000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
The first thing to do is remove the offending driver:
Code:
RTL8192u fffff880`06871000 fffff880`068fb000 Thu Sep 11 21:38:11 2008 (48c9e423) 0007a341 None RTL8192u.sys
RTL8192u.sys
Actually, seeing that it is a USB wireless network adapter; remove it from the system. You are using a USB wireless network adapter that has Vista drivers, and this is a recipe for blue screen crashes. We see this a lot on these forums.
If that does not work, run Disk Check with both boxes checked. Schedule it to run on next restart. Restart the computer and let it run.
Quote