BSOD after nvidia driver updates - computer will only boot in safemode

Problems started earlier in the month when updating my NVidia drivers. Computer worked for the last few weeks but would get random display errors. I attempted to revert to previous drivers however it did not fix the problem. 2 days ago, computer started crashing and will now only boot in safemode. I attempted a restore prior to the NVidia install, but the restore point was not available for that time period.

I've also uninstalled/reinstalled the video card and windows automatically installs the drivers.

I uploaded the zip file per instructions.

Thanks in advance,
Joe

Boot in safe mode and Install the NVIDIA DRIVERS 314.22WHQL only as described.

• 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
• Boot normally now. Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Does it do any better? Let us know.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {10, 2, 1, fffff80002ec9f1f}

*** 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+e08fc )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ec9f1f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f8100
GetUlongFromAddress: unable to read from fffff800030f81c0
 0000000000000010 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeAcquireInStackQueuedSpinLock+5f
fffff800`02ec9f1f 488717          xchg    rdx,qword ptr [rdi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

TRAP_FRAME:  fffff80000ba23c0 -- (.trap 0xfffff80000ba23c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff80000ba2630 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ec9f1f rsp=fffff80000ba2550 rbp=fffffa800ebdc000
 r8=fffff80000ba2630  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KeAcquireInStackQueuedSpinLock+0x5f:
fffff800`02ec9f1f 488717          xchg    rdx,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ec0169 to fffff80002ec0bc0

STACK_TEXT:  
fffff800`00ba2278 fffff800`02ec0169 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00ba2280 fffff800`02ebede0 : fffff800`00ba24f0 00000000`00000004 fffff800`00ba24f8 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba23c0 fffff800`02ec9f1f : fffff880`04a485d5 00000000`000007ff fffffa80`0f500000 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00ba2550 fffff880`049648fc : fffffa80`0ebdc000 00000000`00000000 fffffa80`0ebdc000 00000000`c1d000a1 : nt!KeAcquireInStackQueuedSpinLock+0x5f
fffff800`00ba25a0 fffffa80`0ebdc000 : 00000000`00000000 fffffa80`0ebdc000 00000000`c1d000a1 fffffa80`0f4267a0 : nvlddmkm+0xe08fc
fffff800`00ba25a8 00000000`00000000 : fffffa80`0ebdc000 00000000`c1d000a1 fffffa80`0f4267a0 fffffa80`00000001 : 0xfffffa80`0ebdc000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+e08fc
fffff880`049648fc ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+e08fc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52314e10

FAILURE_BUCKET_ID:  X64_0xA_nvlddmkm+e08fc

BUCKET_ID:  X64_0xA_nvlddmkm+e08fc

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`04884000 fffff880`0537b000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Sep 12 10:46:00 2013 (52314E10)
    CheckSum:         00AC9E83
    ImageSize:        00AF7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80102a7010, fffff88004a372b0, 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+1392b0 )

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: fffffa80102a7010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004a372b0, 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+1392b0
fffff880`04a372b0 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`025c6888 fffff880`0485d140 : 00000000`00000116 fffffa80`102a7010 fffff880`04a372b0 00000000`00000000 : nt!KeBugCheckEx
fffff880`025c6890 fffff880`0485ce4a : fffff880`04a372b0 fffffa80`102a7010 fffffa80`0fc9e010 fffffa80`0fc9d010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`025c68d0 fffff880`053b8f13 : fffffa80`102a7010 00000000`00000000 fffffa80`0fc9e010 fffffa80`0fc9d010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`025c6900 fffff880`053e2cf1 : 00000000`ffffffff 00000000`000003f2 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`025c69e0 fffff880`053e1437 : 00000000`00000102 00000000`00000006 00000000`000003f2 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`025c6a10 fffff880`053b42d2 : ffffffff`ff676980 fffffa80`0fc9d010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`025c6ab0 fffff880`053e0ff6 : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0f2e7c58 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`025c6bc0 fffff800`031222ea : 00000000`029b07b7 fffffa80`0fcc34c0 fffffa80`0cd62740 fffffa80`0fcc34c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`025c6c00 fffff800`02e768e6 : fffff800`03000e80 fffffa80`0fcc34c0 fffff800`0300ecc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`025c6c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+1392b0
fffff880`04a372b0 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+1392b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51427b3c

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`048fe000 fffff880`053a9000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Mar 15 07:07:00 2013 (51427B3C)
    CheckSum:         00A8D47C
    ImageSize:        00AAB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Remove the GPU. Either use another one (with updated driver, obviously) or use the onboard graphics (with updated driver, similarly). Let us know if the situation is the same or not.

Apparently it is a good news.

Observe the situation for some more time. Let us know how it is working after a few days ... provided there is no more issue within that time.