Wyłącza się komp, resetuje i nie chce się uruchomić

[mateo8898]

Dokładny problem to taki, uruchamiam kompa zresetuje się ale czasami mi się już nie uruchamia. Chodzi słychać, ale nie ładuje system. Wciskam reset ale nie zawsze się zaczyna ładować czasem wyłączę na przełączniku i chce go włączyć i nic niby się uruchomi ale systemu nie ładuje nie ma nawet tego dźwięku (pik coś tam coś tam). Dzieje się to coraz częściej, moje pytanie jest takie, czy idzie to sprawdzić jakimś programem co powie co mu dolega albo wy powiedzie
Aha i czasem taki komunikat: driver irql not less or equal.

[mateo8898]

W którym dokładnie momencie komputer się resetuje???

aha i czasem taki komunikat driver irql not less or equal.

Odczytaj plik .dmp viewtopic.php?f=36&t=15501#p83353

[tygrs55]

jestem w trakcie instalacji programu
Komputer resetuje się różnie podczas oglądania filmu słuchania muzyki przeglądani internetu podczas ładowania systemu a czasem jak ino go włączę zresetuje sie
aha dodam może ważną rzecz oglądam coś lub robię i mam taki komunikat:
pojawienie się problemu i system windows zostanie zamknięty aby zapobiec uszkodzeniu komputera.
jeśli widzisz po raz pierwszy widzisz ekran błędu Stop ponownie uruchom komputer jeżeli ekran pojawił sie ponownie wykonaj następujące kroki
upewnij sie że na dysku jest wystarczająco dużo miejsca jeżeli sterownik jest zindentyfikowany w komunikacie stop. wyłącz go lub skontaktuj sie z producentem
w sprawie aktualizacji sterownika. spróbuj zmienić karty wideo.
skontaktuj sie z dostawcą sprzętu w sprawie aktualizacji systemu BIOS wyłącz opcję pamięci systemu BIOS takie jak buforowanie przesyłanie
jeżeli do usunięcia lub wyłączenia składników użyć trybu awaryjnego ponownie uruchom komputer i naciśnij f8 aby wyświetlić zaawansowane opcję startowe a następnie wybierz tryb awaryjny
informacje techniczne ***Stop:0x0000008E (0x0000005, 0x805677bb, 0xBa240C7C, 0x00000000)
rozpoczęcie zrzucania fizycznej pamięci zrzut pamięci fyzycznej został zakończony
w sprawie dalszej pomocy skontaktuj sie z administratorem systemu lub obsługą techniczną

to jest ten komunikat i mam pytanko ten program co mam pobrać to jest to http://www.microsoft.com/whdc/devtools/ ... llx86.mspx

[mateo8898]

to jest ten komunikat i mam pytanko ten program co mam pobrać to jest to http://www.microsoft.com/whdc/devtools/ ... llx86.mspx

Tak. Jeśli odczytasz ten plik .dmp to wrzuć tu jego zawartość.

[tygrs55]

mam problem nie mam pliku minidump
http://img205.imageshack.us/img205/9374/komuter.jpg
jednie wyszukiwarka na kompie znajduje c program files microsoft DKs windows 7.1 lib taka lokalizacja nic wicej

[mateo8898]

Prawoklik na Mój komputer Właściwości zakładka Zaawansowane w sekcji "Uruchamianie i odzyskiwanie" wejdź w Ustawienia Sprawdź, czy masz odznaczoną opcję "Automatycznie uruchom ponownie" oraz w sekcji "Zapisywanie informacji o debugowaniu" ustawiony Mały zrzut pamięci oraz katalog małego zrzutu %SystemRoot%\Minidump. Jeśli nie to tak właśnie ustaw.

Wrzuć także napięcia i temperatury np. z Everesta http://www.instalki.pl/programy/downloa ... ition.html

[tygrs55]

tak ma być to ustawione? jeśli tak dalej nie idzie
http://img149.imageshack.us/img149/301/147ou.jpg
everest
http://img36.imageshack.us/img36/2325/147147.jpg

[mateo8898]

Tak właśnie ma być ustawione. Było tak wcześniej, czy teraz dopiero ustawiłeś??

[tygrs55]

ustawiłem teraz było inaczej całkiem
uruchomić kompa czy ponowić instalacje ?

[mateo8898]

Teraz musisz czekać na niebieski ekran z błędem, czyli BSOD, jeśli się pojawi to sprawdź, czy utworzył się plik .dmp, powinien być w folderze C:\Windows\Minidump

[tygrs55]

ok a on sie sam zrobi niebieski ekran czyli to co ja powyżej wcześniej opisywałem tak?

[mateo8898]

Tak, musisz czekać aż się pojawi.

[tygrs55]

ok jak sie pojawi odczytam dam znać dzieki

[tygrs55]

oto plik
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini101010-01.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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sun Oct 10 09:37:09.015 2010 (UTC + 2:00)
System Uptime: 0 days 0:02:20.580
*********************************************************************
* 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 Npfs.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Npfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for Npfs.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {a33f1b40, 0, 8054bbad, 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 ***
*** ***
*************************************************************************
Probably caused by : Npfs.SYS ( Npfs+5f86 )

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

[tygrs55]

2 raz miałem niebieski ekran i ponownym uruchomieniu tabelke
http://yfrog.com/f/n39999999999999999999j/

i następny raport moje pytanie jest takie czy dawać za każdym razem raport czy te wystarcza ?
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, 82fd2bb8, 82fd33a0, afd0007}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** 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 ***
*** ***
*************************************************************************
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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+5c846 )

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