none
我的WIN7 64位 玩魔兽世界 总是蓝屏 用windbg分析DMP文件 求高人解答~ RRS feed

  • 问题

  • 万分感谢!

    这是最近几天蓝屏的DMP文件:  http://cid-8e6ac70cf7d4e78d.office.live.com/self.aspx/%e8%93%9d%e5%b1%8f/Minidump.rar

    分析结果如下:

    这是3天前蓝屏的dmp文件:

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


    Loading Dump File [C:\Windows\Minidump\082610-17487-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 Vista Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Kernel base = 0xfffff800`04816000 PsLoadedModuleList = 0xfffff800`04a53e50
    Debug session time: Thu Aug 26 23:15:10.731 2010 (GMT+8)
    System Uptime: 0 days 2:33:32.744
    Loading Kernel Symbols
    ...........................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7F, {8, 80050031, 6f8, fffff8000488c672}

    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

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

    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050031
    Arg3: 00000000000006f8
    Arg4: fffff8000488c672

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


    BUGCHECK_STR:  0x7f_8

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_RC

    PROCESS_NAME:  Wow.exe

    CURRENT_IRQL:  2

    LAST_CONTROL_TRANSFER:  from fffff80004885ca9 to fffff80004886740

    STACK_TEXT: 
    fffff880`045dbce8 fffff800`04885ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
    fffff880`045dbcf0 fffff800`04884172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`045dbe30 fffff800`0488c672 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    00fff880`009b0fb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterrupt+0x32


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!KiDoubleFaultAbort+b2
    fffff800`04884172 90              nop

    SYMBOL_STACK_INDEX:  2

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

    SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

    FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

    BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

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

    这是今天蓝屏的DMP文件分析:

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


    Loading Dump File [C:\Windows\Minidump\082910-19593-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 Vista Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Kernel base = 0xfffff800`0484a000 PsLoadedModuleList = 0xfffff800`04a87e50
    Debug session time: Sun Aug 29 13:36:32.517 2010 (GMT+8)
    System Uptime: 0 days 16:03:46.345
    Loading Kernel Symbols
    ..............................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..................................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 10E, {1f, fffff8a009dc0b00, 0, 8e16a7}

    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 )

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

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

    VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
    The video memory manager encountered a condition that it can't recover from. By crashing,
    the video memory manager is attempting to get enough information into the minidump such that
    somebody can pinpoint what lead to this condition.
    Arguments:
    Arg1: 000000000000001f, The subtype of the bugcheck:
    Arg2: fffff8a009dc0b00
    Arg3: 0000000000000000
    Arg4: 00000000008e16a7

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


    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_RC

    BUGCHECK_STR:  0x10E

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff8800185722f to fffff800048ba740

    STACK_TEXT: 
    fffff880`052e8878 fffff880`0185722f : 00000000`0000010e 00000000`0000001f fffff8a0`09dc0b00 00000000`00000000 : nt!KeBugCheckEx
    fffff880`052e8880 fffff880`059c4098 : fffff8a0`0cde3b80 fffff8a0`09dc0b00 00000000`008e16a7 00000000`00000000 : watchdog!WdLogEvent5+0x11b
    fffff880`052e88d0 fffff880`059c18af : 00000000`00000000 fffffa80`07c8b640 00000000`00000c3a fffffa80`463352c8 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x148
    fffff880`052e8910 fffff880`059db65d : 00000000`00000000 fffff8a0`09f61770 fffffa80`00000000 fffffa80`07352230 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
    fffff880`052e8ae0 fffff880`059db398 : fffff880`009edf40 fffff880`059dad00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
    fffff880`052e8cd0 fffff880`059dae96 : 00000000`00000000 fffffa80`045cfc50 00000000`00000080 fffffa80`057a8010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`052e8d00 fffff800`04b5ec06 : 00000000`0cf1e7d8 fffffa80`057adb60 fffffa80`0396d890 fffffa80`057adb60 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`052e8d40 fffff800`04898c26 : fffff880`009e9180 fffffa80`057adb60 fffff880`009f3fc0 fffff880`01234a90 : nt!PspSystemThreadStartup+0x5a
    fffff880`052e8d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
    fffff880`059c4098 c7442450c5f3ffff mov     dword ptr [rsp+50h],0FFFFF3C5h

    SYMBOL_STACK_INDEX:  2

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: dxgmms1

    IMAGE_NAME:  dxgmms1.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

    SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148

    FAILURE_BUCKET_ID:  X64_0x10E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148

    BUCKET_ID:  X64_0x10E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148

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

    1: kd> lmvm dxgmms1
    start             end                 module name
    fffff880`059a3000 fffff880`059e9000   dxgmms1    (pdb symbols)          c:\temp\dxgmms1.pdb\685AF9F266284BE19008B39B739A572B1\dxgmms1.pdb
        Loaded symbol image file: dxgmms1.sys
        Mapped memory image file: c:\temp\dxgmms1.sys\4A5BC57846000\dxgmms1.sys
        Image path: \SystemRoot\System32\drivers\dxgmms1.sys
        Image name: dxgmms1.sys
        Timestamp:        Tue Jul 14 07:38:32 2009 (4A5BC578)
        CheckSum:         0004AD44
        ImageSize:        00046000
        File version:     6.1.7600.16385
        Product version:  6.1.7600.16385
        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.7600.16385
        FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
        FileDescription:  DirectX Graphics MMS
        LegalCopyright:   © Microsoft Corporation. All rights reserved.

    电脑配置:CPU:AMD x4 630  内存:2G DDR3 1333 X2 主板:微星 870A-G54 显卡:迪兰恒进 4870 512 火钻

    问题详细描述:每次都是玩 魔兽世界 玩大概1个小时左右 突然屏幕花屏瞬间变蓝屏 然后大概记得有个错误代码 STOP 0x0000010E

    已经蓝屏很多次了 实在太纠结了!求高手帮忙看下到底什么问题

    驱动什么的都是安装的最新的!

    2010年8月29日 7:25

答案

  • 该KB文章是面向于Windows Vista操作系统的,对于Windows 7操作系统并不适用,但错误代码所标识的错误原因是相同的。

    所以,请尝试以下:

    • 检查计算机硬件设备的温度,将BIOS设置还原到默认设置,若有超频请还原为原始频率;
    • 安装由AMD提供的适用于Windows 7 64位操作系统的Radeon显示卡驱动程序软件;
    • 安装由Microsoft提供的DirectX 9.0c End-User Runtime程序的最新版本;
    • 将显卡的TurboCache功能(自动共享物理内存)关闭。


    请将已解决的问题标记为“答案”,以便更多的朋友能够方便的找到问题解决方案。 - MVP | Windows Desktop Experience | Virtualization Sino
    2010年8月29日 9:54
    版主

全部回复

  • 你好,

    通过上述的分析结果,可以确定该问题是由于硬件及驱动程序软件工作不正常导致,不排除是硬件兼容性问题或故障。建议你按照以下思路来解决问题:

    检查计算机硬件设备的温度,将BIOS设置还原到默认设置,若有超频请还原为原始频率;

    安装由AMD提供的适用于Windows 7 64位操作系统的Radeon显示卡驱动程序软件;

    安装由Microsoft提供的DirectX 9.0c End-User Runtime程序的最新版本;

    另外,错误0x0000010E被KB953026记录(提供适用于Windows Vista操作系统的修补程序):

    http://support.microsoft.com/kb/953026

    由于迪兰恒进 4870火钻这款显卡的视频内存是512MB,但可以通过Nvidia的TC技术来共享物理内存以便能够使用更多的视频内存,可以尝试将显卡的TC功能暂时关闭检查是否有所好转。


    请将已解决的问题标记为“答案”,以便更多的朋友能够方便的找到问题解决方案。 - MVP | Windows Desktop Experience | Virtualization Sino
    2010年8月29日 8:44
    版主
  • 謝謝你的解答

    但是這個更新WIN7不能用啊!

    另外,错误0x0000010E被KB953026记录(提供适用于Windows Vista操作系统的修补程序):

    http://support.microsoft.com/kb/953026

    2010年8月29日 9:30
  • 该KB文章是面向于Windows Vista操作系统的,对于Windows 7操作系统并不适用,但错误代码所标识的错误原因是相同的。

    所以,请尝试以下:

    • 检查计算机硬件设备的温度,将BIOS设置还原到默认设置,若有超频请还原为原始频率;
    • 安装由AMD提供的适用于Windows 7 64位操作系统的Radeon显示卡驱动程序软件;
    • 安装由Microsoft提供的DirectX 9.0c End-User Runtime程序的最新版本;
    • 将显卡的TurboCache功能(自动共享物理内存)关闭。


    请将已解决的问题标记为“答案”,以便更多的朋友能够方便的找到问题解决方案。 - MVP | Windows Desktop Experience | Virtualization Sino
    2010年8月29日 9:54
    版主