Niebieski ekran śmierci nvidia stop: 0x00000116

**Posty:** 2 · przez **mino6** 20 Paź 2013, 12:34

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 Z570
Procesor Intel(R) Core(TM) i3-2350M CPU 2.30 GHz
pamięć ram 8 GB
system 64 bit
procesor graficzny GeForce GT 630M (wersja sterownika 320.49)
windows 7
servoce pack 1

wklejam zdjęcie http://zapodaj.net/2785a538408a7.jpg.html

minidump:

Kod: Zaznacz wszystko: Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\DUMP3eb4.tmp] Kernel Summary Dump File: Only kernel address space is 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+ * ********************************************************************* *** 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 x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Machine Name: Kernel base = 0xfffff800`03053000 PsLoadedModuleList = 0xfffff800`032966d0 Debug 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 Symbols Loading 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.

**Posty:** 681 · przez **XMan 1** 20 Paź 2013, 13:35

Sprawdzałeś inne sterowniki do karty graficznej ?
Najnowsze lub starsze ?

**Posty:** 1308 · przez **apg2312** 20 Paź 2013, 14:11

Zacząłbym od zaktualizowania sterowników graficznych do najnowszej wersji - w tej chwili dostępna jest wersja 327.23
http://www.nvidia.pl/download/driverResults.aspx/66751/pl

**Posty:** 2 · przez **mino6** 22 Paź 2013, 17:24

Sterowniki mam najnowsze jeszcze cieple bo wersja z wczoraj 331.58. 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.

@edit

zrobiłem przegląd everestem i przedstawiam wam co widzę

http://zapodaj.net/ef5dbc55b6ef0.jpg.html

http://zapodaj.net/3c449a730441b.jpg.html

@edit

podczas uruchomiania everesta wyskoczył mi komunikat

http://zapodaj.net/361356f16b50d.jpg.html

przedstawiam też temperatury

http://zapodaj.net/9346546a9435c.png.html

Dodano Dzisiaj, 13:11:
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 3000

GeForce GT 630M