none
请问 我需要下载热修复补丁 但是失败 RRS feed

答案

  • 驱动 都是装好系统就装了的...装了 微星主板驱动  p67 c43主板,NV最新的显卡驱动 64位版,也没有啥特别的。。。还有个情况是我开始插满四条内存,现在拔了一条 貌似不蓝屏了

    2011年6月15日 14:13
  • 那么可以在插满四条内存时用 Windows 内存诊断工具检测一下内存稳定性。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "peress"
     
    驱动 都是装好系统就装了的...装了 微星主板驱动 p67 c43主板,NV最新的显卡驱动 64位版,也没有啥特别的。。。还有个情况是我开始插满四条内存,现在拔了一条 貌似不蓝屏了
     
     
    2011年6月16日 12:00

全部回复

  • 0x0000007E 不一定都是一个原因,除非你在分析 Crash Dump 时也有相同的结果。
     
    热修复更新如果邮箱反馈的链接暂不可用,请拨打微软客户服务电话联系。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "peress"
     
    我机器蓝屏,参考了http://social.microsoft.com/Forums/en-US/window7betacn/thread/9ad1ad19-bca6-44e1-aeeb-ec5b95437ee7
     
     
    2011年6月12日 10:08
  • 您好 谢谢您回答我

    我的详细是

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    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: C:\Program Files\Debugging Tools for Windows (x64)\Symbols
    Executable search path is:
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`0445a000 PsLoadedModuleList = 0xfffff800`0469fe90
    Debug session time: Sun Jun 12 15:16:22.548 2011 (UTC + 8:00)
    System Uptime: 0 days 0:00:10.422
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    Loading Kernel Symbols
    ...............................................................
    ......................................................
    Loading User Symbols

    Loading unloaded module list
    ..
    The context is partially valid. Only x86 user-mode context is available.
    The wow64exts extension must be loaded to access 32-bit state.
    .load wow64exts will do this if you haven't loaded it already.
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7E, {ffffffffc0000005, fffff800044e13b9, fffff880051691e8, fffff88005168a40}

    ***** 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                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceSharedLite+f9 )

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

    16.7: kd:x86> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
    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.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800044e13b9, The address that the exception occurred at
    Arg3: fffff880051691e8, Exception Record Address
    Arg4: fffff88005168a40, Context Record Address

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

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

    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: nt

    FAULTING_MODULE: fffff8000445a000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

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

    FAULTING_IP:
    nt!ExAcquireResourceSharedLite+f9
    fffff800`044e13b9 41              inc     ecx

    EXCEPTION_RECORD:  fffff880051691e8 -- (.exr 0xfffff880051691e8)
    ExceptionAddress: 0000000000000000
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 72225721
       Parameter[0]: fffffffffffff800
       Parameter[1]: 0000000000000002
       Parameter[2]: fffffffffffff8a0
       Parameter[3]: 0000000000000000
       Parameter[4]: 0000000000000000
       Parameter[5]: 0000000000000808
       Parameter[6]: 0000000000000000
       Parameter[7]: 0000000000000000
       Parameter[8]: 0000000000000000
       Parameter[9]: 0000000006e0d040
       Parameter[10]: fffffffffffffa80
       Parameter[11]: 0000000000000000
       Parameter[12]: 0000000000000000
       Parameter[13]: 0000000000000000
       Parameter[14]: 0000000000000000
    Attempt to execute non-executable address 0000000000000002

    CONTEXT:  fffff88005168a40 -- (.cxr 0xfffff88005168a40)
    Unable to read context, NTSTATUS 0xC0000147

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x7E

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

    STACK_TEXT: 
    00000000 00000000 00000000 00000000 00000000 0x0


    STACK_COMMAND:  .bugcheck ; kb

    FOLLOWUP_IP:
    nt!ExAcquireResourceSharedLite+f9
    fffff800`044e13b9 41              inc     ecx

    SYMBOL_NAME:  nt!ExAcquireResourceSharedLite+f9

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  ntkrnlmp.exe

    BUCKET_ID:  WRONG_SYMBOLS

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

     

    2011年6月12日 10:58
  • 未知驱动程序故障引起 Windows 内核文件 NTKRNLMP.EXE 加载失败,但原因不一定是与之前那个帖子的 dxgmms1.sys 相同。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "peress"
     
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    BUGCHECK_STR: 0x7E
     
     
    2011年6月13日 11:23
  • 请问该如何处理。。?

    2011年6月13日 11:57
  • 请问如何处理....
    2011年6月14日 14:11
  • 从现有的信息不足以判断引起故障的驱动具体是哪个。请回忆一下首次蓝屏之前曾做过修改或更新的驱动程序设置,尝试卸载或重新安装最后一次改动的驱动设置。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "peress"
     
    请问该如何处理。。?
     
     
    2011年6月15日 4:27
  • 驱动 都是装好系统就装了的...装了 微星主板驱动  p67 c43主板,NV最新的显卡驱动 64位版,也没有啥特别的。。。还有个情况是我开始插满四条内存,现在拔了一条 貌似不蓝屏了

    2011年6月15日 14:13
  • 那么可以在插满四条内存时用 Windows 内存诊断工具检测一下内存稳定性。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "peress"
     
    驱动 都是装好系统就装了的...装了 微星主板驱动 p67 c43主板,NV最新的显卡驱动 64位版,也没有啥特别的。。。还有个情况是我开始插满四条内存,现在拔了一条 貌似不蓝屏了
     
     
    2011年6月16日 12:00