ach a takie łatwe rozwiązanie ](*,) dzięki [b]Żółty[/b]

Wywalić jak wywalic ale spróbować zdeinstalowac i zainstalować ponownie. A prz okazji sprawdzic czy nie ma nowszej wersji. Ostatecznie jak z nowsza będą te same jaja to starszą. Dopiero wówczas zastanawiać się nad całkowitym pozbyciem się Outposta Zerknij jeszcze tutaj -> http://www.outpostfirewall.com/forum/showthread.php?t=21679 - nie czytałem tematu całego - może coś pomocnego znajdziesz.

Use !analyze -v to get detailed debugging information. BugCheck 1000000A, {16, 1c, 0, 80502e9a} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** WARNING: Unable to verify timestamp for afw.sys *** ERROR: Module load completed but symbols could not be loaded for afw.sys *** WARNING: Unable to verify timestamp for NDIS.sys *** ERROR: Module load completed but symbols could not be loaded for NDIS.sys *** WARNING: Unable to verify timestamp for klif.sys *** ERROR: Module load completed but symbols could not be loaded for klif.sys *** WARNING: Unable to verify timestamp for JGOGO.sys *** ERROR: Module load completed but symbols could not be loaded for JGOGO.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 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : afw.sys ( afw+f799 ) Followup: MachineOwner --------------- Czyli afw.sys jest przyczyna (Agitum Outpost ) muszę się go wywalić ?

Nie przez sysdata.xml sa restarty ;) W tym dziale jeden z przyklejonym tematów to taki z debugerem w nazwie - poczytaj, przeanalizuj zrzuty pamięci może cos podpowie debuger.