OuGeeLoc 0 Napisano 27 Października 2008 Udostępnij Napisano 27 Października 2008 Witam. A więc tak: Od samego poczatku jak zakupilem komputer borykam sie z problemami, ale od początku. Najpierw konfiguracja: plyta MSI P7N sli Platinum zasilacz Antec DualTruePower quattro 850W cpu C2D E8400 3ghz grafika Gainward GF8800GT 1gb GS ram GEIL evoone 800Mhz 4gb dysk 750GB Samsung sata2 32Mb cache winXP PRO sp2 1.Windows Vista. Po podziale dysku na partycje instalacja systemu. System udalo sie zainstalowac za mniej więcej 10 razem. Uprzednie 9 prob przerwalo okno z bledem lub tez zwis. Na zainstalowanej Viscie usilowalem zainstalowac sterowniki. Dokładnie sprawdzilem i instalowalem tylko te kompatybilne z Vista. Pierwsza instalacja sterownikow karty graficnzej skonczyla sie niepowodzeniem i zwisem w polowie instalacji. Restart. Instalacja udana. Restart. Od tej pory za kazdym razem system zawieszal sie nie wiecej niz 2minuty po uruchomieniu. Reinstalacja systemu. System bez sterownikow dla karty graficznej tym razem. Nie zainstalowalem ich dla testu. Dzialal dlzuej niz 2 minuty ale wykazywal duza awaryjnosc niebieskie okna i restarty mniej wiecej co godzine.Porazka. 2.Format.Ponowny podzial na partycje.Winows XP PRO sp2. Instalacja pomyslna za 1 razem. Podczas isntalacji sterownikow rowniez zdazyl sie przynajmniej raz zwis. Mimo to system dzialal. Duzo stabilniej niz Vista. Zdazaly sie zwisy (kursor i inneoperacje niemal zamieraja,reakcja na ruch po 2 minutach,nie odpuszcza). Srednio 1-2 na dzien. Na poczatku myslalem ze cos jest nie tak z plyta na ktorej jest Vista.Potem kiedy system byl zaisntalwoany, ze to bedziewnosc Visty(wtedy PC offline,brak aktualizacji). Myslalem tez ze moze RAM jest cos nie teges,ze ''sie gryzie z plyta'' albo jest uszkodzony(przy 1 wlaczeniu komputera czerwoa czcionka komuniakt cos jakby ''automatyczne przetaktowywanie ramu sie nie powiodlo,zrestartuj komputer(?!). Teraz po dluzszej obserwacji wychodzi na to ze cos musi byc z dyskiem twardym bo: -czeste zwisy przy isntalacjach (sytem,stery) -zwisy przy buforowaniu filmow youtube -po restarcie systemu po takim typowym zwisie, komputer nie wykrywa dysku twardego,czarny ekran i napis 'Select proper device to bot' Pomaga na to tylko odlaczenie pradu i wlaczenie go spowrotem - po normalnym(nie po restarcie) wlaczeniu kompa,czasem,bardzo zadko zdarza sie ze widows nei startuje,jest tylko czarny ekran bez zadnych komuniaktow Na dodatek od jakiegos czasu nasililo sie wyskakiwanie niebieskich okienek, a mowa wnich o domniemanym problemie z hardwere. 'jesli dokonales dodania nowego sprzetu to costam blabla'. Bardzo mi zalezy na ocenie fachowym okiem. Jesli wina lezy po stronie sprzetu musze byc tego pewien. Cytuj Link to post Share on other sites
Matuzalem 0 Napisano 28 Października 2008 Udostępnij Napisano 28 Października 2008 Po pierwsze zero OC przy stawianiu i testach. Co do podłoża - najpierw porównaj napięcie dla pamięci w BIOS-ie z informacją od ich producenta (może się okazać, że pracują w zakresie np. 1,9 -2,3V , a BIOS ustawia je na tę dolną wartość) i ich ew. korekta w górę. Próbowałeś stawiać systemy z mniejszą ilością pamieci niż te 4GB, a potem dopiero zmienić wpisy w boot.ini, BCDedit i dołożyć do 4 (nie wspominasz o tym, by systemy były 64-bitowe)? Last not least - aktualizacja, o ile jest możliwa, BIOS-u i - niezależnie od niej - przejrzenie ustawień związanych z podsystemem pamięci przy ich konfrontacji z opisami funkcji w manualu. PS. Sprawdzałeś wpisy w logach tworzonych przy BSOD-ach? - W nich powinno być wiecej szczegółów mogących wskazać przyczyny. Cytuj Link to post Share on other sites
OuGeeLoc 0 Napisano 29 Października 2008 Autor Udostępnij Napisano 29 Października 2008 Dotychczas wystarczylo ze potrafilem zrobic format/zainstalwac system/sterowniki. Jestem laikiem. :oops: Wlasnie przechodze twarda edukacje. Taka krotka biografia powinna chyba znalezc sie na wstepie zebysmy sie rozumieli (ja rozumial was ) Do rzeczy: raporty o blue screenach? Gdzie,jak je sprawdzic. Tresci 'na zywo' nie spisze bo ostatnio pc restartuje sie sam 5s po pojawieniu niebieksiego ekranu. Bede uzupelnial informacje na biezaco. Na poczatek ma mcos takiego. Kilka wpisow z eventvwr.msc. 1.Cala grupka ostrzezen o podobnej tresci. http://images35.fotosik.pl/25/cd69f82e8298fd10m.jpg Tresc (bajty) 0000: 03 00 68 00 01 00 b6 00 ..h...¶. 0008: 00 00 00 00 33 00 04 80 ....3.. 0010: 2d 01 00 00 00 00 00 00 -....... 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 e2 6c 6d 25 00 00 00 .âlm%... 0028: de 02 00 00 00 00 00 00 Þ....... 0030: ff ff ff ff 03 00 00 00 ÿÿÿÿ.... 0038: 40 00 00 82 02 01 01 00 @...... 0040: c0 20 0a 12 42 03 00 40 À ..B..@ 0048: 00 00 00 00 14 00 00 00 ........ 0050: 00 00 06 00 80 2b f2 89 ....+ò 0058: 00 00 00 00 50 29 f2 89 ....P)ò 0060: e0 e9 f8 ba 71 b6 b6 12 àéøºq¶¶. 0068: 28 00 12 b6 b6 71 00 00 (..¶¶q.. 0070: 86 00 00 00 00 00 00 00 ....... 0078: 00 00 00 00 00 00 00 00 ........ 0080: 00 00 00 00 00 00 00 00 ........ 0088: 00 00 00 00 00 00 00 00 ........ Tresc (slowa) 0000: 00680003 00b60001 00000000 80040033 0010: 0000012d 00000000 00000000 00000000 0020: 6d6ce200 00000025 000002de 00000000 0030: ffffffff 00000003 82000040 00010102 0040: 120a20c0 40000342 00000000 00000014 0050: 00060000 89f22b80 00000000 89f22950 0060: baf8e9e0 12b6b671 b6120028 000071b6 0070: 00000086 00000000 00000000 00000000 0080: 00000000 00000000 00000000 00000000 Edit: Przejzalem wszytkie raporty calego miesiaca (tyle stoi aktualna instalajca windowsa).Ten typ bledu zdarzyl sie jedynie raz (ta grupa). Notorycznie za to,powtarza sie cos takiego. http://images27.fotosik.pl/288/527f77d38db8fce7m.jpg Chyba to nie to. Bo to tyczy polaczenia sieciowego ? Dalem to bo regularnie sie powtaza tak jak pady. PC padal takze ofline.Jak zalicze zwis to odrazu sprawdze jakie pojawily sie zapisy i podam. Cytuj Link to post Share on other sites
OuGeeLoc 0 Napisano 29 Października 2008 Autor Udostępnij Napisano 29 Października 2008 Sory , nie widze opcji edytowania posta. Zepsulem cos ze screenami. Teraz powinny byc ok. http://www.fotosik.pl/pokaz_obrazek/cd6 ... 8fd10.html http://www.fotosik.pl/pokaz_obrazek/527 ... 8fce7.html Cytuj Link to post Share on other sites
Matuzalem 0 Napisano 29 Października 2008 Udostępnij Napisano 29 Października 2008 Drugi możesz sobie darować - nie jest istotny, bo dotyczy tylko komunikacji ( co zresztą wynika z opisu ) i jest nawet nie tyle rzeczywistym błędem, ile informacją. Pierwszy na dysk wskazując prowadzi do prozaicznego luzu kabla sygnałowego ew. jego uszkodzenia bądź do poważniejszej sprawy - błąd kontrolera dysku lub płyty. Spróbować powinieneś zmienić kabel łączący dysk z płytą, a jeżeli to nie pomoże to podłaczyć dysk do innego gniazda ( masz jeszcze ze 3 do wyboru ). Gdyby nadal było to samo to zostaje użycie zworki na dysku - dla ograniczenia transferu do poziomu S-ATA(1) i sprawdzenie co wtedy. Warto ównież przed, po lub w trakcie w/w kombinacji przelecieć dysk systemowych chkdsk-iem ( uruchamianaym najlepiej z konsoli odzyskiwania - składnia chkdsk /p /r ), by wpływ ewentualnie już powstałych błedow na próby sprżetowe zminimalizować. PS. W sprawie już ciut obocznej - tego jak sie dobrać do BSOD-ów i wyłuskać co z nich wynika ( zawsze sie przydać może ) - zapoznaj się z tym: http://forum.centrumxp.pl/default.aspx?g=posts&t=108297 - część poświęcona debugging tools w połaczeniu z ustawieniami w sekcji "awaria systemu" takimi jak na pierwszym obrazku w linku ( ew. możesz odhaczyć "automatycznie uruchom ponownie" - wtedy i BSOD sie wyświetli i plik *.dmp zostanie zapisany ). Cytuj Link to post Share on other sites
OuGeeLoc 0 Napisano 29 Października 2008 Autor Udostępnij Napisano 29 Października 2008 HD Tune-wyniki. http://www.fotosik.pl/pokaz_obrazek/0a8 ... 70ca4.html http://www.fotosik.pl/pokaz_obrazek/4a3 ... de1b8.html http://www.fotosik.pl/pokaz_obrazek/445 ... 94130.html http://www.fotosik.pl/pokaz_obrazek/9c1 ... 9c2fa.html http://www.fotosik.pl/pokaz_obrazek/65e ... f87cb.html WinDbg Microsoft ® Windows Debugger Version 6.9.0003.113 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 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 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0 Debug session time: Mon Oct 27 18:18:34.546 2008 (GMT+1) System Uptime: 0 days 0:00:57.296 ********************************************************************* * 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 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 mdhsh.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for mdhsh.sys *** ERROR: Module load completed but symbols could not be loaded for mdhsh.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 10000050, {f5a82949, 0, f5a82949, 2} ***** 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 *** *** *** ************************************************************************* *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.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 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : mdhsh.sys ( mdhsh+38a ) Followup: MachineOwner --------- Microsoft ® Windows Debugger Version 6.9.0003.113 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 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 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0 Debug session time: Sun Oct 26 07:55:45.237 2008 (GMT+1) System Uptime: 0 days 1:59:51.508 ********************************************************************* * 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 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 mdhsh.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for mdhsh.sys *** ERROR: Module load completed but symbols could not be loaded for mdhsh.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 6ed60949, ae374c00, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys *** WARNING: Unable to verify timestamp for rdbss.sys *** ERROR: Module load completed but symbols could not be loaded for rdbss.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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : mdhsh.sys ( mdhsh+38a ) Followup: MachineOwner --------- Microsoft ® Windows Debugger Version 6.9.0003.113 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 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 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0 Debug session time: Sun Oct 26 05:53:13.644 2008 (GMT+1) System Uptime: 0 days 1:40:47.367 ********************************************************************* * 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 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 mdhsh.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for mdhsh.sys *** ERROR: Module load completed but symbols could not be loaded for mdhsh.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 10000050, {f5aba949, 0, f5aba949, 2} ***** 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 *** *** *** ************************************************************************* *** WARNING: Unable to verify timestamp for portcls.sys *** ERROR: Module load completed but symbols could not be loaded for portcls.sys *** WARNING: Unable to verify timestamp for kmixer.sys *** ERROR: Module load completed but symbols could not be loaded for kmixer.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 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : mdhsh.sys ( mdhsh+38a ) Followup: MachineOwner --------- Microsoft ® Windows Debugger Version 6.9.0003.113 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 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 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0 Debug session time: Sun Oct 26 05:55:27.800 2008 (GMT+1) System Uptime: 0 days 0:01:46.546 ********************************************************************* * 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 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 mdhsh.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for mdhsh.sys *** ERROR: Module load completed but symbols could not be loaded for mdhsh.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 10000050, {f5a7a949, 0, f5a7a949, 2} ***** 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 *** *** *** ************************************************************************* *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.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 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : mdhsh.sys ( mdhsh+38a ) Followup: MachineOwner --------- Microsoft ® Windows Debugger Version 6.9.0003.113 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 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 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0 Debug session time: Sun Oct 26 04:11:59.065 2008 (GMT+1) System Uptime: 0 days 0:01:07.812 ********************************************************************* * 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 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 mdhsh.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for mdhsh.sys *** ERROR: Module load completed but symbols could not be loaded for mdhsh.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 10000050, {df30c949, 0, df30c949, 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 *** *** *** ************************************************************************* *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.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 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : mdhsh.sys ( mdhsh+38a ) Followup: MachineOwner --------- Microsoft ® Windows Debugger Version 6.9.0003.113 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 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 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0 Debug session time: Sun Oct 26 04:10:25.413 2008 (GMT+1) System Uptime: 0 days 4:43:28.056 ********************************************************************* * 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 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 mdhsh.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for mdhsh.sys *** ERROR: Module load completed but symbols could not be loaded for mdhsh.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 10000050, {d6aea949, 0, d6aea949, 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 *** *** *** ************************************************************************* *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.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 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : mdhsh.sys ( mdhsh+38a ) Followup: MachineOwner --------- Cytuj Link to post Share on other sites
OuGeeLoc 0 Napisano 29 Października 2008 Autor Udostępnij Napisano 29 Października 2008 W kwestii RAMu. Na opakowaniu mam ze to CAS4. Jesli to jest to samo co cl4 to wedlug producenta powinno byc 4-4-4-12 i 1,9~2,0 V. W biosie mam 1,9V(default) a timingi auto. Cytuj Link to post Share on other sites
Wojciech Lenartek 0 Napisano 29 Października 2008 Udostępnij Napisano 29 Października 2008 Ja bym sprawdził tą konfigurację na innych kościach ram - tak by wykluczyć błąd tego podzespołu. Cytuj Link to post Share on other sites
Matuzalem 0 Napisano 30 Października 2008 Udostępnij Napisano 30 Października 2008 mdhsh.sys - http://www.sophos.com/security/analyses ... g_from=rss - w "more information" znajdziesz nazwy plików z tym ścierwem związanych. A potem sie zobaczy ( napięcie możesz RAM-u podnieść od razu do tych 2V ). Cytuj Link to post Share on other sites
OuGeeLoc 0 Napisano 30 Października 2008 Autor Udostępnij Napisano 30 Października 2008 Nie moge zainstalowac antywirusa. Kasperskiemu brakuje pliku klif.sys. Avast tez nie idzie tyle ze przyczyny nie podaje. Pewnie to samo. Wpadlem na genialny pomysl naprawienia systemu z plytki windows w nadziei ze uzupelnie w ten sposb brakujacy plik. Nie rozumiem tylko dla czego win nie akceptuje poprawnie wpisanego hasla administratora(to nie caps). Z 'problemow z dyskiem twardym' zrobil sie topic 'pan niescenscie'. Cytuj Link to post Share on other sites
OuGeeLoc 0 Napisano 30 Października 2008 Autor Udostępnij Napisano 30 Października 2008 Kolejna wskazowka. Zwis. Restart (bez odciecia pradu). BIOS (AMI). Advanced BIOS Features/Boot Sequence -brak hdd. Standard CMOS features - brak hdd gdziekolwiek (zwykle jest na sata2). Cytuj Link to post Share on other sites
Matuzalem 0 Napisano 31 Października 2008 Udostępnij Napisano 31 Października 2008 To już inna para kaloszy - od prozaicznej baterii na płycie ( mało prawdopodobne, ale mozliwe ) do - wracamy kabla sygnałowego i kontrolerów. - Wracamy do głównego nurtu ( i tego com już wymieniał jako to do dla Ciebie ). Tyle, że teraz poza nim doszedł jeszcze problem zasyfienia systemu, z którym potem wlaczyć Ci przyjdzie ( użyj jakiegoś AV odpalanego w postaci LiveCD ). Cytuj Link to post Share on other sites
OuGeeLoc 0 Napisano 31 Października 2008 Autor Udostępnij Napisano 31 Października 2008 Jest gwarancja wiec chyba go oddam do sklepu. Przydalby sie jakis sposob potem(po naprawie) na sprawdzenie kompa na miejscu (nie widzi mi sie tachanie z nim ponownie). Jakies pomysly? Cytuj Link to post Share on other sites
Wojciech Lenartek 0 Napisano 31 Października 2008 Udostępnij Napisano 31 Października 2008 Przydalby sie jakis sposob potem(po naprawie) na sprawdzenie kompa na miejscu (nie widzi mi sie tachanie z nim ponownie). Jakies pomysly? Może odpalenie jakiegoś systemu z Live Cd lub pendrivea Cytuj Link to post Share on other sites
Recommended Posts
Dołącz do dyskusji
Możesz dodać zawartość już teraz a zarejestrować się później. Jeśli posiadasz już konto, zaloguj się aby dodać zawartość za jego pomocą.