Wątek zamknięty

Win 7 - Bluescreen

 
alejanusz
Nowy
Liczba postów: 4
Post: #5

RE: Win 7 - Bluescreen


Otwieram plik minidump za pomocą Debugging Tools for Windows i po otwarciu tego pliku mam taki podgląd na ten minidump.
Microsoft ® Windows Debugger Version 6.6.0003.5
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\081712-11531-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 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Vista Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17803.x86fre.win7sp1_gdr.120330-1504
Kernel base = 0x81c0e000 PsLoadedModuleList = 0x81d4e230
Debug session time: Fri Aug 17 18:30:11.764 2012 (GMT+2)
System Uptime: 0 days 0:26:25.405
*********************************************************************
* 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 2
*** 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
.....
i taki też wklejam, czy o to chodzi ?

17.08.2012 17:45

Znajdź wszystkie posty użytkownika
Wątek zamknięty


Wiadomości w tym wątku
Win 7 - Bluescreen - alejanusz - 14.08.2012, 16:35
RE: Win 7 - Bluescreen - thermalfake - 16.08.2012, 03:32
RE: Win 7 - Bluescreen - alejanusz - 16.08.2012, 16:01
RE: Win 7 - Bluescreen - thermalfake - 16.08.2012, 16:29
RE: Win 7 - Bluescreen - alejanusz - 17.08.2012 17:45
Podobne wątki
Wątek: Autor Odpowiedzi: Wyświetleń: Ostatni post
W koszu Błąd BCCode:3b i bluescreen mazo88 1 418 03.03.2016 18:01
Ostatni post: thermalfake
W koszu Bluescreen 0x00000124 Win7 64bit po formacie Xylos 1 459 27.01.2016 02:06
Ostatni post: thermalfake
W koszu Bluescreen 0x0000004a lokikoki14 0 557 18.01.2016 13:58
Ostatni post: lokikoki14
W koszu Bluescreen Bluescreeny 1 741 01.01.2016 02:32
Ostatni post: thermalfake
W koszu Format Win 7 bluescreen koxig 2 573 29.11.2015 20:06
Ostatni post: thermalfake
W koszu BAD_SYSTEM_CONFIG_INFO 0x00000074 Bluescreen podczas uruchamiania Win7. koxig 0 405 02.10.2015 19:09
Ostatni post: koxig
« Starszy wątek | Nowszy wątek »

Temat został oceniony na 0 w skali 1-5 gwiazdek.
Zebrano 1 głosów.