Цитата(ArhangeL @ 13.8.2012, 14:24)

Fintok,
Уверяю, ничего интересно в этих дампах не найдешь =) Чтобы их смотреть, нужно иметь исходники того, чей этот дамп.
Если создаются дампы это не есть гуд. Реально надо же понять причину почему эти дампы каждый раз при запуске сервера создаются.
Код
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\dumps\assert_hlds.exe_20120812011524_1.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available
Comment: 'Assert( Assertion Failed: !m_bFindingBestServer ):udpconnection.cpp:1589
'
Windows Server 2003 Version 5.2.3790.3959 (Service Pack 2) MP (2 procs) Free x64 compatible
Product: WinNt, suite: SingleUserTS
Debug session time: Sun Aug 12 01:15:24.000 2012 (GMT+4)
System Uptime: not available
Process Uptime: 0 days 0:00:05.000
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:
................................................................................
..................................................
eax=040e0130 ebx=042f0210 ecx=040e0130 edx=380bd210 esi=000004e0 edi=00000000
eip=7c90e514 esp=0012ecf4 ebp=0012ed58 iopl=0 nv up ei ng nz ac po cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200297
Unable to load image C:\WINDOWS\system32\ntdll.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for ntdll.dll
*** ERROR: Module load completed but symbols could not be loaded for ntdll.dll
ntdll+0xe514:
7c90e514 c3 ret
0:000> !analyze –v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
***** OS symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for tier0_s.dll
*** ERROR: Module load completed but symbols could not be loaded for tier0_s.dll
*** WARNING: Unable to verify timestamp for steamclient.dll
*** ERROR: Module load completed but symbols could not be loaded for steamclient.dll
*** WARNING: Unable to verify timestamp for steam_api_c.dll
*** ERROR: Module load completed but symbols could not be loaded for steam_api_c.dll
*** WARNING: Unable to verify timestamp for swds.dll
*** ERROR: Module load completed but symbols could not be loaded for swds.dll
*** WARNING: Unable to verify timestamp for hlds.exe
*** ERROR: Module load completed but symbols could not be loaded for hlds.exe
*** WARNING: Unable to verify timestamp for filesystem_stdio.dll
*** ERROR: Module load completed but symbols could not be loaded for filesystem_stdio.dll
*********************************************************************
* 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 C:\WINDOWS\system32\advapi32.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for advapi32.dll
*** ERROR: Module load completed but symbols could not be loaded for advapi32.dll
*********************************************************************
* 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+ *
*********************************************************************
*** WARNING: Unable to verify timestamp for mysql_amxx.dll
*** ERROR: Module load completed but symbols could not be loaded for mysql_amxx.dll
*********************************************************************
* 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for CorperfmonExt.dll -
*********************************************************************
* 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 aspnet_perf.dll -
*********************************************************************
* 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+ *
*********************************************************************
*** WARNING: Unable to verify timestamp for aspnet_perf.dll
*** ERROR: Module load completed but symbols could not be loaded for aspnet_perf.dll
*********************************************************************
* 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+ *
*********************************************************************
Unable to load image C:\WINDOWS\system32\traffic.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for traffic.dll
*** ERROR: Module load completed but symbols could not be loaded for traffic.dll
*********************************************************************
* 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+ *
*********************************************************************
*** WARNING: Unable to verify timestamp for crashhandler.dll
*** ERROR: Module load completed but symbols could not be loaded for crashhandler.dll
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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 : tier0_s.dll ( tier0_s+e3eb )
Followup: MachineOwner
---------
Отредактировал: Fintok, - 13.8.2012, 19:01