MultiCharts 14.0 Release 7

MultiCharts 14.0 Release 7 build 24558 is out now!

This release features the highly requested Binance .US data source and broker profile as well as overall fixes and improvements.

You can check the change log in our blog.
>>>Go to Download page<<<

1) It appears that the ability to select an indicator by "right clicking on it" has disappeared. If you right-click on a plot indicator, the indicator does not get selected. As a consequence, you can no longer right click on it and launch the powerlanguage editor to edit the indicator source code.

2) For some reason, the MCsmartshutdown systematically pops up upon windows reboot. It requires confirmation to close "something", which prevents the proper automatic startup of MC.

Hello tcat,

1. Please make sure you do not have the “Orders and Data Series Dragging” mode enabled (Format -> Orders and Data Series Dragging). If it is on, you won’t be able to manage chart objects apart from orders and data series.

2. MCSmartShutdown’s function is to check whether all MultiCharts processes were successfully terminated to avoid possible issues when you launch the platform next time.
Next time you close MC, I’d recommend making sure there are no MC processes left in Task Manager -> Details tab -> Description column before starting the app again or just waiting a bit to let all the processes finish.

Hello Kate,

Thank you for your prompt follow-up and response.

Regarding point 1), I confirm the approach you mentioned and the issue has been solved.

Regarding point 2) on MCSmartShutdown, I still get the error message even after I ensured all MC processed were properly shutdown in the task manager. I still received error messages which refered to process 18324 or 18732, but I can't establish the link with an existing MC process.

Is there a log file which would help me clarify the source of the issue?

Thierry

Hello Kate,

Thank you for your prompt follow-up and response.

Regarding point 1), I confirm the approach you mentioned and the issue has been solved.

Regarding point 2) on MCSmartShutdown, I still get the error message even after I ensured all MC processed were properly shutdown in the task manager. I still received error messages which refered to process 18324 or 18732, but I can't establish the link with an existing MC process.

Is there a log file which would help me clarify the source of the issue?

Thierry

Thierry,

In the “MultiCharts64 modules” window of the SmartShutdown there’s a “Run Feedback to send bug report for analysis” button, please click it to send us a report. In the Feedback window please specify the steps to reproduce the issue and select the following options:
Attach a screenshot;
Attach log files…;
Attach minidump for crash analysis;
Upload collected data to Help Desk;
uncheck other options and click Send.

After we receive the report, our engineers will check it to analyze the reported behaviour.

this append few time ...

not realable to trade in real ! 24/24 7/7 365/365 !

please send me a link to reload release 6 who work better.

this append few time ...

Screenshot 2023-03-25 035452.png

Screenshot 2023-03-26 062820.png

Screenshot 2023-03-26 062849.png


not realable to trade in real ! 24/24 7/7 365/365 !

please send me a link to reload release 6 who work better.

Hello Smoky,

GDI Object limit is a limit of the OS.
GDI objects are all objects that form the MultiCharts window and charts in it (all toolbars, menus, buttons, bars, drawings, etc.). The Windows system limitation per one process is 10,000 objects. For stability reasons MultiCharts has put a limit of 7,500 GDI objects per MultiCharts process.
The alert you are referring to appears in advance to warn you about the GDI Objects reaching the limit in order to avoid the MC processes being terminated. In order to avoid it, you can run multiple instances of MultiCharts application (run MultiCharts several times). Each instance will be able to handle up to 7,500 objects.

As for the Application Error, if you encounter it again, please send us the report as described below so we could investigate what caused it. It is important to collect it at the moment when the issue is reproduced, before MultiCharts is restarted.

Here is how to do that:
Windows Start Menu -> MultiCharts folder -> Feedback. In the Feedback window please specify the steps you took before the error occurred, then check the following boxes:
Attach a screenshot;
Attach Log files…;
Attach minidumps…;
Upload collected data to help desk; and click Send.

If you'd prefer to downgrade to Release 6 after that, you can download it here.

thanks i download R6
i already send files with MC windows send report

thanks i download R6
i already send files with MC windows send report

Hello Smoky,

If you sent an automatic report, kindly let me know via email or private messages which email address was specified.

why i already get R8 ?


about MC click

Version: MultiCharts64 Version 14.0 Release (Build 24673) Login: xxxxxxx User ID: xxxxxxxxx

why i already get R8 ?


about MC click

Version: MultiCharts64 Version 14.0 Release (Build 24673) Login: xxxxxxx User ID: xxxxxxxxx

Hello Smoky,

Release 8 is the latest one at the moment.
If required, Release 7 can be downloaded here.

I try on another laptop, i get many reboot !

here the dump file txt :

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Wed 07/06/2023 22:10:06 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\060723-7484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x42B8F0)
Bugcheck code: 0x101 (0xC, 0x0, 0xFFFF8481879C0180, 0xB)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 06/06/2023 02:29:26 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\060623-6484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x42B8F0)
Bugcheck code: 0x101 (0xC, 0x0, 0xFFFFC6003E975180, 0xA)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 02/06/2023 12:56:59 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\060223-6328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x42B8F0)
Bugcheck code: 0x101 (0xC, 0x0, 0xFFFFE68099175180, 0xA)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 01/06/2023 19:48:11 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\060123-10125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x42B8F0)
Bugcheck code: 0x124 (0x0, 0xFFFF880A85883028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 30/05/2023 10:35:59 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\053023-6203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x42B8F0)
Bugcheck code: 0x124 (0x0, 0xFFFF8F0B8F8CB028, 0xB2000000, 0x30005)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

i switch back on 7 june with R7 and all is fine now, no more crash ! same laptop No change, I delete R8 not the datas and instal R7 ...

Kernel use on R8 ? new functions who crash ?

Hello Smoky,

Please send us a report via the main MultiCharts window -> Help -> Feedback.
In the description field please specify the time of the issue, the steps to reproduce the issue or the steps you took before it occurred.
Then select the following options:
Attach a screenshot;
Attach log files…;
Attach minidump for crash analysis;
Include Backup of Logs from previous sessions;
Upload collected data to Help Desk;
uncheck other options and click Send.

GRRRRRRR

control right digital FAIL AGAIN I LOST ALL MY TRADES CAN'T CLOSE MY POSITION IN AUTO TRADE ! ! ! !
real BUG never connect again i start a new instance who have rights to trade but quotemanager lost all datas from last start ! ! !

I use a small script autokey to flush data every 10 minutes but quotemanager don't save quotes when i retreive right to trade MC have to download data again and i loose time again to close my positions autotrading don't start quikly GRRRRRR.

I have paid 3 lifetimes licences and i can't use your software to trade my stategies GREAT !

Yours DRM servers seems to have problems again, i'm in asia region:
all others softwares are runing well online !

Laptop and router on UPS ...

Hello Smoky,

There were no issues with our server, and we have not received similar reports from other users.
Please send us a report as described above so that we could analyze the case.

Another DRM issue, by luck i was in front of my computer and i saw all.

I was using internet with other software with not any problem, i use a software to monitor my internet issue and here you will find the sceenshot NO LINK LOST !
when i reload MC immediatly , no issue with DRM and it's starting "Online" !
i run speedtest during drm issue ! to show you that my internet is working full speed !
i hope now you will trust me ...

Hello Smoky,

As specified above, we need logs to analyze the case.
Have you sent us a report via the Feedback app?