(01-16-2016, 01:13 AM)lamedude Wrote: [ -> ]http://lmgtfy.com/?q=skylake+bclk+overclocking
Yes we know how it's done lamedude. Our point is that Intel has never in the past (this isn't the first time this has happened) stated that they don't support or allow it. Or at least I have never seen anything personally to suggest this from Intel. As a result of this until I receive a source that says otherwise I must conclude that the statements made by anti-ultimate and DrHouse64 are inaccurate. They have also taken no steps to try to remove it despite the fact that they easily could have done so by now. Quite frankly I don't feel they will as multiplier OCing is still a much better way to go about it and most serious OCers will still gladly pay the extra $20 to unlock it on their (usually) $1,000+ builds.
You're right, Intel never said they don't allow it. Still, they put limitations to non-K processors so they are not as easy to overclock as K processors.
I don't understand this fully. Historically this has been something which is as much dependent on Intel/AMD and motherboard manufacturers according to some stuff I read.
AnyOldName3 Wrote:I don't understand this fully.
Neither do the journalists apparently.
What Terry Myerson actually said Wrote:“Windows 7 was designed nearly 10 years ago before any x86/x64 SOCs existed. For Windows 7 to run on any modern silicon, device drivers and firmware need to emulate Windows 7’s expectations for interrupt processing, bus support, and power states—which is challenging for WiFi, graphics, security, and more,” he continued. “As partners make customizations to legacy device drivers, services, and firmware settings, customers are likely to see regressions with Windows 7 ongoing servicing.”
Windows 7 will be supported for “security, reliability, and compatibility” on previous-generation CPUs through January 14, 2020, while Windows 8.1 will get the same treatment through January 10, 2023. But “as new silicon generations are introduced, they will require the latest Windows platform at that time for support,” Myerson wrote. As an example, he said that Intel's upcoming Kirby Lake, Qualcomm's 8996, and AMD's Bristol Ridge will only support Windows 10.
You are correct that driver support is provided by the cpu/mobo manufacturer, not microsoft. The only thing microsoft has any control over is whether those drivers show up automatically in windows update (you should be downloaded the latest drivers off the manufacturer's site anyways so I don't really care about this at all) and whether security updates are tested to work with that hardware (unlikely to cause any major issues if the manufacturer actually did their job). The journalists make it sound like win 7 isn't going to work with newer cpus. Which is of course a really dumb assertion.
(01-20-2016, 12:06 PM)NaturalViolence Wrote: [ -> ]You are correct that driver support is provided by the cpu/mobo manufacturer, not microsoft.
well...
microsoft does have to sign the driver. else either windows wont install it or show the HEY I DONT TRUST THIS DRIVER DO YOU? errormsg
so if ms starts refusing to sign win7/8 drivers...
![[Image: 48c.jpg]](http://i2.kym-cdn.com/photos/images/newsfeed/000/909/991/48c.jpg)
Since Terry did not mention drivers at all there is no reason to believe that will happen. Plus the manufacturers would throw a fit if Microsoft rejected a proven stable driver for no apparent reason.
You say it's the best idea to download the latest drivers for everything from the manufacturer, but I installed Windows 10 from scratch shortly after its release, and it's done a grand job of getting drivers for everything (except an Oculus Rift DK1, but even the official drivers for that were giving me issues, so Microsoft not signing them or hosting them on Windows Update is very understandable). If people get into the mentality of a Windows install 'just working' they may not even think to get drivers from the manufacturers.
Depends on how niche the hardware is and how behind win update is. If it's a common piece of hardware that gets updated fairly infrequently then yes it will do a fine job. I would still check for the latest version on the manufacturers site though when you're setting up a new build or adding/upgrading hardware.
(01-20-2016, 04:31 PM)NaturalViolence Wrote: [ -> ]Since Terry did not mention drivers at all there is no reason to believe that will happen. Plus the manufacturers would throw a fit if Microsoft rejected a proven stable driver for no apparent reason.
seeing how ms is pushing win10 , i wouldnt be surprised ...
