Restartowanie się komputera.
Witam!
Od pewnego czasu podczas działanie gier lub niektórych programów komputer po prostu się restartuje.
W komputerze mam:
- Płyta główna: ASRock P4S61
- Karta graficzna: nVidia WinFast Leadtek GeForce 7600 GT
- Procesor: Intel Celeron D 3,06 GHz
- 2GB RAM (2x 1GB Kingston)
- Zasilacz: BeQuiet! Straight Power BQT E5-450W
- Windows XP Home Edition SP2
A oto kod błędu przy restarcie:
[code]Pojawił się problem i system Windows został zamknięty, aby zapobiec uszkodzeniu komputera.
Podjęto próbę zapisu do pamięci tylko do odczytu.
Jeżeli po raz pierwszy widzisz ekran błędu STOP, ponownie uruchom komputer. Jeżeli ten ekran pojawi się ponownie wykonaj następujące kroki:
Upewnij się, czy wszelki sprzęt i oprogramowanie są poprawnie zainstalowane.
Jeżeli jest to nowa instalacja, poproś producenta sprzętu lub oprogramowania o wszelkie aktualizacje dla systemu Windows, które mogą być potrzebne.
Jeżeli problemy będą się powtarzały, wyłącz lub usuń wszelki nowo zainstalowany sprzęt i oprogramowanie, wyłącz opcje pamięci systemu BIOS, takie jak buforowanie i przesłanianie.
Jeżeli do usunięcia lub wyłączenia składników musisz użyć trybu awaryjnego, ponownie uruchom komputer, naciśnij klawisz F8, aby wyświetlić zaawansowane opcje startowe, a następnie wybierz opcję Tryb awaryjny.
Informacje techniczne:
*** STOP: 0x000000BE (0x00490056, 0x4FB69025, 0x0000000A)
Rozpoczynanie zrzucania fizycznej pamięci.
Zrzut pamięci fizycznej został zakończony.
w sprawie dalszej pomocy skontaktuj się z administratorem systemu lub obsługi tech[/code]
Bardzo prosiłbym o rady jak rozwiązać ten problem.
Pozdrawiam
Odpowiedzi: 9
Może i mi się uda pomóc w jakiś sposób.
Kiedyś też miałem podobny problem. Komp się restartował w w momencie kiedy używałem programu Alcohol 120%.
Wiem że to trochę śmiesznie brzmi ale poważnie. Miałem jakąś jego starszą wersje, ale kiedy zmieniłem na nieco nowszą restarty się skończyły...
Może więc jest to przyczyna jakiegoś programu, lub czegoś w tym stylu?
Niestety ta pamięć działa tylko z taktowanie 200 i 166... Tzn, że kości są do wymiany, czy można coś z tym zrobić?
Oj może, może - o ile w tym trybie jest do pracy ustawiona.
Jednak rozważył bym co innego - tylko najpiew sprawdź przez CPU-Z ( w zakłądce SPD ) czy rzeczywiście ta pamięć nie chce gadać o szynie 133.
TWój celeron na tkaiej chyba chodzi ( 4x133=533 ) i to moze być kłopot. Teoretycznie pamieći powinny działać z każdym niższym taktowaniem, ale w praktyce nei musi to i nie zawsze bywa prawda.
Gdyby okazłąo się, że jest tak, iz ustawienia dla 133 nie wystepują to to , a nie sama nominalne prędkość pamieci, pewnei bym za przyczynę brał ( pomijam sprawy z zasilaniem itp. związane , bo o nich nic nie wiadomo ).
Dzisiaj zamiast dotychczasowego problemu pojawił się inny. Mianowicie komputer restartuje się, jednak nie pokazuje się żaden niebieski ekran, ani komunikat o błędzie. Bezpośrednio po restarcie komputer po prostu 'zasypia' - ekran jest czarny z migającym "tryb oszczędny" (tak jak się włącza zamiast wygaszacza ekranu), lampka na monitorze jest pomarańczowa, a sam komputer na nic nie reaguje. Można go wyłączyć jedynie guzikiem.
Jak przeczytałem w internecie: cmuda.sys (odpowiedzialny za kilka błędów) jest powiązany z dźwiękiem, a że mam jakieś g**** zintegrowane (dokładnie C-Media CMI 9739A/9761 AC'97) to może jest to wina tego czegoś?
Z drugiej jednak strony ntfs.sys ponoć ma jakiś związek z pamięcią. I tu mam pewien problem. W instrukcji od płyty głównej mam napisane:
[code]Memory: 3 DDR DIMM slots: DDR1, DDR2, and DDR3
PC2100 (DDR266) for 3 DDR DIMM slots, Max. 3GB;
PC2700 (DDR333) for 2 DDR DIMM slots, Max. 2GB;
PC3200 (DDR400) for 1 DDR DIMM slots, Max. 1GB[/code]
A moja pamięć (sprawdzana w Evereście) ma coś takiego
[code]
DIMM1: Kingston K 1 GB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz) (2.5-3-3-7 @ 166 MHz)
DIMM3: Kingston K 1 GB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz) (2.5-3-3-7 @ 166 MHz)[/code]
Moje pytanie: Skoro w instrukcji mam, że może być najwięcej 1GB pamięci PC3200, a ja mam włożone dwie, to może to być problemem tych restartów, czy w ogóle jest to bez znaczenia.
Hmm, memtest to raczej dosyć dobry soft do testowania pamięci... Puściłeś go tak co najmniej na 2 godziny? Spróbuj jeszcze użyć najnowszej wersji, którą znajdziesz tutaj http://www.memtest86.com/. Kontrolnie otwórz kompa i zobacz czy kondensatory na płycie nie napuchnęły. Wejdź również na stronę producenta Twojego dysku twardego i ściągnij jakieś oprogramowanie testujące, może akurat... Z ciekawością będę dalej śledził ten temat, zobaczymy co Zółty jeszcze wymyśli w Twojej sprawie. Dodam jeszcze, że sam też mam pł. gł. Asrock (chociaż inny model) i czasami bywają z nią (tak mi się wydaje) problemy. Ale można gdybać, jak coś jest sprawne to i tak powinno dobrze działać.
Pamięć sprawdzałem Memtestem z dyskietki - wszystko sprawne.
Zawsze podczas występowania błędu jest mowa o zrzucie pamięci fizycznej i zapisywaniu do pamięci tylko do odczytu, mimo różnych błędów, więc może w tym jest coś źle, tylko nie wiem co może być z tym źle.
Pozdrawiam
Pamięci sprawdź czy sa sprawne - bo masz tak dużą różnorodnodność błędów, że może to wskazywać na uszkodzenie sprzętu a nie na problem z systemem.
Jest tego kilka, ponieważ za drugim razem był inny błąd, a za trzcim jeszcze inny... Tylko nie wiem czy wszystko dobrze zrobiłem, bo to trochę długie jest.
[code]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, cd4, 0, 892d47b8}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for dxg.sys
*** ERROR: Module load completed but symbols could not be loaded for dxg.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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : dxg.sys ( dxg+9389 )
Followup: MachineOwner
---------
[/code]
[code]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, 8918e7b0, 8918f7a8, ffff0000}
***** 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 cmuda.sys
*** ERROR: Module load completed but symbols could not be loaded for cmuda.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 : cmuda.sys ( cmuda+58c1b )
Followup: MachineOwner
---------
[/code]
[code]
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {8a000000, 0, f7b73667, 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 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 : Ntfs.sys ( Ntfs+21667 )
Followup: MachineOwner
---------
[/code]
Pozdrawiam
co mówi Debugging Tools for Windows?
Strona 1 / 1
[quote=Kuerone]Może i mi się uda pomóc w jakiś sposób. Kiedyś też miałem podobny problem. Komp się restartował w w momencie kiedy używałem programu Alcohol 120%. Wiem że to trochę śmiesznie brzmi ale poważnie. Miałem jakąś jego starszą wersje, ale kiedy zmieniłem na nieco nowszą restarty się skończyły... Może więc jest to przyczyna jakiegoś programu, lub czegoś w tym stylu? [/quote] To ja jeszcze dorzucę słowo od siebie: ja miałem w/w objawy w przypadku MKS_Vir'a.