game causes BSOD

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by kraken, Oct 18, 2012.

  1. kraken

    kraken New Member

    Joined:
    Oct 18, 2012
    Messages:
    12
    Likes Received:
    0
    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
     
  2. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
  3. kraken

    kraken New Member

    Joined:
    Oct 18, 2012
    Messages:
    12
    Likes Received:
    0
    OK there it is .....
     

    Attached Files:

  4. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    Please visit Windows Update and get ALL available updates.

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

    kraken New Member

    Joined:
    Oct 18, 2012
    Messages:
    12
    Likes Received:
    0
    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)?
     
  6. GeneralHiningII

    GeneralHiningII Honorable Member

    Joined:
    Sep 21, 2012
    Messages:
    745
    Likes Received:
    7
    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.
     
  7. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    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.
     
    #7 usasma, Oct 20, 2012
    Last edited: Oct 20, 2012
  8. kraken

    kraken New Member

    Joined:
    Oct 18, 2012
    Messages:
    12
    Likes Received:
    0
    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 in C:\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
    [FONT=Arial, Helvetica, sans-serif]7 - To finish get the [/FONT]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
     
  9. kraken

    kraken New Member

    Joined:
    Oct 18, 2012
    Messages:
    12
    Likes Received:
    0
    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 in C:\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
    [FONT=Arial, Helvetica, sans-serif]7 - To finish get the [/FONT]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
     
  10. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    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.
     
  11. GeneralHiningII

    GeneralHiningII Honorable Member

    Joined:
    Sep 21, 2012
    Messages:
    745
    Likes Received:
    7
    Have you tried doing a clean install​ of your video driver?
     
  12. kraken

    kraken New Member

    Joined:
    Oct 18, 2012
    Messages:
    12
    Likes Received:
    0
    PROBLEM SOLVED :cool: !!!!!, I'm not sure what exactly solve the problem cause i made a lot of things at the same time. but to leave for the posterior problem of anyone this is the thing i made:

    1 - the Cmd process, that usama describe two posts before,
    2 - download in Nvidia the last update of the driver (my driver already have been updated 2 times(1 by the windows another by download) with the same version) but that time how recomended GeneralHiningII using the "clean install" (an option box during the instalation)
    3 - Reconfigured the Nvidia properties (the clean installation already delete existent) but this time mixing a lot of tips I have read in forums and tutorials. I configured the video card to run in "performance mode" (it really don't change significantly the graphics but my notebook stop with the inconvenient overheat that slow down the games), but not in the "adjust image settings", at really in "manage 3D settings" changing the features that has an "performance mode" and changing in "multi-display/mixed-GPU" from "multi-display" to "compatibility" (i have read that could exist same incompatibilities between intel-graphics and GT540m), and (for the same reason of the las change) at "set PhysX Configuration" I changed the PhysX processor from "auto-select" to "GeForce GT540M".


    So I guess one of this is the solution, but what is really important that now I am playing for 6 Hours the game that last just 15 minutes before appears BSOD, and surprising me now I'm Playing in higher quality graphics configurations than before tank you guys with the help!!!
     
  13. GeneralHiningII

    GeneralHiningII Honorable Member

    Joined:
    Sep 21, 2012
    Messages:
    745
    Likes Received:
    7
    Well that's good then, enjoy your game! :)
     

Share This Page

Loading...