BSOD Windows 7 - ntoskrnl.exe+7cc40

As Promised:

Driver Verifier enabled as directed and ran it into the ground.

Seem to be alot of views... Is my problem common or just scaring away the Gurus?

Here are a few things I have tried.

Rolled back AMD driver to last version, Crashed.

Removed all peripherals except USB keyboard and Mouse and monitor.

Ran GPUZ through a crash. Log attached.

I will be going to Saphire's site and downloading any driver they have listed there for my Video Card (Radeon HD 6850)

Please help if you can.

Code:

Loading Dump File [F:\BSODDmpFiles\garthrs\Windows_NT6_BSOD_jcgriff2\021312-20950-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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c17000 PsLoadedModuleList = 0xfffff800`02e5c670
Debug session time: Mon Feb 13 14:18:13.726 2012 (GMT-7)
System Uptime: 0 days 0:50:22.412
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, 10, fffff880089a3870, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: 0000000000000010, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880089a3870, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
+0
00000000`00000010 ??              ???

CONTEXT:  fffff880089a3870 -- (.cxr 0xfffff880089a3870)
rax=fffffa80051ef020 rbx=0000000000000000 rcx=fffffa80080b4000
rdx=0000000000000550 rsi=fffff9801b970f00 rdi=fffff880089a4430
rip=0000000000000010 rsp=fffff880089a4258 rbp=fffff88009510000
 r8=0000000026f80000  r9=0000000000000000 r10=0000000000000550
r11=fffff8a0093c0000 r12=fffffa80062a0000 r13=000000000001ffa4
r14=ffffffffc000000d r15=fffffa80081e0000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
00000000`00000010 ??              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x3B

PROCESS_NAME:  DunDefGame.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000010

STACK_TEXT:  
fffff880`089a2fa8 fffff800`02c931e9 : 00000000`0000003b 00000000`c0000005 00000000`00000010 fffff880`089a3870 : nt!KeBugCheckEx
fffff880`089a2fb0 fffff800`02c92b3c : fffff880`089a4018 fffff880`089a3870 00000000`00000000 fffff880`052fbdec : nt!KiBugCheckDispatch+0x69
fffff880`089a30f0 fffff800`02cbf4fd : fffff960`0034f930 fffff960`0031575c fffff960`00060000 fffff880`089a4018 : nt!KiSystemServiceHandler+0x7c
fffff880`089a3130 fffff800`02cbe2d5 : fffff800`02dde788 fffff880`089a31a8 fffff880`089a4018 fffff800`02c17000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`089a3160 fffff800`02ccf361 : fffff880`089a4018 fffff880`089a3870 fffff880`00000000 fffff880`089a4430 : nt!RtlDispatchException+0x415
fffff880`089a3840 fffff800`02c932c2 : fffff880`089a4018 00000000`00000000 fffff880`089a40c0 fffff980`1b970f00 : nt!KiDispatchException+0x135
fffff880`089a3ee0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSystemServiceHandler+7c
fffff800`02c92b3c b801000000      mov     eax,1

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiSystemServiceHandler+7c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x3B_VRF_nt!KiSystemServiceHandler+7c

BUCKET_ID:  X64_0x3B_VRF_nt!KiSystemServiceHandler+7c

Followup: MachineOwner
---------

Loading Dump File [F:\BSODDmpFiles\garthrs\Windows_NT6_BSOD_jcgriff2\021112-22854-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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c5f000 PsLoadedModuleList = 0xfffff800`02ea4670
Debug session time: Sat Feb 11 05:16:41.275 2012 (GMT-7)
System Uptime: 0 days 1:43:33.867
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80000000000, 0, fffff800030f8ffc, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PfTCreateTraceDump+37c )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff80000000000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030f8ffc, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0e100
 fffff80000000000 

FAULTING_IP: 
nt!PfTCreateTraceDump+37c
fffff800`030f8ffc 4c3b36          cmp     r14,qword ptr [rsi]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880097db940 -- (.trap 0xfffff880097db940)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a011dd5918 rbx=0000000000000000 rcx=000000000000ffff
rdx=000000000000027c rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030f8ffc rsp=fffff880097dbad8 rbp=0000000000000001
 r8=0000000000000010  r9=fffff8a0041dd000 r10=000000000000827c
r11=fffff880097dbb00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!PfTCreateTraceDump+0x37c:
fffff800`030f8ffc 4c3b36          cmp     r14,qword ptr [rsi] ds:0002:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c879fc to fffff80002cdbc40

