Blue screen w windows 7


(Icebeast1) #1

Witam prosiłbym o pomoc z rozwiązaniem problemu blue screena.

Opis problemu

Podpis problemu:

  Nazwa zdarzenia problemu:	BlueScreen

  Wersja systemu operacyjnego:	6.1.7601.2.1.0.256.1

  Identyfikator ustawień regionalnych:	1045


Dodatkowe informacje o problemie:

  BCCode:	116

  BCP1:	FFFFFA80070EB010

  BCP2:	FFFFF8800840CADC

  BCP3:	FFFFFFFFC000009A

  BCP4:	0000000000000004

  OS Version:	6_1_7601

  Service Pack:	1_0

  Product:	256_1


Pliki pomagające opisać problem:

  C:\Windows\Minidump\013013-18283-01.dmp

  C:\Users\Marcin\AppData\Local\Temp\WER-71978-0.sysdata.xml


Przeczytaj w trybie online nasze zasady zachowania poufności informacji:

  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0415


Jeśli zasady zachowania poufności informacji w trybie online nie są dostępne, przeczytaj nasze zasady zachowania poufności informacji w trybie offline:

  C:\Windows\system32\pl-PL\erofflps.txt

Logi z DBG

Microsoft (R) Windows Debugger Version 6.6.0003.5

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C]

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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows Vista Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333

Kernel base = 0xfffff800`03611000 PsLoadedModuleList = 0xfffff800`03855670

Debug session time: Wed Jan 30 09:23:06.946 2013 (GMT+1)

System Uptime: 0 days 0:02:38.179

*********************************************************************

* 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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 2

*** 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 2

*** 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, {fffffa80070eb010, fffff8800840cadc, ffffffffc000009a, 4}


***** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT***

******

*************************************************************************

*************************************************************************

******

******

***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: dxgkrnl!_TDR_RECOVERY_CONTEXT***

******

*************************************************************************

*************************************************************************

******

******

***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: dxgkrnl!_TDR_RECOVERY_CONTEXT***

******

*************************************************************************

*************************************************************************

******

******

***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: dxgkrnl!DXGADAPTER***

******

*************************************************************************

*************************************************************************

******

******

***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***

******

*************************************************************************

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for dxgmms1.sys

*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys

Probably caused by : nvlddmkm.sys ( nvlddmkm+929adc )


Followup: MachineOwner

---------

Jako ze to moja pierwsza potyczka z blue screenem prosiłbym o wyjaśnienie co jeszcze mam podać.


(falcon89) #2

Zainstaluj najnowsze/starsze sterowniki do karty graficznej, odinstaluj poprzednie sterowniki, wyczyść system z pozostałości po sterownikach za pomocą Driver Sweeper (usuń tylko do karty graficznej).


(Icebeast1) #3

Chciałbym sie tylko upewnić ze mam zaznaczyć Chipset Display oraz PhysX po czym Analyse oraz clean ?


(falcon89) #4

Usuń Nvidia Display i PhysX (przycisk Czyść).


(Icebeast1) #5

Już to zrobiłem, coś jeszcze czy tylko błąd ze sterownikami od karty graficznej ?


(rgabrysiak) #6

Cześć

Jeżeli wszystko działa poprawnie to znaczy że to już wszystko :wink:


(falcon89) #7

Czy zainstalowałeś najnowsze/starsze sterowniki do karty graficznej (jeśli miałeś najnowsze to zainstaluj starsze i na odwrót).


(Icebeast1) #8

Działało wszystko ok tak przez pół miesiąca po czym znowu blue screen i znowu długo działało jak przeinstalowałem stery do grafy i dzisiaj znowu blue screen…

Czy to na pewno od nvidii? bo coś widzę w tym jeszcze directa a mam 11.

Logi:

Microsoft (R) Windows Debugger Version 6.6.0003.5

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C]

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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows Vista Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431

