Welcome,
I have analyzed your dmp files. The probable cause is wireless drivers or modem drivers. Update them or just uninstall and install the most current from the manufacturers website.
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_060610-23774-01%20-%20Copy[1].zip\060610-23774-01 - Copy.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.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x8280b000 PsLoadedModuleList = 0x82953810
Debug session time: Sat Jun 5 19:13:10.700 2010 (GMT-4)
System Uptime: 0 days 0:05:15.651
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, 825c6703, 8cde5ba8, 8cde5780}
Probably caused by : ewusbnet.sys ( ewusbnet+2703 )
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: c0000005, The exception code that was not handled
Arg2: 825c6703, The address that the exception occurred at
Arg3: 8cde5ba8, Exception Record Address
Arg4: 8cde5780, 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
825c6703 f6400605 test byte ptr [eax+6],5
EXCEPTION_RECORD: 8cde5ba8 -- (.exr 0xffffffff8cde5ba8)
ExceptionAddress: 825c6703 (ewusbnet+0x00002703)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000006
Attempt to read from address 00000006
CONTEXT: 8cde5780 -- (.cxr 0xffffffff8cde5780)
eax=00000000 ebx=870220d8 ecx=00000008 edx=00000000 esi=87022000 edi=870220d4
eip=825c6703 esp=8cde5c70 ebp=8cde5c84 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00250202
ewusbnet+0x2703:
825c6703 f6400605 test byte ptr [eax+6],5 ds:0023:00000006=??
Resetting default scope
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 82973718
Unable to read MiSystemVaType memory at 82953160
00000006
FOLLOWUP_IP:
ewusbnet+2703
825c6703 f6400605 test byte ptr [eax+6],5
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 82873b33 to 825c6703
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8cde5c84 82873b33 00000000 85037008 000001ef ewusbnet+0x2703
8cde5ccc 825d576c 82847443 87025008 87020f38 nt!IopfCompleteRequest+0x128
8cde5ce0 825d4b73 87025008 87025a5c 87025184 ewusbnet+0x1176c
8cde5d50 82a196bb 01025008 a7092ce0 00000000 ewusbnet+0x10b73
8cde5d90 828cb0f9 825d46c2 87025008 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 0xffffffff8cde5780 ; kb
FAILURE_BUCKET_ID: 0x7E_ewusbnet+2703
BUCKET_ID: 0x7E_ewusbnet+2703
Followup: MachineOwner
---------
Quote