x-kom hosting

Komputer -wyłącza się

Rafiko
utworzono
utworzono

Witam.

Mam system Windows XP pack 3. Wszystko działa poprawie poza jednym detalem. Za każdym razem gdy chce włączyć ściąganie na noc lub w dzień i odchodzę od PC on samodzielnie się wyłącza. Sprawdzałem antywirusem (płatnym), defragmentowałem dyski, przeczyściłem jednostkę centralną, ale wszystkie moje działania spęzły na niczym. Proszę was o rady gdyż jesteście moją ostatnią szansą przed formatowaniem komputera.

Pozdrawiam Rafał

Psycholandia
komentarz
komentarz

Wykonaj:
http://www.forumpc.pl/index.php?showtopic=16074
http://www.forumpc.pl/index.php?showtopic=68409

Rafiko
komentarz
komentarz

Numer błędu to:

[b]*** STOP: 0x00000019 (0x00000020, 0x87916BF0, 0x87916CD0, 0x0A1C000A)[/b]

Psycholandia
komentarz
komentarz

Wykonaj jeszcze to: http://www.forumpc.pl/index.php?showtopic=16074
Podaj konfigurację komputera.

- ściągnij program [b]Memtest86+[/b], nagraj na płytę, zresetuj komputer, wciśnij F11 i niech się uruchomi z płyty i przez noc przetestuje ram
- pobierz program [b]HDTune[/b]; wykonaj [b]error scan[/b] i daj zrzut po skanowaniu + rzut z [b]benchmark[/b] i [b]health[/b]

Rafiko
komentarz
komentarz

Już się do nich zabierać będę.
PS: przypuszczam, że wina leży po stronie [b]dysku twardego[/b], gdyż kiedy go używam np do ściągania (ściąga np 100 kb/s) lub gdy gram w Battlefield 2 (po którejś zmianie mapy zaczął się lekko przycinać w niektórych momentach co zakończyło się auto resetem).

Niedługo podam resztę informacji jak tylko będę mógł.

Niestety mam troszkę dłuższy ten komunikat. Oto on:


[b]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, 878fb6c0, 878fb7a0, a1c0004}

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for AFPAnsi.sys
*** ERROR: Module load completed but symbols could not be loaded for AFPAnsi.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 : AFPAnsi.sys ( AFPAnsi+6ed )

Followup: MachineOwner
---------[/b]

http://w941.wrzuta.pl/obraz/4Jmr7GaAaL3/error_scan
http://w941.wrzuta.pl/obraz/1fx3gnqVZYp/benchmark
http://w941.wrzuta.pl/obraz/01Lxfm7AQH3/health

Pliki mają złe rozszerzenie, więc zostawiam je w postaci linków i są tam ukazane wszystkie operację, które poleciłaś mi zrobić.

Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!

Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.

×
×
  • Dodaj nową pozycję...

Powiadomienie o plikach cookie

Strona wykorzystuje pliki cookies w celu prawidłowego świadczenia usług i wygody użytkowników. Warunki przechowywania i dostępu do plików cookies możesz zmienić w ustawieniach przeglądarki.