The number is almost certainly a memory address, making it useless for troubleshooting, since it's going to vary depending on what else the computer has going on. Errors that reboot the computer are usually errors that corrupt core memory areas or hardware drivers. So whatever happened basically made your computer fail by corrupting an essential memory location.
As to what happened ... well, that could be hard to figure. Start with the basics: are all the module and include files intact and being referenced properly; are all the variables being passed correct; is the compiler looking at the correct versions? In my experience, these kind of "no useful message" errors are nearly always module related, so that's where I would start looking. Also, make sure none of your source files themselves have been corrupted due to an improper shutdown, or something of that nature.
I am getting a little tired of re-compiling my workspace; getting this same compiler error. I am using Win 7 Pro 64 bit...with Netlinx Studio 4.1.1251
I can hit the compile button and fail... and it can fail 2-5 times, then a successful compile occurs...without changing anything. Anyone else having this annoying trouble?
I am getting a little tired of re-compiling my workspace; getting this same compiler error. I am using Win 7 Pro 64 bit...with Netlinx Studio 4.1.1251
I can hit the compile button and fail... and it can fail 2-5 times, then a successful compile occurs...without changing anything. Anyone else having this annoying trouble?
I do get this behavior occasionally as well. I started noticing it a lot in NS3xxx
NS4xxx has been better but it's still there. There are times when I have to restart NS to get it to quit.
I used to get it a lot more, and one thing that seemed to help was adding an exclusion to my anti-virus software for the folder structure where I keep my amx working code.
I am using a SSD-drive for both C:\ and \ because the speed of another program (hello! DTools and Lutron QS). My project files etc do not have anything to do with a "syncing" Dropbox or Qsync (Qnap NAS). I do have McAfee antivirus, and I will try disabling it to see if that helps next time I get a flurry of crashes.
AMX is claiming that no one is calling in to report these compiler crashes...I know I am not the only one, it would be nice if y'all could jump on the bandwagon (email at least) and report these issues (the squeaky wheel gets the grease). I am going to email them a link to this thread; don't think it will help much, but the annoyance level is high and I would like to see it get resolved.
Comments
As to what happened ... well, that could be hard to figure. Start with the basics: are all the module and include files intact and being referenced properly; are all the variables being passed correct; is the compiler looking at the correct versions? In my experience, these kind of "no useful message" errors are nearly always module related, so that's where I would start looking. Also, make sure none of your source files themselves have been corrupted due to an improper shutdown, or something of that nature.
I am getting a little tired of re-compiling my workspace; getting this same compiler error. I am using Win 7 Pro 64 bit...with Netlinx Studio 4.1.1251
I can hit the compile button and fail... and it can fail 2-5 times, then a successful compile occurs...without changing anything. Anyone else having this annoying trouble?
I do get this behavior occasionally as well. I started noticing it a lot in NS3xxx
NS4xxx has been better but it's still there. There are times when I have to restart NS to get it to quit.
I am using a SSD-drive for both C:\ and
AMX is claiming that no one is calling in to report these compiler crashes...I know I am not the only one, it would be nice if y'all could jump on the bandwagon (email at least) and report these issues (the squeaky wheel gets the grease). I am going to email them a link to this thread; don't think it will help much, but the annoyance level is high and I would like to see it get resolved.
Thanks for reading.