STACK_TEXT:  
fffff880`097db7d8 fffff800`02c879fc : 00000000`00000050 fffff800`00000000 00000000`00000000 fffff880`097db940 : nt!KeBugCheckEx
fffff880`097db7e0 fffff800`02cd9d6e : 00000000`00000000 fffff800`00000000 00000000`00008000 fffff8a0`041ba908 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`097db940 fffff800`030f8ffc : fffff800`030f8fdd fffff8a0`041ba8f8 00000000`00000001 fffff8a0`11dd58f8 : nt!KiPageFault+0x16e
fffff880`097dbad8 fffffa80`0aa0bb01 : fffff800`031480b0 fffff880`097dbc10 fffff8a0`041b8018 fffff8a0`11dcb000 : nt!PfTCreateTraceDump+0x37c
fffff880`097dbbd8 fffff800`031480b0 : fffff880`097dbc10 fffff8a0`041b8018 fffff8a0`11dcb000 fffff8a0`11dca000 : 0xfffffa80`0aa0bb01
fffff880`097dbbe0 fffff800`0314dca3 : fffffa80`0aa0bb01 00000000`00000080 fffffa80`099e39e0 fffff800`02e63da8 : nt!PfTGenerateTrace+0x10
fffff880`097dbc10 fffff800`02f76fee : ffffffff`ff676980 fffffa80`0aa0bb60 fffff880`097dbdb0 fffffa80`0aa0bb60 : nt!PfTLoggingWorker+0x113
fffff880`097dbd40 fffff800`02ccd5e6 : fffff880`02fd5180 fffffa80`0aa0bb60 fffff880`02fdffc0 fffff880`0102dcb0 : nt!PspSystemThreadStartup+0x5a
fffff880`097dbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PfTCreateTraceDump+37c
fffff800`030f8ffc 4c3b36          cmp     r14,qword ptr [rsi]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!PfTCreateTraceDump+37c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x50_nt!PfTCreateTraceDump+37c

BUCKET_ID:  X64_0x50_nt!PfTCreateTraceDump+37c

Followup: MachineOwner
---------

Loading Dump File [F:\BSODDmpFiles\garthrs\Windows_NT6_BSOD_jcgriff2\020912-19905-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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e52670
Debug session time: Thu Feb  9 18:16:39.666 2012 (GMT-7)
System Uptime: 1 days 4:42:10.352
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff680000d3518, 862000006161b847, fffff6800001a048}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+330bc )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff680000d3518
Arg3: 862000006161b847
Arg4: fffff6800001a048

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_403

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002c313f6 to fffff80002c89c40

STACK_TEXT:  
fffff880`06ecf7a8 fffff800`02c313f6 : 00000000`0000001a 00000000`00000403 fffff680`000d3518 86200000`6161b847 : nt!KeBugCheckEx
fffff880`06ecf7b0 fffff800`02cbbbb7 : fffff700`01080000 fffff680`000d3ff8 fffffa80`051d9990 996f9e52`52faa500 : nt! ?? ::FNODOBFM::`string'+0x330bc
fffff880`06ecf960 fffff800`02c770ff : fffffa80`00000000 00000000`1b9f1fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`06ecfb20 fffff800`02c88ed3 : ffffffff`ffffffff 00000000`0501e810 00000000`0501e808 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`06ecfc20 00000000`76ec14fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0501e7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ec14fa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+330bc
fffff800`02c313f6 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+330bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+330bc

BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+330bc

Followup: MachineOwner
---------

1. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...
2. Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...
3. Possible causes are Memory problems... Drivers...

Thanks to Dave76 for help understanding possible causes.



Do you have the full versions of Malwarebytes and Microsoft Security Essentials running at the same time? Two full security systems that accomplish the same tasks running at once is known to cause stability problems.

Please remove the program that uses this driver. AMD Overdrive or AMD Vision Engine Control Center are the most likely candidates.

Code:

AODDriver2	fffff880`07c31000	fffff880`07c62000	Wed Jun 15 02:38:35 2011 (4df86f8b)	00012df4		AODDriver2.sys

We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

• If you are overclocking any hardware, please stop.
  
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. Run Driver Verifier
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.

Thanks for responding.

I have done alot of troubleshooting in the 3 days since I posted the message.

I tried swapping out the video card again since i had found bad ram after the initial swap.

The problem seems to have solved itself.

