BSOD Blue Screen przy uruchamianiu serwera. Opcje

[kapuch]

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:
CPU: Intel Core Duo T2400 @ 1,83GHz - 1,83GHz
RAM: 2,00 GB
OS: 32 bit Windows Vista Home Basic SP 2

A oto ostatni plik dump:
Chcialem wkleic tutaj w QUOTE, ale byl zbyt dlugi tekst, wiec podaje linka:
http://wklej.org/hash/43ca7173071/txt/

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 :/

PS. Jesli bedzie trzeba, to moge wkleic poprzednie pliki DUMP, ktore powstaly za czasow Vertrigo.
PS 2: Przejrzalem tak na szybko reszte plikow dump i za kazdym razem na koncu jest taki komunikat:

Probably caused by : csrss.exe

Czyli tak jakby ten proces byl odpowiedzialny za te restarty, ale co to jest, to nie mam pojecia i jak to 'naprawic'?

Ten post edytował kapuch 18.06.2010, 10:33:39

[erix]

Masz wszystkie sterowniki w najnowszych wersjach? Jakieś aktywne firewalle/antywirusy/etc?

[kapuch]

Masz wszystkie sterowniki w najnowszych wersjach? Jakieś aktywne firewalle/antywirusy/etc?

Jesli chodzi o antywirusy i firewalle:
- 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!)

Sterowniki raczej mam w najnowszych wersjach, poniewaz mam wlaczona usluge Windows Update i HP cos tam Check, ktory takze aktualizuje mi stery.

PS. Popatrzylem na google i ten plik dump, mozna jeszcze przepuscic z komenda !analyze -v, jesli mi sie to uda to wkleje ten plik juz po analizie.

EDIT: Udala sie analiza, wiec wklejam:

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
---------

Teraz dalo sie wkleic w poscie

Ten post edytował kapuch 18.06.2010, 11:04:59