There's your answer, all.
Intel thinks it's solved the problem and it obviously hasn't. I had the same issue when I spent (read wasted) hours upon hours of my time trying to fathom what Intel had released and the actual drivers underneath each release. The issue you have is two fold. The drivers released from Intel are bundled so that they include drivers for a slew of Intel hardware and so what comes out of the factory is a mixed message of 'here are the new drivers, Yay!' and 'oops, not for this card' as the revision date is the same as last, or at worse earlier...
...all that's new is the release of the bundle, period. Took me a while to work that one out - thanks intel. To add fuel to the fire, intel don't share the bugs fixed report for their driver releases and so you have no idea if the release even attempts to fix this problem. Essentially you're just guessing probably the same as Joe and Mark guess when they say the fix is available. All they're really saying is a new bundle is out and hey presto.
The second problem is the installed software from intel is a real pain to remove and reinstall. I had errors all over the place trying to remove it and add the 'new' drivers. To be frank intel software is has room for improvement and that's saying something as I've seen some pretty shonky software in my time. So Mark Hanna above may well be right that the drivers are out but I'd avoid breaking out the Champaign at this point in time if past performance is a judge of current and future performance.
I go back to my original statement yesterday. Don't lose sleep anymore, guys. Go get an Athlon card off EBay or a local stockist and get 'er done!. Also add note-to-self. AMD processors and avoid intel chipsets across the board where at all possible in the future. This is my mantra when purchasing computing equipment going forward. Go tell your friends and family, you at least owe them that, ey?!
Good luck - signed - a happy Killer Wireless end user with Windows 8 drivers happily working away, quietly, as if they weren't there :-)
C-