Problem Devices:
Code:
Ethernet Controller PCI\VEN_10EC&DEV_8168&SUBSYS_76401462&REV_06\4&1117575A&0&0028 The drivers for this device are not installed.
Security Software (just to check it is working and installed; nothing needs to be done with this information at this time):
Code:
mpcmdrun.exe c:\program files\microsoft security client\antimalware\mpcmdrun.exe 3172 8 200 1380 4/5/2012 11:01 PM 3.0.8402.0 266.95 KB (273,352 bytes) 4/27/2011 5:21 PM
msmpeng.exe c:\program files\microsoft security client\antimalware\msmpeng.exe 888 8 200 1380 4/5/2012 11:00 PM 3.0.8402.0 12.48 KB (12,784 bytes) 4/27/2011 5:21 PM
msseces.exe c:\program files\microsoft security client\msseces.exe 2776 8 200 1380 4/5/2012 11:00 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\BFHunter\Windows_NT6_BSOD_jcgriff2\040599-15802-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03056e50
Debug session time: Sun Apr 5 20:36:31.246 2099 (UTC - 6:00)
System Uptime: 0 days 0:03:29.885
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc000001d, fffff80002e9203d, fffff880009a98f8, fffff880009a9150}
Probably caused by : hardware ( nt!KiCommitThreadWait+1bd )
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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80002e9203d, The address that the exception occurred at
Arg3: fffff880009a98f8, Exception Record Address
Arg4: fffff880009a9150, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
nt!KiCommitThreadWait+1bd
fffff800`02e9203d 660100 add word ptr [rax],ax
EXCEPTION_RECORD: fffff880009a98f8 -- (.exr 0xfffff880009a98f8)
ExceptionAddress: fffff80002e9203d (nt!KiCommitThreadWait+0x00000000000001bd)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff880009a9150 -- (.cxr 0xfffff880009a9150)
rax=0000000000000000 rbx=fffffa8006b8bb60 rcx=0000000000000001
rdx=fffff80003011c40 rsi=fffffa8006b8bc20 rdi=fffff80003003e80
rip=fffff80002e9203d rsp=fffff880009a9b30 rbp=fffffa8006b8bb60
r8=fffffa8006a87050 r9=0000000000000000 r10=0000000000000002
r11=0000000000000000 r12=0000000000000060 r13=000000c832e6baa9
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!KiCommitThreadWait+0x1bd:
fffff800`02e9203d 660100 add word ptr [rax],ax ds:002b:00000000`00000000=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
MISALIGNED_IP:
nt!KiCommitThreadWait+1bd
fffff800`02e9203d 660100 add word ptr [rax],ax
LAST_CONTROL_TRANSFER: from fffff80002ed24c5 to fffff80002e9203d
FAILED_INSTRUCTION_ADDRESS:
nt!KiCommitThreadWait+1bd
fffff800`02e9203d 660100 add word ptr [rax],ax
STACK_TEXT:
fffff880`009a9b30 fffff800`02ed24c5 : fffffa80`06b8bb60 00000000`00000000 fffff800`00000000 00000000`00000091 : nt!KiCommitThreadWait+0x1bd
fffff880`009a9bc0 fffff800`02ed1daa : fffffa80`06a82800 00000000`00000008 00000000`000000ff 00000000`00000000 : nt!KeWaitForGate+0x101
fffff880`009a9c10 fffff800`0312e166 : fffffa80`06b8bb60 00000000`00000080 fffffa80`06b27890 fffff800`02e69479 : nt!MmZeroPageThread+0x2ed
fffff880`009a9d40 fffff800`02e69486 : fffff800`03003e80 fffffa80`06b8bb60 fffff800`03011c40 00002640`e8000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a7700 00000000`00000000 : nt!KxStartSystemThread+0x16
FOLLOWUP_IP:
nt!KiCommitThreadWait+1bd
fffff800`02e9203d 660100 add word ptr [rax],ax
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiCommitThreadWait+1bd
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .cxr 0xfffff880009a9150 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
Your latest crashes are still pointing to hardware... Also, why does the latest date have a year of 2099?
You can probably get the system inspected for free since Fry's screwed up. Most support companies have a guarantee for their services. Did you proceed with the hardware checks in my previous post? What were the results?
Note: the hard disk check may still be worth running in case the new drive is faulty, as well, but it's up to you. You could just run the disk check with "Automatically fix file system errors" to check for corrupted data which takes 5-10 minutes instead of an hour or two with both boxes checked.
You should also try to get your latest Windows Updates installed.
Quote