none
Vista蓝屏 RRS feed

  • 问题

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


    Loading Dump File [D:\Minidump\Mini012710-04.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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18304.x86fre.vistasp1_gdr.090805-0102
    Machine Name:
    Kernel base = 0x81e4c000 PsLoadedModuleList = 0x81f63c70
    Debug session time: Wed Jan 27 13:56:07.990 2010 (GMT+8)
    System Uptime: 0 days 0:34:48.295
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 10000050, {ae2a2ff4, 1, 81e84c28, 0}


    Could not read faulting driver name
    Probably caused by : ntkrpamp.exe ( nt!KiMigrateToNewKernelStack+8d )

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

    1: 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: ae2a2ff4, memory referenced.
    Arg2: 00000001, value 0 = read operation, 1 = write operation.
    Arg3: 81e84c28, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 00000000, (reserved)

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


    Could not read faulting driver name

    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81f83868
    Unable to read MiSystemVaType memory at 81f63420
     ae2a2ff4

    FAULTING_IP:
    nt!KiMigrateToNewKernelStack+8d
    81e84c28 894814          mov     dword ptr [eax+14h],ecx

    MM_INTERNAL_CODE:  0

    CUSTOMER_CRASH_COUNT:  4

    DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  explorer.exe

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 81f050c9 to 81e84c28

    STACK_TEXT: 
    9e9ffa38 81f050c9 ae2a3000 0694e0c4 0694dfbc nt!KiMigrateToNewKernelStack+0x8d
    9e9ffa50 82067d5e 9e9ffb10 9e9ffb14 0694dfbc nt!KiCallUserMode+0x39
    9e9ffaac 9650864f 00000002 9e9ffaf4 00000018 nt!KeUserModeCallback+0xec
    9e9ffb30 9650858f fea4f2c8 00000020 000907e4 win32k!SfnDWORD+0xaf
    9e9ffb78 965074e7 02a4f2c8 00000020 000907e4 win32k!xxxSendMessageToClient+0x16f
    9e9ffbc4 9650755e fea4f2c8 00000020 000907e4 win32k!xxxSendMessageTimeout+0x1f0
    9e9ffbec 964b477b fea4f2c8 00000020 000907e4 win32k!xxxSendMessage+0x1d
    9e9ffc34 964dbc37 fea522f8 000907e4 00000001 win32k!xxxDWP_SetCursor+0x105
    9e9ffcb4 964dd91d fea522f8 00000020 000907e4 win32k!xxxRealDefWindowProc+0x1fa
    9e9ffccc 964b686d fea522f8 00000020 000907e4 win32k!xxxWrapRealDefWindowProc+0x2b
    9e9ffce8 964dd8d4 fea522f8 00000020 000907e4 win32k!NtUserfnNCDESTROY+0x27
    9e9ffd20 81ea3a1a 00010544 00000020 000907e4 win32k!NtUserMessageCall+0xc6
    9e9ffd20 77959a94 00010544 00000020 000907e4 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0694e070 00000000 00000000 00000000 00000000 0x77959a94


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!KiMigrateToNewKernelStack+8d
    81e84c28 894814          mov     dword ptr [eax+14h],ecx

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!KiMigrateToNewKernelStack+8d

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a7965dc

    FAILURE_BUCKET_ID:  0x50_nt!KiMigrateToNewKernelStack+8d

    BUCKET_ID:  0x50_nt!KiMigrateToNewKernelStack+8d

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

    2010年1月27日 6:31

答案

  • 没有哪里表明是显卡问题。0x50 一般是软件兼容问题,你一般在做什么操作时出现蓝屏?
    Alexis Zhang (Microsoft MVP 2004' 2007' 2008' 2009')
    2010年1月27日 8:40

全部回复

  • 个人认为是显卡有问题。也希望大家给点意见和思路。
    2010年1月27日 6:49
  • 没有哪里表明是显卡问题。0x50 一般是软件兼容问题,你一般在做什么操作时出现蓝屏?
    Alexis Zhang (Microsoft MVP 2004' 2007' 2008' 2009')
    2010年1月27日 8:40
  • 没有哪里表明是显卡问题。0x50 一般是软件兼容问题,你一般在做什么操作时出现蓝屏?
    Alexis Zhang (Microsoft MVP 2004' 2007' 2008' 2009')
    感谢回复!一般是VS2008,Perforce,其他的用的不多。
    2010年1月27日 8:47