game causes BSOD

Hi I'm new here in this forum can anyone help with my trouble?
When i play games for same hours the BSOD appears pointing same trouble with my video card Nvidia
PC configurations: i5 - 2,5GHz, Nvidia GT540m (2 GB dedicated/128 bits), 6GB of RAM

Please provide this information for a complete analysis: How to ask for help with a BSOD problem

OK there it is .....

Please visit Windows Update and get ALL available updates.

These devices have problems:

Bluetooth Peripheral Device BTHENUM\{00004C48-0000-1000-8000-00805F9B34FB}_VID&0001000F_PID&0000\8&18398521&0&F01C139B97F5_C00000000 The drivers for this device are not installed.

WebCam SCB-1100N USB\VID_2232&PID_1008&MI_00\7&3115B2D8&0&0000 This device is disabled.

Please install the drivers for the Bluetooth device.
Is the webcam deliberately disabled? If so, why?
Please:
- enable the webcam
- update it's drivers
- disable it again if so desired

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] DuplexSecure - FAQ [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

Here's some general troubleshooting tips for STOP 0x116 errors (the type that you've been having): Video TDR Timeout - 0x116 + 0x117

Older versions of Samsung KIES can also cause BSOD's. Please un-install your version and then install the latest version available from the Samsung website


Update Intel and nVidia video drivers to latest available version
Update Norton product to the latest available version.

The information below this point is for reference only. I already suggested the changes that I thought were necessary in the paragraphs above this.

BSOD SUMMARY:

Code:

Debug session time: Thu Oct 18 19:58:50.684 2012 (UTC - 4:00)
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101812-35037-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:59:50.949
BugCheck 116, {fffffa800c3214e0, fffff8800fa5f9bc, 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+7b09bc )
Bugcheck code 00000116
Arguments: 

Arg1: fffffa800c3214e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff8800fa5f9bc, 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.


DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Oct 18 18:58:35.093 2012 (UTC - 4:00)
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101812-37377-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 1:22:48.342
BugCheck 116, {fffffa800d12a4e0, fffff8800f9bb9bc, 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+7b09bc )
Bugcheck code 00000116
Arguments: 

Arg1: fffffa800d12a4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff8800f9bb9bc, 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.


DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Oct 18 17:35:22.421 2012 (UTC - 4:00)
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101812-36987-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 5:37:43.670
BugCheck 116, {fffffa800bf404e0, fffff8800fa1f9bc, 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+7b09bc )
Bugcheck code 00000116
Arguments: 

Arg1: fffffa800bf404e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff8800fa1f9bc, 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.


DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Oct 18 11:57:16.690 2012 (UTC - 4:00)
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101812-40513-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 23:23:41.954
BugCheck 116, {fffffa800ebd14e0, fffff8800fa579bc, 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+7b09bc )
Bugcheck code 00000116
Arguments: 

Arg1: fffffa800ebd14e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff8800fa579bc, 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.


DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Oct 11 21:13:42.489 2012 (UTC - 4:00)
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101112-43071-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 18:57:24.738
BugCheck 116, {fffffa800d9b1010, fffff8800fa619bc, 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+7b09bc )
Bugcheck code 00000116
Arguments: 

Arg1: fffffa800d9b1010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff8800fa619bc, 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.


DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Oct  8 21:49:53.308 2012 (UTC - 4:00)
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\100812-47424-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime: 1 days 12:46:56.182
BugCheck 116, {fffffa8005fd4010, fffff8800faad9bc, ffffffffc000009a, 4}
*** 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 checksum for win32k.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7b09bc )
Bugcheck code 00000116
Arguments: 

Arg1: fffffa8005fd4010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff8800faad9bc, 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.


DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Sep 23 09:50:33.733 2012 (UTC - 4:00)
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092312-20716-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime: 0 days 0:46:18.997
BugCheck 116, {fffffa800c5674e0, fffff8800fa409bc, ffffffffc000009a, 4}
*** 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 checksum for win32k.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7b09bc )
Bugcheck code 00000116
Arguments: 

Arg1: fffffa800c5674e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff8800fa409bc, 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.


DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Sep 23 00:48:52.042 2012 (UTC - 4:00)
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092312-17908-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime: 0 days 0:50:05.307
BugCheck 116, {fffffa800b6734e0, fffff8800fa719bc, ffffffffc000009a, 4}
*** 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 checksum for win32k.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7b09bc )
Bugcheck code 00000116
Arguments: 

Arg1: fffffa800b6734e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff8800fa719bc, 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.


DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Sep 22 23:58:22.077 2012 (UTC - 4:00)
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092312-33743-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime: 0 days 0:20:41.326
BugCheck 116, {fffffa80060c34e0, fffff8800faa19bc, ffffffffc000009a, 4}
*** 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 checksum for win32k.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7b09bc )
Bugcheck code 00000116
Arguments: 

