Wątek zamknięty

Błąd krytyczny (BSOD)

 
Hip Hop
Nowy
Liczba postów: 4
Post: #3

RE: Błąd krytyczny (BSOD)


Daj mi sekundkę...Otworzyłem przez WinDbg pierwszy plik w folderze minidump.


Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\072811-19624-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`0284c000 PsLoadedModuleList = 0xfffff800`02a89e50
Debug session time: Thu Jul 28 08:12:28.516 2011 (UTC + 2:00)
System Uptime: 0 days 0:00:51.638
*********************************************************************
* 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 1E, {ffffffffc0000005, fffff80002b3175b, 0, ffffffffffffffff}

***** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+2e575b )

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

02.09.2011 19:15

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


Wiadomości w tym wątku
Błąd krytyczny (BSOD) - Hip Hop - 02.09.2011, 16:54
RE: Błąd krytyczny (BSOD) - Hip Hop - 02.09.2011 19:15
RE: Błąd krytyczny (BSOD) - Hip Hop - 12.09.2011, 14:54
Podobne wątki
Wątek: Autor Odpowiedzi: Wyświetleń: Ostatni post
BSOD 0x00000109 Arhq 6 3.349 12.07.2015 19:35
Ostatni post: Arhq
Rozwiązany BSOD podczas grania w gry wolffmistrz 10 4.519 03.04.2015 16:23
Ostatni post: wolffmistrz
BSOD - analiza pliku .dmp Ronnie 0 1.824 22.02.2015 19:15
Ostatni post: Ronnie
BSOD ntoskrnl.exe i hal.dll sierakow 2 2.798 16.11.2014 16:13
Ostatni post: Maxim128
Rozwiązany BSOD co chwila malolat79 4 3.595 19.08.2014 17:18
Ostatni post: malolat79
.Net Framework 4 Błąd Krytyczny + Problem. (Windows 7 64 bit) Kruncher 0 3.087 16.05.2014 21:39
Ostatni post: Kruncher
« Starszy wątek | Nowszy wątek »

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