Kernel base = 0xfffff800`03668000 PsLoadedModuleList = 0xfffff800`038ac670

Debug session time: Wed Feb 27 10:30:26.957 2013 (GMT+1)

System Uptime: 0 days 0:16:29.190

*********************************************************************

* 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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 2

*** 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 2

*** 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, {fffffa80071bd010, fffff88007bdf6c4, ffffffffc000009a, 4}


***** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT***

******

*************************************************************************

*************************************************************************

******

******

***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: dxgkrnl!_TDR_RECOVERY_CONTEXT***

******

*************************************************************************

*************************************************************************

******

******

***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: dxgkrnl!_TDR_RECOVERY_CONTEXT***

******

*************************************************************************

*************************************************************************

******

******

***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: dxgkrnl!DXGADAPTER***

******

*************************************************************************

*************************************************************************

******

******

***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***

******

*************************************************************************

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for dxgmms1.sys

*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys

Probably caused by : nvlddmkm.sys ( nvlddmkm+9316c4 )


Followup: MachineOwner

---------

(falcon89) #9

Sprawdź i podaj temperaturę karty graficznej (na pulpicie i pod obciążeniem np. w grze lub benchmarku) za pomocą http://www.dobreprogramy.pl/HWMonitor,P … 33495.html lub http://www.dobreprogramy.pl/GPUZ,Progra … 16750.html (zakładka Sensors).


(rgabrysiak) #10

Cześć

Jeżeli problem występuje zarówno na nowszych jak i starszych sterownikach a karta się nie przegrzewa, to warto ją przetestować na innym komputerze.


(Icebeast1) #11

Niestety nie mam dostępu do innego komputera.

na pulpicie 40-45

w grze (nowej) 70-75 czasem nawet powyzej 80 i komputer chodzi jak suszarka.

Dzisiaj dostałem blue screena chyba takiego jak zawsze:

Microsoft (R) Windows Debugger Version 6.6.0003.5

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C]

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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows Vista Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431

Kernel base = 0xfffff800`03612000 PsLoadedModuleList = 0xfffff800`03856670

Debug session time: Thu Mar 14 09:25:43.273 2013 (GMT+1)

System Uptime: 0 days 0:44:18.506

*********************************************************************

* 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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 2

*** 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 2

*** 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, {fffffa8008d5e010, fffff88007b566c4, ffffffffc000009a, 4}


***** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT***

******

*************************************************************************

*************************************************************************

******

******

***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: dxgkrnl!_TDR_RECOVERY_CONTEXT***

******

*************************************************************************

*************************************************************************

******

******

***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: dxgkrnl!_TDR_RECOVERY_CONTEXT***

******

*************************************************************************

*************************************************************************

******

******

***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: dxgkrnl!DXGADAPTER***

******

*************************************************************************

*************************************************************************

******

******

***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***

******

*************************************************************************

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for dxgmms1.sys

*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys

Probably caused by : nvlddmkm.sys ( nvlddmkm+9316c4 )


Followup: MachineOwner

---------

(falcon89) #12

Zainstaluj http://www.dobreprogramy.pl/DirectX,Pro … 12667.html (DXSETUP.exe).

Czy masz płytę Asusa (podaj konfigurację komputera)?


(Icebeast1) #13

gpu gtx 550 ti

cpu intel i3 2100 @ 3.10ghz x2

8gb ram

1tb dysk

Przy karcie pisze “Nazwa płyty głównej Nieznane”

używam do tego EVEREST Home Edition


(deFco247) #14

Everest Home Edition to przestarzały program (ostatnia wersja z 2005 roku), który nie rozpoznaje nowszych podzespołów komputerowych.

Użyj np. CPU-Z: http://www.dobreprogramy.pl/CPUZ,Progra … 13047.html (pobierz z przycisku 64-bit).


(Icebeast1) #15

Screen plyty glownej http://imgur.com/uPUTRit