Arg1: fffffa80060c34e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff8800faa19bc, 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.


DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Sep 22 23:37:19.393 2012 (UTC - 4:00)
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092312-40575-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime: 0 days 1:04:08.641
BugCheck 116, {fffffa800c3bd4e0, fffff8800fa789bc, ffffffffc000009a, 4}
*** 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 checksum for win32k.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7b09bc )
Bugcheck code 00000116
Arguments: 

Arg1: fffffa800c3bd4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff8800fa789bc, 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.


DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Oct 18 19:58:50.684 2012 (UTC - 4:00)

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
The information below this point is for reference only. I already suggested the changes that I thought were necessary in the paragraphs above this.

Code:

SABI.sys                    Thu May 28 02:38:02 2009 (4A1E314A)
SAMSUNG Kernel Driver
Driver Reference Table - SABI.sys
 
npf.sys                     Tue Oct 20 14:00:19 2009 (4ADDFAB3)
NetGroup Packet Filter Driver, part of the WinPcap packet capture library
Driver Reference Table - npf.sys
 
btwl2cap.sys                Mon Mar  1 21:25:23 2010 (4B8C7713)
Broadcom Bluetooth L2CAP Servicen
Driver Reference Table - btwl2cap.sys
 
rikvm_38F51D56.sys          Wed Apr 28 22:26:32 2010 (4BD8EE58)
Unknown driver, possibly dynamic as it doesn't appear in MSINFO32[br]Maybe associated with Cyberlink Power DVD (from this link:  Some kind of virus? )
Driver Reference Table - rikvm_38F51D56.sys
 
clwvd.sys                   Tue Jul 27 21:13:47 2010 (4C4F844B)
CyberLink WebCam Virtual Driver
Driver Reference Table - clwvd.sys
 
btwaudio.sys                Fri Aug 20 15:16:14 2010 (4C6ED47E)
Broadcom Bluetooth Audio Device
Driver Reference Table - btwaudio.sys
 
btwavdt.sys                 Tue Sep  7 20:18:36 2010 (4C86D65C)
Broadcom Bluetooth AVDT Service 
Driver Reference Table - btwavdt.sys
 
btwrchid.sys                Tue Sep  7 20:19:49 2010 (4C86D6A5)
Bluetooth Remote Control HID Minidriver 
Driver Reference Table - btwrchid.sys
 
btwampfl.sys                Mon Sep 20 16:49:51 2010 (4C97C8EF)
Broadcom bluetooth driver
Driver Reference Table - btwampfl.sys
 
TurboB.sys                  Fri Oct  8 05:32:49 2010 (4CAEE541)
Intel Turbo Boost driver
Driver Reference Table - TurboB.sys
 
HECIx64.sys                 Tue Oct 19 19:33:43 2010 (4CBE2AD7)
Intel Management Engine Interface
Driver Reference Table - HECIx64.sys
 
Ironx64.SYS                 Fri Nov 12 18:06:50 2010 (4CDDC88A)
Symantec/ Norton NIS/ N360 driver
Driver Reference Table - Ironx64.SYS
 
