System się zawiesza

[attachment=1583:ScreenShot009.jpg], te zaznaczone otwory zaklejasz.
[attachment=1584:ScreenShot008.jpg], strzałki wskazują miejsca montażu wentylatorów, przedni panel jest na plastikowe zaciski, wentylator z przodu obudowy montujesz między stojakiem na dysk twardy a przednim panelem, a przykręcasz od strony panelu plastikowego.

Dzięki a trzeba zaklejać te otwory??? A własnie czy wystarczy tylko z tyłu wentylator??? No i jaki koszt w miare dobrego wentylatora???

Wentylatory to kosz max 40zł chodzi o jak najcichsze z tyłu do max 2500 obr/min z przodu do 2000 obr/min z tyłu i z przodu są maleńkie otworki jak w cedzaku i na obrzeżach cztery większe zmierz rozstaw tych czterech otworów. Z boku musisz zakleić wszystkie otworki ale od wewnątrz będzie estetyczniej, cyrkulacja ma być taka jak w kominie że rękę ma porwać.
Wentylatory podpinasz pod gniazdo SYS_FAN lub pod Melexa czyli bezpośrednio pod zasilacz (pod wolny wtyk z zasilacza).

Moim zdaniem przede wszystkim tył kompa powinien być w pewnej odległości od ściany / biurka.

Moim zdaniem przede wszystkim tył kompa powinien być w pewnej odległości od ściany / biurka.

No to oczywiście jest spory zapas...Tak myśle że jest około 20 cm. od kompa do ściany...

Witam poprzednie miałem Vistę i wyskakiwał mi bluescreen winowajcą był stary bios który się kłócił z prockiem i nod32 smart security lecz bluescreeny nadal mi wyskakiwały i postanowiłem zainstalować Win XP SP3

Proszę powiedzieć jak naprawić też 2 błąd z plikiem systemowym czy po przez płytkę czy podmianę pliku jak przez podmianę to jak to się robi??

A więc po zainstalowaniu (formacie c:) systemu Win XP SP3 wywalił mi następujący błąd jako 1.

A więc po zainstalowaniu systemu wyrąbał mi błąd (plik nv4_disp.dll) związany ze sterownikami do karty graficznej. O to wyniki

Microsoft ® Windows Debugger Version 6.9.0003.113 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Marcin\Ustawienia lokalne\Temp\WER67bc.dir00\Mini120208-02.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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Dec 2 20:52:17.218 2008 (GMT+1)
System Uptime: 0 days 0:00:46.968
*********************************************************************
* 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 nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf9dc288, b93d84ec, 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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_disp.dll ( nv4_disp+7288 )

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



Nieco później wyskoczył kolejny błąd trochę inny



Microsoft ® Windows Debugger Version 6.9.0003.113 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Marcin\Ustawienia lokalne\Temp\WER734c.dir00\Mini120208-03.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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Dec 2 21:06:08.671 2008 (GMT+1)
System Uptime: 0 days 0:09:25.408
*********************************************************************
* 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
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, e3977d38, e3977df0, c170660}

***** 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 Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** WARNING: Unable to verify timestamp for fltMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for fltMgr.sys
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 : ntoskrnl.exe ( nt+22f33 )

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


Co oznacza że problem pliku systemowego ale mi żalezy na naprawieniu tylko tego ze sterami do karty graficznej co ja mam zrobić?? dać starszę??

Właściwie to zależy mi na naprawie obu błędów

Po pierwsze znam malo osob ktore czytalyby cala liste ktora wyswietliles a po drugie jeszcze mniej ktora ja zrozumie. Jak wiadomo bledy windows rozumie waskie grono osob. Pierwsza kwestia - na bazie tego co napisales rozumiem ze zmieniales procka, bo tak nagle blad BIOSA sie nie bierze sam z siebie. Jakie modyfikacje robiles ostatnio w komputerze? Co do visty to najlepiej spisac wszelkie parametry sprzetu jaki masz i sciagac sterowniki online ze strony producenta z zaznaczeniem ze maja byc pod viste. Bolesna ale krotka rada: sformatuj partycje systemowa i nie w trybie szybkiego formatowania. Zainstaluj windows jeszcze raz i sterowniki sciagnij z neta - jesli pod viste to tym bardziej sciagaj z neta i to recznie a nie przez instalator. Vista nie laduje zadnych sterownikow poza tymi ktore ma sama badz uznaje za wlasciwe, a najczesciej sterownikow od producenta nie uznaje przy automatycznej instalacji. Wiem co mowie bo kupilem kompa z vista i dostalem plyte z vista i wszystkimi sterownikami od producentow poszczegolnych komponentow i system nie chcial zainstalowac zadnego sterownika z tych ktore mialem na plytach CD... wszystkie, wlacznie ze sterownikami do plyty glownej sciagalem z neta i teraz chodzi. Ponowna instalacje doradzam z tego wzgledu ze windows to taka rzecz w ktorej latanie czegokolwiek nic nie daje. Ja tez chcialbym nauczyc naprawiac sie poszczegolne bledy windowsa, ale sprowadza sie to do tego ze naprawisz teraz jeden blad a za jakis czas znowu sie cos wysypie w systemie. Naprawianie pojedynczych plikow ma sens wtedy jesli zalezy ci bardzo na odzyskaniu danych z komputera, np zapisanych w moim dokumentach.

Modyfikację to tylko aktualizacja biosu ponieważ bluescreen wykakiwał bo bios był stary i kłócił się z prockiem, przy włączaniu kompa było napisane please udpate bios to power full.... coś tam.

I to wszystko.

Co do formatu to czym się różni taki normalny format od szybkiego??? Skoro kasuję to kasuje?

I tak to ile się czeka na taki normalny format partycji 40gb ?? bo szybki to chyba w 10-15 sek.

a tym że szybka to jest na od*** się a normalna jest dokładna

to tak jak by ktoś Tobie kazał wejść na szczyt tatr w minutę

trwa to troche dluzej niz kilka sekund, ale bezpieczniej i pewniej sie czuje

Pierwsze kasujesz partycję systemową lub jeśli chcesz to cały dysk ale nie robisz tego z pod Windowsa tej zasady sie wystrzegaj zawsze trzymaj się następującej zasady przy instalacji re instalacji systemu Windows. Kasujesz i formatujesz partycje lub dysk programem GParted, Partition Logic 0.69, Partition Manager 9.0 Express, Partition Resizer 1.3.4 oraz innych uruchamianych z pod BIOS-a. Jeśli robisz format tylko partycji systemowej to tylko ją formatujesz ale w przypadku jak decydujesz się na zrobienie formatu całego dysku to po podziale dysku na partycje, robisz format wszystkich partycji, byś potem tego nie musiał robić. Po formacie instalując system Windows jak będzie pytanie o format to go nie robisz tylko wykorzystujesz już gotowy wykonany poprzednim programem. Jaka jest różnica między szybkim formatem a normalnym, taka że w szybkim formacie usuwany jest wpis nazwy programu i zamieniany jest kod statusu pliku/ów, to w skrócie. W normalnym formacie to jest kasowany cały plik i z jednoczesnym nadpisaniem zer lub jedynek jednokrotnie. Plik wykasowany opcją szybką, można przywrócić jako plik aktywny do odczytu lub odczytu i zapisu.