Blue screen za każdym włączeniem komputera


(Blaix96) #1

Witam.

Odkąd zainstalowałam Windows 7 wersję 64-bitową Home Premium na moim laptopie firmy Toshiba za każdym razem, jak zamykam system i potem go włączam normalnie wyświetla mi się logo Windows “Trwa uruchamianie systemu”, a potem “nie udało się przywrócić systemu” i trzeba przywracać system. Ostatnio tak mi się zrobiło, bo zachciało mi się instalować jakieś sterowniki i widziałam w szczegółach, że był to błąd sterownika. Teraz nie wiem czemu tak się dzieje. Żadnych nowych programów nie instalowałam ani steroników. Wcześniej też myślę, że to był błąd aktualizacji Windowsa, które potem wyłączyłam. Myślałam, że to rozwiąże problem, ale tak się nie stało. Proszę o pomoc. System jest jak najbardziej oryginalny.

PS Błąd jaki mi wyskakiwał na blue screenie to 0x00… i tutaj były same zera


(adam9870) #2

Poproszę o zrzuty pamięci z C:\windows\minidump

Dwie metody do wyboru w celu odczytu

Pierwsza metoda: WinDbg (zapoznaj się z wiadomością napisaną przez przez Robinhio » 04 grudnia 2006 20:56:00)

Druga metoda: BlueScreenView (zapoznaj się z wiadomością napisaną przez przez deFco247 » 21 stycznia 2010 16:55:07)

Jeżeli w c:\windows\minidump będzie pusto to zobacz komputer-sie-wylacza-t498828.html#p3137602


(Blaix96) #3

Problem w tym, że nie posiadam nawet folderu minidump, a opcje mam zaznaczoną poprawnie w Systemie.


(adam9870) #4

bsody-pusty-folder-minidump-t489452.html


(Blaix96) #5

Dobra, dopiero teraz pojaiwł się blue screen i zapisało się wszystko w folderze. Daję zrzut poniżej:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C]

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 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 7 Kernel Version 7600 MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0xfffff800`02817000 PsLoadedModuleList = 0xfffff800`02a54e50

Debug session time: Wed Jan 2 19:49:21.525 2013 (GMT+1)

System Uptime: 0 days 0:00:34.538

*********************************************************************

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

....

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck F4, {3, fffffa80015b15b0, fffffa80015b1890, fffff80002b91240}


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

******

*************************************************************************

*********************************************************************

* 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 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Probably caused by : wininit.exe


Followup: MachineOwner


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: 0000000000000000 


DEBUG_FLR_IMAGE_TIMESTAMP: 0


PROCESS_OBJECT: fffffa80015b15b0


IMAGE_NAME: wininit.exe


CUSTOMER_CRASH_COUNT: 1


DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT


BUGCHECK_STR: 0xF4


CURRENT_IRQL: 0


STACK_TEXT:  

fffff880`051cdb08 fffff800`02c14142 : 00000000`000000f4 00000000`00000003 fffffa80`015b15b0 fffffa80`015b1890 : nt+0x71f00

fffff880`051cdb10 00000000`000000f4 : 00000000`00000003 fffffa80`015b15b0 fffffa80`015b1890 fffff800`02b91240 : nt+0x3fd142

fffff880`051cdb18 00000000`00000003 : fffffa80`015b15b0 fffffa80`015b1890 fffff800`02b91240 fffff800`02ba1c06 : 0xf4

fffff880`051cdb20 fffffa80`015b15b0 : fffffa80`015b1890 fffff800`02b91240 fffff800`02ba1c06 fffffa80`015b15b0 : 0x3

fffff880`051cdb28 fffffa80`015b1890 : fffff800`02b91240 fffff800`02ba1c06 fffffa80`015b15b0 fffff800`02bc0269 : 0xfffffa80`015b15b0

fffff880`051cdb30 fffff800`02b91240 : fffff800`02ba1c06 fffffa80`015b15b0 fffff800`02bc0269 00000000`00000001 : 0xfffffa80`015b1890

fffff880`051cdb38 fffff800`02ba1c06 : fffffa80`015b15b0 fffff800`02bc0269 00000000`00000001 fffffa80`0340f060 : nt+0x37a240

