Komputeromaniak.net - Forum Komputerowo-Webmasterskie: Bluescreen i reset kompa - jak usunąć błąd ? - Komputeromaniak.net - Forum Komputerowo-Webmasterskie

Skocz do zawartości




Strona 1 z 1
  • Nie możesz napisać tematu
  • Temat jest zamknięty

Bluescreen i reset kompa - jak usunąć błąd ?

#1
lisekx  


  • Tytuł Użytkownik
  • Grupa Użytkownicy
  • Postów 31
  • Rejestracja 28 czerwiec 2013
Witam, od wczoraj mam problem z samoistnym resetem kompa i bluescreen'em. Nie instalowałem od miesiąca żadnych nowych programów.
Komp:
Windows 7
Procesor: Intel Core i3 540, 3066 MHz
Płyta główna: Gigabyte GA-P55-US3L ver.2.0
Grafika: Gigabyte HD 7770 ver. 2.0
Pamięć: Crucial 2x4GB DDR3-1600
Dyski: SSD 250GB Crucial 250MX
WDC 500GB WD5000AACS-00ZUB0
WDC 500GB WD5001AALS-00LWTA0
Zasilacz: CHIEFTEC 450W GPS-450AA-101A
Będę wdzięczny za pomoc. W pliku z raportem błędu mam coś takiego:
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\BLUE\Desktop\120517-11154-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
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23864.amd64fre.win7sp1_ldr.170707-0600
Machine Name:
Kernel base = 0xfffff800`03014000 PsLoadedModuleList = 0xfffff800`03256750
Debug session time: Tue Dec  5 18:24:56.410 2017 (GMT+1)
System Uptime: 0 days 0:19:08.752
*********************************************************************
* 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
*** 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 1E, {0, 0, 0, 0}

***** 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                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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 : ntoskrnl.exe ( nt+6f950 )

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

Jeśli jeszcze jest coś potrzebne do zdiagnozowania problemu to dajcie znać
0

#2
Nelson  


  • Tytuł Super moderatorzy
  • Grupa Moderatorzy
  • Postów 309
  • Rejestracja 22 sierpień 2012
  • Płeć:Mężczyzna
  • Skąd:Małopolskie/Śląsk
  • OS:Windows 7
Z tego, co widzę problem powoduje plik ntoskrnl.exe (Probably caused by : ntoskrnl.exe ( nt+6f950 ), a więc pytanie do Ciebie:

Podkręcałeś coś w BIOSie?

Jeżeli tak, wejdź do biosu i zmień wartości na domyślne.

Sterowniki aktualne?


Jeżeli nie (bądź nie wiesz) zrobisz to np. programem DriverEasy.

Dodatkowo, robimy test pamięci na błędy, czyli pobieramy program MemTest i uruchamiamy.


P.S:

Cytat

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

Użyłeś niepoprawnych symboli. Powtórz debugowanie; otwórz debugger, CTRL+S i wklej

Cytat

SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
.

Po tym otwórz plik .dmp z uprzedniego działania (wybierz CTRL+D) i daj wynik.
0

#3
lisekx  


  • Tytuł Użytkownik
  • Grupa Użytkownicy
  • Postów 31
  • Rejestracja 28 czerwiec 2013
w biosie nie grzebałem
poprawne dane z debbugera


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


Loading Dump File [C:\Users\BLUE\Desktop\120617-13494-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23864.amd64fre.win7sp1_ldr.170707-0600
Machine Name:
Kernel base = 0xfffff800`0301d000 PsLoadedModuleList = 0xfffff800`0325f750
Debug session time: Wed Dec  6 01:33:30.170 2017 (GMT+1)
System Uptime: 0 days 7:07:31.138
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\klbackupdisk.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klbackupdisk.sys
*** ERROR: Module load completed but symbols could not be loaded for klbackupdisk.sys


0

#4
Nelson  


  • Tytuł Super moderatorzy
  • Grupa Moderatorzy
  • Postów 309
  • Rejestracja 22 sierpień 2012
  • Płeć:Mężczyzna
  • Skąd:Małopolskie/Śląsk
  • OS:Windows 7
Robiłeś testy co do reszty? :)

Z tego, co widzę wina leży po stronie programu Kaspersky Lab, dlatego zalecam jego odinstalowanie i przetestowanie co będzie działo się bez niego.

Dodatkowo przeskanuj komputer na obecność wirusów, pamięci również mogą być zawirusowane stąd memtest.

Daj mi jeszcze szczegółówo !analyze -v z Debuggera.
0

#5
lisekx  


  • Tytuł Użytkownik
  • Grupa Użytkownicy
  • Postów 31
  • Rejestracja 28 czerwiec 2013
Kaspersky odinstalowany, sterowniki zaktualizowane, jutro zrobię memtest...

Wyświetl postUżytkownik Nelson dnia 06 grudzień 2017 napisał

Daj mi jeszcze szczegółówo !analyze -v z Debuggera.

tzn ? nie za bardzo wiem o co chodzi :(
0

#6
Nelson  


  • Tytuł Super moderatorzy
  • Grupa Moderatorzy
  • Postów 309
  • Rejestracja 22 sierpień 2012
  • Płeć:Mężczyzna
  • Skąd:Małopolskie/Śląsk
  • OS:Windows 7
Wpisujesz zapytanie w debuggerze ;)

I jak, przyniosło efekty?
0

#7
lisekx  


  • Tytuł Użytkownik
  • Grupa Użytkownicy
  • Postów 31
  • Rejestracja 28 czerwiec 2013
odinstalowałem Kasperskiego, zainstalowałem ponownie starszą wersję i na razie działa bez problemów, dzięki
0

#8
Nelson  


  • Tytuł Super moderatorzy
  • Grupa Moderatorzy
  • Postów 309
  • Rejestracja 22 sierpień 2012
  • Płeć:Mężczyzna
  • Skąd:Małopolskie/Śląsk
  • OS:Windows 7
Cieszę się bardzo :)

Tak więc zamykam i gdyby jeszcze coś się działo (lub miałbyś jakikolwiek inny problem) zapraszam do założenia nowego tematu.
0

Udostępnij ten temat:


Strona 1 z 1
  • Nie możesz napisać tematu
  • Temat jest zamknięty

Użytkownicy przeglądający ten temat: 1
0 użytkowników, 1 gości, 0 anonimowych