Po przywróceniu systemu z partycji recovery mam ciągłe blue screeny.

[virnik]

Cześć
Tak jak w temacie.
Przywróciłem system Vista na moim laptopie z partycji recovery.
Wszystko było ok, zaczęły się robić aktualizacje systemu. Po jakiś 10,15 minutach pojawił się pierwszy blue screen - reference by poitner.
Dałem mu odpocząć bo był nagrzany. Teraz zawsze po jakimś czasie jak włączę go pojawia się kolejny blue screen tylko ,że teraz po chwili sam znika. Jest odliczanie czego wcześniej nie było.
Dlaczego tak się stało i jak temu zaradzić ?
Pozdro !

[color="#ff0000"]//przenoszę do subforum BSOD
//raaz[/color]

[raazor90]

Wykonaj: http://www.forumpc.pl/index.php?showtopic=153598 + http://www.forumpc.pl/index.php?showtopic=16074

[virnik]

Zrobiłem wszystko co pisało w podanych linkach.
[code]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904ab, 8a743b4c, 8a743848, 877508d4}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
[/code]
Tylko mam problem z tymi znakami, wpisuje to SRV*c:\symbols*http://msdl.microsoft.com/download/symbols ale link chyba nie aktywny...

[raazor90]

Pokaż cały wygenerowany log

[virnik]

[code]
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini082210-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d12e10
Debug session time: Sun Aug 22 16:42:08.980 2010 (GMT+2)
System Uptime: 0 days 0:13:09.801
*********************************************************************
* 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 2
*** 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
...
Unable to load image \SystemRoot\System32\Drivers\Ntfs.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904ab, 8a743b4c, 8a743848, 877508d4}

***** 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 ***
*** ***
*************************************************************************
Probably caused by : Ntfs.sys ( Ntfs+588d4 )

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

[/code]

pierwszy bsod jaki sie pojawił:
[code]

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


Loading Dump File [C:\Windows\Minidump\Mini082110-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 2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Sat Aug 21 18:28:35.618 2010 (GMT+2)
System Uptime: 0 days 0:09:25.369
*********************************************************************
* 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 2
*** 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 18, {8367f630, 84d917f8, 2, ffffffff}

***** 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 ***
*** ***
*************************************************************************

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

[/code]

[raazor90]

[quote]Probably caused by : Ntfs.sys ( Ntfs+588d4 )
[/quote]
[quote][b]Ntfs.sys[/b] plik sterownika pozwalający na zapis i odczyt danych na dysku, naprawa za pomocą płyty instalacyjnej Windows/ należy też sprawdzić status SMART dysku[/quote]

Źródło:
http://www.forumpc.pl/index.php?showtopic=163186

[virnik]

A da się to jakoś naprawić bez tej płytki? Nie dostałem jej do laptopa jest tylko ta partycja recovery :/
Może być CD od XP'ka ?
I jak sprawdzić ten status SMART dysku ?
Dzięki za wszystko

[raazor90]

Odczytywanie statusu SMART: http://www.forumpc.pl/index.php?showtopic=157249