Quote Originally Posted by JAZZCNC View Post
Not to be pedantic here Irving but YES it is a far better "Explanation" and more accurate Answer because It shows has nothing to do with noise, windows glitch's etc like you suggested. It explains exactly what or why the kernal speed is important and explains the in's n out's of using it higher than 25K rather than just flat don't use it.!
When you've written a few hi-speed communications device drivers for windows you'll find that Windows (or to be more correct the underlying ancient-ish kernel) is often going off to service interrupts that are random and unexpected and have no purpose or indeed have no damn right to exist at all... call that noise/window's glitches/etc. but its a source of lockups that often have no easy explanation. As Art says, there's little time to play inside the interrupt and he breaks the rules to get things to work... trouble is, you can't be sure his driver is the only one breaking the rules... graphics drivers are pretty bad too sometimes, as are network drivers... and yes, i know ideally you don't want the machine on a network, but you can't do much about graphics drivers. So, I agree, his answer IS more detailed but its only down to certain level of accuracy as was mine... and for most people its moot anyway as they can't do much about it, and I stand by mine... if you don't need to do it, don't, and you gain reliability, and if you do, get a faster box... which is pretty much what Art says... :)

but lets not argue :)