Odczytanie loga z BSOD - pomoc

przez **Lego** w 18 Wrz 2014, 09:22

Odczytanie loga z BSOD - pomoc

przez Lego w 18 Wrz 2014, 09:22

Witam, czy ktoś może zdiagnozować przyczynę BSOD'a podczas grania w nieco bardziej wymagające gry?

Kod: Zaznacz wszystko: Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Ted\Desktop\091714-18656-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 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533 Machine Name: Kernel base = 0xfffff800`02e4a000 PsLoadedModuleList = 0xfffff800`0308d670 Debug session time: Wed Sep 17 23:41:41.359 2014 (GMT+2) System Uptime: 0 days 0:19:54.968 ********************************************************************* * 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 .... Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa8004f68010, fffff88006644e6c, ffffffffc0000001, 3} Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 : atikmpag.sys ( atikmpag+8e6c ) Followup: MachineOwner ---------

przez **Cromm Cruac** w 18 Wrz 2014, 09:45

Za ten post Cromm Cruac otrzymał następujące punkty reputacji:: Lego.

przez **Kpuc** w 18 Wrz 2014, 10:52

Re: Odczytanie loga z BSOD - pomoc

przez Kpuc w 18 Wrz 2014, 10:52

Tak jak napisał ten wyżej, ja jednak bym także sprawdził sam dysk na błędy odczytu oraz zaczął od reinstalacji sterowników graficznych. Skontrolował bym także temperatury.

Podaj specyfikację w szczególności zasilacz.

przez **Lego** w 18 Wrz 2014, 11:15

Re: Odczytanie loga z BSOD - pomoc

przez Lego w 18 Wrz 2014, 11:15

Specyfikacja:

Procesor: Intel Dual Core E5200 2.5 GhZ
GPU: HD Radeon 4870
4GB RAM
zasilacz OCZ 600W

przez **Sivert** w 18 Wrz 2014, 11:16

Re: Odczytanie loga z BSOD - pomoc

przez Sivert w 18 Wrz 2014, 11:16

Kolego, poszukałem w guglach i zobacz, co znalazłem:

http://stackoverflow.com/questions/1203 ... ead-with-w

generalnie sprowadza się to do poinformowania systemu, gdzie znajdują się poszukiwane przez niego zasoby. Odpisz, czy udało Ci się rozwiązać problem.

przez **Cromm Cruac** w 18 Wrz 2014, 12:02

Za ten post Cromm Cruac otrzymał następujące punkty reputacji:: Sivert.

przez **Kpuc** w 18 Wrz 2014, 13:21

Re: Odczytanie loga z BSOD - pomoc

przez Kpuc w 18 Wrz 2014, 13:21

Zasilacz ok, przy takich podzespołach to nawet mocno na wyrost. Sprawdź temperatury karty, zmień sterowniki.
Jak obudowa nie była dawno otwierana to także warto sprawdzić czy nie zalega kurz, kurz to bardzo zdradliwy szkodnik, suchy zachowuje się jak kołderka a wilgotny może przewodzić prąd.

przez **scigacz1975** w 18 Wrz 2014, 17:05

Re: Odczytanie loga z BSOD - pomoc

przez scigacz1975 w 18 Wrz 2014, 17:05

Mi to raczej wygląda na pliki jądra systemu - poczytaj tutaj:

http://windows7forum.pl/problem-z-pliki ... en-14655-t
http://windows7forum.pl/nt-kernel-syste ... it-13710-t
http://windows7forum.pl/bsod-y-przy-pie ... xe-21998-t
http://windows7forum.pl/bsod-spowodowan ... xe-36885-t
http://windows7forum.pl/bsod-rozne-bled ... xe-38963-t