Welcome.
Probably caused by: Linksys, NetGear, DLink or Marvell Wireless USB Network Adapter
Driver Reference Table
Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\USER\Downloads\Compressed\BEYBI-Wed_12_03_2014_221721_72\120314-18033-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0364b000 PsLoadedModuleList = 0xfffff800`0388e890
Debug session time: Thu Dec 4 10:19:26.171 2014 (UTC + 6:00)
System Uptime: 0 days 0:00:21.186
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*** WARNING: Unable to verify timestamp for MRVW24C.sys
*** ERROR: Module load completed but symbols could not be loaded for MRVW24C.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880071112e0, fffff88003554768, fffff88003553fc0}
Probably caused by : MRVW24C.sys ( MRVW24C+102e0 )
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: fffff880071112e0, The address that the exception occurred at
Arg3: fffff88003554768, Exception Record Address
Arg4: fffff88003553fc0, 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:
MRVW24C+102e0
fffff880`071112e0 6642898433ec040000 mov word ptr [rbx+r14+4ECh],ax
EXCEPTION_RECORD: fffff88003554768 -- (.exr 0xfffff88003554768)
ExceptionAddress: fffff880071112e0 (MRVW24C+0x00000000000102e0)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 000000000000064c
Attempt to write to address 000000000000064c
CONTEXT: fffff88003553fc0 -- (.cxr 0xfffff88003553fc0)
rax=0000000000000001 rbx=0000000000000160 rcx=0000000000000698
rdx=fffffa800d242d82 rsi=0000000000000000 rdi=fffffa800c873000
rip=fffff880071112e0 rsp=fffff880035549a0 rbp=fffffa800d242d60
r8=0000000000000002 r9=0000000000000002 r10=fffffa800c8fc630
r11=fffffa800c873000 r12=0000000000000001 r13=0000000000000000
r14=0000000000000000 r15=fffffa800d242d6c
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
MRVW24C+0x102e0:
fffff880`071112e0 6642898433ec040000 mov word ptr [rbx+r14+4ECh],ax ds:002b:00000000`0000064c=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_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: 000000000000064c
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800038f8100
GetUlongFromAddress: unable to read from fffff800038f81c0
000000000000064c Nonpaged pool
FOLLOWUP_IP:
MRVW24C+102e0
fffff880`071112e0 6642898433ec040000 mov word ptr [rbx+r14+4ECh],ax
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880071112e0
STACK_TEXT:
fffff880`035549a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : MRVW24C+0x102e0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: MRVW24C+102e0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: MRVW24C
IMAGE_NAME: MRVW24C.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 472551f7
STACK_COMMAND: .cxr 0xfffff88003553fc0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_MRVW24C+102e0
BUCKET_ID: X64_0x7E_MRVW24C+102e0
Followup: MachineOwner
---------
0: kd> lmvm MRVW24C
start end module name
fffff880`07101000 fffff880`07154200 MRVW24C T (no symbols)
Loaded symbol image file: MRVW24C.sys
Image path: \SystemRoot\system32\DRIVERS\MRVW24C.sys
Image name: MRVW24C.sys
Timestamp: Mon Oct 29 09:22:31 2007 (472551F7)
CheckSum: 00055C61
ImageSize: 00053200
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Sometimes drivers remain and do not get completely uninstalled.
Driver Removal Process:
- Download Driver Sweeper to the desired location.
- Extract the files from the zip.
- Uninstall the driver Program & Features - Control Panel.
- Run Driver Sweeper, check the drivers you want to uninstall or clean registry leftovers of.
Link to full tutorial: Drivers - Clean Left over Files after Uninstalling
Quote