TradingView desktop crashing on startup, randomly during the trading day, or after running for hours? These 7 fixes, in order of frequency, resolve roughly 95% of crash patterns on Windows 10 and 11.
TradingView desktop crashes on Windows have three dominant root causes, in order of frequency: a corrupted local cache (about half of all crashes — clearable in 60 seconds), a misbehaving community Pine Script indicator consuming memory or hanging the render loop (about a quarter of cases), and an outdated GPU driver causing the embedded chart renderer to fault (about 15% of cases). The remaining ~10% require a full reinstall. Crashes that began immediately after Windows Update typically trace to GPU driver mismatches, fixable via Microsoft's driver update guidance. Crashes that began after adding a community indicator from the public Pine Script library are almost always that indicator's fault.
Different crash patterns have different root causes. Match yours to one of these before trying fixes:
| Crash pattern | Most likely cause | Fastest fix |
|---|---|---|
| Crashes on startup, every time | Corrupted cache or GPU driver | Fix 1 (cache), Fix 3 (GPU) |
| Crashes when opening a specific chart | Indicator loop in saved layout | Fix 2 (indicators) |
| Crashes randomly during trading | Memory leak (indicator or too many windows) | Fix 4 (memory) |
| Crashes after 4+ hours of uptime | Cumulative memory leak | Fix 4 (memory), Fix 2 (indicators) |
| Crashes with Windows error dialog | GPU driver or third-party DLL | Fix 3 (GPU), Fix 6 (clean boot) |
Same fix as for "not loading" — corrupted cache is the #1 cause of crashes on startup.
Win + R, paste %AppData%\TradingView, Enter.Cache folder.If crashes started after you added a community Pine Script indicator, that's almost certainly the cause. Community scripts can have infinite loops, excessive request.security calls, or unbounded arrays that exhaust memory.
Shift while clicking the app icon to launch with extensions disabled.TradingView's chart renderer uses GPU acceleration. Outdated drivers (especially on iGPU systems) cause renderer crashes that take down the whole app.
Each open chart window uses 200–400 MB. Each active community indicator uses 50–200 MB. If TradingView's total memory in Task Manager exceeds ~3 GB sustained, you're at risk of crashes.
Ctrl + Shift + Esc), find TradingView, note its memory usage.If GPU driver updates don't help, TradingView's GPU renderer can be forced off. This makes charts slower but eliminates GPU-related crashes.
Re-enable once you've updated drivers. Software rendering is a fallback, not a permanent solution.
Third-party software (screen recorders, RGB controllers, anti-cheat drivers from games, certain VPN drivers) can inject DLLs into TradingView and cause crashes. Test with a clean boot:
Win + R, type msconfig, Enter.If the above don't help:
%LocalAppData%\Programs\TradingView and %AppData%\TradingView.Three main causes: corrupted cache (50% of cases), problematic Pine Script indicator (25%), outdated GPU drivers (15%). Remaining ~10% need a reinstall.
Memory leak — usually from a community Pine Script indicator or too many open chart windows. Watch Task Manager; if memory grows beyond 3 GB, identify the leaking indicator.
App prompts on next launch — accept it. Manually: Help → Send Bug Report. Reply within 1–3 business days.
No — runs identically well on both. If you see crashes only on Windows 11, the cause is GPU driver differences or kernel-mode anti-cheat from a gaming app.
Yes — rarely, via infinite loops or unbounded arrays. If crashes started after adding a community script, remove it.