Problem Devices:
Code:
USB Mass Storage Device USB\VID_066F&PID_8000\18040000E7268D900002DCF617648D90 This device cannot start.
Photosmart C6100 series ROOT\MULTIFUNCTION\0000 The drivers for this device are not installed.
Photosmart C6100 series ROOT\MULTIFUNCTION\0001 The drivers for this device are not installed.
Photosmart C6100 series ROOT\MULTIFUNCTION\0002 The drivers for this device are not installed.
Photosmart C6100 series ROOT\MULTIFUNCTION\0003 The drivers for this device are not installed.
Photosmart C6100 series ROOT\MULTIFUNCTION\0004 This device is disabled.
Security Software (this is just to check that it is installed and working properly; nothing needs to be done with this information at this time):
Code:
mbamservice.exe c:\program files (x86)\malwarebytes' anti-malware\mbamservice.exe 2912 8 200 1380 4/18/2012 1:54 PM Not Available Not Available Not Available
msmpeng.exe c:\program files\microsoft security client\antimalware\msmpeng.exe 972 8 200 1380 4/18/2012 1:52 PM 3.0.8402.0 12.48 KB (12,784 bytes) 4/27/2011 5:21 PM
nissrv.exe c:\program files\microsoft security client\antimalware\nissrv.exe 2988 8 200 1380 4/18/2012 1:52 PM 3.0.8402.0 281.52 KB (288,272 bytes) 4/27/2011 5:21 PM
msseces.exe c:\program files\microsoft security client\msseces.exe 3636 8 200 1380 4/18/2012 1:53 PM 2.1.1116.0 1.37 MB (1,436,736 bytes) 6/15/2011 2:35 PM
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\canario440\Echo\041812-139558-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`0301b000 PsLoadedModuleList = 0xfffff800`0325f650
Debug session time: Wed Apr 18 05:47:31.808 2012 (UTC - 6:00)
System Uptime: 0 days 0:24:38.932
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80080cc028, b419a000, 145}
Probably caused by : hardware
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80080cc028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b419a000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000145, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: chrome.exe
CURRENT_IRQL: f
STACK_TEXT:
fffff880`009f0a88 fffff800`03615a3b : 00000000`00000124 00000000`00000000 fffffa80`080cc028 00000000`b419a000 : nt!KeBugCheckEx
fffff880`009f0a90 fffff800`031a7b33 : 00000000`00000001 fffffa80`080cdd30 00000000`00000000 fffffa80`080cdd80 : hal!HalBugCheckSystem+0x1e3
fffff880`009f0ad0 fffff800`03615700 : 00000000`00000728 fffffa80`080cdd30 fffff880`009f0e30 fffffa80`05a3a900 : nt!WheaReportHwError+0x263
fffff880`009f0b30 fffff800`03615052 : fffffa80`080cdd30 fffff880`009f0e30 fffffa80`080cdd30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f0c80 fffff800`03608e8f : 00000000`001e1388 00000000`00000001 fffff880`009f0eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f0cc0 fffff800`0309656c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`009f0cf0 fffff800`030963d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f0e30 fffff800`030b4522 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`03b88090 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x122
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
Followup: MachineOwner
---------
For the above crash, read through the information in Stop 0x124 - what it means and what to try and use the following to supplement that link.
Make sure to read through the Stop 0x124 - what it means and what to try link carefully.