NT6 JIT Crash

[Kardinal]

I have twice had a J.I.T exception caught that has crashed NT6. In both instances it was in the middle of price action where I did not have any open positions. I was able to get a screen shot of the Windows error message. Is there anywhere else I can look to get more detailed Debug information on the crash?

[NinjaTrader_Dierk]

- which provider/broker/data feed is that?
- which instrument?

[Kardinal]

ZenFire
Mirus Futures
eMini S&P

[NinjaTrader_Dierk]

Hmm ... we never experienced issues with this combination before (ES and ER2 are the most heavily traded instrument on Zen).

So we are left with general checks like:
- what windows version are you using?
- please make sure your machine is on latest windows service packs
- please verfify again your installation prerequesits (e.g. MS jet engine, see download page on web site)
- uninstalling and reinstalling .NET runtime and NT often makes a difference

[Kardinal]

I will look into these points... I don't want to uninstall today as I'm doing well so far with the trades - I'll try at the weekend and update this thread if it happens again.

[NinjaTrader_Dierk]

Sounds good. Which windows version are you on?

[Kardinal]

Windows XP Pro, SP2
Athlon XP 3000+
1GB RAM

Just checked Windows Update and there is .NET Framework 3 available. Should I get this or stick with .NET 2?

[NinjaTrader_Dierk]

Yes, NT6 requires .NET 2. Windows and machine are looking good.

[Kardinal]

I reinstalled .Net completely over the weekend. I had the first JIT error this morning again. I have attached the output. Interesting this time the error hasn't actually crashed NT6, I simply selected continue, and so far it is still running. I would like to get to the bottom of what is causing the error. Is there a Debug option I can enable somewhere to got more information on the NT processes?

[NinjaTrader_Dierk]

Sorry, there is no such debug option. Even if there was one it would not help, since the callstack indicates that (a) the crash happens deep inside the .NET framework (not in NT code)and (b) the failed code is not triggered by NT code but from within the .NET framework.

[Kardinal]

OK - that implies that the cause might be the indicator code as it is written in C# and would be a possible candidate for calling the .Net code. That points me in the right direction - thanks!