BSOD playing Mass Effect 2, bccode 116

Security Software:

Code:

avgcsrva.exe	c:\program files (x86)\avg\avg2012\avgcsrva.exe	464	8	200	1380	21/03/2012 19:53	12.0.0.1786	507,34 KB (519.520 bytes)	15/08/2011 06:21
avgcsrva.exe	c:\program files (x86)\avg\avg2012\avgcsrva.exe	2964	8	200	1380	21/03/2012 19:54	12.0.0.1786	507,34 KB (519.520 bytes)	15/08/2011 06:21
avgidsagent.exe	c:\program files (x86)\avg\avg2012\avgidsagent.exe	2340	8	200	1380	21/03/2012 19:53	12.0.0.1855	4,23 MB (4.433.248 bytes)	12/10/2011 06:25
avgnsa.exe	c:\program files (x86)\avg\avg2012\avgnsa.exe	1876	8	200	1380	21/03/2012 19:53	12.0.0.1883	1,90 MB (1.987.424 bytes)	28/11/2011 02:19
avgtray.exe	c:\program files (x86)\avg\avg2012\avgtray.exe	3684	8	200	1380	21/03/2012 19:54	12.0.0.1912	2,30 MB (2.416.480 bytes)	24/01/2012 18:24
avgwdsvc.exe	c:\program files (x86)\avg\avg2012\avgwdsvc.exe	1904	8	200	1380	21/03/2012 19:53	12.0.0.1773	188,26 KB (192.776 bytes)	02/08/2011 06:09

Possible out of date driver:

Code:

SABI	fffff880`02fd6000	fffff880`02fe0000	Thu May 28 00:38:02 2009 (4a1e314a)	00006e8b		SABI.sys

SABI.sys

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\HFontana\Windows_NT6_BSOD_jcgriff2\032112-24476-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e62000 PsLoadedModuleList = 0xfffff800`030a6650
Debug session time: Wed Mar 21 16:52:42.921 2012 (UTC - 6:00)
System Uptime: 0 days 0:12:00.952
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80083fc4e0, fffff8800fa259bc, 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+7b09bc )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80083fc4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fa259bc, 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.

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


FAULTING_IP: 
nvlddmkm+7b09bc
fffff880`0fa259bc 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0650ba48 fffff880`0ff43000 : 00000000`00000116 fffffa80`083fc4e0 fffff880`0fa259bc ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0650ba50 fffff880`0ff16867 : fffff880`0fa259bc fffffa80`086e4000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0650ba90 fffff880`0ff42e0f : fffffa80`ffffd84d 00000000`00000000 fffffa80`083fc4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0650bb40 fffff880`0f237ec1 : fffffa80`06bec330 00000000`00000080 00000000`00000000 fffffa80`086de010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0650bbc0 fffff800`03178f7a : 00000000`037be56f fffffa80`086fd4d0 fffffa80`03c66990 fffffa80`086fd4d0 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0650bc00 fffff800`02ecf9c6 : fffff800`03053e80 fffffa80`086fd4d0 fffff800`03061cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0650bc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+7b09bc
fffff880`0fa259bc 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+7b09bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d347379

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

A TDR 0x116 crash:

• H2SO4 said:

  These are all stop 0x116 VIDEO_TDR_FAILURE conditions.
  
  It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.
  
  Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash. As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds. If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.
  
  If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling.
  The above quote was taken from https://www.sevenforums.com/crashes-d...tml#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining STOP 0x116: VIDEO_TDR_ERROR troubleshooting and proceed through each step. Let us know if you need further help.

Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.

Thanks writhziden.

I runned some tests and at least it wasn't hardware problem.

Formatted the note and reinstalled all drivers, but the problem still happened.

But i found a solution, on the nvidia control panel I changed the config to performance over quality and the BSOD stopped.

Could that be overheating? (strange because the furMark runned until 90º for 6 minutes and did't got any error)

I attached the highest temperature of my note with that performance config, are those normal?

I'm thinking about buying a support with cooler for my note, that will probably help, right!?

Thanks again for your reply.

90 C is definitely on the high side for a graphics card. It is not abnormal, but it could be indicative of a heat problem. It may also be that your card manages the GPU and RAM differently in performance mode versus quality mode. Do you see any noticeable performance change between the two? Videos choppy, games not as fast fps, furmark tests give different fps results?

I played Mass Effect 2 again with that setting and everything seems normal, but i will run fur with both configs to compare.

Thanks

You're welcome. Let us know how things go and whether the system remains stable with performance settings enabled.

writhziden, still got problems

I bought a notebook support with cooler and even so after +- 01:00 the game freezes... and the bsod appears.

The performance config just delayed the problem from 5 minutes to 1 hour.

I'm thinking about trying to contact samsung to find a fix for it, or to know if that could be a hardware defect...

Got any other idea?

Thank you.

Since the system is still new and under warranty, I would recommend contacting Samsung. This seems like a hardware issue to me, and there is little you can do to fix hardware problems on a laptop.


Since the system is brand new, you could also try doing a recovery using the factory system image to set it back to how it was when you first bought it. The steps to do so are

• shut down and turn off your computer
• Turn on your computer and immediately tap the F4 key 3-5 times until the recovery starts
• Follow the instructions to do a factory reset/recovery

Make sure to back up any important files first.

If a factory reset resolves the problem, it would mean there was a software/driver conflict. If it does not, the problem is likely hardware. When you do the factory reset, install Windows updates 5-10 at a time and test stability after each set. Then install software one program at a time and test stability after. Try not to add new devices to the system after the factory restore, either (use the mousepad and keyboard and not an external mouse, no gaming devices, etc.; avoid plugging devices into USB ports until you are sure the system is stable or not stable; avoid SD cards, firewire devices, PMCIA cards or their equivalent, etc.).

Gonna take it to the samsung technical support, a brand new notebook shouldn't be behaving this way =(
Thanks for all the help writhziden