"no signal" i samoczynny reset komputera podczas grania

[kornik94]

Mam problem z komputerem , otóż gdy załączę jakąś grę np.CS 1.5 robi mi się czarny ekran pisze "no signal" słyszę jak staje dysk twardy i od nowa załącza się system. Nie wiem co jest nie tak ten komputerek ma juz swoje latka ok. 5 lat
tak więc wymieniłem mu paste na grafice i na procku.
Sprzęt:
Procek AMD athlon XP +2000 1.67 GHZ
Grafika NVIDIA Geforce4 MX 440
RAM 512MB
HD 60GB Samsung
Zasilacz NTT 350W
Płyta Główna As Rock nie wiem za dokładnie

[rokko]

Zobacz czy tworzą sie pliki DMP. Odczytaj je w debugerze i daj raporty na forum.

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

[kornik94]

[code]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 80042000, 0, 0}

***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 : ntoskrnl.exe ( nt+12635 )

Followup: MachineOwner
---------




*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 80042000, 0, 0}

***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 : ntoskrnl.exe ( nt+12635 )

Followup: MachineOwner[/code]
---------


[/quote]
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {818018b8, 817fa558, f896dcb4, 1}

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

*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.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 : nv4_mini.sys ( nv4_mini+34ba7 )

Followup: MachineOwner
---------

następny:D





*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, cd4, 2011011, 81998088}

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

*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*** WARNING: Unable to verify timestamp for epfwtdir.sys
*** ERROR: Module load completed but symbols could not be loaded for epfwtdir.sys
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.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!PVOID ***
*** ***
*************************************************************************
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
*************************************************************************
*** ***
*** ***
*** 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!_POOL_HEADER ***
*** ***
*************************************************************************
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
*************************************************************************
*** ***
*** ***
*** 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!_POOL_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_POOL_TRACKER_BIG_PAGES ***
*** ***
*************************************************************************
Cannot get _POOL_TRACKER_BIG_PAGES type size
*************************************************************************
*** ***
*** ***
*** 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 : epfwtdir.sys ( epfwtdir+2e12 )

Followup: MachineOwner
---------

Tylko tyle ich jest

i jeszcze cos takiego mi sie dzieje i w grach i wlasnie przy mocnym uzywaniu komputera

http://img25.imageshack.us/i/beztytuubbt.jpg/ <----- To co sie dzieje :)

[Psycholandia]

[quote]Probably caused by : ntoskrnl.exe[/quote]
ściągnij na sam początek program Memtest 86+ , wypal na płytę i uruchom z płyty , niech przetestuje pamięci przez noc , żebyśmy coś mogli wykluczyć

spróbuj skopiować go z płytki instalacyjnej używając konsoli odzyskiwania - kiedy instalator zaproponuje jej użycie trzeba nacisnąć r, po ukazaniu się konsoli wpisać numer systemu( konsola wyświetli) i enter, jeszcze raz enter, jeśli nie ma hasła i wpisać polecenia
expand [b]X:\i386\ntoskrnl.ex_ C:\WINDOWS\system32\ntoskrnl.exe[/b] ([b]X[/b] - literka CD-ROMu, a ta pozioma kreseczka "_" w pierwszej części komendy ma być!)

[quote]Probably caused by: nv4_mini.sys [/quote]
Zainstaluj inne sterowniki od karty graficznej.
Sprawdź temperatury karty czy się nie przegrzewa, przeczyść ją z kurzu.

[quote]Probably caused by : epfwtdir.sys[/quote]
Używasz Eseta? Przeinstaluj.

[kornik94]

[quote name='Andziorka' date='04 listopad 2009 - 14:07 ' timestamp='1257340026' post='893222']
ściągnij na sam początek program Memtest 86+ , wypal na płytę i uruchom z płyty , niech przetestuje pamięci przez noc , żebyśmy coś mogli wykluczyć

spróbuj skopiować go z płytki instalacyjnej używając konsoli odzyskiwania - kiedy instalator zaproponuje jej użycie trzeba nacisnąć r, po ukazaniu się konsoli wpisać numer systemu( konsola wyświetli) i enter, jeszcze raz enter, jeśli nie ma hasła i wpisać polecenia
expand [b]X:\i386\ntoskrnl.ex_ C:\WINDOWS\system32\ntoskrnl.exe[/b] ([b]X[/b] - literka CD-ROMu, a ta pozioma kreseczka "_" w pierwszej części komendy ma być!)


Zainstaluj inne sterowniki od karty graficznej.
Sprawdź temperatury karty czy się nie przegrzewa, przeczyść ją z kurzu.


Używasz Eseta? Przeinstaluj.
[/quote]

Zmienilem z ESEta na Avire:D
Przez konsole odzyskiwania nie wyszło :/
a memtest nie wiem jaki plik skopiowac na tą błytę

[Psycholandia]

Miał być Memtest86+: [b][url="http://www.programosy.pl/program,memtest86.html"]KLIK[/url][/b] czyli rozpakowujesz i masz 1 plik, który nagrywasz na płytę i testujesz przez noc.
BSOD-y nadal występują?
[quote]Przez konsole odzyskiwania nie wyszło :/[/quote]
A dokładniej?

[kornik94]

[quote name='Andziorka' date='04 listopad 2009 - 17:24 ' timestamp='1257351884' post='893363']
Miał być Memtest86+: [b][url="http://www.programosy.pl/program,memtest86.html"]KLIK[/url][/b] czyli rozpakowujesz i masz 1 plik, który nagrywasz na płytę i testujesz przez noc.
BSOD-y nadal występują?

A dokładniej?
[/quote]
Wyszło ze nie umi znaleźć tego pliku do podmiany, ale te problemy mogą być z karty graficznej bo CS 1.6 jak gram na Software jest nice a jak na OpenGL pada, wiesza się robią się paski itd....

[Psycholandia]

Testowałeś memtestem?
Sprawdź temperatury karty Everestem na przykład i je podaj, zmień sterowniki do grafiki uprzednio kasując te, które masz teraz Drive Cleanerem 3.