nusb3hub.sys                Thu Nov 18 20:34:24 2010 (4CE5D420)
NEC Electronics USB 3.0 Host Controller Driver (previous issues w/BSOD's)
Driver Reference Table - nusb3hub.sys
 
nusb3xhc.sys                Thu Nov 18 20:34:25 2010 (4CE5D421)
NEC Electronics USB 3.0 Host Controller Driver (previous issues w/BSOD's)
Driver Reference Table - nusb3xhc.sys
 
SYMDS64.SYS                 Tue Dec  7 19:16:58 2010 (4CFECE7A)
Symantec/ Norton NIS/ N360 driver
Driver Reference Table - SYMDS64.SYS
 
nvBridge.kmd                Mon Jan 17 11:43:41 2011 (4D3471BD)
nVidia Compatible Vista Kernel Mode Driver (likely belongs to nForce chipset drivers)
Driver Reference Table - nvBridge.kmd
 
nvlddmkm.sys                Mon Jan 17 11:51:05 2011 (4D347379)
nVidia Video drivers
Driver Reference Table - nvlddmkm.sys
 
nvpciflt.sys                Mon Jan 17 11:51:49 2011 (4D3473A5)
nVidia 3D Vision Display driver
Driver Reference Table - nvpciflt.sys
 
iaStor.sys                  Fri Feb 18 11:10:50 2011 (4D5E9A0A)
Intel Storage drivers
Driver Reference Table - iaStor.sys
 
SYMEFA64.SYS                Sun Mar 13 23:20:58 2011 (4D7D899A)
Symantec Extended File Attributes
Driver Reference Table - SYMEFA64.SYS
 
SYMEVENT64x86.SYS           Thu Mar 24 19:02:36 2011 (4D8BCD8C)
Norton Internet Security
Driver Reference Table - SYMEVENT64x86.SYS
 
SRTSP64.SYS                 Tue Mar 29 22:46:12 2011 (4D929974)
Symantec Real Time Storage Protection
Driver Reference Table - SRTSP64.SYS
 
SRTSPX64.SYS                Tue Mar 29 22:46:18 2011 (4D92997A)
Symantec Real Time Storage Protection (PEL) x64
Driver Reference Table - SRTSPX64.SYS
 
SYMNETS.SYS                 Tue Apr 19 18:33:31 2011 (4DAE0DBB)
Symantec/ Norton NIS/ N360 driver
Driver Reference Table - SYMNETS.SYS
 
ssadwh.sys                  Thu May 12 09:06:44 2011 (4DCBDB64)
SAMSUNG Android USB Modem
Driver Reference Table - ssadwh.sys
 
ssadcm.sys                  Thu May 12 09:09:45 2011 (4DCBDC19)
SAMSUNG Android USB Modem
Driver Reference Table - ssadcm.sys
 
Rt64win7.sys                Mon May 16 10:53:31 2011 (4DD13A6B)
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
Driver Reference Table - Rt64win7.sys
 
RTKVHD64.sys                Fri Jun 24 06:44:10 2011 (4E046A7A)
Realtek High Definition Audio Function Driver
Driver Reference Table - RTKVHD64.sys
 
bcmwl664.sys                Fri Jul  1 09:53:54 2011 (4E0DD172)
Broadcom 802.11g Network Adapter - Dell Wireless 1390 WLAN Mini-Card
Driver Reference Table - bcmwl664.sys
 
IntcDAud.sys                Tue Aug 23 09:12:57 2011 (4E53A759)
Intel Graphics Media Accelerator HD Driver
Driver Reference Table - IntcDAud.sys
 
igdkmd64.sys                Tue Jan 10 17:28:09 2012 (4F0CBB79)
Intel Graphics driver
Driver Reference Table - igdkmd64.sys
 
dtsoftbus01.sys             Fri Jan 13 08:45:46 2012 (4F10358A)
Daemon Tools driver
Driver Reference Table - dtsoftbus01.sys
 
ETD.sys                     Wed Apr 25 07:40:27 2012 (4F97E2AB)
ELAN PS/2 Port Smart Pad
Driver Reference Table - ETD.sys
 
EraserUtilRebootDrv.sys     Tue Jul 31 19:36:50 2012 (50186C12)
Symantec /Norton
Driver Reference Table - EraserUtilRebootDrv.sys
 
eeCtrl64.sys                Tue Jul 31 19:36:51 2012 (50186C13)
Symantec Eraser Control driver
Driver Reference Table - eeCtrl64.sys
 
IDSvia64.sys                Tue Aug 28 22:48:40 2012 (503D8308)
Norton Internet Security
Driver Reference Table - IDSvia64.sys
 
BHDrvx64.sys                Tue Aug 28 23:12:41 2012 (503D88A9)
Symantec Heuristics Driver
Driver Reference Table - BHDrvx64.sys
 
EX64.SYS                    Wed Sep  5 18:31:45 2012 (5047D2D1)
Norton Anti-Virus
Driver Reference Table - EX64.SYS
 
ENG64.SYS                   Wed Sep  5 18:33:39 2012 (5047D343)
Norton Anti-Virus
Driver Reference Table - ENG64.SYS

Tanks for the help!!! I uninstalled the daemon tools and used the SPTD, solve Bluetooth and webcam troubles and updated the Nvidia Driver, but just more same question the "DRIVER PRESENT IN DUMP FILES" I need to update those or something? And about the TDR 0x116 errors i read in the link that over heat could cause this error, and the notebook get a little hotter then usual during games, I guess there is the villain, there are same improvement that I can do about this, like configure an accelerate in the cooler speed in somewhere (I already put in windows configurations to put in active mode)?

Just because the notebook gets a little hotter doesn't mean it's the problem - It's like expecting a V8 race car to be -100 Celsius after a match, it's natural for the temp to get a bit higher than usual.

The 3rd party driver stuff is primarily for reference (and that's part of what was missing in the formatting). I mentioned the drivers/programs that needed updating/removal in the body of my post - so don't worry about the 3rd party drivers just yet.

Give me a couple of minutes and I'll go back and edit it

EDIT is done above...

Temperatures are relative - if it's overheating it can break things. But as GeneralHiningII states, it's normal for them to get a bit hotter when being stressed (by the game).

The best tips for laptops are (IMO):
- blow out all vents with canned air (DO NOT use an air compressor or a vacuum cleaner - as they can damage components)
- only use the laptop on a hard surface
- use a cooling pad to ensure a good supply of cooler air to the bottom of the laptop.

The problem persist, overheat are discarded i used a big fan under the note and still appeared the BSOD , this time i read the message that accuses nvlddmkm.sys failure like in BSOD SUMARY, I made same researches about the theme and my notebook line "Samsung RF511" apparently have a history with this problem, and i read in another forum that recommends a solution using the prompt to solve this issue,I don't
have to much pratice with DOS so I guess i made it wrong if you can evaluate and tell me if is a true and where i could be wrong there is the translation of the conten in that forum




1 - Find the nvlddmkm.sy_ (in my case it was inC:\Program Files\NVIDIA Corporation\Installer2\Display.Driver.0)
2 - Copy nvlddmkm.sy_ to C:
3 - Now find the nvlddmkm.sys (C:\Windows\System32\drivers)
4 - Rename the file to nvlddmkm.sys.old
5 - Run Cmd and type "CD" (the guide says that is for "get in" the C: , don´t know how exactly to translate that part)
6 - Then still in Cmd type "expand.exe nvlddmkm.sy_ nvlddmkm.sys" (the guide says that extract the "unzip" nvlddmkm.sy_ to get a corrected nvlddmkm.sys
7 - To finish get the nvlddmkm.sys in C:\nvlddmkm.sys and paste in C:\Windows\System32\drivers

But I can't do the "unzip" the Cmd accuses "cant open the input file: nvlddmkm.sy_"

If someone has the same notebook and issue that has fixed it could help I will be gratefull, and usama you are been very helpfully can evaluate if its a real solution and are something wrong in that guide

the link of the forum that i translated up here is Plantage de "nvlddmkm.sys" : la solution
I read an translation of that in Travamento do "nvlddmkm.sys" : a solução

The problem persist, overheat are discarded i used a big fan under the note and still appeared the BSOD , this time i read the message that accuses nvlddmkm.sys failure like in BSOD SUMARY, I made same researches about the theme and my notebook line "Samsung RF511" apparently have a history with this problem, and i read in another forum that recommends a solution using the prompt to solve this issue,I don't
have to much pratice with DOS so I guess i made it wrong if you can evaluate and tell me if is a true and where i could be wrong there is the translation of the conten in that forum




1 - Find the nvlddmkm.sy_ (in my case it was inC:\Program Files\NVIDIA Corporation\Installer2\Display.Driver.0)
2 - Copy nvlddmkm.sy_ to C:
3 - Now find the nvlddmkm.sys (C:\Windows\System32\drivers)
4 - Rename the file to nvlddmkm.sys.old
5 - Run Cmd and type "CD" (the guide says that is for "get in" the C: , don´t know how exactly to translate that part)
6 - Then still in Cmd type "expand.exe nvlddmkm.sy_ nvlddmkm.sys" (the guide says that extract the "unzip" nvlddmkm.sy_ to get a correctednvlddmkm.sys
7 - To finish get the nvlddmkm.sys in C:\nvlddmkm.sys and paste in C:\Windows\System32\drivers

But I can't do the "unzip" the Cmd accuses "cant open the input file: nvlddmkm.sy_"

If someone has the same notebook and issue that has fixed it could help I will be gratefull, and usama you are been very helpfully can evaluate if its a real solution and are something wrong in that guide

the link of the forum that i translated up here is Plantage de "nvlddmkm.sys" : la solution
I read an translation of that in Travamento do "nvlddmkm.sys" : a solução

I have no clue if the fix will work, but here's my take on how to do it:

STEP 1: Find the nvlddmkm.sy_ (in my case it was inC:\Program Files\NVIDIA Corporation\Installer2\Display.Driver.0)

STEP 2: Copy nvlddmkm.sy_ to the Desktop

STEP 3: Now find the nvlddmkm.sys (C:\Windows\System32\drivers)

STEP 4: Rename the file to nvlddmkm.sys.old

STEP 5: It's asking you to change directory to the C: drive (it depends on where you are in the Command Prompt)
In my instructions it's change to the Desktop for your profile. To do this, type the following commands (and press Enter after each one):

cd\

C:

cd %userprofile%\Desktop

That will put you in a command prompt at your desktop.

STEP 6: Then still in Cmd type "expand.exe nvlddmkm.sy_ nvlddmkm.sys" (the guide says that extract the "unzip" nvlddmkm.sy_ to get a correctednvlddmkm.sys

STEP 7: To finish, copy the nvlddmkm.sys in %userprofile%\Desktop\nvlddmkm.sys and paste in C:\Windows\System32\drivers

I believe the command would be:

copy %userprofile%\Desktop\nvlddmkm.sys C:\Windows\System32\drivers\nvlddmkm.sys

press Enter once the command is typed into the command prompt

Or, you can use Windows Explorer and just copy it from your desktop and paste it into the C:\Windows\System32\drivers directory.
Then check in C:\Windows\System32\drivers to make sure the new one is there.