Solved BSOD a couple times a day. Firefox?

[Woox]

Windows 7 64-bit. Freezing and BSODing mostly while browsing facebook. Also it aint so long ago that I updated my graphics drivers for Geforce GTX 560 Ti. Adobe flash also caused problems while ago but I reinstalled it.

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? yes
- an OEM or full retail version? OEM
- What is the age of system (hardware)? 3 year
- What is the age of OS installation (have you re-installed the OS?) I have reinstalled about 6 months ago.

 

[Arc]

Woox, the questions those you answered is not any necessary in this case. Please answer the following questions with the appropriate data where necessary.

1. Was it the same before you update the display driver to 327.23 WHQL? How did the computer run with the display driver 314.22 WHQL?(dont try to later drivers without asking, lest there be any mistake).
2. 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.
3. Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
   eXtreme Power Supply Calculator
   Also let us know the wattage of your PSU.
4. Stress test the Graphics Card using Furmark.
   Video Card - Stress Test with Furmark
5. Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
   How To Clear CMOS (Reset BIOS)
6. Also, have you ever opened the cabinet?Is there enough space inside to flow air? When you dis the dusting/dismantle for the last time?

As it is an old branded desktop ...... HP Pavilion Elite HPE-140sc Desktop PC of late 2009/early 2010, the heat report and the PSU info is a must to debug a TDR.
________________________________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800f0b04e0, fffff8800841b6b4, 0, 2}

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
Probably caused by : nvlddmkm.sys ( nvlddmkm+14d6b4 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800f0b04e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800841b6b4, 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+14d6b4
fffff880`0841b6b4 803d4e3e6a0000  cmp     byte ptr [nvlddmkm+0x7f1509 (fffff880`08abf509)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`043d8858 fffff880`0748b140 : 00000000`00000116 fffffa80`0f0b04e0 fffff880`0841b6b4 00000000`00000000 : nt!KeBugCheckEx
fffff880`043d8860 fffff880`0748ae4a : fffff880`0841b6b4 fffffa80`0f0b04e0 fffffa80`0da64d50 fffffa80`0b8df410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`043d88a0 fffff880`07531f13 : fffffa80`0f0b04e0 00000000`00000000 fffffa80`0da64d50 fffffa80`0b8df410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`043d88d0 fffff880`0755fed6 : fffffa80`ffffffff 00000000`001c7693 fffff880`043d8a30 fffffa80`0b8df410 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`043d89b0 fffff880`0755ba6c : 00000000`00000000 ffffffff`feced300 fffffa80`0f5d9ec0 fffff880`0755cbee : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`043d89f0 fffff880`0755a679 : fffffa80`0b8df510 00000000`00000001 fffffa80`0b8df410 fffff880`043d8d00 : dxgmms1!VidSchiWaitForFence+0xf4
fffff880`043d8ae0 fffff880`0755a514 : fffff800`00b96080 fffff880`07559f3c fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0xe1
fffff880`043d8cd0 fffff880`0755a012 : 00000000`00000000 fffffa80`0da64d50 00000000`00000080 fffffa80`0b8df410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`043d8d00 fffff800`03315bae : 00000000`031d44ce fffffa80`0b8c1760 fffffa80`06955040 fffffa80`0b8c1760 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`043d8d40 fffff800`030688c6 : fffff800`031f2e80 fffffa80`0b8c1760 fffff800`03200cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`043d8d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+14d6b4
fffff880`0841b6b4 803d4e3e6a0000  cmp     byte ptr [nvlddmkm+0x7f1509 (fffff880`08abf509)],0

SYMBOL_NAME:  nvlddmkm+14d6b4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52314e10

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`082ce000 fffff880`08dc5000   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

 

[Woox]

1. It didnt BSOD with 314.22, but it didn't start immediatly with the new ones... If I remember right.

2. Attachment

3. I got 600W PSU and the site recommended 450W.

4. I ran the stress test for 5 mins without artifacts.

5. Not overclocking GPU, CPU or RAM. Haven't touched BIOS.

6. My cabinet is open from the side and I got a desk fan blowing there.

 

[Arc]

Also clean the fan grills, so that it can blow the hot air.

When done, let us see another speccy screenshot, and let us know how the computer is running.

 

[Woox]

I found out from the nvidia forums that people with 560 TI do get freezes and crashes with the latest drivers. So I went back to old drivers and everything has gone smoothly. Also cleaned the fan grills. Haven't yet renewed thermal paste. I guess this seems to be solved for me now.

Thank you.

 

[Arc]

Yes, you need to use old driver, the 314.22 WHQL.

But, better you re-apply the thermal paste. It is needed for your computer.