Vista trochę długo się zamyka - logi

przez **kominekl** » 23 Paź 2011, 11:42

OK. W takim razie czekamy. Tylko pamiętaj o odznaczeniu opcji

Quick Scan.

przez **marcos_777** » 23 Paź 2011, 12:28

[strona nie jest już dostępna]

[strona nie jest już dostępna]

[strona nie jest już dostępna]

przez **marcos_777** » 25 Paź 2011, 00:05

Oto Gmer.log:
http://www.wklej.eu/index.php?id=a503813cc7

Ale wydaje mi się, że już jest z lapciem wszystko Ok. Może jakaś kosmetyka w skrypcie OTL?
Zaraz podam świeżego OTL.
Tymczasem CCleaner i
Advanced SystemCare log:http://www.wklej.eu/index.php?id=cc7c9064a8

Drive has been repaired
Drive C will been repair on next startup

Po aktualizacji i restarcie włączył się Chkdsk i poprzetwarzał jakieś wpisy.

OTL.txt:
http://www.wklej.eu/index.php?id=389135590e

OTL.Extras:
http://www.wklej.eu/index.php?id=d5d5937a68

przez **mateo8898** » 25 Paź 2011, 16:13

Więcej nic tu do usuwania nie ma.

W OTL kliknij Sprzątanie

przez **marcos_777** » 25 Paź 2011, 19:45

Ok, ale jeszcze jedna sprawa.
Bo akurat dzisiaj jak wróciłem z pracy laptop przywitał mnie Blue Screenem 0x000000F4.
Udało mi się zapisać szczegóły i skopiowałem te "pliki pozwalające opisać problem" w inne miejsce, bo mi znikały wcześniej.

Podpis problemu:
Nazwa zdarzenia problemu: BlueScreen
Wersja systemu operacyjnego: 6.0.6002.2.2.0.768.2
Identyfikator ustawień regionalnych: 1045

Dodatkowe informacje o problemie:
BCCode: f4
BCP1: 00000003
BCP2: 87ECD758
BCP3: 87ECD8A4
BCP4: 8422FAB0
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Pliki pomagające opisać problem:
C:\Windows\Minidump\Mini102511-01.dmp
C:\Users\user\AppData\Local\temp\WER-273329-0.sysdata.xml
C:\Users\user\AppData\Local\temp\WERF305.tmp.version.txt

Przy okazji zajrzałem w zakładkę Problemy z wydajnością i były tam 3, które rozwinąłem i zrobiłem screena.
[strona nie jest już dostępna]

[strona nie jest już dostępna]

Odkurzacza nie używam już od dawna.

przez **kominekl** » 25 Paź 2011, 19:47

Podaj odczyt pliku minidump z tego zdarzenia

debugging-tools-for-windows-t15501.html

przez **marcos_777** » 25 Paź 2011, 20:23

Proszę, poniżej odczyt Minidump.
Ale pobieranie z tamtego linka to porażka, ładuje się jakiś Microsoft Windows SDK for Windows 7 and .NET Framework 4 i trwa i trwa...
lepiej tu zassać: http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.402.msi

Kod: Zaznacz wszystko: Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\user\Desktop\BlueScreen_Martita\Mini102511-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 6002 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0x84009000 PsLoadedModuleList = 0x84120c70 Debug session time: Tue Oct 25 13:53:50.386 2011 (GMT+2) System Uptime: 0 days 0:00:41.964 ********************************************************************* * 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 F4, {3, 87ecd758, 87ecd8a4, 8422fab0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. unable to get nt!KiCurrentEtwBufferOffset unable to get nt!KiCurrentEtwBufferBase ************************************************************************* *** *** *** *** *** 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 : wininit.exe Followup: MachineOwner --------- kd> .restart /f Loading Dump File [C:\Users\user\Desktop\BlueScreen_Martita\Mini102511-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 6002 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0x84009000 PsLoadedModuleList = 0x84120c70 Debug session time: Tue Oct 25 13:53:50.386 2011 (GMT+2) System Uptime: 0 days 0:00:41.964 ********************************************************************* * 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 F4, {3, 87ecd758, 87ecd8a4, 8422fab0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. unable to get nt!KiCurrentEtwBufferOffset unable to get nt!KiCurrentEtwBufferBase ************************************************************************* *** *** *** *** *** 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 : wininit.exe Followup: MachineOwner ---------

przez **kominekl** » 25 Paź 2011, 20:28

Spróbuj na początek przetestować pamięć RAM bootowalnym programem MemTest86+

http://www.instalki.pl/programy/downloa ... est86.html. Test minimum 6 godzin dla każdej z posiadanej kości.

przez **marcos_777** » 25 Paź 2011, 20:37

Z tym MemTestem będzie teraz problem, ponieważ córka używa lapcia do pracy w domu. Może kiedy indziej. Spróbujemy coś innego?

Aha, jeszcze szczegóły z WinDebuggera:

Kod: Zaznacz wszystko: ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: wininit FAULTING_MODULE: 00000000 DEBUG_FLR_IMAGE_TIMESTAMP: 0 PROCESS_OBJECT: 87ecd758 IMAGE_NAME: wininit.exe CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xF4 CURRENT_IRQL: 0 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 8c7cdccc 8429bc40 000000f4 00000003 87ecd758 nt+0xcdb3f 8c7cdcf0 841fa35d 8422fab0 87ecd8a4 87ecd7d8 nt+0x292c40 8c7cdd20 841fa304 87ecd758 87f72bb0 00000005 nt+0x1f135d 8c7cdd54 84053c7a 00000000 00000005 0021fe90 nt+0x1f1304 8c7cdd64 77d95ca4 badb0d00 0021fe7c 00000000 nt+0x4ac7a 8c7cdd68 badb0d00 0021fe7c 00000000 00000000 0x77d95ca4 8c7cdd6c 0021fe7c 00000000 00000000 00000000 0xbadb0d00 8c7cdd70 00000000 00000000 00000000 00000000 0x21fe7c STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- kd> lmvm wininit start end module name kd> !process ffffffff87ecd758 3 GetPointerFromAddress: unable to read from 8414086c NT symbols are incorrect, please fix symbols

przez **kominekl** » 25 Paź 2011, 20:47

Jednak najprawdopodobniej winna jest pamięć RAM.

przez **marcos_777** » 13 Gru 2011, 22:25

Więcej się to już nie powtórzyło, tzn. samoistnie nie wystąpiło.
Bo odkryłem powód tych BS - przy okazji odłączenia dysku zewnętrznego WD bez uprzedniego Wyłącz bezpiecznie,
bo po prostu nie dało się go zrobić, bo system nie pozwalał, że niby dysk zajęty.
I wtedy dzieci przyznały się, że miały wcześniej tak samo.
Tak więc temat do zamknięcia.
Dzięki za pomoc. :564:

Vista trochę długo się zamyka - logi

Re: Vista trochę długo się zamyka - logi

Re: Vista trochę długo się zamyka - logi

Re: Vista trochę długo się zamyka - logi

Re: Vista trochę długo się zamyka - logi

Re: Vista trochę długo się zamyka - logi

Re: Vista trochę długo się zamyka - logi

Re: Vista trochę długo się zamyka - logi

Re: Vista trochę długo się zamyka - logi

Re: Vista trochę długo się zamyka - logi

Re: Vista trochę długo się zamyka - logi

Re: Vista trochę długo się zamyka - logi

Kto jest na forum