none
0x0000008E蓝屏 RRS feed

  • 问题


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


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

    Symbol search path is: F:\Windows\Symbols
    Executable search path is:
    Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
    Product: Server, suite: Enterprise TerminalServer SingleUserTS
    Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
    Kernel base = 0x81c18000 PsLoadedModuleList = 0x81d2fc70
    Debug session time: Sun Feb 13 02:48:04.675 2011 (GMT+8)
    System Uptime: 0 days 3:53:09.086
    WARNING: Unable to reset page directories
    Loading Kernel Symbols
    ......................................Missing image name, possible paged-out or corrupt data.
    .Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - NTSTATUS 0xC0000147

    WARNING: .reload failed, module list may be incomplete
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 8E, {c0000005, 12c, a38a9c58, 0}

    *** WARNING: Unable to verify timestamp for Unknown_Module_00000001
    *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000001
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 0000012c, The address that the exception occurred at
    Arg3: a38a9c58, Trap Frame
    Arg4: 00000000

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx

    FAULTING_IP:
    Unknown_Module_00000001+12b
    0000012c ??              ???

    TRAP_FRAME:  a38a9c58 -- (.trap ffffffffa38a9c58)
    Unable to read trap frame at a38a9c58

    DEFAULT_BUCKET_ID:  VISTA_RC

    BUGCHECK_STR:  0x8E

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 00000000 to 81ce5b0d

    STACK_TEXT: 
    a38a9818 00000000 00000000 00000000 00000000 nt!KeBugCheckEx+0x1e


    STACK_COMMAND:  .trap 0xffffffffa38a9c58 ; kb

    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME:  Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    BUCKET_ID:  ZEROED_STACK

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

    唉,有高手帮忙分析下么?用的是GT450的显卡,显卡驱动换了好多版本.硬盘是0阵列.

    2011年2月13日 4:08

答案

  • 请您提供一份或几份MINIDUMP以供进一步的分析。此外,若蓝屏频发而对象不定,亦不妨关注硬件工作状态,典型如内存。对于内存,可执行内存诊断复查其可靠性。
    2011年2月14日 13:55
  • 这回是内存管理错误,但不一定代表你的物理内存有毛病,故障原因可能与之前相同,还是主板芯片组驱动的问题。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "abenlee123"
     
    BugCheck 1A, {5003, c0802000, 1558f, 20090201}
    Probably caused by : memory_corruption ( nt!MiAllocateWsle+7d )
     
     
    2011年2月15日 8:02

