BSOD after 10-30 minutes playing any graphics-intensive game

Hi, thanks for helping. I'm not great with computers but I've been searching for a solution to this problem and can't find one so decided to start my own thread.

Windows 7 Ultimate x64-based, Asus laptop with Intel Core i5 and Geforce 610M with 2GB graphics memory.

I've tried playing Dark Souls 2, Fifa 14 and NBA 2k14. All run fine for 10-30 minutes until the BSOD.

Seemed to start when I started using an Xbox for Windows controller. I have updated the graphics card driver, the controller driver, and all windows updates are installed, including optional ones.

I also tried running NBA 2k14 without a controller plugged in and the same BSOD happened after about 10 minutes.

And I disabled Avast antivirus, also to no avail.

I have used the SF Diagnostics tool to grab the information. It is in the zip file attached.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8800F5EC95E
BCP3: FFFFF880031BD748
BCP4: FFFFF880031BCFA0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Hi joe27.

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. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Install the NVIDIA DRIVERS 314.22WHQL only, because it is needed to see the performance on a known stable driver.

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

Let us know the results.

For any further BSOD, upload all the files generated by the tool. Dont deduct any file. They are generated because those all are needed to troubleshoot an issue.
______________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800f5ec95e, fffff880031bd748, fffff880031bcfa0}

Probably caused by : nvlddmkm.sys ( nvlddmkm+50d95e )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800f5ec95e, The address that the exception occurred at
Arg3: fffff880031bd748, Exception Record Address
Arg4: fffff880031bcfa0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nvlddmkm+50d95e
fffff880`0f5ec95e 448b0401        mov     r8d,dword ptr [rcx+rax]

EXCEPTION_RECORD:  fffff880031bd748 -- (.exr 0xfffff880031bd748)
ExceptionAddress: fffff8800f5ec95e (nvlddmkm+0x000000000050d95e)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000024
Attempt to read from address 0000000000000024

CONTEXT:  fffff880031bcfa0 -- (.cxr 0xfffff880031bcfa0;r)
rax=0000000000000000 rbx=0000000000000001 rcx=0000000000000024
rdx=fffffa8009acd000 rsi=fffffa8009ae8ef0 rdi=0000000000000001
rip=fffff8800f5ec95e rsp=fffff880031bd980 rbp=fffffa8009a7a000
 r8=fffffa8009ae8ef0  r9=0000000000006400 r10=fffffa8009ae8f98
r11=fffff880031bd9e8 r12=fffffa8007d31500 r13=fffffa8009ae9000
r14=fffffa8009acd000 r15=fffffa8009ac3000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nvlddmkm+0x50d95e:
fffff880`0f5ec95e 448b0401        mov     r8d,dword ptr [rcx+rax] ds:002b:00000000`00000024=????????
Last set context:
rax=0000000000000000 rbx=0000000000000001 rcx=0000000000000024
rdx=fffffa8009acd000 rsi=fffffa8009ae8ef0 rdi=0000000000000001
rip=fffff8800f5ec95e rsp=fffff880031bd980 rbp=fffffa8009a7a000
 r8=fffffa8009ae8ef0  r9=0000000000006400 r10=fffffa8009ae8f98
r11=fffff880031bd9e8 r12=fffffa8007d31500 r13=fffffa8009ae9000
r14=fffffa8009acd000 r15=fffffa8009ac3000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nvlddmkm+0x50d95e:
fffff880`0f5ec95e 448b0401        mov     r8d,dword ptr [rcx+rax] ds:002b:00000000`00000024=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000024

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbd100
GetUlongFromAddress: unable to read from fffff80002cbd1c0
 0000000000000024 Nonpaged pool

FOLLOWUP_IP: 
nvlddmkm+50d95e
fffff880`0f5ec95e 448b0401        mov     r8d,dword ptr [rcx+rax]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from ffffffffffffffff to fffff8800f5ec95e

