I hope i could get some help here on figuring out what the issue is. Im thinking one of my graphics cards are failing but im not 100% sure. So i was playing bf3 last night and after about 30 minutes my computer locked up and the screen went black. I lost my DVI connection and about 10 seconds later the computer restarted itself. After it started back up i tried to run bf3 again and it locked up on the loading screen. After a hard reset i launched the game again and everything was fine for the 2 hours i played.
Now today i start bf3 up again and play one match with no issues. I start my second round and about half way though the computer locks up and does the same thing that happened last night. Played for about an hour total. When it locked up and restarted itself the computer didnt give me any driver crash errors or BSOD just restarted itself like everything was normal. I have both my cards clocked up to 1200 but have had them set at that since the day i got them. Top card i bought on 5/29 and the bottom one on 6/13. I have a 1200w Corsair psu so i know there getting plenty of juice. The top card never went over 61c and the bottom one never went over 59c so i know its not a temp issue. My room is a ice box from my AC so i never have any temp problems. The cpu also is clocked to 4.3hz but never went over 49c.
I went in the computer and found my crash dump reports, but to be honest i dont know 100% what im looking at. But from the parts i can understand seems like a issue with one of my cards. But if someone knows how to read these let me know what you think. Thanks
The one from last night:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Neal\Desktop\080412-8595-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*
http://msdl.microsoft.com..nload/symbolsExecutable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030Machine Name:Kernel base = 0xfffff800`03264000 PsLoadedModuleList = 0xfffff800`034a8670Debug session time: Sat Aug 4 19:45:53.343 2012 (UTC - 4:00)System Uptime: 0 days 1:03:11.530Loading Kernel Symbols............................................................................................................................................................................................Loading User SymbolsLoading unloaded module list......******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800ca60010, fffff8800ff601a4, ffffffffc000009a, 4}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : nvlddmkm.sys ( nvlddmkm+d431a4 )
Followup: MachineOwner---------
3: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************
VIDEO_TDR_FAILURE (116)Attempt to reset the display driver and recover from timeout failed.Arguments:Arg1: fffffa800ca60010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).Arg2: fffff8800ff601a4, The pointer into responsible device driver module (e.g. owner tag).Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:------------------
FAULTING_IP: nvlddmkm+d431a4fffff880`0ff601a4 4883ec28 sub rsp,28h
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT: fffff880`0bc6aa48 fffff880`07cc1000 : 00000000`00000116 fffffa80`0ca60010 fffff880`0ff601a4 ffffffff`c000009a : nt!KeBugCheckExfffff880`0bc6aa50 fffff880`07c94867 : fffff880`0ff601a4 fffffa80`0a13b000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xecfffff880`0bc6aa90 fffff880`07cc0e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`0ca60010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3fffff880`0bc6ab40 fffff880`07d8fec1 : fffffa80`0c56e470 00000000`00000080 00000000`00000000 fffffa80`0a134010 : dxgkrnl!TdrResetFromTimeout+0x23fffff880`0bc6abc0 fffff800`03579e6a : 00000000`01aa53e3 fffffa80`0a136200 fffffa80`06973890 fffffa80`0a136200 : dxgmms1!VidSchiWorkerThread+0x101fffff880`0bc6ac00 fffff800`032d3ec6 : fffff800`03455e80 fffffa80`0a136200 fffff800`03463cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5afffff880`0bc6ac40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP: nvlddmkm+d431a4fffff880`0ff601a4 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+d431a4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4fb20748
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner---------
The one from this afternoon:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Neal\Desktop\080512-8720-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*
http://msdl.microsoft.com..nload/symbolsExecutable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030Machine Name:Kernel base = 0xfffff800`03257000 PsLoadedModuleList = 0xfffff800`0349b670Debug session time: Sun Aug 5 14:22:42.920 2012 (UTC - 4:00)System Uptime: 0 days 0:41:55.107Loading Kernel Symbols............................................................................................................................................................................................Loading User SymbolsLoading unloaded module list......******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800c6f13c0, fffff8800ff761a4, ffffffffc000009a, 4}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : nvlddmkm.sys ( nvlddmkm+d431a4 )
Followup: MachineOwner---------
2: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************
VIDEO_TDR_FAILURE (116)Attempt to reset the display driver and recover from timeout failed.Arguments:Arg1: fffffa800c6f13c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).Arg2: fffff8800ff761a4, The pointer into responsible device driver module (e.g. owner tag).Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:------------------
FAULTING_IP: nvlddmkm+d431a4fffff880`0ff761a4 4883ec28 sub rsp,28h
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT: fffff880`0bc6aa48 fffff880`0795a000 : 00000000`00000116 fffffa80`0c6f13c0 fffff880`0ff761a4 ffffffff`c000009a : nt!KeBugCheckExfffff880`0bc6aa50 fffff880`0792d867 : fffff880`0ff761a4 fffffa80`0a153000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xecfffff880`0bc6aa90 fffff880`07959e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`0c6f13c0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3fffff880`0bc6ab40 fffff880`07a37ec1 : fffffa80`09151010 00000000`00000080 00000000`00000000 fffffa80`0a14b010 : dxgkrnl!TdrResetFromTimeout+0x23fffff880`0bc6abc0 fffff800`0356ce6a : 00000000`01abeac4 fffffa80`0a14c060 fffffa80`06973890 fffffa80`0a14c060 : dxgmms1!VidSchiWorkerThread+0x101fffff880`0bc6ac00 fffff800`032c6ec6 : fffff800`03448e80 fffffa80`0a14c060 fffff800`03456cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5afffff880`0bc6ac40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP: nvlddmkm+d431a4fffff880`0ff761a4 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+d431a4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4fb20748
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner---------