全部回复

  • 故障类型属于未知且无法确定引起故障的映像名称,可能是未知的硬件问题。
     
    如果以前没有问题,是在最近修改过什么设置或添加删除过什么程序或设备驱动后出现的问题,请回忆一下引起故障前的最近操作或修改。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "abenlee123"
     
    Microsoft (R) Windows Debugger Version 6.6.0007.5
    Copyright (c) Microsoft Corporation. All rights reserved.
     
     
    2011年2月13日 12:52
  • 电脑配置如下:

     CPU: AMD840T

    内存: 12GB(4GB+4GB+2GB+2GB) DDR3宇瞻内存--我用MEMTEST跑过八个小时没发现问题;

    硬盘: 希捷500GX2 0阵列;

    显卡: 影驰GT450; 主板: 华硕M4A88TD-M

    电源: Huntkey 350W;

    windows2008的操作系统

    以前出现过0x0000007E或8E蓝屏,发现是dxgkrnl.sys的问题,我就更新了显卡驱动.然后出现了上面的情况;现在WINDOWS下面的dmp文件有500多MB,一个正常的不可能这么大吧。

    以前还出现过0x0000001---ndis.sys蓝屏; 以上是玩魔界二时蓝屏的,另外开的软件还有内存释放专家来释放内存,如果不释放,机子就太卡了,因为内存太小了。 到底是什么硬件问题呀。机子配回来一直这样。不是天天蓝,是开机一二天左右不定时的蓝。

    2011年2月13日 19:05

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


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

    Symbol search path is: F:\Windows\Symbols
    Executable search path is:
    Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
    Product: Server, suite: Enterprise TerminalServer SingleUserTS
    Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
    Kernel base = 0x81c0a000 PsLoadedModuleList = 0x81d21c70
    Debug session time: Mon Feb 14 13:43:27.592 2011 (GMT+8)
    System Uptime: 0 days 1:30:31.962
    Loading Kernel Symbols
    .....................................................................................................................................
    Loading User Symbols

    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {c02030a8, 9, 8, c02030a8}

    *** ERROR: Module load completed but symbols could not be loaded for ahcix86s.sys
    *** ERROR: Module load completed but symbols could not be loaded for processr.sys
    Probably caused by : ahcix86s.sys ( ahcix86s+21daa )

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: c02030a8, memory referenced
    Arg2: 00000009, IRQL
    Arg3: 00000008, value 0 = read operation, 1 = write operation
    Arg4: c02030a8, address which referenced memory

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


    WRITE_ADDRESS:  c02030a8

    CURRENT_IRQL:  9

    FAULTING_IP:
    +ffffffffc02030a8
    c02030a8 ??              ???

    DEFAULT_BUCKET_ID:  VISTA_RC

    BUGCHECK_STR:  0xD1

    PROCESS_NAME:  System

    TRAP_FRAME:  91569b20 -- (.trap ffffffff91569b20)
    ErrCode = 00000010
    eax=c02030a8 ebx=00010000 ecx=88ac28f4 edx=88c7bcc8 esi=88ac28ac edi=84c7be58
    eip=c02030a8 esp=91569b94 ebp=91569bac iopl=0         nv up ei ng nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
    c02030a8 ??              ???
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from c02030a8 to 81c57fb9

    STACK_TEXT: 
    91569b20 c02030a8 badb0d00 88c7bcc8 91569b44 nt!KiTrap0E+0x2e1
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    91569b90 90bd3daa 00256cb2 84c7be58 84c7be58 0xc02030a8
    91569bac 90bd2f35 88ac2584 88ac28ac 84c7be58 ahcix86s+0x21daa
    91569bf8 90bd32b7 88ac25e4 40000001 88ac2584 ahcix86s+0x20f35
    91569c10 90bb5662 88ac2584 88a28008 91569c2c ahcix86s+0x212b7
    91569c20 90914bab 88ac2004 91569c38 90915137 ahcix86s+0x3662
    91569c2c 90915137 88a28ac8 00000000 81c50970 storport!RaCallMiniportInterrupt+0x1b
    91569c38 81c50970 88879000 88a28a10 89f1e020 storport!RaidpAdapterInterruptRoutine+0x26
    91569c64 81c508e9 8aa57202 000000a2 91569cf8 nt!KiChainedDispatch2ndLvl+0x44
    91569c64 909a99d8 8aa57202 000000a2 91569cf8 nt!KiChainedDispatch+0x29
    91569cf8 81cbac94 8953db78 00000000 8a53ed78 processr+0x29d8
    91569d50 81cb2841 00000000 0000000e 1a3aa383 nt!PoIdle+0x2d1
    91569d54 00000000 0000000e 1a3aa383 01c85a60 nt!KiIdleLoop+0xd


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    ahcix86s+21daa
    90bd3daa 8b06            mov     eax,dword ptr [esi]

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  ahcix86s+21daa

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: ahcix86s

    IMAGE_NAME:  ahcix86s.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4adf0eab

    FAILURE_BUCKET_ID:  0xD1_W_ahcix86s+21daa

    BUCKET_ID:  0xD1_W_ahcix86s+21daa

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

    今天又蓝了.代码如上,是什么原因呀,唉.

    2011年2月14日 5:56
  • 500MB 的是核心内存转储,在“启动与故障恢复”选项中修改为“小内存转储(64KB/128KB)”就可以减小了。
     
    NDIS.SYS 驱动的问题可能与 ACPI 高级电源选项配置不当有关,或者是计算机部分硬件驱动程序有冲突。建议重新安装主板芯片组驱动以修复一下高级电源选项设置。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "abenlee123"
     
    现在WINDOWS下面的dmp文件有500多MB,一个正常的不可能这么大吧。
    以前还出现过0x0000001---ndis.sys蓝屏; 以上是玩魔界二时蓝屏的,
     
     
    2011年2月14日 8:40
  • 最新的这次蓝屏是 ahcix86s.sys 驱动程序引起的,应该是主板芯片组提供的 AHCI 驱动。请重新安装一下主板芯片组驱动。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "abenlee123"
     
    Microsoft (R) Windows Debugger Version 6.6.0007.5
    Copyright (c) Microsoft Corporation. All rights reserved.
     
     
    2011年2月14日 8:42

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


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

    Symbol search path is: F:\Windows\Symbols
    Executable search path is:
    Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
    Product: Server, suite: Enterprise TerminalServer SingleUserTS
    Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
    Kernel base = 0x81c37000 PsLoadedModuleList = 0x81d4ec70
    Debug session time: Mon Feb 14 17:57:29.461 2011 (GMT+8)
    System Uptime: 0 days 0:13:12.176
    Loading Kernel Symbols
    .....................................................................................................................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 7ffd400c).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1A, {5003, c0802000, 1558f, 20090201}

    Probably caused by : memory_corruption ( nt!MiAllocateWsle+7d )

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

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

    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 00005003, The subtype of the bugcheck.
    Arg2: c0802000
    Arg3: 0001558f
    Arg4: 20090201

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


    BUGCHECK_STR:  0x1a_5003

    DEFAULT_BUCKET_ID:  VISTA_RC

    PROCESS_NAME:  mw2.exe

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 81c96b48 to 81d04b0d

    STACK_TEXT: 
    b842dc4c 81c96b48 0000001a 00005003 c0802000 nt!KeBugCheckEx+0x1e
    b842dc84 81caf7f0 c0102690 878122a0 00000000 nt!MiAllocateWsle+0x7d
    b842dcd4 81cd0b7a 00000001 204d2000 c0102690 nt!MiResolveDemandZeroFault+0x681
    b842dd4c 81c84db4 00000001 204d2000 00000001 nt!MmAccessFault+0x191a
    b842dd4c 77ab9e05 00000001 204d2000 00000001 nt!KiTrap0E+0xdc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012f554 00000000 00000000 00000000 00000000 0x77ab9e05


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!MiAllocateWsle+7d
    81c96b48 cc              int     3

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!MiAllocateWsle+7d

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  49e0199e

    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  0x1a_5003_nt!MiAllocateWsle+7d

    BUCKET_ID:  0x1a_5003_nt!MiAllocateWsle+7d

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

    主板驱动升级了下, 现在又这样蓝了,请帮忙分析下. PROCESS_NAME:  mw2.exe是我正在玩的游戏魔界二.

    2011年2月14日 10:25
  • 请您提供一份或几份MINIDUMP以供进一步的分析。此外,若蓝屏频发而对象不定,亦不妨关注硬件工作状态,典型如内存。对于内存,可执行内存诊断复查其可靠性。
    2011年2月14日 13:55
  • 这回是内存管理错误,但不一定代表你的物理内存有毛病,故障原因可能与之前相同,还是主板芯片组驱动的问题。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "abenlee123"
     
    BugCheck 1A, {5003, c0802000, 1558f, 20090201}
    Probably caused by : memory_corruption ( nt!MiAllocateWsle+7d )
     
     
    2011年2月15日 8:02

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


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

    Symbol search path is: F:\Windows\Symbols
    Executable search path is:
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    Unable to read PsLoadedModuleList
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    KdDebuggerData.KernBase < SystemRangeStart
    Windows Vista Kernel Version 6002 MP (4 procs) Free x86 compatible
    Product: Server, suite: Enterprise TerminalServer SingleUserTS
    Kernel base = 0x00000000 PsLoadedModuleList = 0x81d2bc70
    Debug session time: Sat Feb 19 20:27:07.875 2011 (GMT+8)
    System Uptime: 2 days 17:52:40.108
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    Unable to read PsLoadedModuleList
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    KdDebuggerData.KernBase < SystemRangeStart
    Loading Kernel Symbols
    Unable to read PsLoadedModuleList
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    CS descriptor lookup failed
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get program counterGetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck F4, {3, 8a080020, 8a08016c, 81e3a650}

    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

    GetContextState failed, 0xD0000147
    Unable to read selector for PCR for processor 0
    GetContextState failed, 0xD0000147
    Unable to read selector for PCR for processor 0
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    唉,怎么回事呀...

    2011年2月19日 12:32

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


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

    Symbol search path is: F:\Windows\Symbols
    Executable search path is:
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    Unable to read PsLoadedModuleList
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    KdDebuggerData.KernBase < SystemRangeStart
    Windows Vista Kernel Version 6002 MP (4 procs) Free x86 compatible
    Product: Server, suite: Enterprise TerminalServer SingleUserTS
    Kernel base = 0x00000000 PsLoadedModuleList = 0x81d58c70
    Debug session time: Sat Feb 19 22:33:36.974 2011 (GMT+8)
    System Uptime: 0 days 0:04:36.057
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    Unable to read PsLoadedModuleList
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    KdDebuggerData.KernBase < SystemRangeStart
    Loading Kernel Symbols
    Unable to read PsLoadedModuleList
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    CS descriptor lookup failed
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get program counterGetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    *******************************************************************************
    *                                                                             *
    *                        Exception Analysis                                   *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    GetContextState failed, 0xD0000147
    Unable to read selector for PCR for processor 0
    WARNING: Unable to reset page directories
    GetContextState failed, 0xD0000147
    Unable to read selector for PCR for processor 0
    WARNING: Unable to reset page directories
    ***** Debugger could not find ntdll in module list, module list might be corrupt, error 0x80070057.

    GetContextState failed, 0xD0000147
    Unable to read selector for PCR for processor 0
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to read selector for PCR for processor 0
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147

    2011年2月19日 14:45
  • 这一次是 0x000000F4 错误,请参考一下这里:
     
    http://support.microsoft.com/kb/330100/zh-cn
     
    通常是硬盘及数据线引起的问题。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "abenlee123"
     
    Microsoft (R) Windows Debugger Version 6.6.0007.5
    Copyright (c) Microsoft Corporation. All rights reserved.
     
     
    2011年2月19日 16:40
  • Microsoft (R) Windows Debugger  Version 6.6.0007.5
    Copyright (c) Microsoft Corporation. All rights reserved.


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

    Symbol search path is: F:\Windows\Symbols
    Executable search path is:
    Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
    Product: Server, suite: Enterprise TerminalServer SingleUserTS
    Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
    Kernel base = 0x81c51000 PsLoadedModuleList = 0x81d68c70
    Debug session time: Sun Feb 20 16:51:41.501 2011 (GMT+8)
    System Uptime: 0 days 18:10:39.312
    Loading Kernel Symbols
    .....................................................................................................................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 7ffdf00c).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1A, {5003, c0802000, 24f07, 422f8201}

    Probably caused by : memory_corruption ( nt!MiAllocateWsle+7d )

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

    2011年2月20日 11:31
  • 这个与上次相同,内存管理错误。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "abenlee123"
     
    Microsoft (R) Windows Debugger Version 6.6.0007.5
    Copyright (c) Microsoft Corporation. All rights reserved.
     
     
    2011年2月20日 13:40

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


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

    Symbol search path is: F:\Windows\Symbols
    Executable search path is:
    Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
    Product: Server, suite: Enterprise TerminalServer SingleUserTS
    Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
    Kernel base = 0x82004000 PsLoadedModuleList = 0x8211bc70
    Debug session time: Sat Feb 26 06:11:23.849 2011 (GMT+8)
    System Uptime: 0 days 5:13:19.482
    Loading Kernel Symbols
    ......................................................................................................................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 7ffda00c).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 8E, {c0000005, 9e559160, 80fc3c68, 0}

    Page 31e6c2 not present in the dump file. Type ".hh dbgerr004" for details
    Probably caused by : win32k.sys ( win32k!TimersProc+75 )

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

    蓝屏后电脑无法启动,屏幕也不亮,拿掉两条单根4G的内存后, 才能开机. 难道M4A88TD-M主板不支持单条4G的内存? 可在MEMTEST下测试了一天也没事的.

    2011年2月26日 1:12
  • 请您尝试暂时安装较少的内存并进行进一步的观察,并可尝试对BIOS进行更新(最新版本似乎是1706)
    2011年2月26日 15:10
  • 华硕 M4A88TD-M 支持单条 4GB 内存,最大支持 16GB。
     
    综合这么多次的蓝屏故障信息来看,可以认定主板有问题。如果可以自己刷新主板 BIOS 请试试重新刷一下。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "abenlee123"
     
    蓝屏后电脑无法启动,屏幕也不亮,拿掉两条单根4G的内存后, 才能开机. 难道M4A88TD-M主板不支持单条4G的内存? 可在MEMTEST下测试了一天也没事的.
     
    2011年2月27日 9:35