Yeah,well people should know better than to complain and want to switch motherboards because of S3 sleep not working when overclocked.
You would think four years of this would teach people a lesson...But I guess not.
Computers are *designed* to be used at stock speeds, and sleep was designed as a stock feature. Overclocking is a bonus, not a right. Manufacturers TRY to cater to us as best they can, but S3 has ALWAYS been problematic on overclocked systems. That's why Intel is in no hurry to fix something like this. They have far more important things to do on the queue list...when you're using PLL Overvoltage, you're running OUTSIDE the specifications of the system; it's not something that is exactly warranted (guaranteed). PLL is already erratically stable enough as it is, without throwing S3 into the picture.
Back in the core 2 days, there were problems with computers locking up from sleep, due to the chipset straps resetting and causing the RAM timings to be completely out of specification for the FSB (which was why the boards refused to resume; think of trying to run CAS 3 at 1000 mhz to see how that easily happens). This was later fixed in many boards, but in some cases it took months, in others, a year or more.
Now, something like VT-D, I can understand, since that's a non-K advertised feature that is SUPPOSED to work at all times...that I can relate to...
Bookmarks