BSOD watching videos at web screen turns green


  1. Posts : 3
    Windows 7
       #1

    BSOD watching videos at web screen turns green


    So when i use my chrome and watch some videos i get on some pages a green screen on the videos then it plays for 10sec, and then i get it again, its really irritating. Occasionally but quite rarely my whole screen goes black and then blue screen appears with some txt. then the pc might reboot itself.

    Some system info:
    pc: Acer Aspire X1920
    prosessor: Pentium(R) Dual-Core CPU E6700 @ 3.20GHz 3.20 GHz
    RAM: 4Gt
    System: Windows 7 64-bit
    Graphics: Nvidia GeForce 405

    I have updated graph card and some other things but it doesnt change anything, not sure if this is some file corruption problem or does my graph card going broken. Also i have tried to disable hardware accelerations on the video, but...
    Please help!
    Thanks!
      My Computer


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

    Hi janhur.

    Install the NVIDIA DRIVERS 314.22WHQL only, as a test.

    • Uninstall All nvidia items in Control Panel > Programs and features
      • 3D Vision Control Driver
      • 3D Vision Driver
      • Graphics Driver
      • HD Audio Driver
      • PhysX
      • nvidia Update

      (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:


    Let us know the results.
    ___________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8006b704e0, fffff8800f23de20, 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+153e20 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8006b704e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f23de20, 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+153e20
    fffff880`0f23de20 803dc20a750000  cmp     byte ptr [nvlddmkm+0x8a48e9 (fffff880`0f98e8e9)],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`031da988 fffff880`03d48140 : 00000000`00000116 fffffa80`06b704e0 fffff880`0f23de20 00000000`00000000 : nt!KeBugCheckEx
    fffff880`031da990 fffff880`03d47e4a : fffff880`0f23de20 fffffa80`06b704e0 fffffa80`05cc3c10 fffffa80`05c77410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`031da9d0 fffff880`03c0ff13 : fffffa80`06b704e0 00000000`00000000 fffffa80`05cc3c10 fffffa80`05c77410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`031daa00 fffff880`03c39cf1 : 00000000`ffffffff 00000000`00096942 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`031daae0 fffff880`03c38437 : 00000000`00000102 00000000`00000000 00000000`00096942 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`031dab10 fffff880`03c0b2d2 : ffffffff`ff676980 fffffa80`05c77410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`031dabb0 fffff880`03c37ff6 : 00000000`00000000 fffffa80`068ea6f0 00000000`00000080 fffffa80`05c77410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`031dacc0 fffff800`0371473a : 00000000`fffffc32 fffffa80`05c92060 fffffa80`03ccf040 fffffa80`05c92060 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`031dad00 fffff800`034698e6 : fffff800`035f3e80 fffffa80`05c92060 fffff800`03601cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`031dad40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+153e20
    fffff880`0f23de20 803dc20a750000  cmp     byte ptr [nvlddmkm+0x8a48e9 (fffff880`0f98e8e9)],0
    
    SYMBOL_NAME:  nvlddmkm+153e20
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5315b408
    
    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
    ---------
    
    0: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f0ea000 fffff880`0fd42000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Tue Mar 04 16:37:52 2014 (5315B408)
        CheckSum:         00C20523
        ImageSize:        00C58000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 3
    Windows 7
    Thread Starter
       #3

    when im trying to install the drivers i get "Non 7z archrive" error, why?
      My Computer


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

    Just double click on the downloaded file.
      My Computer


  5. Posts : 3
    Windows 7
    Thread Starter
       #5

    Well it doesnt work, i think it has to do something with nengine.dll error im getting, when i start up pc? seems like every file i download is corrupted or missing something, and i cant use them.
      My Computer


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

    Scan the system for possible virus infection with the following programs.


    Does it point to any infection?
      My Computer


 

  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 12:57.
Find Us