Bu Sorun nerden kaynaklanıyor. anlayan birisi şuna bir cevap yazsın.
Sorun imzası: Sorunlu Olay Adı: BlueScreen OS Sürümü: 6.1.7601.2.1.0.256.1 Yerel Kimlik: 1055
Sorun hakkında ek bilgiler: BCCode: 1000008e BCP1: C0000005 BCP2: 00000000 BCP3: 9FD2F970 BCP4: 00000000 OS Version: 6_1_7601 Service Pack: 1_0 Product: 256_1
Sorunu açıklamaya yardımcı olan dosyalar: C:\Windows\Minidump\011212-15927-01.dmp C:\Windows\Temp\WER-24757-0.sysdata.xml
Arkadaşlar benzer bir sorunda bende var bir türlü çözüm bulamadım. Arkadaş ram ve işlemciyi değiştirdi sorun yine devam ediyor. Herhangi bişey yaparken,hatta kendi halindeyken bile reset atıp mavi ekrana düşüyor. Mavi ekran hata kodu aşağıda fikri olan varsa sevinirim. Saygılar.
Sorun imzası: Sorunlu Olay Adı: BlueScreen OS Sürümü: 6.1.7600.2.0.0.256.1 Yerel Kimlik: 1055
Sorun hakkında ek bilgiler: BCCode: 24 BCP1: 00000000001904FB BCP2: FFFFF88005F4C068 BCP3: FFFFF88005F4B8C0 BCP4: FFFFF88001301A91 OS Version: 6_1_7600 Service Pack: 0_0 Product: 256_1
İşletim sistemim Windows7 64 bit İntel Celeron CPU 2.66 GHZ
Geçen ay bende de oldu böyle bir sorun. Format attım, hiçbir sorun kalmadı.
Merhaba. Öncelikle bu srounun çözümü için mavi ekran hatası esnasında oluşan hata dosyadı(dump ) dosyasını incelemeniz gerekir. Bunun için debugging tools vardır. işletim sisteminize uygun olannını bulun ve dump dosyasını okuyun. Dump dosyasında hangi programın hata verdiği vb bilgiler yer alacaktır. Elde ettiğiniz veriye gore de internette çözüm arayın.
KARDEŞİM DUMP DOSYASINI AÇAN PROGRAMI YÜKLEDİM. EN SON VERDİĞİ HATA SONRA KAYDEDİLEN DUMP DOSYASINI AÇIP AŞAĞIYA YAPIŞTIRDIM. YA ŞUNA BİR BAK BİZİMKİNİN DERDİ NEYMİŞ SANA ZAHMET.
Loading Dump File [C:\Windows\Minidump\011212-15927-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\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x82c38000 PsLoadedModuleList = 0x82d814d0 Debug session time: Thu Jan 12 10:42:44.613 2012 (UTC + 2:00) System Uptime: 0 days 0:07:51.408 ********************************************************************* * 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\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols Loading unloaded module list .... Unable to load image \SystemRoot\system32\DRIVERS\TridVid.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for TridVid.sys *** ERROR: Module load completed but symbols could not be loaded for TridVid.sys ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 0, 9fd2f970, 0}
*** WARNING: Unable to verify timestamp for ks.sys *** ERROR: Module load completed but symbols could not be loaded for ks.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 *** *** *** ************************************************************************* Probably caused by : TridVid.sys ( TridVid+f5e1 )