AdamC wrote:Reading through the forum when the issue first started on my machine caused me to despair at finding a solution to the error. It seemed random enough that I finally just attributed it to "cosmic rays". But then two other machines in our lab developed the same problem... So it's either something we cause or or as you say some bits of weirdness with our systems. We're a Forest Service research station so our machines are USDA issued: maybe that's the common denominator?
I do have some renewed hope that the issue will be diagnosed since it seems to have reemerged in the latest release.
There is a strong tendency for the few bug reports of this type to be based on *government* machines -- which are often strictly locked down, with all sorts of 'security' features which might get in the way (for example, it isn't hard to create a security policy that prevents non-signed, non-commercial applications from running. I tried to install a particular open-source PDF reader I use all the time on a colleagues machine (USGS), and it absolutely refused to open).
Get your IT folks to allow you to boot an offending machine into Safe Mode. If MARK runs, then something is being loaded when full Windows boots up that is causing the problem. If it is security policy related, such things are typically logged, although finding out *where* can be challenging.
Good luck!