Blue Screen podczas wyłączania systemu


(Kamil Kacki695) #1

Witam serdecznie, tak jak w temacie podczas zamykania systemu co trwa ok 10 min komputer restartuje się i pojawia się komunikat

Podpis problemu:

  Nazwa zdarzenia problemu:	BlueScreen

  Wersja systemu operacyjnego:	6.1.7600.2.0.0.768.3

  Identyfikator ustawień regionalnych:	1045


Dodatkowe informacje o problemie:                

  BCCode:	9f

  BCP1:	0000000000000003

  BCP2:	FFFFFA8004F0B060

  BCP3:	FFFFF80003FD4748

  BCP4:	FFFFFA800707A4D0

  OS Version:	6_1_7600

  Service Pack:	0_0

  Product:	768_1


Pliki pomagające opisać problem:

  C:\Windows\Minidump\010413-27144-01.dmp

  C:\Users\Kamil\AppData\Local\Temp\WER-44709-0.sysdata.xml



zrobilem Debuga pliku 010413-27144-01.dmp i otrzymalem taki raport


Loading Dump File [C]

Mini Kernel Dump File: Only registers and stack trace are available


DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`03fd4500?

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 7600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Kernel base = 0xfffff800`02a5b000 PsLoadedModuleList = 0xfffff800`02c98e50

Debug session time: Tue Jan 8 00:30:16.336 2013 (GMT+1)

System Uptime: 0 days 8:56:46.584

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

* 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

.......

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck 9F, {3, fffffa8005d4f440, fffff80003fd4518, fffffa8006e2f010}


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

******

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

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

******

******

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

******

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

Unable to load image \SystemRoot\system32\DRIVERS\USBPORT.SYS, Win32 error 2

*** WARNING: Unable to verify timestamp for USBPORT.SYS

*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS

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

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


Followup: MachineOwner

Co może być przyczyną ciągłego Blue Screena?


(djkamil09061991) #2

Pokaż log z autorunsa być może problem z jakimś procesem. Pobierz plik http://technet.microsoft.com/pl-pl/sysi ... us%29.aspx rozpakuj, uruchom program, automatycznie rozpocznie się skan. Po jego zakończeniu. Menu Plik Save - zapisz raport na dysku. Spakuj ten raport i wrzuć na jakiś hosting. Link do niego podajesz tutaj.


(Kamil Kacki695) #3

http://hostuje.net/file.php?id=d0a079c4 ... 36625a8889 raport o którym mówiłeś jakieś pomysły?


(djkamil09061991) #4

Uruchom autorunsa i odznacz w:

HKLM\System\CurrentControlSet\Control\Terminal Server\Wds\rdpwd\StartupPrograms

-rdpclip

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

-RTHDVCPL

HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run

-Adobe ARM

-SunJavaUpdateSched

HKCU\Software\Microsoft\Windows\CurrentVersion\Run

-OscarX7Mouse5Mode

Przejdz do zakładki scheduled tasks i odznacz wszystko oprocz:

-avast! Antivirus

-Steam Client Service

Następnie restart kompa, potem po włączeniu kolejny i sprawdz czy coś jest lepiej.


(Kamil Kacki695) #5

zapomniałem dodać że komputer jest świeżo po formacie a ten blue screen pojawia się od czasu do czasu, bywają dni że w ogóle się nie pojawia, póki co zrobię tak jak wyżej napisałeś

-- Dodane 08.01.2013 (Wt) 22:50 --

odznaczyłem wszystko prócz avasta i Steama bo ich nie ma w sheduled tasks


(djkamil09061991) #6

Przepraszam to miala byc zakladka Services. Jeśli to nic nie da to przeinstaluj stery do grafiki i sieci na inne, ewentualnie sprawdz jak będzie bez antywira.


(Kamil Kacki695) #7

jak na razie po Twoich radach wszystko działa jak należy, restartowałem kilka razy komputer i jest okej zobaczymy jak dalej =)

-- Dodane 11.01.2013 (Pt) 14:00 --

Niestety problem wrócił i nadal jest to samo. Jakieś pomysły?

-- Dodane 12.01.2013 (So) 14:27 --

Loading Dump File [C]

Mini Kernel Dump File: Only registers and stack trace are available


DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?

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 7600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Kernel base = 0xfffff800`02a51000 PsLoadedModuleList = 0xfffff800`02c8ee50

Debug session time: Sat Jan 12 14:18:04.005 2013 (GMT+1)

System Uptime: 0 days 2:13:03.268

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

* 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

.....

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck 9F, {3, fffffa8005df2060, fffff80000b9c518, fffffa8003c1ea10}


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

******

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

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

******

******

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

******

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

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

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

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


Followup: MachineOwner

---------

tym razem problem wygląda tak =)