eGospodarka.pl
eGospodarka.pl poleca

eGospodarka.plGrupypl.comp.pecetProszę o pomoc w rozwiązaniu problemu.Re: Proszę o pomoc w rozwiązaniu problemu.
  • Data: 2009-01-13 22:34:59
    Temat: Re: Proszę o pomoc w rozwiązaniu problemu.
    Od: Adamicho <A...@o...pl> szukaj wiadomości tego autora
    [ pokaż wszystkie nagłówki ]

    Dzięki serdeczne. Jutro przeskanuje komputer, podmienię wersje Skype'a
    na inną. Jeżeli nic to nie da spróbuje podmienic ów plik. Poniżej
    wklejam cały tekst diagnostyczny jaki pokazał sie po restarcie peceta
    (długaśne nieco)

    Loading Dump File [C:\Documents and Settings\Właściciel\Pulpit
    \Mini011309-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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86
    compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Tue Jan 13 19:53:30.812 2009 (GMT+1)
    System Uptime: 0 days 1:33:55.506
    ****************************************************
    *****************
    * 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
    ...........
    ****************************************************
    ***************************
    *
    *
    * Bugcheck
    Analysis *
    *
    *
    ****************************************************
    ***************************

    Use !analyze -v to get detailed debugging information.

    BugCheck C2, {7, cd4, 0, 8a5db3b0}

    ***** 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!PVOID
    ***
    ***
    ***
    ****************************************************
    *********************
    unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    ****************************************************
    *********************
    ***
    ***
    ***
    ***
    *** 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!_POOL_HEADER
    ***
    ***
    ***
    ****************************************************
    *********************
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    ****************************************************
    *********************
    ***
    ***
    ***
    ***
    *** 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!_POOL_HEADER
    ***
    ***
    ***
    ****************************************************
    *********************
    ****************************************************
    *********************
    ***
    ***
    ***
    ***
    *** 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!_POOL_TRACKER_BIG_PAGES
    ***
    ***
    ***
    ****************************************************
    *********************
    Cannot get _POOL_TRACKER_BIG_PAGES type size
    ****************************************************
    *********************
    ***
    ***
    ***
    ***
    *** 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!_POOL_HEADER
    ***
    ***
    ***
    ****************************************************
    *********************
    ****************************************************
    *********************
    ***
    ***
    ***
    ***
    *** 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!_POOL_HEADER
    ***
    ***
    ***
    ****************************************************
    *********************
    ****************************************************
    *********************
    ***
    ***
    ***
    ***
    *** 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!_POOL_TRACKER_BIG_PAGES
    ***
    ***
    ***
    ****************************************************
    *********************
    Cannot get _POOL_TRACKER_BIG_PAGES type size
    ****************************************************
    *********************
    ***
    ***
    ***
    ***
    *** 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 : ntoskrnl.exe ( nt+22f43 )

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

    Pzdr.

Podziel się

Poleć ten post znajomemu poleć

Wydrukuj ten post drukuj


Następne wpisy z tego wątku

Najnowsze wątki z tej grupy


Najnowsze wątki

Szukaj w grupach

Eksperci egospodarka.pl

1 1 1

Wpisz nazwę miasta, dla którego chcesz znaleźć jednostkę ZUS.

Wzory dokumentów

Bezpłatne wzory dokumentów i formularzy.
Wyszukaj i pobierz za darmo: