locked
[Windows 7] Bilgisayarım ara ara mavi ekran veriyor. ntkrnlpa.exe RRS feed

  • Soru

  • İnternetten araştırmalarım sonucunda windbg adlı programı kurdum ve ntkrnlpa.exe adlı uygulamanın problemli oldugu yazıyordu. İsterseniz kopyala-yapıştır da yapabilirim. Lütfen yardımcı olun, şimdiden teşekkürler
    22 Nisan 2011 Cuma 18:34

Yanıtlar

  • Merhaba HFZ61

    Sorununuz söylemiş olduğum işlemleri gerçekleştirdikten sonra devam ediyor ise aşağıdaki yönergeleri izleyiniz.

     

    http://cid-3abf63b02cec49f5.skydrive.live.com/browse.aspx/Dumpfiles?sa=475194785 adresinde bulunan 4 adet dump dosyasını bilgisayarınıza indirin ve indirmiş olduğunuz bu 4 adet dump dosyasını c:\windows\minidump      klasörüne kopyalayın.

    Bu işlemi yapmadan önce bilgisayarınızın yedeğini almanız önemle rica olunur. Aksi bir durum ile karşılaşırsanız tekrar kurulum gerekebilir. 

    Bu işlemlerin neticesinde problemin devam etmesi durumunda probleminizi buradan bizimle paylaşırsanız yardımcı olmaya çalışabilirz.


    Konu ile ilgili mesajım sorununuzun çözümünde size fayda sağladı ise LÜTFEN "Yardımcı Olarak Oyla" üçgenine tıklayın. Saygılarımla Kaan Gürsoy
    25 Nisan 2011 Pazartesi 22:18

Tüm Yanıtlar

  • Merhaba HFZ61

    Bilgisayarınızın mavi ekran vermesi yazılımsal bir problem olabileceği gibi donanımdan kaynaklanan bir problem de olabilir.

    Öncelikle Başlat tıklayıp arama menüsüne msconfig   yazalım ve enter a basalım.

    Bu işlemi başlat / çalıştır/ msconfig şeklinde de uygulayabilirsiniz.

    Karşımıza çıkan ekranda Hizmetler bölümüne gelelim ve burada bulunan TÜM MİCROSOFT HİZMETLERİNİ GİZLE kutucuğunu işaretleyelim.

    Bu kutucuğu işaretledikten sonra sağ tarafta bulunan  TÜMÜNÜ DEVRE DIŞI BIRAK sekmesine tıklayalım.

    Bu işlemden sonra HİZMETLER sekmesinin yanında bulunan BAŞLATMA sekmesine gidelim ve burada bulunan TÜMÜNÜ DEVRE DIŞI BIRAK sekmesine tıklayalım bu işlemin ardından uygula ve tamam a tıklayalım

    Bilgisayarın yeniden başlatılması için bir yönerge ekrana gelecektir.Bilgisayarı yeniden başlat sekmesine tıklayalım.

    Bilgisayar açıldıktan sonra bir süre bu şekilde kullanalım ve mavi ekran hatası alıyormuyuz bunu kontrol edelim.

    Bu işlemlerden gerçekleşen herhangi bir hata olduğunda buradan paylaşırsanız yardımcı olamaya çalışabiliriz.


    Konu ile ilgili mesajım sorununuzun çözümünde size fayda sağladı ise LÜTFEN "Yardımcı Olarak Oyla" üçgenine tıklayın. Saygılarımla Kaan Gürsoy
    23 Nisan 2011 Cumartesi 13:26
  • Dediğiniz gibi yaptım. Yaklasık 45 dakikadır resetlenmedi. Hata dökümanını buraya yazayım. Umarım sorunu bulmanıza daha yardımcı olur. İlgilendiğiniz için teşekkür ederim tekrar. Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\041211-15568-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 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x82a02000 PsLoadedModuleList = 0x82b4a810 Debug session time: Tue Apr 12 20:24:17.547 2011 (GMT+3) System Uptime: 0 days 0:19:19.060 ********************************************************************* * 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
    25 Nisan 2011 Pazartesi 19:43
  • Merhaba HFZ61

    Sorununuz söylemiş olduğum işlemleri gerçekleştirdikten sonra devam ediyor ise aşağıdaki yönergeleri izleyiniz.

     

    http://cid-3abf63b02cec49f5.skydrive.live.com/browse.aspx/Dumpfiles?sa=475194785 adresinde bulunan 4 adet dump dosyasını bilgisayarınıza indirin ve indirmiş olduğunuz bu 4 adet dump dosyasını c:\windows\minidump      klasörüne kopyalayın.

    Bu işlemi yapmadan önce bilgisayarınızın yedeğini almanız önemle rica olunur. Aksi bir durum ile karşılaşırsanız tekrar kurulum gerekebilir. 

    Bu işlemlerin neticesinde problemin devam etmesi durumunda probleminizi buradan bizimle paylaşırsanız yardımcı olmaya çalışabilirz.


    Konu ile ilgili mesajım sorununuzun çözümünde size fayda sağladı ise LÜTFEN "Yardımcı Olarak Oyla" üçgenine tıklayın. Saygılarımla Kaan Gürsoy
    25 Nisan 2011 Pazartesi 22:18
  • Dediklerinizi uyguladım. Şimdi de bu hatayı veriyor. Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\041711-27190-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 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x82a12000 PsLoadedModuleList = 0x82b5a810 Debug session time: Sun Apr 17 20:57:01.612 2011 (GMT+3) System Uptime: 0 days 1:33:15.000 ********************************************************************* * 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 ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {7d4bc5d4, 2, 1, 82a7b0fc} *** WARNING: Unable to verify timestamp for luafv.sys *** ERROR: Module load completed but symbols could not be loaded for luafv.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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ********************************************************************* * 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+ * ********************************************************************* ********************************************************************* * 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+ * ********************************************************************* Probably caused by : luafv.sys ( luafv+1358 ) Followup: MachineOwner ---------
    1 Mayıs 2011 Pazar 18:04