Welcome
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_BSOD Issues.zip\Windows_NT6_BSOD_jcgriff2\061011-18096-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 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16792.x86fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0x82015000 PsLoadedModuleList = 0x8215d810
Debug session time: Fri Jun 10 05:36:56.989 2011 (GMT-4)
System Uptime: 0 days 1:53:25.708
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
...........
Unable to load image \SystemRoot\system32\DRIVERS\ewusbnet.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ewusbnet.sys
*** ERROR: Module load completed but symbols could not be loaded for ewusbnet.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, a5f8f703, b1581ba8, b1581780}
Probably caused by : ewusbnet.sys ( ewusbnet+2703 )
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: c0000005, The exception code that was not handled
Arg2: a5f8f703, The address that the exception occurred at
Arg3: b1581ba8, Exception Record Address
Arg4: b1581780, 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:
ewusbnet+2703
a5f8f703 f6400605 test byte ptr [eax+6],5
EXCEPTION_RECORD: b1581ba8 -- (.exr 0xffffffffb1581ba8)
ExceptionAddress: a5f8f703 (ewusbnet+0x00002703)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000006
Attempt to read from address 00000006
CONTEXT: b1581780 -- (.cxr 0xffffffffb1581780)
eax=00000000 ebx=83d940d8 ecx=00000008 edx=00000000 esi=83d94000 edi=83d940d4
eip=a5f8f703 esp=b1581c70 ebp=b1581c84 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
ewusbnet+0x2703:
a5f8f703 f6400605 test byte ptr [eax+6],5 ds:0023:00000006=??
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: 00000006
READ_ADDRESS: GetPointerFromAddress: unable to read from 8217d718
Unable to read MiSystemVaType memory at 8215d160
00000006
FOLLOWUP_IP:
ewusbnet+2703
a5f8f703 f6400605 test byte ptr [eax+6],5
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 8207dc53 to a5f8f703
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b1581c84 8207dc53 00000000 842c4360 000005a0 ewusbnet+0x2703
b1581ccc a5f9e76c 82051413 83ab9008 83c13120 nt!IopfCompleteRequest+0x128
b1581ce0 a5f9db73 83ab9008 83ab9a5c 83ab9184 ewusbnet+0x1176c
b1581d50 822239df 01ab9008 a8ca74cf 00000000 ewusbnet+0x10b73
b1581d90 820d5219 a5f9d6c2 83ab9008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ewusbnet+2703
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ewusbnet
IMAGE_NAME: ewusbnet.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b1ce833
STACK_COMMAND: .cxr 0xffffffffb1581780 ; kb
FAILURE_BUCKET_ID: 0x7E_ewusbnet+2703
BUCKET_ID: 0x7E_ewusbnet+2703
Followup: MachineOwner
---------
It appears that the problem is from a driver. Update driver
Ewusbnet.sys file description
Productname:Huawei Technologies Co., Ltd. USB NDIS Miniport Driver
Description:USB NDIS Miniport Driver
Company:Huawei Technologies Co., Ltd.
Quote