BSOD linked to graphics card - "failed to reset the display adapter"

Hey, I got my computer last September and it has been working perfectly up until last night when I was watching BBC iPlayer and suddenly it froze, Firefox Crashed, then it froze again and everything went black. Now whenever I try to boot up I get a BSOD saying that it failed to reset the display adapter. I can boot into safe mode and I've tried uninstalling and reinstalling drivers for my graphics cards. I get an error on the hardware info saying that the AMDA00 driver can't be run. If I manually disable the graphics cards then I can boot with no problems just using the onboard graphics.

I've attached the SF Diagnostic folder, any help is greatly appreciated.

EDIT: Got a shot of the BSOD to finally read the error as:
STOP: 0x00000116 (0xFFFFFA800A89F010, 0xFFFFF8800F3A1034, 0x0000000000000000,0x0000000000000002)
nvlddmkm.sys - Address FFFFF8800F3A1034 base at FFFFF8800F24E000, Datestamp 5267afe

Try other versions of the display driver.
You may try the drivers on a trial and error basis:

• 320.49 WHQL
• 327.23 WHQL
• 331.58 WHWL
• 331.65 WHQL
• 331.82 WHQL
• 332.21 WHQL

Get them from Drivers - Download NVIDIA Drivers

Do a clean install on all of them. Uninstall the previously installed driver first.
Uninstall All nvidia items in Control Panel > Programs and features

• 
  
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Download the target WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Lengthy process, but the only stable version of nvidia is 314.22 lately, which does not support 700 series GPU.

Also, check it physically that the GPU is properly seated in the PCIe slot.

If you anyhow can boot into windows with the GPU on, stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

If no improvement anyhow, we have to accept that the GPU is over.
______________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800a8192f0, fffff8800f3fa034, 0, 2}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+153034 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800a8192f0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f3fa034, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+153034
fffff880`0f3fa034 803dee1a730000  cmp     byte ptr [nvlddmkm+0x884b29 (fffff880`0fb2bb29)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`055f4888 fffff880`0ff3b140 : 00000000`00000116 fffffa80`0a8192f0 fffff880`0f3fa034 00000000`00000000 : nt!KeBugCheckEx
fffff880`055f4890 fffff880`0ff3ae4a : fffff880`0f3fa034 fffffa80`0a8192f0 fffffa80`0a28bd50 fffffa80`09ef0410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`055f48d0 fffff880`0f20ff13 : fffffa80`0a8192f0 00000000`00000000 fffffa80`0a28bd50 fffffa80`09ef0410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`055f4900 fffff880`0f239cf1 : 00000000`ffffffff 00000000`00000179 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`055f49e0 fffff880`0f238437 : 00000000`00000102 00000000`00000000 00000000`00000179 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`055f4a10 fffff880`0f20b2d2 : ffffffff`ff676980 fffffa80`09ef0410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`055f4ab0 fffff880`0f237ff6 : 00000000`00000000 fffffa80`0a28bd50 00000000`00000080 fffffa80`09ef0410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`055f4bc0 fffff800`033742ea : 00000000`00e8c057 fffffa80`09f13a00 fffffa80`069f0040 fffffa80`09f13a00 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`055f4c00 fffff800`030c88e6 : fffff880`03290180 fffffa80`09f13a00 fffff880`0329b0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`055f4c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+153034
fffff880`0f3fa034 803dee1a730000  cmp     byte ptr [nvlddmkm+0x884b29 (fffff880`0fb2bb29)],0

SYMBOL_NAME:  nvlddmkm+153034

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52676afe

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

6: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f2a7000 fffff880`0fede000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Oct 23 11:51:50 2013 (52676AFE)
    CheckSum:         00C0CF0F
    ImageSize:        00C37000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

jimbop117 said:

Thanks for the help!

I've worked my way through everything you suggested and it's still giving me the same BSOD every time I try booting with the card in so it must just be a bad card.

I've contacted the site that I got my PC from and they said they'll send me out a replacement since it's still in warranty.:)

That is good. Hope the replacement one will work stable.