First have a look at the trace file. It should tell you something about the offensive indicator or strategy.
If you look for an answer from us, we would need more information. Which datafeed do you use? Which indicator or strategy caused the problem? What was the lookback period of your tick chart? Which was the instrument? How many other indicators were on your chart? How much RAM has your PC?
Due to time constraints, please do not PM me if your question can be resolved or answered on the forum.
Need help? 1) Stop changing things. No new indicators, charts, or methods. Be consistent with what is in front of you first. 2) Start a journal and post to it daily with the trades you made to show your strengths and weaknesses. 3) Set goals for yourself to reach daily. Make them about how you trade, not how much money you make. 4) Accept responsibility for your actions. Stop looking elsewhere to explain away poor performance. 5) Where to start as a trader? Watch this webinar and read this thread for hundreds of questions and answers. 6) Help using the forum? Watch this video to learn general tips on using the site.
If you want to support our community, become an Elite Member.
Thanks Fat Tails. I should have provided more information to start with. I was not having this issue ever it is only since past month that I have this issue. I was trying the elimination route to isolate the issue since I thought something else on my laptop could be causing this. I tested by using a naked chart with 15 day period look up using 4 Renko (previously I used to have 4 similar charts with 5-6 indicators on each). I suspect ever since I upgraded to the latest service pack that I have been having this issue. There is no issue with RAM or any other factor. I checked the trace file and could not get any material information over the issue.
forgive me if this is not remotely the problem -- but i have had similiar error when
programming and the code is run and it has hit a division by zero which it cannot cope
with.... are you running a strategy/indicator that you need to debug?