BSOD do przenalizowania POMOC


(Mateusz16b) #1

Witam.

W ostatnim czasie podczas normalnego użytkowania wystąpił błąd. Wyskoczył Bluescreen. Posiadam system Windows 8 Pro x64. Wysyłam zawartość pliku DUMP. Prosiłbym o jego przeanalizowanie w czym może być problem. Dodam, że dysk oraz pamięć RAM przetestowałem i są sprawne. Z góry dziękuję za pomoc.

Microsoft ® Windows Debugger Version 6.2.0013.1

Copyright © 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 2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows Longhorn Kernel Version 9200 MP (4 procs) Free AMD x86-64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 9200.16384.amd64fre.win8_rtm.120725-1247

Kernel base = 0xfffff8032c26c000 PsLoadedModuleList = 0xfffff8032c536a60

Debug session time: Wed Apr 03 09:54:27 2013

System Uptime: 0 days 0:18:31.931

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

* 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 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 unloaded module list

.........

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa8153cb8390, 0, fffff8032c38636b, 2}

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

*** ***

*** ***

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

*** WARNING: Unable to verify timestamp for hal.dll

*** ERROR: Module load completed but symbols could not be loaded for hal.dll

Unable to load image \SystemRoot\system32\mcupdate_GenuineIntel.dll, Win32 error 2

*** WARNING: Unable to verify timestamp for mcupdate_GenuineIntel.dll

*** ERROR: Module load completed but symbols could not be loaded for mcupdate_GenuineIntel.dll

Probably caused by : Unknown_Image ( nt+11a36b )

Followup: MachineOwner



(Fanboj O) #2

http://forum.pclab.pl/topic/799484-CRIT ... -BSOD-109/


(Mateusz16b) #3

U mnie ten plik mcupdate_GenuineIntel.dll już istnieje. Czy mam go zastąpić ?