%APPDATA%\MetaQuotes\Crashes
Forum on trading, automated trading systems and testing trading strategies
Slava, 2006.12.18 10:58
Thank You. At restarting client terminal sends crashlog file to the server automatically.
Answer from MetaQuotes :
"Crash report can be lost due to critical exception".
A crash is always a bug in the platform which should not crash. However it's in most cases triggered by some code running inside the platform, your EA or maybe an indicator.
You should either try to isolate the portion of code that triggers it, but as I understand that seems hard to reproduce in your case.
I would rather suggest you to upgrade, and not downgrade, as the developers received your crashlog, so they will check it and fix the problem. You can already try Build 3815 by downloading it from this site.
A crash is always a bug in the platform which should not crash. However it's in most cases triggered by some code running inside the platform, your EA or maybe an indicator.
You should either try to isolate the portion of code that triggers it, but as I understand that seems hard to reproduce in your case.
I would rather suggest you to upgrade, and not downgrade, as the developers received your crashlog, so they will check it and fix the problem. You can already try Build 3815 by downloading it from this site.
Build 3815 did not solve my problem, I had to wait until September for build 4000. Now, after more than one month without crashes, I can say that my problem is resolved!
I'm very happy, but disappointed because it's not possible to roll back to a previous version: MT5 autonomously decides to update and this can (of course) introduce a new bug. If you just want to try your previous version (which maybe worked perfectly), it has simply gone forever. I started having these problems in June, the solution came in September, with MT5 crashing every one or two days for 3 months!!!
If I could ask a new feature to MetaQuotes, this is the possibility to roll back to a previous version and a better control of the updates.
Now for example, as explained in my new post https://www.mql5.com/en/forum/456223, it seems that these new versions fixed a problem but introduced another bug. Maybe it's my fault, maybe it's an error that I introduced in my code, but if I cannot try on a platform that never showed a problem like this I can only hope and wait for a new update (and a new bug?) or spend hours in looking for a bug that could be not mine.
- 2023.10.23
- www.mql5.com
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
I'm experiencing some problems with build 3802: MT5 crashes every couple of days with erros like this in the log:
QQ 3 05:25:01.605 Exception C0000005 at 00007FF7CFD51F88 read to FFFFFFFFFFFFFFFF
CD 3 05:25:01.606 Exception C0000005 at 00007FFDDE40E55C read to FFFFFFFFFFFFFFFF
EQ 2 05:25:01.606 Terminal crashlog generated
I'm not using any external DLL, and MT5 also crashes if I only run strategies I compiled many weeks ago and used for a long time without any problem on previous versions of MT5.
Anyway, for better understanding what happened, I would like to have a look at this crashlog file, but I've not been able to find it. Any idea on where it is?
Thanks in advance!