图拉丁吧 关注:7,929,805贴子:131,986,128
  • 6回复贴,共1

求帮忙看下蓝屏记录找下原因

只看楼主收藏回复

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021217-7534-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 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff800`04862000 PsLoadedModuleList = 0xfffff800`04aa6890
Debug session time: Sun Feb 12 20:18:59.756 2017 (GMT+8)
System Uptime: 0 days 4:05:38.577
*********************************************************************
* 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
Loading unloaded module list
...........
Unable to load image dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8014a3d110, fffff880101559ec, ffffffffc000009a, 4}
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Unable to load image dxgmms1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
Unable to load image ataport.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ataport.SYS
*** ERROR: Module load completed but symbols could not be loaded for ataport.SYS
***** Kernel symbols are WRONG. Please fix symbols to do analysis.


IP属地:辽宁1楼2017-02-12 20:42回复
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***


    IP属地:辽宁2楼2017-02-12 20:43
    回复
      2025-09-01 14:11:49
      广告
      不感兴趣
      开通SVIP免广告
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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 ***
      *** ***
      *************************************************************************


      IP属地:辽宁3楼2017-02-12 20:43
      回复
        *************************************************************************
        *** ***
        *** ***
        *** 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+ *
        *********************************************************************
        Probably caused by : nvlddmkm.sys ( nvlddmkm+9169ec )
        Followup: MachineOwner
        ---------频繁蓝屏要死了。。。


        IP属地:辽宁4楼2017-02-12 20:43
        回复
          = =求大神看下啊


          IP属地:辽宁5楼2017-02-12 20:47
          回复
            = =求大神看下啊


            IP属地:辽宁6楼2017-02-12 20:57
            回复
              蓝屏问题最后怎么解决的,和你一样的问题,求助一下


              IP属地:山东来自Android客户端7楼2023-03-29 00:55
              回复