kapuch utworzono 18 czerwca 2010 utworzono 18 czerwca 2010 (edytowane) Witam Mam dosc powazny problem, mianowicie przy uruchamianiu serwera localhost (wczesniej Vertrigo), teraz Webserv od czasu do czasu (losowo 50/50) wyskakuje mi blue screen. Myslalem ze jest to wina serwera Vertrigo, wiec go odinstalowalem i zainstalowalem Webserv, chodzil 1 dzien (3 uruchomienia), a dzisiaj pojawil mi sie znowu niebieski ekran. Nie wiem co jest grane, system mam oryginalny - aktualizowany, prosze o pomoc. Specyfikacja laptopa: [quote]CPU: Intel Core Duo T2400 @ 1,83GHz - 1,83GHz RAM: 2,00 GB OS: 32 bit Windows Vista Home Basic SP 2[/quote] Jesli chodzi o antywirusy i firewalle: [quote]- Avast Home (aktualizowany) - Firewall ten wbudowany w system - wlaczony - Windows defender - wylaczony bo denerwowaly mnie skany w najmniej odpowiednim momencie (ale moge wlaczyc jak ma to pomoc) - Kontrola uzytkownikow - wylaczona (bo to tylko utrudnia zyie!)[/quote] Sterowniki raczej mam w najnowszych wersjach, poniewaz mam wlaczona usluge Windows Update i HP cos tam Check, ktory takze aktualizuje mi stery. A oto ostatni plik dump w stanie surowym: [spoiler]Microsoft ® Windows Debugger Version 6.6.0007.5 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini061810-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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0x81c03000 PsLoadedModuleList = 0x81d1ac70 Debug session time: Fri Jun 18 11:01:13.936 2010 (GMT+2) System Uptime: 0 days 1:14:17.701 ********************************************************************* * 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Loading Kernel Symbols ............................................................................................................................................................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck F4, {3, 8b64d918, 8b64da64, 81e29710} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ***** 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!_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!_KPRCB *** *** *** ************************************************************************* Probably caused by : csrss.exe Followup: MachineOwner ---------[/spoiler] a tu ten sam plik dump po analizie komenda "kd> !analyze -v": [spoiler]0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_OBJECT_TERMINATION (f4) A process or thread crucial to system operation has unexpectedly exited or been terminated. Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no longer function. Arguments: Arg1: 00000003, Process Arg2: 8b64d918, Terminating object Arg3: 8b64da64, Process image file name Arg4: 81e29710, Explanatory message (ascii) Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ***** 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!_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!_KPRCB *** *** *** ************************************************************************* MODULE_NAME: csrss FAULTING_MODULE: 00000000 DEBUG_FLR_IMAGE_TIMESTAMP: 0 PROCESS_OBJECT: 8b64d918 IMAGE_NAME: csrss.exe CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WRONG_SYMBOLS BUGCHECK_STR: 0xF4 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 8bf454e4 81e9570c 000000f4 00000003 8b64d918 nt+0xcdb8d 8bf45508 81df3fbd 81e29710 8b64da64 8b64db40 nt+0x29270c 8bf45538 81df3f64 8b64d918 83d211a0 c0000005 nt+0x1f0fbd 8bf4556c 81c4dc7a ffffffff c0000005 8bf459b0 nt+0x1f0f64 8bf4557c 81c4cccd badb0d00 8bf455f4 00000000 nt+0x4ac7a 8bf459b0 81c29288 8bf459dc 00000000 8bf45d64 nt+0x49ccd 8bf45d34 81c517cb 0177f530 0177f54c 00000000 nt+0x26288 8bf45d50 81c4dc7a 0177f530 0177f54c 00000000 nt+0x4e7cb 8bf45d64 770d5e74 badb0d00 0177f524 00000000 nt+0x4ac7a 8bf45d68 badb0d00 0177f524 00000000 00000000 0x770d5e74 8bf45d6c 0177f524 00000000 00000000 00000000 0xbadb0d00 8bf45d70 00000000 00000000 00000000 00000000 0x177f524 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------[/spoiler] Prosze o pomoc, bo zaraz oszaleje, duzo pracuje na localhoscie i teraz przed kazdym uruchomieniem serwera boje sie ze zakonczy sie to restartem kompa. W dodatku, odkad bawie sie na laptopie, nie mam nawyku czestego zapisywania projektow, wiec juz pare razy tracilem przez ten BSOD efekt kilkugodzinnej pracy :/ Jesli bedzie trzeba, to moge wkleic poprzednie pliki DUMP, ktore powstaly za czasow Vertrigo. Przejrzalem tak na szybko reszte plikow dump i za kazdym razem na koncu jest taki komunikat: [quote]Probably caused by : csrss.exe[/quote] Czyli tak jakby ten proces byl odpowiedzialny za te restarty, ale czemu, to nie mam pojecia i jak to 'naprawic'? W menadzerze mam uruchomione dwa procesy csrss.exe. Pozdrawiam
Evil_Genius komentarz 18 czerwca 2010 komentarz 18 czerwca 2010 Nie żebym zaczynał flamewar ale to wina Visty i jej różnych dziwnych zachowań. Proponuje Win7 albo xp
kapuch komentarz 18 czerwca 2010 Autor komentarz 18 czerwca 2010 (edytowane) Niestety to laptop, a ciezko tutaj zmieniac system, bo jest ryzyko utraty ukrytej partycji z winda, przez co utracil bym oryginalna viste - nie mam plyty CD. Po drugie nie mam innego oryginalnego systemu, a piratow nie bede instalowal :/ PS. Juz kiedys nosilem sie z zamiarem zmiany systemu (na XP - z racji wzglednie niskiej ceny), ale po przeczytaniu ile jest z tym problemow, no i ze mozna stracic poprzedniego windowsa - zrezygnowalem. EDIT: Przepraszam, z przyzwyczajenia naciskam Odpowiedz pod danym postem :/ [color="#ff0000"] //nie cytujemy całych postów //raaz[/color]
raazor90 komentarz 18 czerwca 2010 komentarz 18 czerwca 2010 Daj loga z OTL do działu Logi do sprawdzenia, w nazwie tematu napisz [quote]BSOD csrss.exe[/quote] Podejrzewam infekcję plików systemowych
kapuch komentarz 18 czerwca 2010 Autor komentarz 18 czerwca 2010 [quote name='raazor90' date='18 czerwiec 2010 - 19:18' timestamp='1276885234' post='1037673'] Daj loga z OTL do działu Logi do sprawdzenia, w nazwie tematu napisz Podejrzewam infekcję plików systemowych [/quote] OK dzieki wielkie - jest jakas nadzieje, bo juz myslalem, ze jestem na te restarty skazany. Z drugiej strony mam nadzieje, ze to nie wirus, bo tyle zabezpieczen wlaczanych + stala aktualizacja, na marne :/ Zaraz skonczy sie skanowanie i zaloze temat. Pozdrawiam
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.