Od jakiegoś czasu męczą mnie Blue Screeny nie mam już do tego siły. Testowałem pamięci. Wszystkie pojedyńczo. Jedna wywalała błędy, wyjąłem ją. Zostawiłem 2 x 2Gb 10 razy przeszły MemTest. Dalej to samo. Podczas obojętnie jakiej gry BSOD. Testowałem różne sterowniki grafiki. Stare nowe i dalej to samo. Zrobiłem format wgrałem tylko sterowniki karty sieciowj i najnowsze grafiki, bez zmian BSOD. Nie mam pojęcia co może być przyczyną może wy mi pomożecie. Temperatury w normie.
Specyfikacja kompa:
| CPU : AMD Phenom II X4 965 BE @ 3.4 Ghz
I COOLER : Phanteks PH-TC14PE
| MBO : AsRock 970 extr3me
| RAM : 8GB (4x2) DDR3 1333Mhz
| HDD : 120GB OCZ Vertex 4 for OS + Seagate 500Gb 7200 RPM
| GPU : SAPPHIRE R9 280X TOXIC 3GB GDDR5 @ 1150/1600
| PSU : Seasonic 760W 80+ Platinum
| HEADSET : Sony MDR-XB300
| KEYBOARD: MS Sidewinder x4
| MOUSE : Cyborg R.A.T 7 5600DPI
| MOUSEMAT : Razer GOLIATHUS EXTENDED XL SPEED
| MONITOR : ACER 17" + LG 32"
| CASE : COOLER MASTER PC Storm Trooper (SGC-5000-KKN1)
Screny:
http://imageshack.com/a/img801/6413/vw8k.jpg
Microsoft ® Windows Debugger Version 6.6.0003.5
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021114-7971-01.dmp]
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 <symbol_path> 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
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Kernel base = 0xfffff800
0284f000 PsLoadedModuleList = 0xfffff80002a8ce50Debug session time: Tue Feb 11 17:17:15.201 2014 (GMT+1)
System Uptime: 0 days 1:24:08.965
*********************************************************************
* 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+ *
*********************************************************************
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 1E, {ffffffffc0000005, fffff880012658f0, 0, a8}
***** 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 ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\System32\Drivers\Ntfs.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by : Ntfs.sys ( Ntfs+e8f0 )
Followup: MachineOwner
