BSoD when watching YouTube


  1. DippingSauce
    Posts : 3
    Windows 7 Home Premium 64bit
       New #1

    BSoD when watching YouTube


    So my computer is a Windows 7 Home Premium 64-bit. OEM and I bought it back in August 2010 at Tiger Direct.

    My problem is that everytime I try to watch videos on youtube in fullscreen, I get a BSoD after several minutes into the video. My browser is Google Chrome and is updated to the latest version. The BSoD doesn't happen right away though. First the screen appears to go into Power-saving mode but I still hear the sounds. Then the sound gets stuck and repeats and that's when the BSoD occurs. I've rebooted my computer several times and tried watching the same video again and again. It only started happening yesterday too. I've run a quick scan on Microsoft Security Essentials and nothing comes up.

    Please help!
      My Computer
    Quote Quote

  3. zigzag3143
    Posts : 28,845
    Win 8 Release candidate 8400
       New #2

    DippingSauce said:
    So my computer is a Windows 7 Home Premium 64-bit. OEM and I bought it back in August 2010 at Tiger Direct.

    My problem is that everytime I try to watch videos on youtube in fullscreen, I get a BSoD after several minutes into the video. My browser is Google Chrome and is updated to the latest version. The BSoD doesn't happen right away though. First the screen appears to go into Power-saving mode but I still hear the sounds. Then the sound gets stuck and repeats and that's when the BSoD occurs. I've rebooted my computer several times and tried watching the same video again and again. It only started happening yesterday too. I've run a quick scan on Microsoft Security Essentials and nothing comes up.

    Please help!

    These were all virtually Identical. They were all caused by your dxgkrn.sys and nvlddmkm.sys driver which is part of your video driver.

    Please un-install and re-install using these instructions.
    When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

    When it is removed then download and install the fresh copy.


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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\010311-13587-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;srv*e:\symbols
*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 Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03006000 PsLoadedModuleList = 0xfffff800`03243e50
Debug session time: Mon Jan  3 17:50:27.229 2011 (GMT-5)
System Uptime: 0 days 0:21:40.852
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8009af5310, fffff88004763d30, 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
Probably caused by : nvlddmkm.sys ( nvlddmkm+e0d30 )

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: fffffa8009af5310, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004763d30, 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:
------------------


FAULTING_IP: 
nvlddmkm+e0d30
fffff880`04763d30 803d8184970000  cmp     byte ptr [nvlddmkm+0xa591b8 (fffff880`050dc1b8)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`035cd9c8 fffff880`042deef8 : 00000000`00000116 fffffa80`09af5310 fffff880`04763d30 00000000`00000000 : nt!KeBugCheckEx
fffff880`035cd9d0 fffff880`042dec02 : fffff880`04763d30 fffffa80`09af5310 fffffa80`09206830 fffffa80`09578410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`035cda10 fffff880`04385f07 : fffffa80`09af5310 00000000`00000000 fffffa80`09206830 fffffa80`09578410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`035cda40 fffff880`043afb75 : 00000000`ffffffff 00000000`000144f4 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`035cdb20 fffff880`043ae2bb : 00000000`00000102 00000000`00000000 00000000`000144f4 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`035cdb50 fffff880`043812c6 : ffffffff`ff676980 fffffa80`09578410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`035cdbf0 fffff880`043ade7a : 00000000`00000000 fffffa80`092bf850 00000000`00000080 fffffa80`09578410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`035cdd00 fffff800`0331ac06 : 00000000`fffffc32 fffffa80`091d6b60 fffffa80`0548b990 fffffa80`091d6b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`035cdd40 fffff800`03054c26 : fffff880`02dd3180 fffffa80`091d6b60 fffff880`02dddfc0 fffff880`01423534 : nt!PspSystemThreadStartup+0x5a
fffff880`035cdd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+e0d30
fffff880`04763d30 803d8184970000  cmp     byte ptr [nvlddmkm+0xa591b8 (fffff880`050dc1b8)],0

SYMBOL_NAME:  nvlddmkm+e0d30

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4aa6aa2d

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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: fffffa8009af5310, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004763d30, 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:
------------------


FAULTING_IP: 
nvlddmkm+e0d30
fffff880`04763d30 803d8184970000  cmp     byte ptr [nvlddmkm+0xa591b8 (fffff880`050dc1b8)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`035cd9c8 fffff880`042deef8 : 00000000`00000116 fffffa80`09af5310 fffff880`04763d30 00000000`00000000 : nt!KeBugCheckEx
fffff880`035cd9d0 fffff880`042dec02 : fffff880`04763d30 fffffa80`09af5310 fffffa80`09206830 fffffa80`09578410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`035cda10 fffff880`04385f07 : fffffa80`09af5310 00000000`00000000 fffffa80`09206830 fffffa80`09578410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`035cda40 fffff880`043afb75 : 00000000`ffffffff 00000000`000144f4 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`035cdb20 fffff880`043ae2bb : 00000000`00000102 00000000`00000000 00000000`000144f4 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`035cdb50 fffff880`043812c6 : ffffffff`ff676980 fffffa80`09578410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`035cdbf0 fffff880`043ade7a : 00000000`00000000 fffffa80`092bf850 00000000`00000080 fffffa80`09578410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`035cdd00 fffff800`0331ac06 : 00000000`fffffc32 fffffa80`091d6b60 fffffa80`0548b990 fffffa80`091d6b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`035cdd40 fffff800`03054c26 : fffff880`02dd3180 fffffa80`091d6b60 fffff880`02dddfc0 fffff880`01423534 : nt!PspSystemThreadStartup+0x5a
fffff880`035cdd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+e0d30
fffff880`04763d30 803d8184970000  cmp     byte ptr [nvlddmkm+0xa591b8 (fffff880`050dc1b8)],0

SYMBOL_NAME:  nvlddmkm+e0d30

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4aa6aa2d

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

    Ken J
      My Computer
    Quote Quote

  4. DippingSauce
    Posts : 3
    Windows 7 Home Premium 64bit
    Thread Starter
       New #3

    So, I'm supposed to completely uninstall my graphic driver with the program you linked to by following its instructions and then reinstall with the CD that comes with my computer?
      My Computer
    Quote Quote

 

  Related Discussions
Got BSOD while watching youtube
in BSOD Help and Support

hi guys i was watching a you tube from a facebook this was a video and i suddenly got BSoD TRANCE) from this video first my antivrus pop uped while i was a waching the vidoe and then it got BSOD and when my pc got restarted and i logged in back to my pc everything was normal and i didn't had...
BSOD while watching youtube.
in BSOD Help and Support

So the most recent bsod i had was when i was watching youtube, but I forgot to note down the error. Before this, i had many different bsods and so I formatted my laptop, ran chkdsk and SFC, where the sfc found corrupted files but unable to fix them. I also ran Windows Defender Offline which...
BSOD while watching youtube
in BSOD Help and Support

Brand new machine Shuttle sh67h3 -- h67 motherboard with an Intel i3-2105 processor. 8 gig memory, using HD3000 integrated graphics,
BSOD while watching youtube
in BSOD Help and Support

Is Windows 7 . . . - x86 (32-bit) or x64 ? x64 - the original installed OS on the system? Yes this is the original - an OEM or full retail version? OEM - OEM = came pre-installed on system - Full Retail = you purchased it from retailer - What is the age of system (hardware)? Almost a year...
Would appreciate any help. Thank you! I just want to make sure it's nothing too serious. When I was watching the Tumblr Video, It went all green, and then I got a popup bubble from the task bar saying something crash and restarted successfully, then when i went to YouTube i clicked the video to...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 03:30.
Find Us