EVE Online » ISXEVE

Crash Reporting¶

• Crash Reporting
• How to report an ISXEVE crash
  • Crash during extension load
  • Installing WinDBG
    • Running WinDbg
    • Attaching WinDbg to the Game
  • Submitting the Crash Report

How to report an ISXEVE crash¶

Crash during extension load¶

If EVE crashes the instant that you load ISXEVE or if ISXEVE is working fine one day, and then not working the next day - and there was an EVE patch in-between these instances , then you need to do the following:

• • Wait for a new release of ISXEVE (isxeve.dll) that is time-stamped later than your current ExeFile.exe. If you're impatient, come on IRC and help test.

Installing WinDBG¶

1. Download a copy of 'WinDbg' from Microsoft at

• http://msdn.microsoft.com/en-us/windows/hardware/gg463009

• Follow the instructions for 'Install Debugging Tools for Windows as a Standalone Component', unless you want the entire windows SDK (~400mb)

Running WinDbg¶

WinDbg link will be installed to the Start Menu under "Debugging Tools for Windows (x86)" or "Debugging Tools for Windows (x64)"

If you have the option, run the x86 version, otherwise the x64 is fine.

Attaching WinDbg to the Game¶

You can play EVE with the debugger attached forever without harming your playing experience.

You'll want to make sure you're playing in the windowed mode, not full screen mode -- otherwise you won't be able to get to WinDbg when the crash occurs.

1. Run WinDbg Before or after EVE loads, doesn't matter

1. Hit 'F6' and select "exefile.exe" from the list. This can be done at any time, as long as EVE hasn't crashed yet

1. Execute the following commands in WinDbg:
2. 1. !load wow64exts (It's ok if this fails, it's only in case you're running the x64 debugger)
3. 1. .effmach x86 (It's ok if this fails, it's only in case you're running the x64 debugger)

• Extended instructions are required for .NET applications

• Extended instructions result in a superset of Basic instruction logs, so if you want to run them anyway, feel free.

Debug Log¶

Execute the following commands in WinDbg:

1. .sympath SRV*C:\Temp*http://msdl.microsoft.com/download/symbols

1. Load SOS Debugging Extension, using one of the following methods: (stop as soon as it loads properly, which will mean it prints nothing)
2. 1. .load C:\Windows\Microsoft.NET\Framework\v4.0.30319\sos.dll (for .NET 4)
3. 1. .load C:\Windows\Microsoft.NET\Framework64\v4.0.30319\sos.dll (for .NET 4 using WinDbg x64)
4. 1. .load C:\Windows\Microsoft.NET\Framework\v2.0.50727\sos.dll (for .NET 2.0 thru 3.5)
5. 1. .load C:\Windows\Microsoft.NET\Framework64\v2.0.50727\sos.dll (for .NET 2.0 thru 3.5 using WinDbg x64)
6. 1. .loadby sos clr
7. 1. .loadby sos mscorwks
8. 1. .load sos

1. .chain

1. Hit 'F5' in WinDbg to resume EVE (until you press F5 EVE WILL BE HUNG)

1. Run your normal EVE procedures, unless otherwise requested

After crashing, type these commands in WinDbg: (You won't be able to until the debugger breaks on an exception, like it will on a crash)

Note, if you're not crashing, but instead hanging, go to Debug, Break in WinDbg AS SOON AS POSSIBLE after the hang.

1. kp

1. r

1. !DumpStack

1. !analyze -v

1. !analyze -v -hang (IF THIS IS A FREEZE/HANG, AND NOT A CRASH)

1. Edit Menu, 'Write Window Text to File', "ISXEVE_username.txt"

If this is for the extension, you go to 'Submitting the Crash Report' unless otherwise requested

If this is for a .NET application (Requested by a bot author), also run the following:

1. ~0 kp

1. ~0 r

1. ~*e !DumpStack

1. ~*e !DumpStackObjects

1. !clrstack -a -i (if this results in an error, remove the -i)

1. !Threads

1. Edit Menu, 'Write Window Text to File', "ISXEVE_DOTNET_username.txt"

Submitting the Crash Report¶

Email the file(s) to isxeve AT isxgames.com -- this will reach Amadeus and CyberTech

If using StealthBot, also email it to support AT stealthsoftware.net