mino6 Posted October 20, 2013 Report Share Posted October 20, 2013 Witam jestem nowy na forum i mam nadzieję że odnajdę u was pomoc.Przy odpalaniu gry lub gdy chcę wejść i zmienić ustawienia grafiki wyskakuje mi "niebieski ekran śmierci". Chciałbym prosić was o pomoc, gdyż zaczyna się robić już to drażniące.mój sprzęt:laptop lenovo Z570Procesor Intel? Core? i3-2350M CPU 2.30 GHzpamięć ram 8 GBsystem 64 bitprocesor graficzny GeForce GT 630M (wersja sterownika 320.49)windows 7servoce pack 1wklejam zdjęcie http://zapodaj.net/2...8408a7.jpg.htmlminidump:Microsoft ? Windows Debugger Version 6.11.0001.404 X86Copyright ? Microsoft Corporation. All rights reserved.Loading Dump File [D:\DUMP3eb4.tmp]Kernel Summary Dump File: Only kernel address space is availableSymbol 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+ ************************************************************************* ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532Machine Name:Kernel base = 0xfffff800`03053000 PsLoadedModuleList = 0xfffff800`032966d0Debug session time: Fri Oct 18 08:33:16.650 2013 (GMT+2)System Uptime: 0 days 0:13:07.509********************************************************************** 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+ ************************************************************************* ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -Loading Kernel Symbols....................................................................................................................................................................................Loading User SymbolsLoading unloaded module list....*** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgkrnl.sys -******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 116, {fffffa80078fe4e0, fffff880059af6b4, 0, 2}*** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgmms1.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 ****** ******************************************************************************* ERROR: Symbol file could not be found. Defaulted to export symbols for nvlddmkm.sys -**************************************************************************** ****** ****** 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 : nvlddmkm.sys ( nvlddmkm+14d6b4 )Followup: MachineOwner---------Dzięki wielkie za pomoc. Link to comment Share on other sites More sharing options...
[Ekspert] antros22 Posted October 20, 2013 Report Share Posted October 20, 2013 Próbowałeś reinstalacji/zmiany sterowników od karty ("porządnej") - klik? Link to comment Share on other sites More sharing options...
mino6 Posted October 22, 2013 Author Report Share Posted October 22, 2013 Sterowniki mam najnowsze jeszcze cieple bo wersja z wczoraj 331.58 (sprawdzałem tez stare). Odinstalowałem wszystko zainstalowałem od nowa i dalej ten sam problem. Dzieje się tak po formacie systemu, przed formatem nie miałem tego problemu.zrobiłem przegląd everestem i przedstawiam wam co widzęhttp://zapodaj.net/ef5dbc55b6ef0.jpg.htmlhttp://zapodaj.net/3c449a730441b.jpg.html Link to comment Share on other sites More sharing options...
[Ekspert] antros22 Posted October 22, 2013 Report Share Posted October 22, 2013 Sprawdź temperatury. Link to comment Share on other sites More sharing options...
mino6 Posted October 22, 2013 Author Report Share Posted October 22, 2013 podczas uruchomiania everesta wyskoczył mi komunikathttp://zapodaj.net/361356f16b50d.jpg.htmltutaj przedstawiam temperaturyhttp://zapodaj.net/9346546a9435c.png.html Link to comment Share on other sites More sharing options...
[Ekspert] antros22 Posted October 22, 2013 Report Share Posted October 22, 2013 1. Daj sobie spokój z Everestem, jest przestarzały.2. W Twoim przypadku wypadałoby sprawdzić przede wszystkim temperaturę karty graficznej, samo sprawdzenie temperatury procesora to za mało (na dodatek w spoczynku). Użyj programu HWMonitor (jeśli monitoruje temperaturę karty) i najlepiej daj screena z temperaturami w stresie.3. Tak w ogóle - jakoś mi to umknęło - czy masz problem tylko z jedną grą (pisałeś o grze w liczbie pojedynczej)? Link to comment Share on other sites More sharing options...
mino6 Posted October 23, 2013 Author Report Share Posted October 23, 2013 w moim modelu lapka sa 2 karty graficznej slabsza intelowska i lepsza nvidii, problem polega na tym ze przy jakim kolwiek uruchomieniu sie karty graficznej nvidii wyskakuje niebieski ekran, wiec zbytnio nie mam jak sprawdzic jaką temp osiąga ta karta. Po wejsćiu w panel steroniania nvidii > wyreguluj ustawienia obrazu... tak że pokazuję się niebieski ekran. Chciałem użyć programu GPU-Z, podczas jego uruchomiania niebeski ekran, przy odpaleniu jakiejkolwiek gry niebieski ekran.karty graficzne:intel hd graphics 3000GeForce GT 630M Link to comment Share on other sites More sharing options...
[Ekspert] antros22 Posted October 23, 2013 Report Share Posted October 23, 2013 Hm, chyba nie potrafię Ci pomóc. Jeżeli nie jest to kwestia jakichś ustawień (BTW, nie zaszkodzi przywrócenie "defaultowych" ustawień w Biosie) - o których nie mam pojęcia (przynajmniej tak na odległość) - lub mieszania programów/sterów, to w grę wchodzi uszkodzenie sprzętowe, które z obiektywnych przyczyn (w laptopie nie podmienisz karty na próbę, a ją trzeba by sprawdzić w pierwszej kolejności) ciężko namierzyć. Można by - co prawda - sprawdzić pamięci, bo niekoniecznie musiałoby to być uszkodzenie karty (tu podobny problem, okazało się, że to wina płyty), ale to szukanie zupełnie po omacku. Zatem, jeśliby nikt nie miał więcej pomysłów, pozostaje serwis. Link to comment Share on other sites More sharing options...
