co za błędy
Witam
podgląd zdarzeń sypie takimi błędem:
System zdarzeń modelu COM+ nie mógł zwolnić metody ConnectionMade dla subskrypcji {3D8DE50A–4532–47C8–8491–D2037EACB707}–{00000000–0000–0000–0000–000000000000}–{00000000–0000–0000–0000–000000000000}. Subskrybent zwrócił HRESULT 80004001
oraz
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini010102–02.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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** 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 UP Free x86 compatible
Product: WinNt
Kernel base = 0x804d0000 PsLoadedModuleList = 0x80545b28
Debug session time: Tue Jan 1 00:40:39.296 2002 (GMT+1)
System Uptime: 0 days 0:00:37.859
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** 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 100000EA, {81653020, 81678d80, 817a8168, 1}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Unable to load image watchdog.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for watchdog.sys
*** ERROR: Module load completed but symbols could not be loaded for watchdog.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: watchdog!_DEFERRED_WATCHDOG ***
*** ***
*************************************************************************
Followup: MachineOwner
–––––––––
Prosze o pomoc
podgląd zdarzeń sypie takimi błędem:
System zdarzeń modelu COM+ nie mógł zwolnić metody ConnectionMade dla subskrypcji {3D8DE50A–4532–47C8–8491–D2037EACB707}–{00000000–0000–0000–0000–000000000000}–{00000000–0000–0000–0000–000000000000}. Subskrybent zwrócił HRESULT 80004001
oraz
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini010102–02.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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** 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 UP Free x86 compatible
Product: WinNt
Kernel base = 0x804d0000 PsLoadedModuleList = 0x80545b28
Debug session time: Tue Jan 1 00:40:39.296 2002 (GMT+1)
System Uptime: 0 days 0:00:37.859
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** 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 100000EA, {81653020, 81678d80, 817a8168, 1}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Unable to load image watchdog.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for watchdog.sys
*** ERROR: Module load completed but symbols could not be loaded for watchdog.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: watchdog!_DEFERRED_WATCHDOG ***
*** ***
*************************************************************************
Followup: MachineOwner
–––––––––
Prosze o pomoc
Odpowiedzi: 3
spróbuj, moźe pomoźe
taki błąd ukazał sie zaraz po instalacji, czy mimo wszystko expandować plik??
ntoskrnl.exe to plik systemowy, spróbuj go podmienić poleceniem expand z konsoli odzyskiwania
Strona 1 / 1