none
电脑蓝屏,贴dump代码 RRS feed

  • 问题

  •  

    ............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {ee657645, 2, 1, 80700a2a}

    Probably caused by : win32k.sys ( win32k!GreReleaseSemaphore+a )

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

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

    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: ee657645, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, bitfield :
     bit 0 : value 0 = read operation, 1 = write operation
     bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 80700a2a, address which referenced memory

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

    WRITE_ADDRESS:  ee657645

    CURRENT_IRQL:  2

    FAULTING_IP:
    hal!KeAcquireInStackQueuedSpinLock+3a
    80700a2a 8902            mov     dword ptr [edx],eax

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  CSRSS.EXE

    LAST_CONTROL_TRANSFER:  from bf8018df to 80700a2a

    STACK_TEXT: 
    f8780918 bf8018df bf89c152 bc6606e8 e224b5c0 hal!KeAcquireInStackQueuedSpinLock+0x3a
    f878091c bf89c152 bc6606e8 e224b5c0 81c01260 win32k!GreReleaseSemaphore+0xa
    f8780940 bf84e691 0301003a 00000001 e224cc10 win32k!GreRealizeDefaultPalette+0xa4
    f87809b4 bf8444f5 bc6606e8 00000046 00000000 win32k!xxxDesktopWndProc+0x1b5
    f8780a18 bf801f20 e224b5c0 bf9aa5a0 e224b5c0 win32k!xxxReceiveMessage+0x295
    f8780a54 bf88964b f8780aa4 000025ff 00000000 win32k!xxxRealInternalGetMessage+0x1d7
    f8780d30 bf87262c bf9aa5a0 00000001 f8780d54 win32k!xxxDesktopThread+0x3f6
    f8780d40 bf8010ba bf9aa5a0 f8780d64 0079fff4 win32k!xxxCreateSystemThreads+0x6a
    f8780d54 804de99f 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23
    f8780d54 7c92eb94 00000000 00000022 00000000 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    00000000 00000000 00000000 00000000 00000000 0x7c92eb94

    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    win32k!GreReleaseSemaphore+a
    bf8018df ff253cc298bf    jmp     dword ptr [win32k!_imp__KeLeaveCriticalRegion (bf98c23c)]

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  win32k!GreReleaseSemaphore+a

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME:  win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  461b68f2

    FAILURE_BUCKET_ID:  0xA_W_win32k!GreReleaseSemaphore+a

    BUCKET_ID:  0xA_W_win32k!GreReleaseSemaphore+a

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

    2009年2月13日 2:22

全部回复

  • 不好意思,我以为刚才没有发上来,多按了一下。
    2009年2月13日 2:27
  • 应该是软件兼容问题,在做什么操作或修改什么设置后出现的问题?
    Alexis Zhang (Microsoft MVP 2004' 2007' 2008')
    2009年2月13日 4:06
    版主
  •  错误的位置是hal!KeAcquireInStackQueuedSpinLock+3a,这个是系统的HAL.dll中的

    有关KeAcquireInStackQueuedSpinLock请参看http://msdn.microsoft.com/zh-cn/library/ms801649(en-us).aspx

    其中描述
    Queued spin locks are a variant of spin locks that are more efficient for high contention locks on multiprocessor machines. On multiprocessor machines, using queued spin locks guarantees that processors acquire the spin lock on a first-come first-served basis. Drivers for Windows XP and later operating systems should use queued spin locks instead of ordinary spin locks.

    The driver supplies storage for the spin lock, and initializes it with KeInitializeSpinLock. The driver uses KeAcquireInStackQueuedSpinLock to acquire the queued spin lock, and KeReleaseInStackQueuedSpinLock to release it.”

    解决办法
      1.重新启动
      2.启动在字符菜单界面的时候按F8
      3.选择 Last Known Good Configuration选项(最近一次成功的启动配置,中文大概是这个)
    一种原因是有一个不兼容的驱动或系统服务,或者是有病毒扫描或备份工具。
      1.检测系统日志中的错误消息(系统中有一个叫Event Viewer的东东),来确定到底是哪个东西导致了错误。
      2.在BIOS中将Memory Caching 给禁用掉
      3.运行硬件诊断,特别是内存扫描,这个过程,请看你购机的用户手册。
      4.装好所有的SP补丁
      5如果你的系统有SCSI,手动更新Windows驱动。再在SCSI BIOS中禁用sync negotiation,并检测SCSI的线
      6.如果你是IDE设备, 将主板的IDE口定成 Primary only. 还有, 检测每个IDE设备的master/subordinate/stand-alone设置. 将除了启动硬盘的所有的IDE拿掉.
    Microsoft Certified Systems Engineer 如果您觉得对您有帮助,请在“是否有帮助”点“是”;如果你觉得回复很满意,请“标记为已解答”
    2009年2月13日 7:23