BSOD playing movies, Hp Elitebook 8540p

BEASTFlo · 20 Apr 2012

Hi all,

Thanks for your response writhziden. I've done many tests (GPU memtest, GPU test, all with OCCT) but BSOD are still there... All the tests shows no errors.

My laptop is an HP Elitebook 8540p. When playing movies or sometimes Flash, my laptop is crashing (my laptop doesn't respond, hard reboot needed). The problem always occurs when im playing movies and sometimes I get BlueScreen.

My OS is Windows 7 Professional 64bit, OEM.

The age of the system is 2years and the age of the OS installation is 4 months.

I have attached the Windows_NT6_BSOD_jcgriff2 folder.

Also, here is my file dump :

Code:

Microsoft (R) Windows Debugger Version 6.2.8229.0 AMD64Copyright (c) Microsoft Corporation. All rights reserved.




Loading Dump File [C:\Windows\Minidump\041312-18720-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16973.amd64fre.win7_gdr.120305-1504
Machine Name:
Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`03049e70
Debug session time: Fri Apr 13 13:29:49.103 2012 (UTC + 2:00)
System Uptime: 0 days 1:52:38.679
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
..................
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 116, {fffffa8008f57010, fffff880101c3db0, 0, 2}


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
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b1db0 )


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


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


VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008f57010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880101c3db0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.


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


TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2


FAULTING_IP: 
nvlddmkm+1b1db0
fffff880`101c3db0 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`055db9c8 fffff880`06cd6000 : 00000000`00000116 fffffa80`08f57010 fffff880`101c3db0 00000000`00000000 : nt!KeBugCheckEx
fffff880`055db9d0 fffff880`06cd5d0a : fffff880`101c3db0 fffffa80`08f57010 fffffa80`0665bd50 fffffa80`06649290 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`055dba10 fffff880`06d7cf07 : fffffa80`08f57010 00000000`00000000 fffffa80`0665bd50 fffffa80`06649290 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`055dba40 fffff880`06da6b75 : 00000000`ffffffff 00000000`00069b03 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`055dbb20 fffff880`06da52bb : 00000000`00000102 00000000`00000000 00000000`00069b03 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`055dbb50 fffff880`06d782c6 : ffffffff`ff676980 fffffa80`06649290 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`055dbbf0 fffff880`06da4e7a : 00000000`00000000 fffffa80`04710160 00000000`00000080 fffffa80`06649290 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`055dbd00 fffff800`0311c6e6 : 00000000`fffffc32 fffffa80`06660060 fffffa80`03b71ae0 fffffa80`06660060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`055dbd40 fffff800`02e5bac6 : fffff880`031d3180 fffffa80`06660060 fffff880`031ddfc0 fffff880`0145f2b4 : nt!PspSystemThreadStartup+0x5a
fffff880`055dbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16




STACK_COMMAND: .bugcheck ; kb


FOLLOWUP_IP: 
nvlddmkm+1b1db0
fffff880`101c3db0 4883ec28 sub rsp,28h


SYMBOL_NAME: nvlddmkm+1b1db0


FOLLOWUP_NAME: MachineOwner


MODULE_NAME: nvlddmkm


IMAGE_NAME: nvlddmkm.sys


DEBUG_FLR_IMAGE_TIMESTAMP: 4f6b8533


FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys


BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys


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

When I connect a projector (VGA connector, Samsung LCD display, 17"), I don't get theses crashes (I also don't get crashes in Ubuntu distribution).

I have this problem since 6months and any help would be really appreciated.

For information, my antivirus is BitDefender Internet Security 2012, and it is up to date. But it's not listed in the list of Windows 7 compatible softwares Compatibilité Windows 7 pour Sécurité : Pare-feu & Sécurité Internet Programmes logiciels : Télécharger des mises à jour de logiciels.

Thanks in advance!

zigzag3143 · 20 Apr 2012

8 of 13 point to this
"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.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps

STOP 0x116: VIDEO_TDR_ERROR troubleshooting

BEASTFlo · 20 Apr 2012

Thanks for your response, but I already checked this post (like writhziden told me).

Any suggestions ?

zigzag3143 · 20 Apr 2012

BEASTFlo said:

Thanks for your response, but I already checked this post (like writhziden told me).

Any suggestions ?

116's are almost always heat, occasionally power, a driver, sli, etc.

BEASTFlo · 21 Apr 2012

116's ?

Graphic card drivers are up to date..

zigzag3143 · 21 Apr 2012

BEASTFlo said:

116's ?

Graphic card drivers are up to date..

BCC116 Video reset