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\091110-19827-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03211000 PsLoadedModuleList = 0xfffff800`0344ee50
Debug session time: Fri Sep 10 12:02:54.324 2010 (GMT-4)
System Uptime: 0 days 0:00:54.479
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800658701a, fffff88003370998, fffff88003370200}
Probably caused by : usbvideo.sys ( usbvideo!LoadPowerLineFrequency+2ce )
Followup: MachineOwner
---------
5: 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: fffff8800658701a, The address that the exception occurred at
Arg3: fffff88003370998, Exception Record Address
Arg4: fffff88003370200, 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:
usbvideo!LoadPowerLineFrequency+2ce
fffff880`0658701a 448b4a44 mov r9d,dword ptr [rdx+44h]
EXCEPTION_RECORD: fffff88003370998 -- (.exr 0xfffff88003370998)
ExceptionAddress: fffff8800658701a (usbvideo!LoadPowerLineFrequency+0x00000000000002ce)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000044
Attempt to read from address 0000000000000044
CONTEXT: fffff88003370200 -- (.cxr 0xfffff88003370200)
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8a0037b7420
rdx=0000000000000000 rsi=fffffa800703bd30 rdi=fffff8a001f6dd90
rip=fffff8800658701a rsp=fffff88003370bd0 rbp=fffffa80080bee20
r8=0000000000000001 r9=000000000000000d r10=fffff80003211000
r11=fffffa8003b6bb60 r12=fffffa800498ba00 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
usbvideo!LoadPowerLineFrequency+0x2ce:
fffff880`0658701a 448b4a44 mov r9d,dword ptr [rdx+44h] ds:002b:00000000`00000044=????????
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: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000044
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b90e0
0000000000000044
FOLLOWUP_IP:
usbvideo!LoadPowerLineFrequency+2ce
fffff880`0658701a 448b4a44 mov r9d,dword ptr [rdx+44h]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffff8800658a63a to fffff8800658701a
STACK_TEXT:
fffff880`03370bd0 fffff880`0658a63a : fffffa80`00000010 fffffa80`00000001 ffffffff`80000978 fffffa80`0703bd30 : usbvideo!LoadPowerLineFrequency+0x2ce
fffff880`03370c50 fffff800`0357dc43 : 00000000`00000000 fffffa80`065ee520 fffffa80`065ee520 fffffa80`03b6bb60 : usbvideo!PassiveWakeup+0x26
fffff880`03370c80 fffff800`0328e961 : fffff800`03426500 fffff800`0357dc20 fffffa80`03b6bb60 fffffa80`03b6bb60 : nt!IopProcessWorkItem+0x23
fffff880`03370cb0 fffff800`03525c06 : 00000000`00000000 fffffa80`03b6bb60 00000000`00000080 fffffa80`03b52740 : nt!ExpWorkerThread+0x111
fffff880`03370d40 fffff800`0325fc26 : fffff880`03167180 fffffa80`03b6bb60 fffff880`031720c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03370d80 00000000`00000000 : fffff880`03371000 fffff880`0336b000 fffff880`0336fca0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: usbvideo!LoadPowerLineFrequency+2ce
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbvideo
IMAGE_NAME: usbvideo.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc24
STACK_COMMAND: .cxr 0xfffff88003370200 ; kb
FAILURE_BUCKET_ID: X64_0x7E_usbvideo!LoadPowerLineFrequency+2ce
BUCKET_ID: X64_0x7E_usbvideo!LoadPowerLineFrequency+2ce
Followup: MachineOwner
---------
