Forum
Bildirimler
Hepsini Temizle
Windows Client
10
Yazılar
6
Üyeler
0
Reactions
1,750
Görüntüleme
Konu başlatıcı
Merhaba,
Windows 8.1 yüklü 1 aylık masaüstü bilgisayarımız devamlı mavi ekran vererek kendini resetliyor. Bu sorun bazen günde 3 defa yaparken, bazen 4-5 gün boyunca yapmıyor. Güncellemeleri yaptım, Bios'u default'a çektim, driver'ları kontrol ettim. Sorun hala devam ediyor.
Son oluşturulan dump dosyasını paylaşıyorum. Yorumlayabilir misiniz acaba?
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\030314-4500-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 0n2
WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff800`c908e000 PsLoadedModuleList = 0xfffff800`c9352990
Debug session time: Mon Mar 3 08:09:07.037 2014 (UTC + 2:00)
System Uptime: 0 days 0:14:50.797
******************************************************************
* 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 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
......
******* Symbol Loading Error Summary ********
Module name Error
ntoskrnl The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
****************************************************************************
* *
* Bugcheck Analysis *
* *
****************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800c9177140, ffffd0003466d420, 0}
** Kernel symbols are WRONG. Please fix symbols to do analysis.
**********************************************************************
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
*******************************************************************
*******************************************************************
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
*******************************************************************
*******************************************************************
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 : ntoskrnl.exe ( nt+e9140 )
Followup: MachineOwner
---------
Gönderildi : 03/03/2014 16:58
win 8.1 de genellikle güncellemelerden sonra oluyor.
1 Güncellemeleri tek tek kaldırıp hangi güncellemenin hata verdiğini bulabilirsin.
2 başlat-çalıştır-cmd-chkdsk /r ile diskindeki hataları görererk /r ile onarabilirsin
3- http://support.microsoft.com/kb/314477/tr bu makaleyi bir inceleyin .
4-sistem geri yükleme tavsiyemdir.
Gönderildi : 03/03/2014 18:16
Konu başlatıcı
Merhaba,
Güncelleştirmelerle alakası olduğunu düşünmüyorum. Cihaz ilk güncelleştirmeyi Şubat'ın 21inde aldı. Biz sorunu makinayı ilk kullanmaya başladığımız andan beri yaşıyoruz.
Chkdsk yaptım. Herhangi bir hata ile karşılaşmadı.
Sistem geri yükleme yapıp bir süre test edeceğim. Düzelmemesi durumunda sistemi tekrar kuracağım. Eğer tekrar kurmama rağmen sorun hala devam ediyorsa, makinayı koltuk altıma alıp Gold'un yolunu tutacağım...
Yardımınız için teşekkürler.
Gönderildi : 03/03/2014 21:10
Sistem restore kesın çözum olacaktır
Gönderildi : 06/03/2014 02:08
Driverlar kontrol edildi derken nasıl bir kontrol işlemi yapıldı? Donanım üretici sitesinden kontrol mü edildi? Kullandığınız bilgisayar marka bir bilgisayar mı? Modeli ya da nasıl bir sistem olduğunu anlayabileceğimiz bir adı var mı bilgisayarın?
http://msdn.microsoft.com/en-us/library/windows/hardware/ff558949%28v=vs.85%29.aspx
Gönderildi : 07/03/2014 14:44
Belleği değiştir en başta.Kolay gelsin.
Gönderildi : 07/03/2014 16:04
son durum nedir ?
Gönderildi : 18/03/2014 14:12
Konu başlatıcı
İşletim sistemini tekrar kurdum. Eskisinden daha sık mavi ekran vermeye başladı makina. Son zamanda çıkan hata kodlarında sıklıkla Memory Management'a rastlamaya başladım. Ram'le alakalı bir sıkıntı olabileceğini düşünüyorum. Dün itibari ile bilgisayarı teknik servise gönderdim. Sonucu sizlerle paylaşacağım.
Gönderildi : 19/03/2014 17:44
İşletim sistemini tekrar kurdum. Eskisinden daha sık mavi ekran vermeye başladı makina. Son zamanda çıkan hata kodlarında sıklıkla Memory Management'a rastlamaya başladım. Ram'le alakalı bir sıkıntı olabileceğini düşünüyorum. Dün itibari ile bilgisayarı teknik servise gönderdim. Sonucu sizlerle paylaşacağım.
Merhaba,
Yazılımsal olduğunu düşünmüyorsunuz sanırsam. Peki ısınma durumunu kontrol ettiniz mi hiç ?
Gönderildi : 19/03/2014 19:40
Konu başlatıcı
Merhaba Yusuf Bey,
Evet kontrol ettim. Herşey normal görünüyordu. Zaten şöyle bişey var; bilgisayarı açıp bir sürü flashlı sayfa ve video açarak, tabiri caizse abanarak 5 gün boyunca hata vermediği de oldu, makinayı açtıktan sonra hiçbirşey çalışmazken 5 dk. sonra hata vererek kapandığı da. Yani her seferinde farklılık gösteriyor hata.
Gönderildi : 20/03/2014 19:12
