locked
BSOD dxgmms1.sys Chrome.exe RRS feed

  • Question

  • I have a user with a Dell laptop Latitude E5440, Windows 7 Pro 64 bit. He is getting intermittent BSOD's and I can't seem to track it down.  I got the latest drivers from the Dell site, system updates are current.  Here is the output from WinDBG:

    __________________________________________________________________________________
    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Temp\bob\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available


    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\Windows\symbol_cache*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
    Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
    Machine Name:
    Kernel base = 0xfffff800`0321f000 PsLoadedModuleList = 0xfffff800`03463890
    Debug session time: Wed Feb 25 15:36:27.947 2015 (UTC - 4:00)
    System Uptime: 4 days 12:49:19.145
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................Page 1afd84 not present in the dump file. Type ".hh dbgerr004" for details
    .Page 1adc53 not present in the dump file. Type ".hh dbgerr004" for details
    ...............................................
    .........
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00000000`fffdf018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    ....................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 4E, {7, 7c551, 1, 0}

    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31 )

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

    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
    Arg2: 000000000007c551, page frame number
    Arg3: 0000000000000001, current share count
    Arg4: 0000000000000000, 0

    Debugging Details:
    ------------------


    BUGCHECK_STR:  0x4E_7

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  chrome.exe

    CURRENT_IRQL:  2

    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

    LAST_CONTROL_TRANSFER:  from fffff8000325ca73 to fffff80003293ec0

    STACK_TEXT:  
    fffff880`06bb4838 fffff800`0325ca73 : 00000000`0000004e 00000000`00000007 00000000`0007c551 00000000`00000001 : nt!KeBugCheckEx
    fffff880`06bb4840 fffff800`03307716 : 00000000`00000000 00000000`00000000 fffffa80`0dd56000 fffff880`05362b56 : nt! ?? ::FNODOBFM::`string'+0x165e6
    fffff880`06bb4880 fffff880`05373051 : 00000001`a80c0082 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x368d5
    fffff880`06bb4910 fffff880`05371e1c : 00000000`00000000 fffff880`0536d77e fffffa80`00000088 00000000`00000000 : dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+0x31
    fffff880`06bb4940 fffff880`0536ca21 : fffff8a0`1dcc8010 fffff8a0`1dcc8010 fffffa80`1eb05300 00000000`00000000 : dxgmms1!VIDMM_SEGMENT::UnlockAllocationBackingStore+0x90
    fffff880`06bb49a0 fffff880`0535f37d : fffff8a0`1dcc8010 fffffa80`0dd56000 fffffa80`1eb05310 fffffa80`0dd56000 : dxgmms1!VIDMM_APERTURE_SEGMENT::EvictResource+0x159
    fffff880`06bb49f0 fffff880`0535a46c : fffffa80`1a25fda0 00000000`00000080 00000000`00000000 fffff880`06bb4b60 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x979
    fffff880`06bb4b10 fffff880`053782e9 : fffffa80`00000000 fffffa80`0dca5010 00000000`6d4d6956 fffff880`00000174 : dxgmms1!VidMmiProcessTerminationCommand+0x4c
    fffff880`06bb4b60 fffff880`05377574 : fffff880`035e8f40 fffffa80`1d9c33e0 00000000`00000000 fffffa80`0dca5010 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
    fffff880`06bb4b90 fffff880`05377012 : 00000000`00000000 fffffa80`1d9c33e0 00000000`00000080 fffffa80`0dca5010 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
    fffff880`06bb4bc0 fffff800`03532b8a : 00000000`05357ae0 fffffa80`0db03b50 fffffa80`069e3b30 fffffa80`0db03b50 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`06bb4c00 fffff800`032858e6 : fffff880`035e4180 fffffa80`0db03b50 fffff880`035eefc0 fffffa80`0000001f : nt!PspSystemThreadStartup+0x5a
    fffff880`06bb4c40 00000000`00000000 : fffff880`06bb5000 fffff880`06baf000 fffff880`06bb4540 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31
    fffff880`05373051 4c8b1d60d0fdff  mov     r11,qword ptr [dxgmms1!_imp_g_loggerInfo (fffff880`053500b8)]

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: dxgmms1

    IMAGE_NAME:  dxgmms1.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

    IMAGE_VERSION:  6.1.7601.18126

    FAILURE_BUCKET_ID:  X64_0x4E_7_dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31

    BUCKET_ID:  X64_0x4E_7_dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_0x4e_7_dxgmms1!vidmm_segment::safeunlockpages+31

    FAILURE_ID_HASH:  {7e1087c5-2f4b-2cf8-f79e-489e578a1ca5}

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

    1: kd> lmvm dxgmms1
    start             end                 module name
    fffff880`0533f000 fffff880`05385000   dxgmms1    (pdb symbols)          c:\windows\symbol_cache\dxgmms1.pdb\93AB163000A844D5BF442A979FB6FF991\dxgmms1.pdb
        Loaded symbol image file: dxgmms1.sys
        Image path: \SystemRoot\System32\drivers\dxgmms1.sys
        Image name: dxgmms1.sys
        Timestamp:        Tue Apr 09 23:27:15 2013 (5164DC13)
        CheckSum:         00043C9B
        ImageSize:        00046000
        File version:     6.1.7601.18126
        Product version:  6.1.7601.18126
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     dxgmms1.sys
        OriginalFilename: dxgmms1.sys
        ProductVersion:   6.1.7601.18126
        FileVersion:      6.1.7601.18126 (win7sp1_gdr.130409-1534)
        FileDescription:  DirectX Graphics MMS
        LegalCopyright:   © Microsoft Corporation. All rights reserved.

    _______________________________________________________________________________

    It appears that it is a problem with direct x.  This user keeps a very clean system, no games, no connected USB hardware.

    Can anybody help me with where to start looking?

    Thanks,

    Jim


    -Jim


    • Edited by jtpryan Thursday, March 26, 2015 3:25 PM
    Thursday, March 26, 2015 3:10 PM

Answers

All replies