May be a driver issue as running in Safe Mode seems to be okay. I've attached the requested files for you to take a look at. The only driver issue flagged in perfmon was my logitech illuminated keyboard.
All three are blamed on your video driver. I would also run a system file check to verify your system files and update the below drivers.
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper
When it is removed then download and install the fresh copy.
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW
read here for more information SFC /SCANNOW Command - System File Checker
Let us know the results from the report at the end.
Ken
Code:
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\091610-21281-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`02a58000 PsLoadedModuleList = 0xfffff800`02c95e50
Debug session time: Thu Sep 16 16:59:25.540 2010 (GMT-4)
System Uptime: 0 days 0:34:43.836
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88010bba2a3, fffff88004fa8668, fffff88004fa7ed0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::EndPreparation+7b )
Followup: MachineOwner
---------
6: 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: fffff88010bba2a3, The address that the exception occurred at
Arg3: fffff88004fa8668, Exception Record Address
Arg4: fffff88004fa7ed0, 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:
dxgmms1!VIDMM_GLOBAL::EndPreparation+7b
fffff880`10bba2a3 488b01 mov rax,qword ptr [rcx]
EXCEPTION_RECORD: fffff88004fa8668 -- (.exr 0xfffff88004fa8668)
ExceptionAddress: fffff88010bba2a3 (dxgmms1!VIDMM_GLOBAL::EndPreparation+0x000000000000007b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88004fa7ed0 -- (.cxr 0xfffff88004fa7ed0)
rax=fffffa80068ceb10 rbx=fffffa8009508000 rcx=45e180fffffa8009
rdx=0000000000000000 rsi=0000000000000003 rdi=0000000000000003
rip=fffff88010bba2a3 rsp=fffff88004fa88a0 rbp=fffffa8009580260
r8=0000000000000000 r9=fffffa8009508c40 r10=fffffa8009508c40
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
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
dxgmms1!VIDMM_GLOBAL::EndPreparation+0x7b:
fffff880`10bba2a3 488b01 mov rax,qword ptr [rcx] ds:002b:45e180ff`fffa8009=????????????????
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 fffff80002d000e0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::EndPreparation+7b
fffff880`10bba2a3 488b01 mov rax,qword ptr [rcx]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88010bb279d to fffff88010bba2a3
STACK_TEXT:
fffff880`04fa88a0 fffff880`10bb279d : 00000000`00000000 fffffa80`09582010 00000000`00000003 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::EndPreparation+0x7b
fffff880`04fa8910 fffff880`10bcc65d : 00000000`00000000 fffff8a0`0013df20 fffffa80`00000000 fffffa80`09580260 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd09
fffff880`04fa8ae0 fffff880`10bcc398 : fffff800`00b96080 fffff880`10bcbd00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`04fa8cd0 fffff880`10bcbe96 : 00000000`00000000 fffffa80`0957e830 00000000`00000080 fffffa80`0945f010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`04fa8d00 fffff800`02d6cc06 : 00000000`03c48c5a fffffa80`09502060 fffffa80`05b10040 fffffa80`09502060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`04fa8d40 fffff800`02aa6c26 : fffff800`02c42e80 fffffa80`09502060 fffff800`02c50c40 fffff880`0123b534 : nt!PspSystemThreadStartup+0x5a
fffff880`04fa8d80 00000000`00000000 : fffff880`04fa9000 fffff880`04fa3000 fffff880`04fa8690 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::EndPreparation+7b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
STACK_COMMAND: .cxr 0xfffff88004fa7ed0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::EndPreparation+7b
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::EndPreparation+7b
Followup: MachineOwner
---------
Drivers to update
Code:
PxHlpa64.sys fffff880`00ed4000 fffff880`00edfd00 0x0000bd00 0x47d88a39 3/12/2008 21:58:17
000.fcl fffff880`07a00000 fffff880`07a2b000 0x0002b000 0x48dcdf7a 9/26/2008 09:11:22
CLBUDF.SYS fffff880`07ab5000 fffff880`07b1d000 0x00068000 0x49b726bb 3/10/2009 22:49:31
CLBStor.sys fffff880`02c2a000 fffff880`02c34000 0x0000a000 0x49b726be 3/10/2009 22:49:34
iaStorV.sys fffff880`010b7000 fffff880`011d5000 0x0011e000 0x49dcd76d 4/8/2009 12:57:17
dump_iaStorV.sys fffff880`02cba000 fffff880`02dd8000 0x0011e000 0x49dcd76d 4/8/2009 12:57:17
spldr.sys fffff880`017e6000 fffff880`017ee000 0x00008000 0x4a0858bb 5/11/2009 12:56:27
amdxata.sys fffff880`011de000 fffff880`011e9000 0x0000b000 0x4a12f2eb 5/19/2009 13:56:59
Quote