none
花屏之后蓝屏自动重启 RRS feed

  • 问题

  • 问题一:我的笔记本有时会花屏,之后蓝屏自动重启,怎么了,偶尔出现的这种情况,我4G内存,一个是自带的尔必达第三代DDR3-1333的,另个是三星第三代DDR3-1333的,开了双通道,这个三星内存条安装之后一个月都没出现问题,之后偶尔出现花屏蓝屏问题,会不会与内存有关?

    问题二:显卡是双显卡交火,我有时看cctv电视直播,当出现:用户账户控制,是否对…更改对话框时,我点“确定”,电视直播就卡在那里,花屏一下又正常了(没蓝屏重启),任务栏提示AMD已停止工作,又恢复,这个问题是不是与显卡有关?

    花屏蓝屏的问题每次代码不一样最近几次如下:检测错误: 0x00000116出现过两次,

    检测错误: 0x0000008e (0xc0000005, 0x8a7d62e2, 0xb7eb9360, 0x00000000)。已将转储的数据保存在:C:\windows\MEMORY.DMP。报告 ID: 122211-45567-01

    检测错误: 0x000000fc (0xac1f7312, 0x34e72121, 0xadbe1bfc, 0x00000002)。已将转储的数据保存在:C:\windows\MEMORY.DMP。报告 ID: 122511-25537-01

    检测错误: 0x00000116 (0x86ec1008, 0x93918caa, 0x00000000, 0x00000002)。已将转储的数据保存在:C:\windows\MEMORY.DMP。报告 ID: 010612-29905-01

    看下下面代码的原因

    日志名称:          System
    来源:            Microsoft-Windows-WER-SystemErrorReporting
    日期:            2012/2/18 21:10:30
    事件 ID:         1001
    任务类别:          无
    级别:            错误
    关键字:           经典
    用户:            暂缺
    计算机:           hp-HP
    描述:
    计算机已经从检测错误后重新启动。检测错误: 0x00000116 (0xb32f6008, 0x8afc2caa, 0x00000000, 0x00000002)。已将转储的数据保存在: C:\windows\MEMORY.DMP。报告 ID: 021812-22620-01。
    事件 Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
        <EventID Qualifiers="16384">1001</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-02-18T13:10:30.000000000Z" />
        <EventRecordID>179723</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>hp-HP</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">0x00000116 (0xb32f6008, 0x8afc2caa, 0x00000000, 0x00000002)</Data>
        <Data Name="param2">C:\windows\MEMORY.DMP</Data>
        <Data Name="param3">021812-22620-01</Data>
      </EventData>
    </Event>


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


    Loading Dump File [C:\Users\hp\Desktop\新建文件夹\021812-22620-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows Vista Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
    Kernel base = 0x84243000 PsLoadedModuleList = 0x8438c4d0
    Debug session time: Sat Feb 18 21:09:21.253 2012 (GMT+8)
    System Uptime: 0 days 1:20:21.861
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ............................................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ...........
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: b32f6008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: 8afc2caa, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 00000002, Optional internal context dependent data.

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

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT                 ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT                 ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT                 ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: dxgkrnl!DXGADAPTER                            ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *** WARNING: Unable to verify timestamp for dxgmms1.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
    Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys

    FAULTING_MODULE: 84243000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4dddc8da

    FAULTING_IP:
    atikmpag+5caa
    8afc2caa 8bff            mov     edi,edi

    DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

    VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffffffb32f6008
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT                 ***
    ***                                                                   ***
    *************************************************************************
    Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

    CUSTOMER_CRASH_COUNT:  1

    BUGCHECK_STR:  0x116

    STACK_TEXT: 
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8c96fbb0 938a207b 00000116 b32f6008 8afc2caa nt+0xdeef4
    8c96fbd4 93896937 8afc2caa 00000000 00000002 dxgkrnl+0x8d07b
    8c96fbf8 938d292c 00000000 00000000 af32c788 dxgkrnl+0x81937
    8c96fc70 938fc944 fffffcfb 0004b451 00000000 dxgmms1+0x692c
    8c96fc98 938d99af 00000004 89a2a778 893a5980 dxgmms1+0x30944
    8c96fd28 938fe3c9 af32c788 8427a509 af32c788 dxgmms1+0xd9af
    8c96fd3c 938fe485 af32c788 00000000 89f38d48 dxgmms1+0x323c9
    8c96fd50 8444bfda af32c788 9aa76685 00000000 dxgmms1+0x32485
    8c96fd90 842f41f9 938fe406 af32c788 00000000 nt+0x208fda
    00000000 00000000 00000000 00000000 00000000 nt+0xb11f9


    STACK_COMMAND:  .bugcheck ; kb

    FOLLOWUP_IP:
    atikmpag+5caa
    8afc2caa 8bff            mov     edi,edi

    SYMBOL_NAME:  atikmpag+5caa

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: atikmpag

    IMAGE_NAME:  atikmpag.sys

    BUCKET_ID:  WRONG_SYMBOLS

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

     



    • 已编辑 ufolaiye 2012年2月19日 6:01
    2012年2月19日 5:45

全部回复

  • 笔记本上用 CrossFire 吗?这个不大常见。请确认你使用的驱动是否支持当前笔记本显卡型号及 CrossFire,重新安装一下显示驱动。
     
    如果可以确认驱动没有问题,请暂时禁用 CrossFire,看看单显卡模式有没有花屏的问题?
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "ufolaiye"
     
    问题一:我的笔记本有时会花屏,之后蓝屏自动重启,怎么了,偶尔出现的这种情况,我4G内存,一个是自?亩卮锏谌鶧DR3-1333的,另个是三星第三代DDR3-1333的,
     
     
    2012年2月19日 22:19
    版主
  • 这次花屏蓝屏之前我没安装crossfire,花屏之后我把crossfire安装了,玩游戏还还没出现过这种现象,会不会是内存不兼容?可我用MemTest 4.0检测了三个多小时,没发现错误,偶尔花屏又恢复正常(没蓝屏和自动重启)应该是显卡有点小问题,可偶尔的花屏然后蓝屏重启是不是同一个问题?偶尔的出现蓝屏重启,能确定内存不兼容吗?毕竟安装内存条的时候之后一个月没出现问题,有时也没玩游戏或干其他的,偶尔性出现蓝屏重启。

    2012年2月20日 14:14
  • 与内存关系不大,主要是显示驱动设置的问题。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "ufolaiye"
     
    这次花屏蓝屏之前我没安装crossfire,花屏之后我把crossfire安装了,玩游戏还还没出现过这种现象,会不会是内存不兼容?可我用MemTest 4.0检测了三个多小时,没发现错误,偶尔花屏又恢复正常
     
    2012年2月20日 22:14
    版主
  • 哦,谢谢了!

    2012年2月22日 11:17