Meta Trader 4 crash details

New comment
 

This keeps happening, usually when there are many orders - and usually while I'm sleeping or away. It's happening at 2 different brokers. The brokers told me to reinstall the platform, which I did. Still happens.


There has been a critical error

Time : 2010.06.01 21:36
Program : Client Terminal
Version : 4.00 (build: 226, 24 Mar 2009)
OS : Windows Vista Professional 6.1 (Build 7600)
Processors : 2 x X86 (level 15)
Memory : 2097151/1929984 kb
Exception : C000001D
Address : 00554EFF
Access Type : NA
Access Addr : 00000000

Registers : EAX=00000002 CS=001b EIP=00554EFF EFLGS=00010202
: EBX=03A4B449 SS=0023 ESP=0655B21C EBP=24648D00
: ECX=0655B1BC DS=0023 ESI=0655F825 FS=003b
: EDX=77B764F4 ES=0023 EDI=0655F818 GS=0000

Stack Trace : 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000

Modules :
1 : 00400000 004BB000 c:\program files\metatrader 4 at forex.com\terminal.exe
2 : 10000000 0001F000 c:\windows\system32\iavlsp.dll
3 : 66020000 0011C000 c:\windows\system32\mfc42.dll
4 : 6E540000 0008A000 c:\windows\system32\odbc32.dll
5 : 70420000 00038000 c:\windows\system32\odbcint.dll
6 : 708D0000 00012000 c:\windows\system32\pnrpnsp.dll
7 : 708F0000 00010000 c:\windows\system32\napinsp.dll
8 : 70A60000 00008000 c:\windows\system32\winrnr.dll
9 : 70B30000 00006000 c:\windows\system32\rasadhlp.dll
10 : 70B40000 00025000 c:\program files\bonjour\mdnsnsp.dll
11 : 738E0000 00038000 c:\windows\system32\fwpuclnt.dll
12 : 739F0000 00007000 c:\windows\system32\winnsi.dll
13 : 73A00000 0001C000 c:\windows\system32\iphlpapi.dll
14 : 73C00000 00005000 c:\windows\system32\msimg32.dll
15 : 73C20000 00007000 c:\windows\system32\midimap.dll
16 : 73C30000 00014000 c:\windows\system32\msacm32.dll
17 : 73C50000 00036000 c:\windows\system32\audioses.dll
18 : 74190000 00010000 c:\windows\system32\nlaapi.dll
19 : 741A0000 00004000 c:\windows\system32\ksuser.dll
20 : 74250000 00030000 c:\windows\system32\wdmaud.drv
21 : 74360000 00032000 c:\windows\system32\winmm.dll
22 : 743A0000 00008000 c:\windows\system32\msacm32.drv
23 : 748C0000 00040000 c:\windows\system32\uxtheme.dll
24 : 74900000 000F5000 c:\windows\system32\propsys.dll
25 : 74A00000 00039000 c:\windows\system32\mmdevapi.dll
26 : 74B90000 0019E000 c:\windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_421189da2b7fabfc\comctl32.dll
27 : 751C0000 00005000 c:\windows\system32\wshtcpip.dll
28 : 751D0000 00007000 c:\windows\system32\avrt.dll
29 : 751E0000 00021000 c:\windows\system32\ntmarta.dll
30 : 754D0000 0003B000 c:\windows\system32\rsaenh.dll
31 : 755B0000 00044000 c:\windows\system32\dnsapi.dll
32 : 756F0000 0003C000 c:\windows\system32\mswsock.dll
33 : 75730000 00016000 c:\windows\system32\cryptsp.dll
34 : 75B90000 0001A000 c:\windows\system32\sspicli.dll
35 : 75C00000 0000C000 c:\windows\system32\cryptbase.dll
36 : 75C70000 0000E000 c:\windows\system32\rpcrtremote.dll
37 : 75D30000 00027000 c:\windows\system32\cfgmgr32.dll
38 : 75D60000 0004A000 c:\windows\system32\kernelbase.dll
39 : 75F60000 00012000 c:\windows\system32\devobj.dll
40 : 75F80000 000A1000 c:\windows\system32\rpcrt4.dll
41 : 76030000 00019000 c:\windows\system32\sechost.dll
42 : 76190000 000A0000 c:\windows\system32\advapi32.dll
43 : 76230000 0007B000 c:\windows\system32\comdlg32.dll
44 : 764B0000 000C9000 c:\windows\system32\user32.dll
45 : 76580000 0001F000 c:\windows\system32\imm32.dll
46 : 765A0000 00083000 c:\windows\system32\clbcatq.dll
47 : 76630000 00057000 c:\windows\system32\shlwapi.dll
48 : 766E0000 0000A000 c:\windows\system32\lpk.dll
49 : 766F0000 00006000 c:\windows\system32\nsi.dll
50 : 76700000 000AC000 c:\windows\system32\msvcrt.dll
51 : 767B0000 0009D000 c:\windows\system32\usp10.dll
52 : 76850000 0008F000 c:\windows\system32\oleaut32.dll
53 : 768E0000 00045000 c:\windows\system32\wldap32.dll
54 : 76930000 00C49000 c:\windows\system32\shell32.dll
55 : 77580000 000D4000 c:\windows\system32\kernel32.dll
56 : 77660000 000CC000 c:\windows\system32\msctf.dll
57 : 77830000 0019D000 c:\windows\system32\setupapi.dll
58 : 779D0000 0015C000 c:\windows\system32\ole32.dll
59 : 77B30000 0013C000 c:\windows\system32\ntdll.dll
60 : 77C70000 00035000 c:\windows\system32\ws2_32.dll
61 : 77D10000 0004E000 c:\windows\system32\gdi32.dll

