server 2003 sistem ...
 
Bildirimler
Hepsini Temizle

server 2003 sistem ciddi bir hatadan kurtarıldı hatası ve mavi ekran  

  RSS
ercan özçapkın
(@ercanozcapkin)
Üye

arkadaşlar merhaba exchange server kurulu olam makinamız, açılışta sistem ciddi bir hatadan kurtarıldı katası veriyor ve bu hata sürekli ekranda

Olay Kimliği: 1003

Kaynak: Sistem

Açıklama: code 000000d1, parameter1 f94ec0da, parameter2 00000002,
parameter 3 00000000, parameter4 f94ec0da

 şeklinde bir event id mevcut, sistem belli aralıklarla restart oluyor ve mavi ekrana düşüyor memory check yaptıktan sonra tekrar açılıyor yeni bir donanım vs kurulmadı makineye memorydump dökümü aşağıdadır yardımcı olabilek arkadaş varsa memnun olurum

 

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Documents and Settings\ercano\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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+                                    *
*********************************************************************
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe -
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (8 procs) Free x86 compatible
Product: LanManNt, suite: Enterprise TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.100216-1301
Machine Name:
Kernel base = 0xe0800000 PsLoadedModuleList = 0xe08a6ea8
Debug session time: Wed Jun 23 08:59:57.149 2010 (GMT+3)
System Uptime: 0 days 0:19:07.015
*********************************************************************
* 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+                                    *
*********************************************************************
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe -
Loading Kernel Symbols
...............................................................
.................................................
Loading User Symbols

Loading unloaded module list
......
*** ERROR: Module load completed but symbols could not be loaded for netbt.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {54, d0000002, 1, f2799984}

*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** ERROR: Module load completed but symbols could not be loaded for tmtdi.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for tcpip.sys -
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                     ***
***                                                                   ***
*************************************************************************
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for NDIS.sys -
*** ERROR: Module load completed but symbols could not be loaded for bxnd52x.sys
*** ERROR: Module load completed but symbols could not be loaded for bxvbdx.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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 : netbt.sys ( netbt+1984 )

Followup: MachineOwner
---------

 

Alıntı
Gönderildi : 23/06/2010 14:34
Alper OZDEMIR
(@alperozdemir)
Üye

Sistem için gereken sembolleri yüklememişsiniz veya yanlış sistem için sembol kurmuşsunuz microsofttan kendi sisteminize uygun sembol dosyalarını dowload edip örnek olarak c:\sembol dizinine açtıktan sonra tekrar debugger e girip file kısmından sembol dizinini eklemeniz gerekiyor ardından !analyze -v komutunu yürüterek detaylı bilgi alabilirsiniz sorun hakkında. Aşağıdaki makalede detaylı anlatılıyor göz atabilirsiniz.


 


http://www.cozumpark.com/blogs/windows_server/archive/2008/08/03/microsoft-diagnostics-and-recovery-toolset.aspx

CevapAlıntı
Gönderildi : 23/06/2010 14:38
ercan özçapkın
(@ercanozcapkin)
Üye

teşekkür ederim inceliyorum makaleyi

CevapAlıntı
Gönderildi : 23/06/2010 14:58
ercan özçapkın
(@ercanozcapkin)
Üye

peki bu sembol files hangi lokasyonda bulunuyor? system 32 altındamı? birde makaledeki link kırık bu doğru symbol files nereden indireceğim daha doğrusu doğru sybol files olduğunu konfigurasyondanmı çözeceğim?

CevapAlıntı
Gönderildi : 23/06/2010 15:11
Alper OZDEMIR
(@alperozdemir)
Üye

Merhaba aşağıdaki linkten uygun dosyayı çekip 2003 sp1 se farklı sp2 ise farklıdır indirme bittikten sonra tıklıyorsunuz size dosyayı nereye açacağınızı soruyor. C.\symbol dizinini örnek olarak verdim istediğibiz yere açabilirsiniz açtıktan sonra programa path i verip ardından dump dosyasını seçip ardından komutu yürütüyorsunuz bu kadar. SP2 için olanların kısa yolunuda veriyorum farklıysa linkten indiriniz.


http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx


Windows Server 2003 Service Pack 2 x86 retail symbols, all languages  Windows 2003 32 bitler için


Windows Server 2003 with Service Pack 2 x64-based retail symbols, all languages  Windows 2003 64 bitler için


 

CevapAlıntı
Gönderildi : 23/06/2010 15:23
ercan özçapkın
(@ercanozcapkin)
Üye

Alper Bey çok teşekkür ederim yardımlarınız için

CevapAlıntı
Gönderildi : 23/06/2010 15:52
Alper OZDEMIR
(@alperozdemir)
Üye

Ben teşekkür ederim kolay gelsin.

CevapAlıntı
Gönderildi : 23/06/2010 16:27
Paylaş: