Random BSOD 116 nvlddmkm.sys

This is a new laptop, had it for almost a month and I've been randomlly getting BSOD 116 throughout my entire time with it. I am using Windows 7 Home Premium 64 bit OS that I migrated from my old HP laptop because the new laptop didn't come with an OS (It's a clevo/sager brand). The OS and some programs are on my ssd while everything else is on my hdd. My old HP from which I migrated the OS from has an integrated AMD graphics card while my new one has integrated Intel and dedicated Nvidia. Initially, I had trouble with the leftover ati pci 3gio filter driver after using DDU to uninstall AMD. There was not enough resources for my Intel and Nvidia graphics but I fixed it after updating the 3gio driver to "PCI bus". Anyway, the BSOD seems to happen at least once a day or every other day and I've only started to keep track of the recent crashes.

The first time since I started to keep track with WhoCrashed, it just randomlly BSOD'd and I don't recall anything that could have triggered it. The second time was when I turned the power off to my charger since my laptop was ~98% done. As soon as the laptop went from charging to not charging, it BSOD'd. The third time, I had just finished downloading my windows updates and logged onto my computer. After I got to my desktop, it BSOD'd again. I have already tried reinstalling windows and graphics drivers multiple times (using DDU to uninstall) and with different versions, nothing seems to work. I have reset my bios with the latest one from my reseller and the BSODs still persist. All of the BSOD's are 116.

I am starting to think it has something to do with my dedicated graphics card being faulty (Nvidia gtx 965m) because I have tried running a 3dmark 11 benchmark and I set the Nvidia control settings for the program to use the Nvidia GPU but I only get 1 FPS in all the benches. I haven't played or downloaded any graphics intensive game yet but the benchmark and problems are enough to make me think this has something to do with a faulty card. At this point, I'm wondering if there is anything else I could do or if I should RMA it.


These are the dumps from WhoCrashed:

computer name: HANNA-HP
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: M5 Pro6, EUROCOM
CPU: GenuineIntel Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8468439040 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 7/1/2015 12:12:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\063015-8502-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1405D4)
Bugcheck code: 0x116 (0xFFFFFA800A4DE010, 0xFFFFF8800497D5D4, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 350.12
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 350.12
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 350.12 , NVIDIA Corporation).
Google query: NVIDIA Corporation VIDEO_TDR_ERROR



On Tue 6/30/2015 8:42:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\063015-6364-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x833128)
Bugcheck code: 0x116 (0xFFFFFA80075E4460, 0xFFFFF880052B9128, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 350.12
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 350.12
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 350.12 , NVIDIA Corporation).
Google query: NVIDIA Corporation VIDEO_TDR_ERROR



On Mon 6/29/2015 2:22:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062815-6084-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x833128)
Bugcheck code: 0x116 (0xFFFFFA800AADC4E0, 0xFFFFF88005129128, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 350.12
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 350.12
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 350.12 , NVIDIA Corporation).
Google query: NVIDIA Corporation VIDEO_TDR_ERROR





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 350.12 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

Hello and welcome Hannah now I am wondering why you migrated the OS and is that OS a retail one? If the OS is a retail then I would, have done a clean install and then redone the data over via an image or such like.
I am no expert but that's what I would have done. By the by if the OS is an OEM then that will be tied to the original board and it is then a matter of whether Microsoft will let you reinstall it on another board. They are usually pretty reasonable say in the event of the board going south.

The OS came with the HP computer so I'm assuming that means it's OEM. If it's tied to the motherboard and I migrate it to another board, is that what's causing the issue? I migrated the OS in hopes of saving money from paying for windows again but if the issue is caused by that, I will just purchase the retail one.

Also, when I only had the intel drivers installed, the BSOD's stopped but once I installed the nvidia drivers, they started happening again. Would this point to an issue between the OS and motherboard or the card itself?

Ok mate and I stand to be corrected but the OS would be an OEM that the manufacturer would have a licence to install en mass and each machine they put out and will have it's own dedicated activation code for the OS - it will be on the Microsoft sticker the manufacturer puts on the machine.

So therefore that copy of Windows will be tied to the original motherboard and cannot be transferred. Having said that I have in the past had motherboards die and a phone call to Microsoft to explain my predicament had them let me use the code for the OS on the replacement board and on one occasion when my brother was sold a dud Dell install disk they let me use the code to install that OS.

If you want you can run the validation tool from Microsoft it will tell you if the copy is genuine or not on the new board and if not then personally an OEM would be the cheapest choice of reinstalling. https://www.microsoft.com/en-au/down....aspx?id=20888

But if you get the retail version that means that you can use it on a another machine if the first install goes south. The one condition for the retail version is that it can only be used on one machine at any one time so for example you could not have it installed on your desktop and your laptop at the same time.