What to do if the Server Crashes

[someone]

First method: Using DrWatson

A. Windows XP:

1. Press the Start button, choose Run, type drwtsn32 and hit Enter;

2. In the dialog that appears check the Log File Path and Crash Dump paths;

3. Set the Crash Dump Type to Full;

4. Make sure the Dump Symbol Table option is checked, then click the OK button;

5. Reproduce the issue;

6. drwtsn32.log and user.dmp files will be created in the directories specified in Log File Path and Crash Dump.

Which is usually:

\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson

 

B.Windows 7

1. Reproduce the issue (application crash);

2. Do not close the Application has stopped working window;

3. Run Task Manager (press Ctrl-Shift-Esc);

 

(!) If you are running a 64-bit operating system, run 32-bit Task Manager: C:\Windows\syswow64\taskmgr.exe

4. Go to Processes tab and right-click on the crashed process;

5. Select the Create Dump File item:

6. Pick the .DMP file created:

7. Open Start-Run, type %USERPROFILE%\AppData\Local\Microsoft\Windows\WER\ReportArchive string and hit Enter:

 

8. After that you will see a folder (or a few folders), the name of which starts with Report

9. Collect the Report.wer file from the last created folder.

 

When you post on the forum just post the dump file and the wer one(the second one is not hat necessary).

 

Second Method:Using Process Explorer(Only for 32Bit Systems)

1. Download Process Explorer

2

2. Wait till the server file crashed (do not close )

3. Go to Process Explorer, right click on your process ->create Dump->MiniDump(Or Full Dump)

 

Post the minidump(fulldump), on the forum.

[Warmonger]

The proper way is to attach a debugger and let that handle the problems.

 

So, download OllyDbg (a debugger). Well use it to catch the crash, and give us the information we need. Once downloaded, extract somewhere permanent (like C:\ollydbg). For as long as its setup, you should never move or rename this folder, otherwise it wont be able to catch any crashes for us!

 

Now run OllyDbg (you can say "yes" to removing the old PSAPI DLL). At the top, click on the menu "Options" and then select "Just-in-time debugging".

 

 

Hit the first button ("Make OllyDbg just-in-time-debugger"), and then hit "Done".

 

 

You can now exit OllyDbg, and proceed to trigger (or wait for) the next crash. When it crashes, Windows should ask you what to do - we want to "Debug" the server (or client!), so select "Debug" as shown below:

 

 

Finally, OllyDbg will appear - but its containing windows may not be fully visible. If theyre not shown as in the screenshot below, drag them out so theyre similar. Also note my comment in the below screenshot: scroll up 3 or 4 lines, so that we can see the code directly prior to where it crashed at.

 

 

Now youre good to take a screenshot and post it in your help thread!

[CADH]

Hello my Connecter always crashes after about 10 to 20 minutes.

And i have uploaded the 2 files."connector.dmp and report.wer".

[ATTACH=CONFIG]463[/ATTACH]

(Sry when i postet wrong here )

[Phyyl]

2

 

Hier der Dump

 

2

 

Hier der Screen.

 

Beim Connector steht immer

 

Cannot Update Player DB oder so

und immer die ID 47 also Spieler 47 disconnectet

warscheinlich wegen 52 spielern bei 52 crasht er immer.

 

2

[BashVendetta]

Only bad thing about these files is the Connector, I been dumping everytime it crashes and also monitoring behaviours in game, I found and fixed a few small problems but there is a big issue with how the server handles specific calls, guess eventually this will be fixed but these files are not stable enough.

[netoforlan]

help connector error

 

connector error 10 playes help

[roseon]

here one crash i can show

[someone]

posting Images will not work(read the guide).

[StyLeRZockeR]

Someone please look now why my Connector ever Crash ...

 

Here my Dump : 2