Why Your Forex Charts Are Crashing: Top Platform Server Fixes

Before you troubleshoot an open position: if your platform has crashed while you hold trades, use your broker's web or mobile platform, or phone their dealing desk, to manage the position first. Fix the desktop terminal afterwards. This guide is technical help, not investment advice.

First, rule out the obvious

A surprising number of 'crashes' are not faults at all. Check these three things before anything else.

• Is the market open? Spot FX trades around the clock on weekdays, but closes from roughly 10pm UK time on Friday to 10pm on Sunday, as IG explains in its trading-hours guide. Flat, frozen charts over the weekend are normal.
• Is the broker or platform down? Check the broker's status page or social channels. TradingView publishes live service status at status.tradingview.com.
• Is it just one symbol? If a single pair stops updating while others move, the issue is usually that symbol's data feed or trading session, not your computer.

Read the logs: where each platform records errors

Guessing wastes time. Every major platform writes a log, and the log usually says what went wrong.

In MetaTrader 5, the log files live in the platform's Data Folder (open it from File → Open Data Folder). Each day gets its own file named in YYYYMMDD.LOG format, so the file for 15 October 2026 is 20261015.log. Keep a copy of the log from the day of a crash: your broker's support team will usually ask for it.

Fix 1: 'No connection' or 'Invalid account'

This is the most common message traders report, and it is often a login problem rather than a server fault.

• Check you are using the trading-account login, not your website username. IG, for example, notes that its MT4 login details differ from your IG username; use File → Login to Trade Account with the MT4 account number and password.
• Check the server name. Demo and live accounts sit on different servers. Picking a demo server for a live account (or the reverse) returns 'Invalid account'.
• Rescan servers. Several brokers, including RoboMarkets, document that clicking the 'No connection' status in the bottom-right corner of MetaTrader and choosing Rescan servers reconnects the terminal to the fastest available access point.
• Try an alternative server. Brokers such as FXCM publish alternative server addresses for when the main access point is unreachable. Check your broker's help centre.
• Check your firewall and VPN. A security update can block the terminal's outgoing connection. A VPN can route you to a distant or blocked network.

Fix 2: Charts freeze or the terminal runs out of memory

If the terminal connects but charts stop redrawing, or the whole program becomes unresponsive, it is usually overloaded.

MetaTrader 4 loads chart history from your computer's disk and tops it up from the server. If no history exists for a symbol, it downloads the most recent 512 bars, then more as you scroll back, according to the MT4 help on chart history. A terminal can hold up to 99 charts. That ceiling is not a target: dozens of open charts, each with heavy indicators, will exhaust most home computers.

• Reduce Max bars in chart (Tools → Options → Charts) and restart the terminal.
• Close charts you are not actively trading.
• Remove custom indicators and Expert Advisors one at a time to find the one that causes the freeze. The Journal tab often names it.
• Restart the terminal at least once a day if you run automated strategies.

Our guide to setting up a forex platform for lower latency covers these settings in more detail.

Fix 3: Corrupted or missing chart history

Gaps in charts, candles in the wrong place or a chart that will not load a symbol can mean the stored history is damaged.

In MetaTrader 5, history is stored in the Data Folder under Bases, in a folder for each trade server. A common approach is to close the terminal, rename (rather than delete) the folder for the affected server, then reopen the terminal so it downloads fresh history. Renaming keeps a backup you can restore if something goes wrong.

Many forum guides suggest deleting MT4's .hst and .hcc history files to force a re-download. This is community practice rather than documented MetaQuotes guidance, so back up the files first, close the terminal before touching them, and ask your broker's support team if you are unsure.

Fix 4: TradingView Desktop freezes or shows a blank screen

TradingView publishes its own troubleshooting steps for the desktop app. In order, they are:

• Close unused tabs. Each open tab runs its own charts and scripts.
• Clear the cache: Settings → Service → Clear cache.
• Reset the app: Settings → Service → Back to defaults, if clearing the cache does not help.
• Disable hardware acceleration if charts flicker, render blank or freeze. Graphics-driver problems are a frequent cause.
• Check [status.tradingview.com](https://status.tradingview.com/) before assuming the fault is local.

If you trade through a broker connected to TradingView, remember that order routing still depends on the broker. A frozen chart does not necessarily mean an order failed, so check the broker's own platform for the true position.

Fix 5: cTrader will not connect or keeps crashing

Spotware, which makes cTrader, publishes a connectivity issues guide. Its main steps are:

• Close every running instance of cTrader, including any minimised to the system tray.
• Delete the Spotware settings folder in AppData\Roaming on Windows, which resets the application's stored settings.
• Restart cTrader and log in again.
• Check your network, firewall and antivirus rules if the problem persists.
• Press Ctrl + Shift + Alt + T to generate a troubleshooting report to send to your broker.

Resetting the settings folder removes saved workspaces, so export anything you want to keep first if the app will open.

When the problem is the broker, not you

If the logs show repeated disconnections from the trade server while your internet connection is stable, and other users of the same broker report the same thing, the fault is probably on the broker's side. Contact support with:

• the date, time (UK) and duration of the outage;
• the account number and server name;
• the relevant log file and any order tickets affected;
• what you were trying to do at the time.

If you lose money because a firm's systems failed, complain to the firm in writing first. If you are unhappy with its final response, or it has not responded within eight weeks, you can usually take the complaint to the Financial Ombudsman Service. This route only exists if the firm is authorised in the UK, so check the FCA Register before opening an account.

Reduce the damage of the next crash

No platform is immune to outages. You can limit the impact.

• Place stop-loss orders on the broker's server, not just mental stops or terminal-side alerts.
• Install the broker's mobile app and log in once, so you are ready if the desktop fails.
• Save your broker's dealing-desk phone number somewhere you can find it quickly.
• Remember the FCA's retail CFD protections, including negative balance protection and a 50% margin close-out, which apply at FCA-authorised firms regardless of your platform's state.