Blue Screen while trying to play HD Video on YouTube

Page 1 of 2 12 LastLast

  1. Posts : 10
    Windows 7 Ultimate 64-bit Service Pack 1
       #1

    Blue Screen while trying to play HD Video on YouTube


    ok , it start today i got 2 Blue Screen errors , some time wen the YouTube video set's on HD and the screen turns black and the blue screen appears then the PC comes back after the error and creates the dmp file , i get the blue screen wen the video is on HD i tried to avoid HD because is playing really worst , it was like 2 months since i can't play HD Videos on Youtube now i guess it got worst , after the second error i stop watching videos and made this threat

    My Video card is new it's 1 year old since I bought it.
    and the HDD is new to 1 year old , but the rest is 5 years old so i guess that it's time to change the PC
    I intend on doing so but i need this PC to last 1 more year .
    Last edited by XadarxBlack; 20 Aug 2014 at 04:28.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Update teh display driver to the latest. Drivers | GeForce

    When done, Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Also report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

    Let us know the results.
    ____________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8001b394e0, fffff8800f16dbbc, 0, 2}
    
    *** 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+153bbc )
    
    Followup: MachineOwner
    ---------
    
    kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8001b394e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f16dbbc, 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+153bbc
    fffff880`0f16dbbc 803d86de730000  cmp     byte ptr [nvlddmkm+0x891a49 (fffff880`0f8aba49)],0
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    fffff880`02fd79c8 fffff880`0fcc0134 : 00000000`00000116 fffffa80`01b394e0 fffff880`0f16dbbc 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02fd79d0 fffff880`0fcbfe3e : fffff880`0f16dbbc fffffa80`01b394e0 fffffa80`036bfc00 fffffa80`036b4010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`02fd7a10 fffff880`0fd67f13 : fffffa80`01b394e0 00000000`00000000 fffffa80`036bfc00 fffffa80`036b4010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`02fd7a40 fffff880`0fd91cf1 : 00000000`ffffffff 00000000`00028388 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`02fd7b20 fffff880`0fd90437 : 00000000`00000102 00000000`00000000 00000000`00028388 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`02fd7b50 fffff880`0fd632d2 : ffffffff`ff676980 fffffa80`036b4010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`02fd7bf0 fffff880`0fd8fff6 : 00000000`00000000 fffffa80`0378db90 00000000`00000080 fffffa80`036b4010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`02fd7d00 fffff800`0351b73a : 00000000`fffffc32 fffffa80`036f2060 fffffa80`01849840 fffffa80`036f2060 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`02fd7d40 fffff800`032708e6 : fffff800`033fae80 fffffa80`036f2060 fffffa80`029c1640 fffff880`02f54201 : nt!PspSystemThreadStartup+0x5a
    fffff880`02fd7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+153bbc
    fffff880`0f16dbbc 803d86de730000  cmp     byte ptr [nvlddmkm+0x891a49 (fffff880`0f8aba49)],0
    
    SYMBOL_NAME:  nvlddmkm+153bbc
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  52b326bc
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys
    
    FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}
    
    Followup: MachineOwner
    ---------
    
    kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f01a000 fffff880`0fc63000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Thu Dec 19 22:32:52 2013 (52B326BC)
        CheckSum:         00C19112
        ImageSize:        00C49000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 10
    Windows 7 Ultimate 64-bit Service Pack 1
    Thread Starter
       #3

    It works , i have run a video in HD 720p on YouTube and it runs smooth, of course i will no't run HD since my PC barely holds

    http://speccy.piriform.com/results/h...yHZTpeGx6o4NsL

    I haven't stop my PC so this is the screenshot , since i both the Video Card that was the temperature that it run's every day .

    Thanks for the Help
    Last edited by XadarxBlack; 20 Aug 2014 at 01:35.
      My Computer


  4. Posts : 10
    Windows 7 Ultimate 64-bit Service Pack 1
    Thread Starter
       #4

    It happen again , This time i was playing the video it set's on HD , i pause the video change to 480p and click the play , then it happen , the black screen and after the Blue screen , after the error i made the dmp report , with the last 2 dmp and the new one that got like 1 minute ago
      My Computer


  5. Posts : 10
    Windows 7 Ultimate 64-bit Service Pack 1
    Thread Starter
       #5

    Can any one help me with this????
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Same issue.

    When the situation is just the same irrespective of the driver version, it is not driver but something else.

    The system is not overheating, too.

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Let us know the result.
    ____________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8001ab6310, fffff8800f1cb93c, 0, 2}
    
    *** 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+15393c )
    
    Followup: MachineOwner
    ---------
    
    kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8001ab6310, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f1cb93c, 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+15393c
    fffff880`0f1cb93c 48ff256d6d7200  jmp     qword ptr [nvlddmkm+0x87a6b0 (fffff880`0f8f26b0)]
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    fffff880`02fce9c8 fffff880`0fd63134 : 00000000`00000116 fffffa80`01ab6310 fffff880`0f1cb93c 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02fce9d0 fffff880`0fd62e3e : fffff880`0f1cb93c fffffa80`01ab6310 fffffa80`038a9d50 fffffa80`038a7410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`02fcea10 fffff880`0f00ff13 : fffffa80`01ab6310 00000000`00000000 fffffa80`038a9d50 fffffa80`038a7410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`02fcea40 fffff880`0f039cf1 : 00000000`ffffffff 00000000`0009d258 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`02fceb20 fffff880`0f038437 : 00000000`00000102 00000000`00000000 00000000`0009d258 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`02fceb50 fffff880`0f00b2d2 : ffffffff`ff676980 fffffa80`038a7410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`02fcebf0 fffff880`0f037ff6 : 00000000`00000000 fffffa80`01a945f0 00000000`00000080 fffffa80`038a7410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`02fced00 fffff800`0351773a : 00000000`fffffc32 fffffa80`03904060 fffffa80`01849840 fffffa80`03904060 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`02fced40 fffff800`0326c8e6 : fffff800`033f6e80 fffffa80`03904060 fffffa80`0384cb50 fffff880`02f5b201 : nt!PspSystemThreadStartup+0x5a
    fffff880`02fced80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+15393c
    fffff880`0f1cb93c 48ff256d6d7200  jmp     qword ptr [nvlddmkm+0x87a6b0 (fffff880`0f8f26b0)]
    
    SYMBOL_NAME:  nvlddmkm+15393c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53b4446a
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys
    
    FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}
    
    Followup: MachineOwner
    ---------
    
    kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f078000 fffff880`0fd06000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Wed Jul 02 23:12:02 2014 (53B4446A)
        CheckSum:         00C4C7C9
        ImageSize:        00C8E000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  7. Posts : 10
    Windows 7 Ultimate 64-bit Service Pack 1
    Thread Starter
       #7

    I have try with Furmark it get's to 67°C and it runs real bad i got the lowest score , i think my CPU is at fault almost every time it runs at 100% , or my PSU. i could try to re-install my Windows , maybe in that way it will be solved.
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    How long you ran furmark? Can you complete the built in 15 minutes benchmark test?

    If you think it is the CPU that is failing, test it.

    Stress test the CPU.
    Hardware - Stress Test With Prime95

    But usually CPU failures are differently recorded in the crash dumps.

    You cannot test the PSU unless you are an electrician. But you may apply a different PSU on a test basis.

    A clean install should not help you in this issue, logically. But who knows.
      My Computer


  9. Posts : 10
    Windows 7 Ultimate 64-bit Service Pack 1
    Thread Starter
       #9

    or i could get the blue screen on YouTube videos only if i use Chrome ???
    I had tried with FireFox and Safari on HD with or without it runs good :/ ..... games i can run it , i will try for 15 minute but how i set it?
      My Computer


  10. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #10

    Sorry, I can say only what the crash dump says. None of the statements are of me. So I will not change my saying based on anything else.

    The 15 minutes preset is there ....

    Attachment 329911
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
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 15:36.
Find Us