Let me know when you find a different answer and I will try your answer as well with HyperThreading on.
I may do a BIOS update and turn it back on, thanks for the tip but I get excellent perf on my machine with HyperThreading off in all my apps so in my case I don't see the big deal. Agree or Disagree it worked for me. I have no idea if it will work for others but when my kids in Tokyo were chatting with me and it became glacially slow, crashed, and took down several other apps many times a week I spend a hour each day on Google researching slowness, crashes with little fruitful answers (hitting all the way through page 20 of the search results, speedreading forums answers, etc. tedious stuff). One day I spent 4 hours one day just googling Y!M! crashes and slowness and the answers were all pretty worthless so I took a chance on a theory that for me panned out and for others won't. Its a Thinkpad G41 with 2 gigs of RAM, other hardware may not act like my Thinkpad but it sure ended my problem. If I turn back on hyperthreading, my Yahoo Messenger eats up all the CPU actions that take seconds tart taking minutes if it notices at all, it crashes, etc. Runs like a champ without it. I recommend you at least try it, but hey if you don't want to try it, its your crash/100% CPU problem and I hope you find an answer you like more. Not all solutions/errors are documented. I found no articles in Google about Y!M Hyperthreading bugs but that does not mean it is not a problem. Just an obscure one. I do know in the past when I was a Help Desk engineer supporting computer BIOS settings can often be the source of some bizarre computer behavior so I looked at what BIOS settings my Thinkpad has and it does not have a lot of settings to adjust except that. Its a pretty minimal low feature BIOS. The fact big name commercial and OS software has documented hyperthreading bugs means any software could have undocumented hyperthreading bugs. On 1/23/07, Wayne Harke <[EMAIL PROTECTED]> wrote:
I researched the issue about hyperthreading and I disagree with your advice to disable hyperthreading. It seems that there may be an issue with SQL server and hyperthreading but that's about it. The problem with hyperthreading doesn't seem to be hardware related, it seems software related and from what I've read, upgrading to the latest revision of the software solves any problem with hyperthreading. DIsabling hyperthreading in the BIOS seems to be drastic measure.
