Metatrader problem...help!!!

Hi all

I've had some problems with metatrader recently when installing certain new indicators, but once removing them it's been fine. a message would come up apologising for the crash and then it would crash.

Anyway, today I uploaded a metatrader update and it worked fine earlier but now it just crashes and this time no message comes up. Is this some sort of trial period restriction or something like that...any ideas would be appreciated.

Thanks in advance.

Bobby

Withor without the new indicators?

If it's with, try removing them from the experts/indicators directory.

I updated to build 207 today w/IBFX , no problems so far, though I have had some problems in the past, and still have some indicators/eas that no longer work. One thing you might try, though- look at the indicator/ea file that is no longer working, and if it is a .mq4 instead of .ex4 extension, right-click on it and hit modify, if it is a .mq4 file, clicking modify will open it in the metaquotes editor, click compile, then exit the editor- this will re-compile the file w/the new compiler, if it has been updated, and you should be able to reload it by attaching it to a chart. Hope this helps.

The critical error message doesnt come up any more and the the chart hasnt updated either to the most current time.

I'm using apari for my data.

I've tried deleting the most current indicators/templates I've saved but still nothing.

Maybe uninstall and reinstall...a bit drastic so want to try all other options 1st.

I've just deleted every new indicator I had added...now seems to work...thanks for your help guys,

Why is it that indicators that are working fine all of a sudden just make metatrader crash?

Something in the new build? Or you might have loaded an indicator it didn't like.

I had that problem, anytime I loaded my NZD profile it would freeze metatrader. Eventually had to go delete all my indicators out and add 1 at a time back. Annoying, but thats what Saturdays are for.

Hi

I would like to restart this thread as I've been experiencing similiar problem with my MT4.

I was running single instance of terminal.exe on a VPS with 20 EAs working (of two kinds) - everything was running smoothly without any crashes. I added another 3 EAs (still the same version of the one previously utilized) and since then I started to experience crashes each day. Despite the fact that both terminals seem to excess neither RAM nor proccessor capability of the VPS, I decided to install another instance of MT4 and move some of the EAs over there. The problem still occurs (on that "new" terminal). Below I enclose an error message - can somebody elaborate on this and help me to point out the reason for crashes?


I would be grateful for any quick help.

Best regards
Tomasz


-----------------------------------------------------------------------

There has been a critical error
Time : 2010.05.31 10:56
Program : Client Terminal
Version : 4.00 (build: 226, 24 Mar 2009)
OS : Windows 2003 Server 5.2 Service Pack 2 (Build 3790)
Processors : 4 x X86 (level 6)
Memory : 1228800/1037408 kb
Exception : C0000005
Address : 0051E004
Access Type : read
Access Addr : 78CF4E38
Registers : EAX=78CF4E38 CS=0023 EIP=0051E004 EFLGS=00010206
: EBX=00000000 SS=002b ESP=002CC538 EBP=002CC554
: ECX=050A0020 DS=002b ESI=78CF4E38 FS=0053
: EDX=73C54E18 ES=002b EDI=04FF9A08 GS=002b
Stack Trace : 00549AAC FFFFFFFE 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
Modules :
1 : 00400000 004BB000 crogram files (x86)alpari uk_mt4_2terminal.exe
2 : 00980000 0009B000 c:windowssyswow64advapi32.dll
3 : 04220000 0008B000 c:windowssyswow64oleaut32.dll
4 : 042B0000 00052000 c:windowssyswow64shlwapi.dll
5 : 04750000 00017000 c:windowssystem32odbcint.dll
6 : 053A0000 002C5000 c:windowssystem32xpsp2res.dll
7 : 48890000 0003D000 c:windowssystem32odbc32.dll
8 : 5F270000 0005A000 c:windowssystem32hnetcfg.dll
9 : 71AE0000 00008000 c:windowssystem32wshtcpip.dll
10 : 71BB0000 00009000 c:windowssystem32wsock32.dll
11 : 71BF0000 00008000 c:windowssystem32ws2help.dll
12 : 71C00000 00017000 c:windowssystem32ws2_32.dll
13 : 73EB0000 00121000 c:windowssystem32mfc42.dll
14 : 76190000 00012000 c:windowssyswow64msasn1.dll
15 : 761B0000 00093000 c:windowssyswow64crypt32.dll
16 : 76280000 00005000 c:windowssystem32msimg32.dll
17 : 762B0000 00049000 c:windowssyswow64comdlg32.dll
18 : 76AA0000 0002D000 c:windowssystem32winmm.dll
19 : 77210000 000AB000 c:windowssyswow64wininet.dll
20 : 77670000 00139000 c:windowssyswow64ole32.dll
21 : 77BA0000 0005A000 c:windowssyswow64msvcrt.dll
22 : 7C8D0000 007FE000 c:windowssyswow64shell32.dll
23 : 7D4C0000 00130000 c:windowssyswow64kernel32.dll
24 : 7D600000 000F0000 c:windowssystem32ntdll.dll
25 : 7D800000 00090000 c:windowssyswow64gdi32.dll
26 : 7D8D0000 00050000 c:windowssyswow64secur32.dll
27 : 7D930000 000D0000 c:windowssyswow64user32.dll
28 : 7DA20000 000E0000 c:windowssyswow64rpcrt4.dll
29 : 7DB30000 00080000 c:windowssystem32mswsock.dll
30 : 7DBD0000 00103000 c:windowswinsxswow64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.3790.3959_x-ww_5fa17f4ecomctl32.dll
31 : 7DF50000 00070000 c:windowssystem32uxtheme.dll
Call stack :