Witam, mam następujący problem: podczas klikania przycisku “zamknij” w menu start w celu wyłączenia komputera wyskakuje mi Blue Screen Of Death , przy próbie zrobienia przywracania systemu do wcześniejszej daty dzieje się to samo gdy komputer chce uruchomić się ponownie. Korzystam z Windows 7 w wersji 64-bitowej, komputer ma dopiero jakieś 2 miesiące, więc trochę mnie martwi ten problem. Dzieję się tak od wczoraj po uruchomieniu gry Assassins creed III wchodziłem tylko do menu i ustawiałem wszystko na max po czym wyłączyłem grę, ponieważ nie pójdzie mi na zintegrowanej karcie graficznej, a dziś własnie doszła mi nowa Radeon HD 6850 i miałem nadzieję sobie pograć, tylko najpierw chciałbym rozwiązać owy problem.
Specyfikacja komputera:
Procesor: Intel Core i5 2320 4x3.0 Ghz i w nim zintegrowana Karta graficzna: Intel HD graphics 2000
Pamięć RAM: 8 GB RAM DDR3 1333 MHz firmy Patriot
Płyta główna: Gigabyte GA-H61MA-D3V
Dysk twardy: WD Caviar green 500 GB sata III
Tutaj jest zawartość raportu, który wyświetlił się po ponownym uruchomieniu komputera:
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: f4
BCP1: 0000000000000003
BCP2: FFFFFA80099E93F0
BCP3: FFFFFA80099E96D0
BCP4: FFFFF80002FC5240
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Pliki pomagające opisać problem:
C:\Windows\Minidump\112012-15132-01.dmp
C:\Users\Migu\AppData\Local\Temp\WER-22292-0.sysdata.xml
Oraz zawartość pliku dmp, który został podany w tymże raporcie:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
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 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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Tue Nov 20 07:15:49.651 2012 (UTC + 1:00)
System Uptime: 0 days 0:18:28.947
*********************************************************************
* 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 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
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa80099e93f0, fffffa80099e96d0, fffff80002fc5240}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
----- ETW minidump data unavailable-----
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
Probably caused by : explorer.exe
Followup: MachineOwner
---------
Proszę o szybką pomoc i z góry dziękuję !
– Dodane 20.11.2012 (Wt) 18:48 –
Poszperałem jeszcze trochę w internecie, pobrałem program malwarebytes antimalware, przeskanowałem dysk i znalazło mi 5 zagrożeń, po czym je usunąłem i problem zniknął. Wcześniej jeszcze skanowałem dysk za pomocą ESET Smart Security 5 i owych zagrożeń nie wykryło.
Temat można zamknąć !