locked
win7 64位 旗舰版 蓝屏 求助! RRS feed

  • 问题

  • 电脑这2天突然蓝屏,用windbg分析了上次的错误,请高手帮看看什么问题,怎么解决。


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


    Loading Dump File [C:\Windows\Minidump\082311-15662-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\temp*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
    Built by: 7600.20994.amd64fre.win7_ldr.110622-1505
    Machine Name:
    Kernel base = 0xfffff800`04401000 PsLoadedModuleList = 0xfffff800`04635ed0
    Debug session time: Tue Aug 23 21:28:17.399 2011 (GMT+8)
    System Uptime: 0 days 0:44:22.632
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {fffff81401fb9ea4, 0, fffff880121cfcf7, 5}


    Could not read faulting driver name
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b )

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

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

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff81401fb9ea4, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff880121cfcf7, If non-zero, the instruction address which referenced the bad memory
     address.
    Arg4: 0000000000000005, (reserved)

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


    Could not read faulting driver name

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800046a00e0
     fffff81401fb9ea4

    FAULTING_IP:
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
    fffff880`121cfcf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh

    MM_INTERNAL_CODE:  5

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    TRAP_FRAME:  fffff88004b52710 -- (.trap 0xfffff88004b52710)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff8a00a44f5f0 rbx=0000000000000000 rcx=fffffa8005db2000
    rdx=fffffa8003a538e0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880121cfcf7 rsp=fffff88004b528a0 rbp=fffffa800471fae8
     r8=fffffa8003ccdc01  r9=0000000000000000 r10=0000000000000000
    r11=0000000000000090 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b:
    fffff880`121cfcf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh ds:da10:00000000`00000054=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff80004482169 to fffff800044674c0

    STACK_TEXT: 
    fffff880`04b525b8 fffff800`04482169 : 00000000`00000050 fffff814`01fb9ea4 00000000`00000000 fffff880`04b52710 : nt!KeBugCheckEx
    fffff880`04b525c0 fffff800`044655ae : 00000000`00000000 fffff814`01fb9ea4 00000000`00000000 fffff814`01fb9e50 : nt!MmAccessFault+0x71a
    fffff880`04b52710 fffff880`121cfcf7 : 00000000`ffffd978 00000000`00000009 fffffa80`05da1000 fffffa80`05da1f30 : nt!KiPageFault+0x16e
    fffff880`04b528a0 fffff880`121cced3 : 00000000`00000000 fffffa80`05ae33a0 00000000`0000001c 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b
    fffff880`04b528d0 fffff880`121e765d : 00000000`00000000 fffff8a0`0ae43630 fffffa80`00000000 fffffa80`03ccdc60 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
    fffff880`04b52aa0 fffff880`121e7398 : fffff800`057ee080 fffff880`121e6d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
    fffff880`04b52c90 fffff880`121e6e96 : 00000000`00000000 fffffa80`03b0e920 00000000`00000080 fffffa80`05d2a410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`04b52cc0 fffff800`04708bba : 00000000`028bf5f1 fffffa80`0596da10 fffffa80`03656890 fffffa80`0596da10 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`04b52d00 fffff800`04444106 : fffff800`045e2e80 fffffa80`0596da10 fffff800`045f0cc0 00320076`000002a8 : nt!PspSystemThreadStartup+0x5a
    fffff880`04b52d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
    fffff880`121cfcf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: dxgmms1

    IMAGE_NAME:  dxgmms1.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

    FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

    BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

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

     

    2011年8月23日 13:48

答案

  • dxgmms1.sys是显卡驱动相关的文件,所以如果每次蓝屏都与该文件有关,那么请根据显卡型号,重新下载并安装适用于Windows 7的显卡驱动试试。
    在IT的路上,You'll never walk alone
    • 已标记为答案 Cloud_TS 2011年8月29日 9:46
    2011年8月24日 1:19

全部回复

  • dxgmms1.sys是显卡驱动相关的文件,所以如果每次蓝屏都与该文件有关,那么请根据显卡型号,重新下载并安装适用于Windows 7的显卡驱动试试。
    在IT的路上,You'll never walk alone
    • 已标记为答案 Cloud_TS 2011年8月29日 9:46
    2011年8月24日 1:19
  • 貌似这个和卡巴有关系,我使用的是kis2012 只要关闭卡巴就没事,也去卡巴论坛看了,好像是kilf.sys的问题
    2016年3月25日 5:17