FYI:
"Please remove the program that uses this driver. AMD Overdrive or AMD Vision Engine Control Center are the most likely candidates. "

This is the default software AMD uses to control its card chipset. You cannot download the driver without since the driver is part of the software. AMD Overdrive is function of that software. One I do not use. Thanks for pointing it out. I'll make sure it is not turned on.

A friend of mine gave me four sticks of dominator ram to test in the machine and it crashed with same faults as before.

The Motherboard was verfified by ASUS less than 10 days ago.

The RAM is functional

I am pretty sure that my issues was caused by corrupt ram on the video card. I'll be sending it to Sapphire to repair... I'll let you know once it gets back what was wrong.

Thanks again for responding.

You're welcome, and those are all excellent troubleshooting steps. Well done!

Look forward to hearing the results of the graphics card replacement.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Mike\Documents\Kingston\BSODDmpFiles\garthrs\minidump1\021812-18501-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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03090670
Debug session time: Sat Feb 18 18:43:00.449 2012 (GMT-7)
System Uptime: 0 days 0:34:08.729
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 119, {7000000, fffffa8007810010, fffffa80054aa010, fffffa80055d0300}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCheckConditionDeviceCommand+8c )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000007000000, The subtype of the bugcheck:
Arg2: fffffa8007810010
Arg3: fffffa80054aa010
Arg4: fffffa80055d0300

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  GameClient.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff880015d822f to fffff80002ec7c40

STACK_TEXT:  
fffff880`06c8d6e8 fffff880`015d822f : 00000000`00000119 00000000`07000000 fffffa80`07810010 fffffa80`054aa010 : nt!KeBugCheckEx
fffff880`06c8d6f0 fffff880`0420e318 : fffff8a0`0d24fa70 00000000`00000000 fffffa80`055d0300 fffff8a0`0d24fa70 : watchdog!WdLogEvent5+0x11b
fffff880`06c8d740 fffff880`04201d1f : fffffa80`0000378e fffffa80`07821000 fffff8a0`0d24fa70 fffffa80`07810010 : dxgmms1!VidSchiCheckConditionDeviceCommand+0x8c
fffff880`06c8d770 fffff880`0430698e : fffff8a0`0c3f2000 fffff8a0`0c3f2000 00000000`00000001 00000000`00000000 : dxgmms1!VidMmTerminateAllocation+0x203
fffff880`06c8d850 fffff880`0430a79c : fffff8a0`0a124200 fffff880`06c8dca0 00000000`00000000 fffff880`042d13af : dxgkrnl!DXGDEVICE::TerminateAllocations+0x166
fffff880`06c8d8a0 fffff880`0430ce57 : fffff8a0`0c3f2000 fffff880`06c8d9b0 fffffa80`084f2c01 00000000`00000001 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x448
fffff880`06c8d930 fffff960`0021f5e2 : 00000000`00000000 fffffa80`055b8790 00000000`00000020 00000000`730a6168 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`06c8dbf0 fffff800`02ec6ed3 : fffffa80`055b8790 00000000`000004a4 00000000`00000000 fffffa80`057ea480 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`06c8dc20 00000000`730c141a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0b5ae2a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x730c141a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiCheckConditionDeviceCommand+8c
fffff880`0420e318 c744243071c8ffff mov     dword ptr [rsp+30h],0FFFFC871h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VidSchiCheckConditionDeviceCommand+8c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiCheckConditionDeviceCommand+8c

BUCKET_ID:  X64_0x119_dxgmms1!VidSchiCheckConditionDeviceCommand+8c

Followup: MachineOwner
---------

I have never seen this error, but it looks similar to 0x116; refer to STOP 0x116: VIDEO_TDR_ERROR troubleshooting.

Also, what is GameClient.exe?

I believe that gameclient is a steam application used to run the games through the steam interface.

I'll check out the link.

I somehow knew that I'd have some obscure issue that no one can solve. My luck is pretty bad.

These errors are all over the place...

I ran the prime95 test and got a video driver error. Which I downloaded from AMD's site just three days ago.

Minidump attached.

I seriously have no idea what to do...

You may want to try re-installing the video driver. Use these steps to re-install the latest driver (I know you have the latest, but it is possible it is corrupted).

1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Display adapters
7. Do the following for each adapter (in case you have multiple display cards)
   
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts

Alternatively:

1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. Do the following for each adapter (in case you have multiple display cards)
   
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts

If the above does not work, try installing an older driver and see if it provides more stability. Run the hardware tests again to check stability with each driver.