bsod while playing video

[seubanks]

please help cant read these dump files

 

[zigzag3143]

please help cant read these dump files

Hi and welcome

all of these crashes were caused by your video driver. Yoou also have several old drivers as listed below.

I would
download and install a fresh copy of the video driver
runs a system file check
type cmd in search>right click and run as admin>sfc /scannow
If you are overclocking STOP

let us know the results

Ken

smwdm.sys        0x8dda6000    0x8dddbf40    0x00035f40    0x42481278    3/28/2005 9:19:36 AM                        
BLKWGU.sys        0x9034d000    0x903af600    0x00062600    0x4372b67f    11/9/2005 9:54:55 PM                        
secdrv.SYS        0x901e6000    0x901f0000    0x0000a000    0x45080528    9/13/2006 8:18:32 AM                        
e100b325.sys        0x8efd5000    0x8effbc00    0x00026c00    0x473de72c    11/16/2007 1:53:32 PM

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\New folder\013010-19250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82844000 PsLoadedModuleList = 0x8298c810
Debug session time: Sun Jan 31 01:57:24.213 2010 (GMT-5)
System Uptime: 0 days 1:01:01.102
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[B]VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 85729510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 9650aa30, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.
[/B]
Debugging Details:
------------------

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

FAULTING_IP: 
nvlddmkm+e2a30
9650aa30 55              push    ebp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8da5bb74 96fc2adb 00000116 85729510 9650aa30 nt!KeBugCheckEx+0x1e
WARNING: Stack unwind information not available. Following frames may be wrong.
8da5bb98 96fc38fa 9650aa30 00000000 00000002 dxgkrnl+0x8cadb
8da5bbbc 928c092c 00000000 00000102 881d5008 dxgkrnl+0x8d8fa
8da5bc34 928eaa32 fffffcfb 000393f0 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8da5bc5c 928eb153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
8da5bc98 928c78f0 8da5bc90 88220748 88220b48 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
8da5bd28 928ec4b7 881d5008 828803f1 881d5008 dxgmms1!VidSchiScheduleCommandToRun+0xaa
8da5bd3c 928ec573 881d5008 00000000 881e3d48 dxgmms1!VidSchiRun_PriorityTable+0xf
8da5bd50 82a5266d 881d5008 bdcbd71f 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8da5bd90 829040d9 928ec4f4 881d5008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+e2a30
9650aa30 55              push    ebp

SYMBOL_NAME:  nvlddmkm+e2a30

FOLLOWUP_NAME:  MachineOwner

[B]MODULE_NAME: nvlddmkm[/B]

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4c0972

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

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

 

[seubanks]

It is a nvidea 6200 and I saw when it dumped the first time the driver name and updated to the latest one from nvidea site

 

[seubanks]

Oh and this is my sons comp. its not 64 bit

 

[seubanks]

8.17.11.9621 driver

 

[zigzag3143]

It is a nvidea 6200 and I saw when it dumped the first time the driver name and updated to the latest one from nvidea site

If thats before these dmps you mave have a vid card problem These were defineately caused by the vid card reset. You might also have a heat or power issue.

Like I said before DL Gpu-z and keep track of the video temps.

 

[seubanks]

well its not temp problems all shows good, just crashes when video plays

 

[zigzag3143]

well its not temp problems all shows good, just crashes when video plays

It is video related. If not the driver maybe a video card problem