fffff880`051cdb40 fffffa80`015b15b0 : fffff800`02bc0269 00000000`00000001 fffffa80`0340f060 fffffa80`015b15b0 : nt+0x38ac06

fffff880`051cdb48 fffff800`02bc0269 : 00000000`00000001 fffffa80`0340f060 fffffa80`015b15b0 fffffa80`82ac8000 : 0xfffffa80`015b15b0

fffff880`051cdb50 00000000`00000001 : fffffa80`0340f060 fffffa80`015b15b0 fffffa80`82ac8000 00000000`00000000 : nt+0x3a9269

fffff880`051cdb58 fffffa80`0340f060 : fffffa80`015b15b0 fffffa80`82ac8000 00000000`00000000 00000000`00000000 : 0x1

fffff880`051cdb60 fffffa80`015b15b0 : fffffa80`82ac8000 00000000`00000000 00000000`00000000 fffffa80`015b15b0 : 0xfffffa80`0340f060

fffff880`051cdb68 fffffa80`82ac8000 : 00000000`00000000 00000000`00000000 fffffa80`015b15b0 00000000`0000000e : 0xfffffa80`015b15b0

fffff880`051cdb70 00000000`00000000 : 00000000`00000000 fffffa80`015b15b0 00000000`0000000e fffffa80`0340f060 : 0xfffffa80`82ac8000



STACK_COMMAND: kb


FOLLOWUP_NAME: MachineOwner


BUCKET_ID: WRONG_SYMBOLS


Followup: MachineOwner

---------


0: kd> lmvm wininit

start end module name

(adam9870) #6

Użyj Driver Verifiera dla wininit.exe i ntoskrnl.exe

Narzędzie uruchomisz poprzez:

Start - Wszystkie programy - akcesoria - uruchom - c:\windows\system32\verifier.exe

Instrukcja użycia na YouTube.

Uprzedzam, że po użyciu Driver Verifiera system może pokazywać bluescreeny w trakcie uruchamiania. Tak ma być. Na podstawie danych, które wtedy powstaną będzie można dojść do przyczyny problemu (przykład z forum bsod-jakis-czas-moze-byc-przyczyna-t513558.html). Podaję metodę jak naprawić problem bluescreenów po użyciu Driver Verifiera.

  1. Wejdź do trybu awaryjnego

Podczas uruchamiania komputera, jeszcze przed ekranem ładowania Windows przyciskaj F5 albo F8. Powinieneś ujrzeć planszę:

image_id: 4865

Sterowanie? Strzałki góra, dół. Wybierasz “Tryb awaryjny” i wciskasz Enter. Nie musisz się obawiać, kiedy wciśniesz przycisk. Najwyżej system uruchomi się w trybie normalnym i nie pokaże planszy z wyborem trybu, w jakim uruchomić system. Gdybyś miał problem z uruchomieniem w trybie awaryjnym, zobacz: http://www.fixitpc.pl/topic/5694-start- … safe-mode/

  1. Będąc w trybie awaryjnym:
  • albo przywróć system do stanu kiedy system uruchamiał się

Start - wszystkie programy - akcesoria - narzedzia systemowe - przywracanie systemu

  • albo odinstaluj w Dodaj/Usuń programy Daemon Tools

Jeżeli tryb awaryjny nie działa to uruchom komputer z płyty Windows 7 i stamtąd skorzystaj z Przywracania systemu przeglad-metod-naprawy-problemow-uruchamianiem-windows-t497796.html

Gdy system odpali się, pokaż pliki z C:\windows\minidump, które powstały gdy nie mogłeś uruchomić komputera.


(Blaix96) #7

Nie dało się wininit.exe uruchomić za pomocą tego programu.

Microsoft (R) Windows Debugger Version 6.11.0001.402 X86

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C]

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 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 7600 MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Machine Name:

Kernel base = 0xfffff800`02804000 PsLoadedModuleList = 0xfffff800`02a41e50

Debug session time: Sat Jan 5 10:22:15.498 2013 (GMT+1)

System Uptime: 0 days 0:00:31.512

*********************************************************************

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

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck C000021A, {fffff8a0005f5160, c0000189, 0, 0}


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

******

*************************************************************************

*********************************************************************

* 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 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Probably caused by : ntoskrnl.exe ( nt+71f00 )


Followup: MachineOwner

---------