none
win32k.sys蓝屏。帮我更详细的分析下? RRS feed

  • 问题


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


    Loading Dump File [C:\Windows\Minidump\040910-21153-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 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16481.x86fre.win7_gdr.091207-1941
    Machine Name:
    Kernel base = 0x84a38000 PsLoadedModuleList = 0x84b80810
    Debug session time: Fri Apr  9 15:39:57.613 2010 (GMT+8)
    System Uptime: 0 days 4:27:33.689
    *********************************************************************
    * 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 0n2
    *** 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
    .......
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 0000000d, type of pool violation the caller is guilty of.
    Arg2: fe7a3008
    Arg3: 63637355
    Arg4: 8a2b5030

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

    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    ***** 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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************
    *********************************************************************
    * 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+                                    *
    *********************************************************************
    *********************************************************************
    * 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+                                    *
    *********************************************************************

    ADDITIONAL_DEBUG_TEXT: 
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: win32k

    FAULTING_MODULE: 84a38000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc2a2

    BUGCHECK_STR:  0xc2_d

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 84aefe06 to 84b14e10

    STACK_TEXT: 
    WARNING: Stack unwind information not available. Following frames may be wrong.
    ce6da86c 84aefe06 000000c2 0000000d fe7a3008 nt+0xdce10
    ce6da8f4 84b58a76 fe7a3008 00000000 ce6da910 nt+0xb7e06
    ce6da904 83811a41 fe7a3008 ce6dabcc 8378dd55 nt+0x120a76
    ce6da910 8378dd55 ce6da960 4df9cb07 fe8336e8 win32k+0xd1a41
    ce6dabcc 837b2b60 fe8336e8 0000000d 000000fe win32k+0x4dd55
    ce6dac00 837dfa77 fe8336e8 0000000d 000000fe win32k+0x72b60
    ce6dac64 837f9826 ffabc008 4df9cc7f 0217da70 win32k+0x9fa77
    ce6dacb4 837f1da6 ce6dace4 000025ff 00000000 win32k+0xb9826
    ce6dad18 84a7b47a 0217da70 00000000 00000000 win32k+0xb1da6
    ce6dad34 773264f4 badb0d00 0217d9ec 00000000 nt+0x4347a
    ce6dad38 badb0d00 0217d9ec 00000000 00000000 0x773264f4
    ce6dad3c 0217d9ec 00000000 00000000 00000000 0xbadb0d00
    ce6dad40 00000000 00000000 00000000 00000000 0x217d9ec


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    win32k+d1a41
    83811a41 ??              ???

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  win32k+d1a41

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  win32k.sys

    BUCKET_ID:  WRONG_SYMBOLS

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

    2010年4月13日 2:29

全部回复

  • 这个。顺便提一下。是在玩游戏的时候出现的。蓝屏。不玩这个游戏倒是没任何问题。

    主要那破游戏厂商都一个月了还没解决这个问题。我想发到这里看看 有没有其它可能的解决方法。

    2010年4月13日 2:32
  • 建议在安全模式下彻底卸载该游戏,在重新安装一下。
    在IT的路上,You'll never walk alone
    2010年4月13日 2:44
  • 如果楼主的计算机中所安装的ATi显卡,这应该是一个兼容性问题,可以尝试禁用“ATIExternalEventUtility”服务的方式来解决问题。要禁用该服务可以参考以下步骤: 

    1. 单击“开始”按钮,并在开始菜单的搜索条中输入“Services.Msc”并敲击回车键。
    2. 在“服务”窗口中找到“ATiExternalEventUtilityService”项目单击右键,选择“属性”选项。
    3. 将启动类型改为“禁用”(Disabled)。
    4. 单击“确定”按钮并关闭窗口 。
    5. 重新启动计算机

    由于此操作会禁用掉ATi的显示器外部显示器的检测,比如接入外部显示器或拔出现有显示器。

    或者更换其他版本的显示卡驱动程序可能能够帮助解决问题。


    请将已解决的问题标记为“答案”,以便更多的朋友能够方便的找到问题解决方案。
    2010年4月13日 3:00
    版主
  • 不好意思。我的显卡是INTEL集成X3100

    2010年4月13日 3:34
  • 以上只是提供的一个示win32k.sys引起问题的解决示例,并没有说能够解决楼主的问题。

    win32k.sys用于管理驱动程序,这是一个兼容性问题,可能需要更新游戏、驱动程序软件或者硬件来解决。

    PS 楼主在提问时最好能够附上设备环境,解答者拥有更多的信息以便解决问题。


    请将已解决的问题标记为“答案”,以便更多的朋友能够方便的找到问题解决方案。
    2010年4月13日 4:57
    版主
  • 你附上的信息中能用来判断的实在是太少,建议你将dmp文件上传,我们来帮你分析。

    个人名字乃古代三豪杰之名各自取一组合而成:
    天人三策称圣意 董生一举天下知—董仲舒;
    人生自古谁无死,留取丹心照汗青—文天祥;
    一片丹心昭日月,满腔铁血莽昆仑—龙且。
    2010年4月13日 10:12
    版主
  • 你可以把dump文件上传到  SkyDrive 上并告知链接。也可以直接联系微软技术支持来分析dump文件。http://support.microsoft.com/select/default.aspx?target=assistance&c1=509&


    Vivian Xing - MSFT
    2010年4月14日 7:53