Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I think you need to start with a clean workspace and make sure that this is the only workspace open.
Then add indicators one by one until the problem reoccurs. It is quite easy to code an indicator in a way that it will freeze NinjaTrader. One single coding error in an indicator can be at the origin of your problems.
That said, I have no experience with the CQG adapter. If the CQG datafeed / server is not properly working ( I do not know whether NinjaTrader servers are used to host that datafeed), this may also be at the origin of the problem.
Or let me give another example. I am located in Europe. If the data server is in the US and there is a problem with the bandwidth of the transatlantic lines used by my internet provider, this will slow down the data feed, although the local transmission rate of the IP is perfect. I have had this once, and then shifted my data feed connection to a swiss server, and now I am no more relying on the transatlantic bandwidth of my IP provider, but the transatlantic bandwith of my data provider, which is more reliable.
These are just some ideas for causes for a freeze.
However, if your default workspace does not suffer, then it is probably not linked to bandwidth, unless you use a market analyzer with hundreds of instruments.
yes, on the 1000.7 here as well and not seeing any issues, rather an improvement since the market replay and sql fixes are in. don't see the updates as annoying, as i like my tools to be sharp and current )
I would suggest you radically trim down your setup as harry already outlined, somewhere in there the bottleneck is to be found and isolated. also I found it helps if you really put your 'non play' software on a serious and dedicated environment / machine, capped general internet access for those and do weekly maintenance on Sat before entering the weekend, helps to add discipline as well generally.
Remove also all 3rd party assemblies / dll's if not essentially needed, the cleaner the better - you can always install the 'to be tested and played with' stuff on another machine that would not be used for anything mission aka $ critical.
I'm still using NT 7.0.1000.5 'cos of all the bias NT 7.0.1000.5+ has towards Windows 7 and considering that I'm adamant on continuing with my Windows XP. So, do I really need to upgrade to NT 7.0.1000.8 ?
If you are the first to upgrade after a new release is out, you are calling for trouble. Best you wait about 2 or 3 weeks. After that period all minor bugs of the first upgrade tend to be fixed. You will be safe, if you upgrade to NT 7.0.1000.8 around Christmas.
This is similar as with a new model of a car. Don't buy the new model within the first six months after it has been released. Buy it after the minor problems that had not been discovered prior to production start are fixed.
But of course you want to get the new model! Don't keep driving your car from the Sixties.
You'll note that I'm still driving my old WinXP/NT car on NT 7.0.1000.5 engine ... I'm always careful on upgrades ... for example, I'm still running Mac OS X Leopard on my Mac machine instead of the Mac OS X Lion that has been available for some months now.
I'm just curious about this NT 7.0.1000.8 upgrade/release, specifically as regard NT's bias towards Windows 7.
Yes, I'll stick to my old WinXP/NT 7.0.1000.5 so long there is this NT 7.0.1000.6+ specifics on using Windows 7. I'll never upgrade my old Win OS until it dies a natural death or until the birth of Windows 8 or even 9.
Release 7.10 is out. I see the trickle of bug fixes has slowed to about 4 in two months, but no enhancements. I wonder what they're up to. There are plenty of really useful things on the list for years now. Some of them really really small, that wouldn't take long at all, and are wanted by more than one user, and have been outstanding for years.
Even though there's no real alternative for me, I'm still a bit irritated that I still spend so much time coding work arounds in Ninja. I have the feeling now that it'll never end.
) 
