none
win7 轻载时 不定时蓝屏,代码124,求救啊 RRS feed

  • 问题

  • 轻载就是一般在浏览网页时,今天偶尔一次是在股票软件里操作的时候出现蓝屏重启了,提示代码bccode:124,

    但是在我玩魔兽世界的时候,不会出现此现象~里头提到了一个ntoskrnl.exe文件,请求专业人士帮忙看看啊~

     

    我用windbg分析了下dump文件如下:

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


    Loading Dump File [C:\Users\Rain\Desktop\081511-16130-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 ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x84014000 PsLoadedModuleList = 0x8415c830
    Debug session time: Mon Aug 15 14:35:50.975 2011 (GMT+8)
    System Uptime: 0 days 0:00:06.817
    *********************************************************************
    * 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 ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    .....................................................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, 895d7024, 0, 0}

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

    *********************************************************************
    * 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+                                    *
    *********************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : hardware

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

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

    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 00000000, MCA_ASSERT
    Arg2: 895d7024, Address of WHEA_ERROR_RECORD structure
    Arg3: 00000000, High 32 bits of MCi_STATUS MSR for the MCA bank that had
     the error
    Arg4: 00000000, Low  32 bits of MCi_STATUS MSR for the MCA bank that had
     the error

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

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

    *********************************************************************
    * 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+                                    *
    *********************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************

    FAULTING_MODULE: 84014000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    WHEA_ERROR_RECORD: !errrec ffffffff895d7024

    BUGCHECK_STR:  0x124_GenuineIntel

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

    STACK_TEXT: 
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8dd13cc4 840e3105 895d7008 8417bc48 8417bc40 nt+0x3224b3
    8dd13ce4 840e3f2f 8417bc40 895d7008 8417bc70 nt+0xcf105
    8dd13d00 8408208b 8417bc40 00000000 868ea640 nt+0xcff2f
    8dd13d50 84222a55 00000001 afb34fc0 00000000 nt+0x6e08b
    8dd13d90 840d4239 84081f7e 00000001 00000000 nt+0x20ea55
    00000000 00000000 00000000 00000000 00000000 nt+0xc0239


    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME:  hardware

    BUCKET_ID:  WRONG_SYMBOLS

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

    2011年8月15日 14:35

答案

  • 你好,

    这个ntoskrnl.exe是和内核有关的,您的WinDBG分析看不出详细的内容。关于这个蓝屏代码,请参考下:http://msdn.microsoft.com/en-us/library/ff560483(v=vs.85).aspx (英文版的文档)

    是不是只有在运行这个股票软件的时候才出现蓝屏的状况?请尝试用兼容模式来运行这个程序看看还会不会再次蓝屏。同时请升级您的BIOS和相关硬件驱动。

    另外,去进一步找出错误,需要分析整个内核dump文件去以及搜集相关信息,这不适合在论坛上进行操作。如果您想进一步弄清楚原因的话,你可以联系微软客户服务:http://support.microsoft.com/?LN=zh-cn&x=13&y=20

    Regards,

    Miya 


    This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    2011年8月18日 5:42
    版主