BSOD (possibly Chrome and IE)


  1. Posts : 1
    W8.1x64
       #1

    BSOD (possibly Chrome and IE)


    My client is having a problem with BSOD

    running WIN7 Home Premium -

    BSOD appears to happen when they access Chrome and IE -

    I have run the SF Diag tool and included the zip file :)

    Thanks in advance for your help !
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome to the forum.

    You need to fix this driver: Driver Reference Table

    Code:
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\admin\Downloads\SF_18-11-2014\SF_18-11-2014\111814-40466-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`02e0a000 PsLoadedModuleList = 0xfffff800`0304d890
    Debug session time: Wed Nov 19 03:33:02.655 2014 (UTC + 6:00)
    System Uptime: 0 days 0:07:24.888
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 119, {1, e7c, e7d, e7d}
    
    *** WARNING: Unable to verify timestamp for mctkmd64.sys
    *** ERROR: Module load completed but symbols could not be loaded for mctkmd64.sys
    Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_SCHEDULER_INTERNAL_ERROR (119)
    The video scheduler has detected that fatal violation has occurred. This resulted
    in a condition that video scheduler can no longer progress. Any other values after
    parameter 1 must be individually examined according to the subtype.
    Arguments:
    Arg1: 0000000000000001, The driver has reported an invalid fence ID.
    Arg2: 0000000000000e7c
    Arg3: 0000000000000e7d
    Arg4: 0000000000000e7d
    
    Debugging Details:
    ------------------
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x119
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  8
    
    TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0
    
    LAST_CONTROL_TRANSFER:  from fffff8800495e22f to fffff80002e7fbc0
    
    STACK_TEXT:  
    fffff800`00b9c558 fffff880`0495e22f : 00000000`00000119 00000000`00000001 00000000`00000e7c 00000000`00000e7d : nt!KeBugCheckEx
    fffff800`00b9c560 fffff880`0517bec5 : fffffa80`0a029480 00000000`00000e7c 00000000`00000000 00000000`00000e7d : watchdog!WdLogEvent5+0x11b
    fffff800`00b9c5b0 fffff880`0517c1f2 : fffffa80`0ab8b000 fffffa80`0a0a86b0 00000000`000011ac fffff880`0f88a42e : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
    fffff800`00b9c5e0 fffff880`0517bf82 : 00000000`00000e7c fffff880`0f88b5b0 fffffa80`0ab8b000 fffffa80`0a1b8000 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x25e
    fffff800`00b9c630 fffff880`0508213f : fffffa80`0a029480 fffffa80`0aab6000 00000000`00000000 fffff880`0f741619 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
    fffff800`00b9c660 fffff880`1030f1dc : fffffa80`0ac57010 fffff800`00b9c8b0 00000000`00000000 fffffa80`0a1b8000 : dxgkrnl!DxgNotifyInterruptCB+0x83
    fffff800`00b9c690 fffffa80`0ac57010 : fffff800`00b9c8b0 00000000`00000000 fffffa80`0a1b8000 00000000`00000000 : mctkmd64+0x81dc
    fffff800`00b9c698 fffff800`00b9c8b0 : 00000000`00000000 fffffa80`0a1b8000 00000000`00000000 00000000`00000000 : 0xfffffa80`0ac57010
    fffff800`00b9c6a0 00000000`00000000 : fffffa80`0a1b8000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`00b9c8b0
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
    fffff880`0517bec5 c744244053eeffff mov     dword ptr [rsp+40h],0FFFFEE53h
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13
    
    FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
    
    BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm mctkmd64
    start             end                 module name
    fffff880`10307000 fffff880`10354000   mctkmd64 T (no symbols)           
        Loaded symbol image file: mctkmd64.sys
        Image path: \SystemRoot\system32\drivers\mctkmd64.sys
        Image name: mctkmd64.sys
        Timestamp:        Tue Oct 05 15:55:21 2010 (4CAAF609)
        CheckSum:         0001DDCB
        ImageSize:        0004D000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      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 15:51.
Find Us