(02-12-2010, 03:22 PM)Beaverbeliever Wrote: This isn't a server crash, its client timeout.
I guess I wasn't clear in my last reply. Sorry.
Anyway, my suggestion about .mdmp, is not relevant to the timeout issue, so please disregard that.
(I didn't have that originally, just that afterward I got mixed up with another thread in this forum, then somehow came back and added the .mdmp suggestion...)
Anyway, regarding the timeout issue (caused by the server side),
1)
To start, at least we need to know:
- which game?
- log files of the game, and of the plugins.
Usually the above are not helpful, but they are the starting point.
2)
As for my own servers, random client timeout happened before, due to:
- my firewall was doing packet filtering.
- inappropriate TCP buffer settings // when I was using Linux.
I assume dualcore1289 is using default network settings, but if problem persists and nothing else works, double-check services and group policy, to examine the related settings.
(02-12-2010, 03:22 PM)Beaverbeliever Wrote: Also, I try to open those files with several encryptions under Notepad++, and it is barely readable. I honestly don't see the reason for these files.
The .mdmp file is very useful for examining crash issues in Windows, so I would like to mention a bit about using it:
1)
Cannot view it with notepad++. (Maybe a line or two would be displayed properly)
2)
You need two things from Microsoft:
- WinDbg 32-bit (
link), or WinDbg 64-bit (
link)
- Windows Symbol Package (
link)
3)
Then, open the .mdmp file as in the following:
4)
Those register infos are only useful for local debugging, as you have to trace them locally, and it is just too much work anyway.
Most of the time the .mdmp shows which file(s) is causing the issue, and the error code. As in my pic, it is:
- ntdll.dll