STACK_TEXT:  
fffff880`031bd980 ffffffff`ffffffff : fffffa80`09a7a000 fffffa80`09ae8ef0 fffffa80`09ae8ef0 ffffffff`ffffffff : nvlddmkm+0x50d95e
fffff880`031bd988 fffffa80`09a7a000 : fffffa80`09ae8ef0 fffffa80`09ae8ef0 ffffffff`ffffffff fffffa80`ffffffff : 0xffffffff`ffffffff
fffff880`031bd990 fffffa80`09ae8ef0 : fffffa80`09ae8ef0 ffffffff`ffffffff fffffa80`ffffffff ffffd319`2ec47bb2 : 0xfffffa80`09a7a000
fffff880`031bd998 fffffa80`09ae8ef0 : ffffffff`ffffffff fffffa80`ffffffff ffffd319`2ec47bb2 fffff880`0f582cc5 : 0xfffffa80`09ae8ef0
fffff880`031bd9a0 ffffffff`ffffffff : fffffa80`ffffffff ffffd319`2ec47bb2 fffff880`0f582cc5 fffffa80`09a7a000 : 0xfffffa80`09ae8ef0
fffff880`031bd9a8 fffffa80`ffffffff : ffffd319`2ec47bb2 fffff880`0f582cc5 fffffa80`09a7a000 fffffa80`09aa9000 : 0xffffffff`ffffffff
fffff880`031bd9b0 ffffd319`2ec47bb2 : fffff880`0f582cc5 fffffa80`09a7a000 fffffa80`09aa9000 fffffa80`09ae8ef0 : 0xfffffa80`ffffffff
fffff880`031bd9b8 fffff880`0f582cc5 : fffffa80`09a7a000 fffffa80`09aa9000 fffffa80`09ae8ef0 00000000`00000001 : 0xffffd319`2ec47bb2
fffff880`031bd9c0 fffffa80`09a7a000 : fffffa80`09aa9000 fffffa80`09ae8ef0 00000000`00000001 fffffa80`09acd000 : nvlddmkm+0x4a3cc5
fffff880`031bd9c8 fffffa80`09aa9000 : fffffa80`09ae8ef0 00000000`00000001 fffffa80`09acd000 fffff880`0f5888b7 : 0xfffffa80`09a7a000
fffff880`031bd9d0 fffffa80`09ae8ef0 : 00000000`00000001 fffffa80`09acd000 fffff880`0f5888b7 ffffffff`ffffffff : 0xfffffa80`09aa9000
fffff880`031bd9d8 00000000`00000001 : fffffa80`09acd000 fffff880`0f5888b7 ffffffff`ffffffff 00000000`00000001 : 0xfffffa80`09ae8ef0
fffff880`031bd9e0 fffffa80`09acd000 : fffff880`0f5888b7 ffffffff`ffffffff 00000000`00000001 fffffa80`0700e040 : 0x1
fffff880`031bd9e8 fffff880`0f5888b7 : ffffffff`ffffffff 00000000`00000001 fffffa80`0700e040 ffffffff`ffffffff : 0xfffffa80`09acd000
fffff880`031bd9f0 ffffffff`ffffffff : 00000000`00000001 fffffa80`0700e040 ffffffff`ffffffff 00000000`00000001 : nvlddmkm+0x4a98b7
fffff880`031bd9f8 00000000`00000001 : fffffa80`0700e040 ffffffff`ffffffff 00000000`00000001 fffff880`0f28a7de : 0xffffffff`ffffffff
fffff880`031bda00 fffffa80`0700e040 : ffffffff`ffffffff 00000000`00000001 fffff880`0f28a7de 00000000`00000001 : 0x1
fffff880`031bda08 ffffffff`ffffffff : 00000000`00000001 fffff880`0f28a7de 00000000`00000001 00000000`00000000 : 0xfffffa80`0700e040
fffff880`031bda10 00000000`00000001 : fffff880`0f28a7de 00000000`00000001 00000000`00000000 00000000`00000001 : 0xffffffff`ffffffff
fffff880`031bda18 fffff880`0f28a7de : 00000000`00000001 00000000`00000000 00000000`00000001 fffffa80`07d315b0 : 0x1
fffff880`031bda20 00000000`00000001 : 00000000`00000000 00000000`00000001 fffffa80`07d315b0 fffffa80`084d0000 : nvlddmkm+0x1ab7de
fffff880`031bda28 00000000`00000000 : 00000000`00000001 fffffa80`07d315b0 fffffa80`084d0000 fffff880`0f588a3b : 0x1


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+50d95e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5315b408

STACK_COMMAND:  .cxr 0xfffff880031bcfa0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+50d95e

BUCKET_ID:  X64_0x7E_nvlddmkm+50d95e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_nvlddmkm+50d95e

FAILURE_ID_HASH:  {a4fda016-3957-2888-2b0a-62c4d62b817b}

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

1: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f0df000 fffff880`0fd37000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue Mar 04 16:37:52 2014 (5315B408)
    CheckSum:         00C20523
    ImageSize:        00C58000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

During the stress test, the temperature is supposed to go high. We need to know the normal system temperature precisely. Dont miss this part of the earlier suggestions.

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: Speccy - Publish Snapshot of your System Specs .

This information is most vital, because if the normal temperatures are not anything critical, it will be assumed to be a GPU failure only.

Yes, temps are not a big issue here.

Let us know about any further issue.

Arc is the master of BSOD

Thank you Joe. Let us know for any further issue.

Thank you too, Colin. You are also very good in it yourself. :)