Laptop BSOD While Playing Modern Games, Error x116

I will be curious about what Arc says. He has put a lot of time into this issue and made himself the expert on this. But, the only conclusion I can draw from your last post is it is not a switching problem, you seem to just have a Graphics card gone bad.

essenbe said:

I will be curious about what Arc says.

Hi Steve.
We took some steps to minimize the network related BSODs (0x9F) ones. Now we need to know what is going on there exactly. If BSODs are there, what is the bugcheck code (at least). Whether display crashes with 0x9F or with x116. That is why I asked for a camera snap of the 0x116 BSOD, to know about it, the bugcheck code and the caught module.

essenbe said:

the only conclusion I can draw from your last post is it is not a switching problem, you seem to just have a Graphics card gone bad.

If display crashes with 0x116, it is the issue from the part of display itself, not switching. And if it happens the same with multiple versions of display driver, system temps are under control and and nothing is overclocked, then it is the graphics card that is failing.

What is the maximum thing I can say from the data here:
On 7th march, he had a stop 0x116, recorded.

Code:

BugCheck 116, {fffffa800cfb1010, fffff8800fe5f7a0, 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+9a57a0 )

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

Saying the display driver is failing, which is

Code:

    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 23:12:02 2014 (53B4446A)

Same on 22nd march ....

Code:

BugCheck 116, {fffffa80169f7010, fffff88007096f38, ffffffffc000009a, 4}

*** 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+7a3f38 )

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

With another driver version.

Code:

    Image name: nvlddmkm.sys
    Timestamp:        Thu Feb 05 23:31:37 2015 (54D3B001)

No crash dump later, but he says the issue continues even now. 4 Days Ago (when he made post #3) there was another display driver.

Code:

10/16/2014 8:31:28 AM  C:\Windows\system32\DRIVERS\nvlddmkm.sys

And the issue still persists whenever the 675M card is in use.

So your conclusion is very valid, the card is failing to take the load of a game. It may be

1. The card failing itself.
2. Due to heat and dust.
3. Due to unstable overclocking.

If the second and third options are minimized, then it is only a failing graphics card which needs to be replaced in order to play some high end games.

It is also to consider that some games are not for platforms like laptops which are not heat efficient by default due to their congested build.

essenbe said:

He has put a lot of time into this issue and made himself the expert on this.

Thanks. :) If I am an expert, it is your success. I learned all the corners of it from you only.

I am sorry we had to deliver the bad news. Y wish we could have found a better solution for you. Please let us know how it turns out for you.