eMule zawiesza komputer...

IP: *.adsl.inetia.pl 04.05.07, 21:44
Witam.
Od jakiegoś czasu eMule zawiesza mi komputer. Po kilku minutach od włączenia
eMule wszystko się zawiesza lub komputer sam się restartuje, po czym pojawia
się komunikat, że system odzyskał sprawność po poważnym błędzie. Program
antywirusowy nic nie wykrywa. Czy to może być spowodowane i jak rozwiązać ten
problem.
Z góry dziękuje za pomoc.
Pozdrawiam:)
    • Gość: Kolobos Re: eMule zawiesza komputer... IP: *.escom.net.pl 04.05.07, 22:38
      Jak masz zainstalowany SP2 to sciagnij sobie XP-AntiSpy i z menu na gorze wybierz opcje zmiany ilosci jednoczesnych polaczen, ustaw na brak limitu.

      Jezeli po niebieskim ekranie utworzyl sie zrzut pamieci to zrob z nim to:
      forum.purepc.pl/index.php?showtopic=104416
      Wynik wklej na forum, a jezeli nie to Panel Sterowania -> System -> Zaawansowane, ostatni przycisk na dole okna i tam masz miec ustawione tak:
      djlizard.net/wp-content/images/minidump.png
      • Gość: fallinginlove Re: eMule zawiesza komputer... IP: *.adsl.inetia.pl 05.05.07, 20:31
        Oto co mi wyszło:)

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


        Loading Dump File [D:\WINDOWS\Minidump\Mini050407-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 2) UP Free x86 compatible
        Product: WinNt, suite: TerminalServer SingleUserTS
        Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
        Debug session time: Fri May 4 21:23:26.410 2007 (GMT+2)
        System Uptime: 0 days 4:56:37.018
        *********************************************************************
        * 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 usbuhci.sys, Win32 error 0n2
        *** WARNING: Unable to verify timestamp for usbuhci.sys
        *** ERROR: Module load completed but symbols could not be loaded for usbuhci.sys
        *******************************************************************************
        * *
        * Bugcheck Analysis *
        * *
        *******************************************************************************

        Use !analyze -v to get detailed debugging information.

        BugCheck 100000D1, {1fd6f82, 2, 1, f8829829}

        ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

        *** WARNING: Unable to verify timestamp for USBPORT.SYS
        *** ERROR: Module load completed but symbols could not be loaded for USBPORT.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 ***
        *** ***
        *************************************************************************
        *************************************************************************
        *** ***
        *** ***
        *** 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
        • Gość: Kolobos Re: eMule zawiesza komputer... IP: *.escom.net.pl 05.05.07, 22:53
          Jezeli masz wiecej niz jeden zrzut to sprawdz wszystkie, a wyniki wklej tutaj:
          wklej.org/ (na forum sie nie miesci z racji limitu znakow) , link podaj na forum.
Pełna wersja