Új hozzászólás Aktív témák

• #1231 Tgdt159 tag Dictator^ #1230

  Új Válasz 2011-01-30 01:31:10 #1231

  Új hozzászólás

  Összes hozzászólása itt Válaszok az összes hozzászólására itt Válaszok erre a hozzászólásra

  Privát üzenet küldése

  

  Tgdt159

  tag

  válasz Dictator^ #1230 üzenetére

  Sikerült megnyitni!

  itt a szöveg :

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

  Loading Dump File [C:\Users\Makai\Documents\012911-24484-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 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
  Product: WinNt, suite: TerminalServer SingleUserTS
  Machine Name:
  Kernel base = 0x82848000 PsLoadedModuleList = 0x82990810
  Debug session time: Sat Jan 29 23:23:03.576 2011 (GMT+1)
  System Uptime: 0 days 0:15:45.998
  *********************************************************************
  * 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
  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 117, {845d9008, 8b09e924, 0, 0}

  *** WARNING: Unable to verify timestamp for mssmbios.sys
  *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
  *** WARNING: Unable to verify timestamp for dxgmms1.sys
  *** ERROR: Module load completed but symbols could not be loaded for dxgmms1.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 ***
  *** ***
  *************************************************************************
  Unable to load image atikmpag.sys, Win32 error 0n2
  *** WARNING: Unable to verify timestamp for atikmpag.sys
  *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
  *************************************************************************
  *** ***
  *** ***
  *** 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 : atikmpag.sys ( atikmpag+5924 )

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

Új hozzászólás Aktív témák