BSOD Probably related to video driver

[circle26]

Hey guys,

So recently I've been getting quite a few BSODs from my 6 month old laptop.
For the research I've installed bluescreenview to see what is causing the crashes.
Here is the logs for the most recent crash I had (Which is about 20 mins earlier):

==================================================
Dump File : 011014-13728-01.dmp
Crash Time : 2014/1/10 下午 10:01:24
Bug Check String :
Bug Check Code : 0x00000116
Parameter 1 : fffffa80`0cf52010
Parameter 2 : fffff880`106712bc
Parameter 3 : ffffffff`c000009a
Parameter 4 : 00000000`00000004
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description : DirectX Graphics Kernel
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\011014-13728-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 478,440
Dump File Time : 2014/1/10 下午 10:02:57
==================================================
If there is any other additional information need, I'm most gladly to provide.

 

[Arc]

Hi circle26.

Update the display driver to 332.21 WHQL.

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

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.

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. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Let us know the results. For any further issue, post it following the Blue Screen of Death (BSOD) Posting Instructions.
_________________________________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800cf52010, fffff880106712bc, 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+99b2bc )

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: fffffa800cf52010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880106712bc, 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+99b2bc
fffff880`106712bc 803de6fceeff00  cmp     byte ptr [nvlddmkm+0x88afa9 (fffff880`10560fa9)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`07136a48 fffff880`06494140 : 00000000`00000116 fffffa80`0cf52010 fffff880`106712bc ffffffff`c000009a : nt!KeBugCheckEx
fffff880`07136a50 fffff880`06467867 : fffff880`106712bc fffffa80`0cc21000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`07136a90 fffff880`06493f4f : fffffa80`ffffd84d 00000000`00000000 fffffa80`0cf52010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`07136b40 fffff880`0656303d : fffffa80`0a726c10 00000000`00000080 00000000`00000000 fffffa80`0cb7d410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`07136bc0 fffff800`05f2d2ea : 00000000`026c1cb4 fffffa80`0ca03b50 fffffa80`06988b30 fffffa80`0ca03b50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`07136c00 fffff800`05c818e6 : fffff880`049b4180 fffffa80`0ca03b50 fffff880`049befc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`07136c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+99b2bc
fffff880`106712bc 803de6fceeff00  cmp     byte ptr [nvlddmkm+0x88afa9 (fffff880`10560fa9)],0

SYMBOL_NAME:  nvlddmkm+99b2bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5280da75

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`0fcd6000 fffff880`10917000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Mon Nov 11 18:54:05 2013 (5280DA75)
    CheckSum:         00C10283
    ImageSize:        00C41000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

 

[circle26]

Dear Arc,

After I posted this article, I realized that my computer isn't using the NVidia Video Drive. Instead it was using the Intel one that is powered by my processor
I tried to restore my computer to 5 days ago but with no progress. I believe that there must be something wrong with the video driver.
I never overclocked any of my hardwares nor have any clue on how to.
Also I always have a fan that is below my laptop that is running the whole time my computer's running.
Before you replied, I have already contacted my provider and sent my computer for a repair for it is still in its warranty.

Still, thanks alot for you and the community's help. I am already touched by your reply.
Cheers and thanks alot
circle26

 

[Arc]

Before you replied, I have already contacted my provider and sent my computer for a repair for it is still in its warranty.

Most appropriate step.

Inform us when you get it back?

 

[circle26]

Sure thing. I'll inform you soon as I get the news back.

 

[Classique]

I am also curious to the result of this. I'm going through the exact same error.