NT8 Goes into "Suspended" when running on Windows 10 Pro

[dmking]

Occasionally, NT 8 will hang/freeze and if I look at Windows 10 Task Manager it will say "Suspended".

Most recently, i was running an optimization on a test strategy? It's happened before when I reconnect to Kinetick. Any ideas as to why this happens?

Running:

Windows 10 Pro
32 GB RAM
Intel i7 4930
NT8 version - 8.0.17.2 64-bit

[NinjaTrader_Kate]

Hello dmking,

Thank you for posting.

So that I may investigate, I would ask that you contact me by email at PlatformSupport [AT] NinjaTrader [DOT] com. In your message please include a link to this forum thread and a message 'ATTN Kate'.

Additionally, please follow the steps below to manually attach your log and trace files to your response so I may investigate this matter further.

• Open your NinjaTrader folder under My Documents.
• Right click on the 'log' and 'trace' folders and select Send To> Compressed (zipped) Folder.
• Send the 2 compressed folders as attachments to this email.
• Once complete, you can delete these compressed folders.

Thanks in advance; I look forward to resolving this item.

[NinjaTrader_Kate]

Hello dmking,

Thank you for your reply.

I received your log and trace files and have looked them over - unfortunately, they're not telling me much. I'm not seeing errors in there to point me in a particular direction.

How many workspaces do you have open? You can check this by going to the Workspaces menu - anything with a green or gray square in front of the name is open. The ones with the gray square are open and active, they're just running in the background and aren't currently visible. I usually recommend closing any workspaces you're not currently using, especially when doing backtesting or optimizations as those can get pretty CPU intensive.

How many charts are open in your primary workspace? Are they different instruments, or are you looking at the same instrument over differing time frames?

Thanks in advance; I look forward to assisting you further.

[dmking]

Kate,

Thanks for looking. I think it must be a system problem. I'll look at my end.