airdamien23 utworzono 24 sierpnia 2010 utworzono 24 sierpnia 2010 (edytowane) Podczas gdy grałem w StarCrafta II stało się Blue Screen chwila przycięcia i niebieski ekran mi się pojawił podaję informację o nim: Nie wiem to jest błąd gry, systemu czy sprzętu czy jak ? Bardzo proszę o pomoc [spoiler]Microsoft ® Windows Debugger Version 6.10.0003.233 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\082310-18468-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Mini Kernel Dump does not have process information 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 ntoskrnl.exe, Win32 error 0n2 *** 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.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`03056000 PsLoadedModuleList = 0xfffff800`03293e50 Debug session time: Mon Aug 23 13:44:07.105 2010 (GMT+2) System Uptime: 0 days 5:48:22.208 ********************************************************************* * 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 ntoskrnl.exe, Win32 error 0n2 *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe 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. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. . ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} *** 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 ndis.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ndis.sys *** ERROR: Module load completed but symbols could not be loaded for ndis.sys ***** 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 *** *** *** ************************************************************************* ********************************************************************* * 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+70710 ) Followup: MachineOwner ---------[/spoiler] [color="#ff0000"]//przenoszę do subforum BSOD //raaz[/color]
raazor90 komentarz 24 sierpnia 2010 komentarz 24 sierpnia 2010 [quote]Probably caused by : ntoskrnl.exe ( nt+70710 )[/quote] [quote][b]ntoskrnl.exe[/b] problem z pamiecią RAM/możliwa naprawa za pomocą płyty instalacyjnej Windows[/quote] Źródło: http://www.forumpc.pl/index.php?showtopic=163186
airdamien23 komentarz 24 sierpnia 2010 Autor komentarz 24 sierpnia 2010 Ale pamięć RAM nie jest uszkodzona. Jest dobra ? Jak mam naprawić to coś za pomocą instalatora Windows 7 ? Proszę o pomoc
raazor90 komentarz 24 sierpnia 2010 komentarz 24 sierpnia 2010 Jeszcze raz, a prawidłowo wykonaj tą część za pomocą Debuggera: [quote][quote]***** Kernel symbols are WRONG. Please fix symbols to do analysis.[/quote] Oznacza to, że musimy [b]pobrać symbole[/b] do swojego systemu dzięki którym odczytamy [b]w całości[/b] plik minidump - na tym etapie jest on niekompletny i może wskazywać nie ten plik co trzeba. Zamykamy Debuggera. Po ponownym jego uruchomieniu klikamy [i]File[/i] -> [i]Symbol File Path[/i] -> wpisujemy: [b]SRV*c:\symbols*http://msdl.microsoft.com/download/symbols[/b] Następnie wciskamy [ctrl] + [D] i wskazujemy znów nasz plik minidump. Trzeba poczekać aż Debugger ściągnie sobie wszystkie symbole i przeanalizuje cały plik. Należy pamiętać że ten proces może nieco potrwać - symbole mogą ważyć nawet ponad 10MB, także trzeba uzbroić się w cierpliwość. 6. Wklejamy część [b]minidumpa[/b], o której mowa, na forum.[/quote]
airdamien23 komentarz 24 sierpnia 2010 Autor komentarz 24 sierpnia 2010 (edytowane) Zrobiłem tak jak napisałeś i odczekałem z 15 minut i: [spoiler] Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\082310-18468-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Mini Kernel Dump does not have process information 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 ntoskrnl.exe, Win32 error 0n2 *** 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.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`03056000 PsLoadedModuleList = 0xfffff800`03293e50 Debug session time: Mon Aug 23 13:44:07.105 2010 (GMT+2) System Uptime: 0 days 5:48:22.208 ********************************************************************* * 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 ntoskrnl.exe, Win32 error 0n2 *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe 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. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. . ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} *** 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 ndis.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ndis.sys *** ERROR: Module load completed but symbols could not be loaded for ndis.sys ***** 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 *** *** *** ************************************************************************* ********************************************************************* * 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+70710 ) Followup: MachineOwner --------- [/spoiler] Proszę o pomoc
raazor90 komentarz 24 sierpnia 2010 komentarz 24 sierpnia 2010 Zbootuj płytkę instalacyjną windowsa ale zamiast opcji instaluj wybierz napraw lub coś w tym stylu, nie wiem dokładnie jak to jest w win7
airdamien23 komentarz 24 sierpnia 2010 Autor komentarz 24 sierpnia 2010 i jak dam napraw to co może się dziać ? Nigdy tego nie robiłem a nie chcę ab się coś spitoliło.
raazor90 komentarz 24 sierpnia 2010 komentarz 24 sierpnia 2010 Powinien rozpocząć się proces naprawy, podmieniania uszkodzonych plików systemowych, nie jestem w stanie powiedzieć jak to dokładnie wygląda na win 7 gdyż nie miałem z nim do czynienia
airdamien23 komentarz 24 sierpnia 2010 Autor komentarz 24 sierpnia 2010 ok dzięki. Ale ze sprzętem wszystko gra ? Pamięci są dobre ?
raazor90 komentarz 25 sierpnia 2010 komentarz 25 sierpnia 2010 Dla pewności możesz przetestować pamięci bootowalnym Memtest 86+
raazor90 komentarz 27 sierpnia 2010 komentarz 27 sierpnia 2010 http://www.forumpc.pl/index.php?showtopic=144212
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.