BSOD with NVIDIA 610M when running with any application

[miyaboy]

Hi

I am using a ASUS K43S Laptop. The laptop is auto configured to run Intel 3000 HD Graphics as display. When I select applications like Adobe Photoshop CS 5 and Diablo 3 to run with the Nvidia graphics card, a BSOD appears. I have tried to update Nvdia graphics to the latest drivers ver. 306.23. I am baffled as to why this happens

The techical details are as follows.

Processor: Intel Core i7-2670 QM, 2.2Ghz (Intel 3000 HD Graphics)
RAM: 8 GB
HDD: 750 GB
Graphics Card: Nvidia 610M
OS: Windows 7 Home Premium x64

Attached is the BSOD zip file.

Please assist to help me to resolve this issue.


Thank you.

 

[koolkat77]

Welcome

Re your bug check 116, go through this guide:
→ http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

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

Use !analyze -v to get detailed debugging information.

[COLOR="red"]BugCheck 116[/COLOR], {fffffa8007ca0010, fffff8800f79c584, 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
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+14b584 )

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

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

[COLOR="Red"]VIDEO_TDR_FAILURE (116)[/COLOR]
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8007ca0010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f79c584, 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+14b584
fffff880`0f79c584 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`046e74f8 fffff880`04b09000 : 00000000`00000116 fffffa80`07ca0010 fffff880`0f79c584 00000000`00000000 : nt!KeBugCheckEx
fffff880`046e7500 fffff880`04b08d0a : fffff880`0f79c584 fffffa80`07ca0010 fffffa80`0c2db810 fffffa80`0c2bd010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`046e7540 fffff880`04baff07 : fffffa80`07ca0010 00000000`00000000 fffffa80`0c2db810 fffffa80`0c2bd010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`046e7570 fffff880`04bddd5a : fffffa80`ffffffff 00000000`0000ab41 fffff880`046e76c0 00000000`00000006 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`046e7650 fffff880`04bc3bb1 : fffffa80`0c2dd000 ffffffff`feced300 00000000`00000006 fffffa80`0c2dd000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`046e7690 fffff880`04bc104c : 00000000`00000001 fffff8a0`148bd630 fffffa80`0c2dd000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`046e7790 fffff880`04bbe803 : 00000000`00000000 fffffa80`07c0d000 00000000`00000014 fffff8a0`148bd630 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xfc
fffff880`046e77d0 fffff880`04bd865d : 00000000`00000000 fffff8a0`12540980 fffffa80`00000000 fffffa80`07146620 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd6f
fffff880`046e79a0 fffff880`04bd8398 : fffff800`00b96080 fffff880`04bd7d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`046e7b90 fffff880`04bd7e96 : 00000000`00000000 fffffa80`077f5d50 00000000`00000080 fffffa80`0c2bd010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`046e7bc0 fffff800`03371e6a : 00000000`0282ea15 fffffa80`0c2dc760 fffffa80`06f93190 fffffa80`0c2dc760 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`046e7c00 fffff800`030cbec6 : fffff800`0324de80 fffffa80`0c2dc760 fffff800`0325bcc0 00000000`00000103 : nt!PspSystemThreadStartup+0x5a
fffff880`046e7c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+14b584
fffff880`0f79c584 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+14b584

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  503f8bb8

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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