Bluescreen 0x0000007A

[kujawiak11]

Witam mój komputer wyłącza się po jakimś czasie sam i pojawia się niebieski ekran z napisami, znalazłem w necie ten sam problem po angielsku ale nadal nic nie rozumiem o co chodzi podaje link Dostępne tylko dla zarejestrowanych użytkowników
Proszę o pomoc.

[me@djohnsc]

Ten niebieski ekran z napisami to Bluescreen BSOD ;]

Czyli jak rozumiem kod błędu był 0x000000D1? Jak tak to tutaj znajdziesz informacje jak usunąć problem => Błędy systemu Windows (kody BSOD)

A najlepiej odczytaj plik DMP i podaj na forum -> Bluescreen (BSOD) - szukanie przyczyny powstawania. Czytanie plików DMP

[kujawiak11]

no więc z problemami ale się udało:)


Dostępne tylko dla zarejestrowanych użytkowników

-- Dzisiaj, 22:15 --

Prosze powiedzcie mi co teraz mam zrobić.

[me@djohnsc]

Kod 0x0000007A informacje jak usunąć błąd znajdziesz w Błędy systemu Windows (kody BSOD) link podałem w poprzednim poście

Podaj odczyt danych SMART dysku z programu HD Tune, zakładka Health => instrukcja odczytu SMART.

Sprawdź pamięć programem Dostępne tylko dla zarejestrowanych użytkowników.
Memtesta ściągasz, wypakowujesz jeżeli potrzeba, aby nagrać plik ISO. Nagrywasz go na płytę, w Nero opcja Dostępne tylko dla zarejestrowanych użytkowników. Potem uruchamiasz na nowo komputer bootując go z płyty (w biosie ustaw: okno Advanced Bios Features->First Boot Device ustaw na CD/DVD).

[kujawiak11]

SMART wczoraj sprawdzałem i wszystko jest ok tak mi tu na forum ktoś powiedział
A z tym mamtest to jest dużo do rozpakowania wszystko mam nagrać czy jak ?

[cosik_ktosik]

Jak ściągniesz to otrzymasz plik ISO, jego nagrywasz z opcją Nagraj obraz na dysk, jak podał me@djohnsc. Jeśli nie będzie odrazu po ściągnięciu ISO, to wypakuj tak, aby mieć właśnie plik ISO. ISO to właśnie obraz dysku.

[kujawiak11]

SMART i Memtest ok jest na koniec memtesta pisało że 0 błędów i że jest ok

-- Dzisiaj, 21:49 --

Co dalej zrobić??

[cosik_ktosik]

Hmm, dziwne. W menu start->uruchom->wpisz->cmd
Wpisz:
chkdsk /F /R
i pozwól, aby system sprawdził dysk przy następnym uruchomieniu systemu.

[kujawiak11]

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini080609-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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x8180d000 PsLoadedModuleList = 0x81924c70
Debug session time: Thu Aug 6 20:46:09.231 2009 (GMT+2)
System Uptime: 0 days 0:16:27.893
*********************************************************************
* 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {c04136c8, c000000e, ce22860, 826d97ed}

*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*********************************************************************
* 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+ *
*********************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntkrnlpa.exe ( nt+899dc )

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

-- Dzisiaj, 20:38 --

Sprawdził dyski i nadal się to wszystko dzieje, ale teraz już chyba pozostaje tylko wymiana sterowników do płyty głównej itd tak ?