Antivirus Software:
Code:
smc.exe c:\program files (x86)\symantec\symantec endpoint protection\12.1.671.4971.105\bin64\smc.exe 2488 8 1024 8192 3/12/2012 1:49 PM 12.1.671.4971 2.47 MB (2,591,232 bytes) 6/17/2011 8:10 PM
ccsvchst.exe c:\program files (x86)\symantec\symantec endpoint protection\12.1.671.4971.105\bin\ccsvchst.exe 1932 8 1024 16384 3/12/2012 1:49 PM 10.1.2.14 134.01 KB (137,224 bytes) 6/14/2011 7:31 PM
ccsvchst.exe c:\program files (x86)\symantec\symantec endpoint protection\12.1.671.4971.105\bin\ccsvchst.exe 3220 8 1024 3072 3/12/2012 1:49 PM 10.1.2.14 134.01 KB (137,224 bytes) 6/14/2011 7:31 PM
Code:
Loading Dump File [D:\Kingston\BSODDmpFiles\mdenner\Windows_NT6_BSOD_jcgriff2\030112-29140-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03064000 PsLoadedModuleList = 0xfffff800`032a9670
Debug session time: Wed Feb 29 20:01:40.738 2012 (UTC - 6:00)
System Uptime: 0 days 0:08:24.985
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.......
Unable to load image \SystemRoot\system32\DRIVERS\nusb3xhc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for nusb3xhc.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff800030e4bb6, fffff8800cef4688, fffff8800cef3ee0}
Probably caused by : nusb3xhc.sys ( nusb3xhc+1abaf )
Followup: MachineOwner
---------
8: 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: fffff800030e4bb6, The address that the exception occurred at
Arg3: fffff8800cef4688, Exception Record Address
Arg4: fffff8800cef3ee0, 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:
nt!KeSetEvent+16
fffff800`030e4bb6 f6037f test byte ptr [rbx],7Fh
EXCEPTION_RECORD: fffff8800cef4688 -- (.exr 0xfffff8800cef4688)
ExceptionAddress: fffff800030e4bb6 (nt!KeSetEvent+0x0000000000000016)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000038
Attempt to read from address 0000000000000038
CONTEXT: fffff8800cef3ee0 -- (.cxr 0xfffff8800cef3ee0)
rax=0000000000000000 rbx=0000000000000038 rcx=0000000000000001
rdx=0000000000000000 rsi=fffffa8013aaa1b0 rdi=0000000000000000
rip=fffff800030e4bb6 rsp=fffff8800cef48c0 rbp=fffffa800d3aaa00
r8=0000000000000000 r9=fffffa800d3aaa00 r10=0000000000000078
r11=0000000000000000 r12=fffffa800d52e101 r13=ffffffffc000000d
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!KeSetEvent+0x16:
fffff800`030e4bb6 f6037f test byte ptr [rbx],7Fh ds:002b:00000000`00000038=??
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: 0000000000000038
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003313100
0000000000000038
FOLLOWUP_IP:
nusb3xhc+1abaf
fffff880`07e56baf ?? ???
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffff88007e56baf to fffff800030e4bb6
STACK_TEXT:
fffff880`0cef48c0 fffff880`07e56baf : fffffa80`0d3aaa00 fffffa80`00000000 04a404e4`04e40500 fffff880`0cef49b0 : nt!KeSetEvent+0x16
fffff880`0cef4930 fffffa80`0d3aaa00 : fffffa80`00000000 04a404e4`04e40500 fffff880`0cef49b0 fffffa80`0d3aaa00 : nusb3xhc+0x1abaf
fffff880`0cef4938 fffffa80`00000000 : 04a404e4`04e40500 fffff880`0cef49b0 fffffa80`0d3aaa00 fffff800`030e4021 : 0xfffffa80`0d3aaa00
fffff880`0cef4940 04a404e4`04e40500 : fffff880`0cef49b0 fffffa80`0d3aaa00 fffff800`030e4021 fffffa80`0d3aaad3 : 0xfffffa80`00000000
fffff880`0cef4948 fffff880`0cef49b0 : fffffa80`0d3aaa00 fffff800`030e4021 fffffa80`0d3aaad3 00000000`00000002 : 0x4a404e4`04e40500
fffff880`0cef4950 fffffa80`0d3aaa00 : fffff800`030e4021 fffffa80`0d3aaad3 00000000`00000002 fffffa80`13aaa060 : 0xfffff880`0cef49b0
fffff880`0cef4958 fffff800`030e4021 : fffffa80`0d3aaad3 00000000`00000002 fffffa80`13aaa060 fffffa80`0d3aaa00 : 0xfffffa80`0d3aaa00
fffff880`0cef4960 fffff880`00d67a4e : fffffa80`0d3aaa00 fffffa80`0d3aaa00 fffffa80`0d3aaa00 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`0cef4a50 fffff800`031deaa2 : fffffa80`0d3aaa00 00000000`00000000 fffffa80`0d3aaa00 fffffa80`13aaa1b0 : pci!PciDispatchPnpPower+0x146
fffff880`0cef4a90 fffff880`07e6e46e : 00000000`00000012 00000000`00000000 fffff880`000000f3 fffff880`090e4965 : nt!IopPoHandleIrp+0x32
fffff880`0cef4ac0 00000000`00000012 : 00000000`00000000 fffff880`000000f3 fffff880`090e4965 fffffa80`0d3aab18 : nusb3xhc+0x3246e
fffff880`0cef4ac8 00000000`00000000 : fffff880`000000f3 fffff880`090e4965 fffffa80`0d3aab18 00000000`00000000 : 0x12
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nusb3xhc+1abaf
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nusb3xhc
IMAGE_NAME: nusb3xhc.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ea60982
STACK_COMMAND: .cxr 0xfffff8800cef3ee0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nusb3xhc+1abaf
BUCKET_ID: X64_0x7E_nusb3xhc+1abaf
Followup: MachineOwner
---------
Points to a USB device or possibly the ports being in a safe power state. Other possible causes are Memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
The above is for if your crashes return again.
For your current problem: Hardware devices are not working or are not detected in Windows