Thanks for your help, we are running 3.2 and have hyperthreading off. I believe we found the source of the problem. It appears to actually be a RAM incompatibility combined with .NET corruption (clobbering manager procedures). Credit goes to the boss for ordering incompatible RAM. Thanks for...
Shot in the dark -- hopefully someone wise will see this. We're on the second stage of our rollout and our hardware vendor is unable to provide the model of PC that we were rolling out during the first phase of the rollout. He's provided us the "closest match" but in reality it's not all that...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.