Witam mam problem z Blue Screenami. Otóż dokładnie tydzień temu podczas włączania komputera wywaliło mi komunikat, że nie można uruchomić systemu bo nie znaleziono pliku C:\WINDOWS\system32\config\system lub jest on uszkodzony (o ile dobrze kojarzę właśnie o ten plik chodziło). Jako, że nie wiedziałem jak to naprawić po prostu sformatowałem dysk C… :roll: Dodam, że komputer zamknąłem poprawnie, żadnych błędów etc, po prostu nie wiem czemu tak się stało.
Wczoraj wystąpił u mnie BSoD tylko nie wiem jaki, w każdym razie po zresetowaniu komputera znów miałem wyżej wymieniony problem z tym plikiem! Pomyślałem, że nie będę tym razem znów formatować i spróbowałem jeszcze raz z naprawą systemu. Udało mi się za pomocą konsoli odzyskiwania systemu to naprawić - wpisałem bodajże bootfix i system normalnie się uruchomił.
W dzienniku nie było jednak, żadnej wzmianki o Blue Screenie.
Dziś natomiast wystąpiły dwa BSoD…
Pierwszy:
Informacje techniczne: 0x0000007A (0xC0386744, 0xC000009C, 0xE19D1B94, 0x0E92B880)
ewentualna fotka błędu tu http://img44.imageshack.us/img44/6236/dsc01185y.jpg
Raport błedu wygenerowany w programie WinDbg:
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 XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sat Jun 27 19:09:16.520 2009 (GMT+2)
System Uptime: 0 days 3:29:51.938
*********************************************************************
* 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 7A, {c0386744, c000009c, e19d1b94, e92b880}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*************************************************************************
******
******
***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 : win32k.sys ( win32k+29bf4 )
Followup: MachineOwner
---------
Kiedy wystąpił błąd? Wyłączyłem grę (Call of Duty) i chciałem włączyć GG. Wtedy niebieski ekran się pojawił. Drugi BSoD: Informacje techniczne **0x0000007A (0xC0387204, 0xC000009C, 0xE1C81558, 0x088A7880)**ewentualna fotka błędu http://img200.imageshack.us/img200/4940/dsc01188k.jpgRaport z WinDbg:
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 XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sat Jun 27 19:30:41.234 2009 (GMT+2)
System Uptime: 0 days 0:19:33.930
*********************************************************************
* 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 7A, {c0387204, c000009c, e1c81558, 88a7880}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*************************************************************************
******
******
***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 : win32k.sys ( win32k+373d0 )
Followup: MachineOwner
---------
Kiedy wystąpił błąd? Podczas normalnego korzystania z komputera a dokładnie z Opery.
Po zresetowaniu komputera po drugim błędzie przed zalogowaniem otrzymałem następujący komunikat:
Ponownie uruchomiłem komputer na nowo i komunikat nie wystąpił. Udało się zalogować na moje konto (z uprawnieniami administratora).
Dodam, że dziś miałem parokrotnie problem z Operą, tj następowało jej zamknięcie. Przed chwilą podczas pisania tego tematu również…
Na koniec jeszcze konfiguracja mojego PC:
CPU: AMD Athlon XP 1800+ 1.54 GHz
MOBO: Epox EP-8RDA3I
RAM: 256 MB DDR
GPU: GeForce 2 MX 400
HDD: 40 GB + 80 GB (kupiony ok 2 lata temu - system postawiony na nim) - oba na ATA, nie pamiętam dokładnie jakie modele.
PSU: TakeMe 350 W o ile dobrze pamiętam (tak wiem no name to shit ale nie inwestuję już ani grosza w tego złoma)
OS: Windows XP HE SP3 oryginalny.
Reszta chyba nie potrzebna. Kpmputer ma prawie 7 lat no ale to nie powód chyba, żeby BS się pojawiały 
P.S. przepraszam, że się tak rozpisałem ale chciałem jak najszerzej opisać problem.
Rano zmienię te taśmy ATA.
