MrBean 

Hi Mike, we always meet under such inauspicious circumstances, well, it was just crashing and leaving behind crash log files, I've just finished deleting everything , I did have some custom indicators (made by pros) so I'm going to be very careful not to load anything suspicious.

"Just crashing" is also not real helpful. That's like saying "my car won't start" but not giving any clues as to what is actually happening, such as out of gas, alternator, battery, etc.

What do the trace files indicate? They will usually point to the problem, read from the bottom up.

If you can't ascertain from the trace files, then I would first uninstall and remove all DLL's from vendors and confirm that everything works 100% without a doubt before you add any of them back in.

Mike

I uninstalled and deleted all traces of NT and indicators, now adding them back one by one, so far so good.

It's usually caused by an Unhandled Exception. NT can deal with some of them without crashing, but not all.
That's why it's a good idea to use error traps in your custom indicators, especially during the development process.

It's always a good idea to look at your output window once in a while, to see if there are any runtime errors in your indicators.

After a crash, unhandled exceptions will usually print messages to the Trace File. UNLESS there is a Stack Overflow.

Stack Overflows are usually caused by infinite loops. They knock out the error handling and reporting capabilities, so do not leave any clues in the Trace file.

If you are able to zero in on the indicator that is causing your crashes, send it to me by PM. If I can find the cause of the problem, I will fix the indicator, explain the cause of the problem, and post the result in this thread.