Bluescreen na win7 64bit, problemy z uruchomieniem komputera

**Posty:** 18 · przez **MikeMitnick** 23 Paź 2012, 22:40

po włączeniu komputera wyskoczył mi bluescreen, pokazało się jakieś odliczanie i komp się zresetował. Ostatnimi czasy miałem problemy z uruchomieniem kompa, włączała się konsola odzyskiwania, jakieś fatal errory, że komp został niewłaściwie zamknięty itd. Taki komunikat wyskoczył mi wczoraj po bluescreenie:

Kod: Zaznacz wszystko: Podpis problemu: Nazwa zdarzenia problemu: BlueScreen Wersja systemu operacyjnego: 6.1.7601.2.1.0.256.48 Identyfikator ustawień regionalnych: 1045 Dodatkowe informacje o problemie: BCCode: 1 BCP1: 000000007711138A BCP2: 0000000000000000 BCP3: 000000000000FFFF BCP4: FFFFF88007896CA0 OS Version: 6_1_7601 Service Pack: 1_0 Product: 256_1 Pliki pomagające opisać problem: C:\Windows\Minidump\102212-33041-01.dmp C:\Users\Michal\AppData\Local\Temp\WER-57002-0.sysdata.xml Przeczytaj w trybie online nasze zasady zachowania poufności informacji: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0415 Jeśli zasady zachowania poufności informacji w trybie online nie są dostępne, przeczytaj nasze zasady zachowania poufności informacji w trybie offline: C:\Windows\system32\pl-PL\erofflps.txt

oto logi z otl (win7 64bit). Podejrzewam padający twardy dysk lub jakiegoś robaka.

**Posty:** 18165 · przez **wojtas** 24 Paź 2012, 16:53

do odinstalowania:
"V9Software" = V9 Homepage Uninstaller

Uruchom OTL i w sekcji własne opcje skanowania / skrypt wklej:

:OTL
IE - HKLM\SOFTWARE\Microsoft\Internet Explorer\Main,Default_Page_URL = http://www.v9.com/?utm_source=b&utm_medium=prs&from=prs&uid=6QF1T9MW_ST3320620AS&ts=1341064412
IE - HKLM\SOFTWARE\Microsoft\Internet Explorer\Main,Start Page = http://startsear.ch/?aff=2&cf=e2a6cde1-1d47-11e2-b065-001f95b9a790
IE - HKLM\..\SearchScopes\{33BB0A4E-99AF-4226-BDF6-49120163DE86}: "URL" = http://startsear.ch/?aff=2&src=sp&cf=e2a6cde1-1d47-11e2-b065-001f95b9a790&q={searchTerms}
IE - HKU\S-1-5-21-3580497392-591079193-3815773299-1000\..\SearchScopes\{33BB0A4E-99AF-4226-BDF6-49120163DE86}: "URL" = http://startsear.ch/?aff=2&src=sp&cf=e2a6cde1-1d47-11e2-b065-001f95b9a790&q={searchTerms}
IE - HKU\S-1-5-21-3580497392-591079193-3815773299-1000\..\SearchScopes\{93FBAD8F-181A-411D-BC05-8B5C5B4B4AD5}: "URL" = http://search.v9.com/web/?q={searchTerms}
IE - HKU\S-1-5-21-3580497392-591079193-3815773299-1000\SOFTWARE\Microsoft\Internet Explorer\Main,Default_Page_URL = http://www.v9.com/?utm_source=b&utm_medium=prs&from=prs&uid=6QF1T9MW_ST3320620AS&ts=1341064412
IE - HKU\S-1-5-21-3580497392-591079193-3815773299-1000\SOFTWARE\Microsoft\Internet Explorer\Main,Start Page = http://startsear.ch/?aff=2&cf=e2a6cde1-1d47-11e2-b065-001f95b9a790
[2012-10-23 21:29:52 | 000,000,792 | ---- | M] () -- C:\Users\Michal\AppData\Roaming\mozilla\firefox\profiles\0f3x9iqs.default\searchplugins\startsear.xml
O4 - HKU\S-1-5-19..\RunOnce: [mctadmin] C:\Windows\System32\mctadmin.exe File not found
O4 - HKU\S-1-5-20..\RunOnce: [mctadmin] C:\Windows\System32\mctadmin.exe File not found
O6 - HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer: NoActiveDesktop = 1
O6 - HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer: NoActiveDesktopChanges = 1

:Commands
[emptytemp]

Kliknij wykonaj skrypt. I potwierdź reset komputera .

Użyj AdwCleaner i kliknij w nim Delete (w przypadku Visty/Windows7 uruchom z prawokliku jako Administrator)
Pokaż raport z niego

pobierz:
http://www.microsoft.com/en-us/download/confirmation.aspx?id=8279
ustaw tak :

i zainstaluj Debugging Tools

Start - programy - Debugging Tools for Windows - WinDbg

File Open Crash Dump

Pojawia sie okienko, w którym wskazujesz plik *.dmp
Znajduje sie w windows\minidump\ (najnowszy)

Na pytanie: Save information for workspace odpowiadasz no , następnie wklej zawartość na forum treść z programu

Następnie uruchamiasz OTL z opcją skanuj. Pokazujesz nowy log OTL.txt oraz raport z czyszczenia (zawartość notatnika, która otworzyła się po restarcie).

**Posty:** 18 · przez **MikeMitnick** 24 Paź 2012, 19:42

Kod: Zaznacz wszystko: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Michal\Desktop\Nowy folder\102212-33041-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\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 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333 Machine Name: Kernel base = 0xfffff800`02815000 PsLoadedModuleList = 0xfffff800`02a59670 Debug session time: Mon Oct 22 21:55:35.824 2012 (UTC + 2:00) System Uptime: 0 days 0:01:12.354 ********************************************************************* * 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\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 .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1, {7711138a, 0, ffff, fffff88007896ca0} ***** 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!_KTHREAD *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* Probably caused by : ntoskrnl.exe ( nt+7efc0 ) Followup: MachineOwner ---------

co może być przyczyną takiego stanu rzeczy?

Dodano Dzisiaj, 19:48:
jeszcze skan z otl

**Posty:** 18165 · przez **wojtas** 24 Paź 2012, 19:56

najprawdopodobniej to będzie problem ze sprzetęm ( błędy dysku ) lub może też uszkodzony Windows

**Posty:** 18 · przez **MikeMitnick** 24 Paź 2012, 20:08

obstawiam właśnie padający hdd, chociaż robiłem skany hddtune (czy jakoś tak) i bad sektorów nie pokazuje... Winda świeżo po reinstalce i formacie

**Posty:** 18165 · przez **wojtas** 24 Paź 2012, 20:14

no to raczej coś ze sprzętem, ewentualnie sterowniki ( mniejsze prawdopodobieństwo)