Welcome to Seven Forums.
The dump files indicate the crash is from:
STOP 0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Which is the same as STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
With the exception 0xC0000005: STATUS_ACCESS_VIOLATION
This indicates a memory access violation occurred.
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control
Is this a new build?
If not what OS did you previously have installed?
Any new components?
Let's start with memtest86+ and test the memory:
RAM - Test with Memtest86+
Follow the instructions on this tutorial, for the first test leave all RAM cards installed.
You need to run it for a full 7 passes, this will take several hours, best to let it run overnight.
You have 8GB RAM DDR3 1600, if you have RAM settings at (800Mhz) 1600 in the BIOS, this will likely be causing the crash.
There is a known issue with AMD CPUs integrated memory controllers having problems running RAM at 1600 MHz and above.
VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's and RAM SPEEDS
Q&A for the topic VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's & RAM....
First, change the RAM frequency to 1333MHz, then run memtest86+.
Code:
*******************************************************************************
* *
* 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: fffff80002f647d2, The address that the exception occurred at
Arg3: fffff880031cb968, Exception Record Address
Arg4: fffff880031cb1d0, 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!CmpDereferenceNameControlBlockWithLock+aa
fffff800`02f647d2 488b02 mov rax,qword ptr [rdx]
EXCEPTION_RECORD: fffff880031cb968 -- (.exr 0xfffff880031cb968)
ExceptionAddress: fffff80002f647d2 (nt!CmpDereferenceNameControlBlockWithLock+0x00000000000000aa)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880031cb1d0 -- (.cxr 0xfffff880031cb1d0)
rax=ff7ff8a008b26c98 rbx=0000000000000000 rcx=0000000000000e00
rdx=ff7ff8a008b26ca0 rsi=fffff8a008b26c98 rdi=fffff8a008b26c90
rip=fffff80002f647d2 rsp=fffff880031cbba0 rbp=0000000000007000
r8=000000009ca3430e r9=000000002cebfc39 r10=fffff8a00d9a5948
r11=fffff8a00013a140 r12=0000000000000001 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
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!CmpDereferenceNameControlBlockWithLock+0xaa:
fffff800`02f647d2 488b02 mov rax,qword ptr [rdx] ds:002b:ff7ff8a0`08b26ca0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
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: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ea90e0
ffffffffffffffff
FOLLOWUP_IP:
nt!CmpDereferenceNameControlBlockWithLock+aa
fffff800`02f647d2 488b02 mov rax,qword ptr [rdx]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff80002f646c8 to fffff80002f647d2
STACK_TEXT:
fffff880`031cbba0 fffff800`02f646c8 : fffff8a0`102ee258 fffff880`031cbc5c 00000000`00000004 00000000`00000001 : nt!CmpDereferenceNameControlBlockWithLock+0xaa
fffff880`031cbbd0 fffff800`02ec8f4e : fffff8a0`102ee258 fffff880`031cbc44 00000000`00000004 00000000`00000002 : nt!CmpCleanUpKcbCacheWithLock+0x34
fffff880`031cbc00 fffff800`02c7e961 : fffff800`02ec8c14 fffff800`02e165f8 fffffa80`06a1bb60 00000000`00000000 : nt!CmpDelayCloseWorker+0x33a
fffff880`031cbcb0 fffff800`02f14bc6 : 0000056e`00000000 fffffa80`06a1bb60 00000000`00000080 fffffa80`06a0b040 : nt!ExpWorkerThread+0x111
fffff880`031cbd40 fffff800`02c4fbc6 : fffff880`02f64180 fffffa80`06a1bb60 fffff880`02f6efc0 0000056e`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031cbd80 00000000`00000000 : fffff880`031cc000 fffff880`031c6000 fffff880`031cb900 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpDereferenceNameControlBlockWithLock+aa
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd34
STACK_COMMAND: .cxr 0xfffff880031cb1d0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!CmpDereferenceNameControlBlockWithLock+aa
BUCKET_ID: X64_0x7E_nt!CmpDereferenceNameControlBlockWithLock+aa
Followup: MachineOwner
---------
Check for an updated driver for this Network Driver Interface Specification (NDIS) 6.0 miniport driver for VIA Rhine Family Fast Ethernet Adapter.
http://www.via.com.tw/en/support/drivers.jsp
Code:
fet6x64.sys Thu Jun 19 19:40:18 2008
Looks like your system crashed while doing a Windows Update.
The event viewer is showing many updates have failed.
Code:
Event[358]:
Log Name: System
Source: Service Control Manager
Date: 2011-05-28T22:55:02.863
Event ID: 7043
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Kennedy-PC
Description:
The Windows Update service did not shut down properly after receiving a preshutdown control.
This is a Secure Channel error, What anti virus do you have installed?
Code:
Event[1392]:
Log Name: System
Source: Schannel
Date: 2011-05-28T19:01:02.668
Event ID: 36888
Task: N/A
Level: Error
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: Kennedy-PC
Description:
The following fatal alert was generated: 10. The internal error state is 10.
D/L and run Western Digital Lifeguard– Quick Test and Extended Test, on both HDDs.
Code:
Event[2974]:
Log Name: System
Source: Disk
Date: 2011-05-28T09:45:36.244
Event ID: 11
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Kennedy-PC
Description:
The driver detected a controller error on \Device\Harddisk1\DR1.