witam mój komputer ostatnio często łapie blue screena i nie wiem czego to jest powodem aktualizowałem sterowniki od karty graficznej i sieciowej i nic . komputer najczęściej łapie blue screeny gdy gram lub siedze na internecie. posiadam windows 7 64 bity. odczytałem plik minidump w programie windbg tylko teraz nie wiem jak odczytać co powoduje błąd wiec mam proźbe aby ktoś kto potrafi zobaczył i sprubował mi pomóc. z góry dziękuje.
o to odczyt pliku minidump.
Microsoft ® Windows Debugger Version 6.2.9200.16384 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [G]
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 Unknown_Module_fffffd60`910d8d48, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_fffffd60`910d8d48
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffffd60`910d8d48
Debugger can not determine kernel base address
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17118.amd64fre.win7_gdr.120830-0334
Machine Name:
Kernel base = 0xfffff80002e19000 PsLoadedModuleList = 0xfffff80003055e70
Debug session time: Wed Jan 16 15:44:47.937 2013 (UTC + 1:00)
System Uptime: 0 days 0:47:34.513
*********************************************************************
* 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 Unknown_Module_fffffd60`910d8d48, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_fffffd60`910d8d48
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffffd60`910d8d48
Debugger can not determine kernel base address
Loading Kernel Symbols
.
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
…
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {eb945110, 2, 0, fffff880018614c3}
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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 : Unknown_Image ( Unknown_Module_fffff880`03f5d000>+162ec61 )
Followup: MachineOwner