BSOD Driver Hang

Upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

Fill up your system specs.
See your system specs and fill it up here.

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.

There are some more things to do after obtaining the data/information.
_________________________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8011cb7420, fffff8800fc87074, 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
Probably caused by : nvlddmkm.sys ( nvlddmkm+994074 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8011cb7420, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fc87074, 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+994074
fffff880`0fc87074 803dae0aefff00  cmp     byte ptr [nvlddmkm+0x884b29 (fffff880`0fb77b29)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`022c6a48 fffff880`04ecf054 : 00000000`00000116 fffffa80`11cb7420 fffff880`0fc87074 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`022c6a50 fffff880`04ea2867 : fffff880`0fc87074 fffffa80`11631000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`022c6a90 fffff880`04ecee63 : 00000000`ffffd84d 00000000`00000080 fffffa80`11cb7420 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`022c6b40 fffff880`04f9e03d : fffffa80`0ce52660 00000000`00000080 00000000`00000000 fffffa80`11621410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`022c6bc0 fffff800`03732bae : 00000000`fffffc32 fffffa80`113eeb50 fffffa80`0ca97890 fffffa80`113eeb50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`022c6c00 fffff800`034858c6 : fffff800`0360fe80 fffffa80`113eeb50 fffff800`0361dcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`022c6c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+994074
fffff880`0fc87074 803dae0aefff00  cmp     byte ptr [nvlddmkm+0x884b29 (fffff880`0fb77b29)],0

SYMBOL_NAME:  nvlddmkm+994074

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

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

7: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f2f3000 fffff880`0ff2a000   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

It would have been better if you have supplied the screenshot of Speccy.

Anyway, the temperature is high. You need to control it.

And, the fan can be damaged. If it is damaged, you should not use the GPU having a damaged fan.

Dismantle the computer. Clean the inside carefully. Clean all the air vents and fan grills so that it can blow the hot air out efficiently. When re-seating, apply new thermal paste to the CPU.



Let us see another speccy screenshot after doing it.

If you have removed the old thermal paste properly before applying new thermal paste, and still it is the same, then you have to spend some more money on this issue.

Apply a new CPU cooler. Can it control the heat? If not, replace the CPU.

I have seen that some coolers can reduce the temperatures dramatically. I will ask my friend AddRAM to suggest something in this regard.

1st off, this IS A LAPTOP correct ?

And you have fully cleaned everything out, correct ?

Are these Speccy tempratures at idle ? ( Personally I`ve never trusted Speccy for correct temprature readings ) Use Core Temp.

Are you using a chill pad / cooler ?