Call stack :
 
Just advice: Delete all *.ex4 files in /experts and /experts/indicators directories.
 
eliteeservices:

This keeps happening, usually when there are many orders - and usually while I'm sleeping or away. It's happening at 2 different brokers. The brokers told me to reinstall the platform, which I did. Still happens. [...]

There's nothing to indicate a problem external to MT4. Roger is basically suggesting an issue with the build number used to compile an EA versus the build number you're using (e.g. see https://www.mql5.com/en/forum/117233), and that recompiling all EAs will make a difference.

If that doesn't work, I'd try downgrading to build 225. Despite the tiny published list of changes (https://www.mql5.com/en/forum/124812), MetaQuotes have clearly done something substantial in build 226: its terminal.exe is almost 1MB smaller than build 225's.

 
jjc:

Roger is basically suggesting an issue with the build number used to compile an EA versus the build number you're using (e.g. see https://www.mql5.com/en/forum/117233), and that recompiling all EAs will make a difference.

Yap, last Metalang build was identical between 224 and 225 (both had Metalang build 224). But this time around there's an update to 226.

 

Response from mt4 broker:


We recently released the most recent build 226 for MetaTrader 4.

Any and all EA’s or custom indicators will need to be compiled, (via the MetaEditor) to build 226.

Typically, this occurs when programs written in build 225 are not updated to build 226 for used by compiling them to the updated build in the Editor.

This is a known issue by MetaQuotes and eventually occurs for any mismatching build/programmed EA.

It is recommended that you save all Expert Advisors and indicators to another file location, uninstall the MetaTrader 4 through Control panel, delete the MetaTrader 4 at Forex.com file from Program Files, then reinstall.

Then, before you launch the program again

1) Copy and paste all indicators and EA’s back to the Experts Folder

2) Open the MetaEditor from the recently downloaded MetaTrader 4 in the Program Files folder

3) Be sure the EA’s and indicators are in the list to the right, and click Compile button at the top of the screen for each indicator/EA you use.

 

Contrary to what you suggest eliteeservices -

I downloaded a new version from my broker onto a clean machine. It was then live updated to 226. I wrote an EA from scratch and it crashed regularly. I went back to 225 and all is fine.

-Jerry

 

Hello,

My broker has advised me that this issue will be fixed in the next version. Can you verify if this is true? And if so, how long will this be.


Regards

Dolmio




eliteeservices:

Response from mt4 broker:


We recently released the most recent build 226 for MetaTrader 4.

Any and all EA’s or custom indicators will need to be compiled, (via the MetaEditor) to build 226.

Typically, this occurs when programs written in build 225 are not updated to build 226 for used by compiling them to the updated build in the Editor.

This is a known issue by MetaQuotes and eventually occurs for any mismatching build/programmed EA.

It is recommended that you save all Expert Advisors and indicators to another file location, uninstall the MetaTrader 4 through Control panel, delete the MetaTrader 4 at Forex.com file from Program Files, then reinstall.

Then, before you launch the program again

1) Copy and paste all indicators and EA’s back to the Experts Folder

2) Open the MetaEditor from the recently downloaded MetaTrader 4 in the Program Files folder

3) Be sure the EA’s and indicators are in the list to the right, and click Compile button at the top of the screen for each indicator/EA you use.

 

Use Process Explorer from http://technet.microsoft.com/en-us/sysinternals/default.aspx to detect if MT4 use a lot of resource. Crash occur usually because MT4 using too many processor resource.


Your MT4 probably has .ex4 that has unlimited loop ('while' or 'for' process) or one that require huge calculation like calculating polynomial regression.

New comment
Reason: