Read more.Removal of BCLK OC feature follows reports of Intel pressure upon motherboard vendors.
Read more.Removal of BCLK OC feature follows reports of Intel pressure upon motherboard vendors.
Comes down to two choices then: either run your Skylake processor with known bugs and be able to OC or have known bugs removed via microcode update and kiss OCing bye bye. Who'd have thought...
Actually, everyone. I'm only surprised it's ASRock that has bitten the bullet first. Perhaps because they aren't (yet) so big to be able to run afoul of Intel.
Naughty intel. I understand the need to make money selling more advanced overclockable chips but blocking it by pushing motherboard vendors to disable features that have already been sold is not on. Hopefully someone can hack it back in so you can get the latest microcode. What's the betting BCLK overclocking will be hardware blocked for the next gen CPUs?
From what I've heard BCLK overclocking is possbile because the FVIR (fully integrated voltage regulator) has been tossed out of the processor again. Apparently, the Haifa team doesn't care for it much. The next (major) processor iteration will be made by the Hillsboro team again, which introduced (and apparently plans to reintroduce) the FVIR.
This is why we need a competitive AMD to stop intel pulling this kind of stuff.
Not naughty Intel at all, they are simply asking motherboard vendors not to enable unsupported configurations, the CPUs in question are sold by Intel as non-overclockable and they have the K range of CPUs with which they support overclocking.
It's naughty of the motherboard vendors to have enabled BCLK overclocking and advertised it without checking it would be alright with Intel - and predictably it isn't.
I wonder if anyone will care enough to demand a refund for their now non-overclockable motherboard/CPU combo? Intel's actions have made it a blatant case of false advertising
Would be interesting to know if the bclk removal is in the microcode or not.....if it isn't then I guess people can just keep their older bios and use UBU to keep the microcode and various firmwares updated.
Main PC: Asus Rampage IV Extreme / 3960X@4.5GHz / Antec H1200 Pro / 32GB DDR3-1866 Quad Channel / Sapphire Fury X / Areca 1680 / 850W EVGA SuperNOVA Gold 2 / Corsair 600T / 2x Dell 3007 / 4 x 250GB SSD + 2 x 80GB SSD / 4 x 1TB HDD (RAID 10) / Windows 10 Pro, Yosemite & Ubuntu
HTPC: AsRock Z77 Pro 4 / 3770K@4.2GHz / 24GB / GTX 1080 / SST-LC20 / Antec TP-550 / Hisense 65k5510 4K TV / HTC Vive / 2 x 240GB SSD + 12TB HDD Space / Race Seat / Logitech G29 / Win 10 Pro
HTPC2: Asus AM1I-A / 5150 / 4GB / Corsair Force 3 240GB / Silverstone SST-ML05B + ST30SF / Samsung UE60H6200 TV / Windows 10 Pro
Spare/Loaner: Gigabyte EX58-UD5 / i950 / 12GB / HD7870 / Corsair 300R / Silverpower 700W modular
NAS 1: HP N40L / 12GB ECC RAM / 2 x 3TB Arrays || NAS 2: Dell PowerEdge T110 II / 24GB ECC RAM / 2 x 3TB Hybrid arrays || Network:Buffalo WZR-1166DHP w/DD-WRT + HP ProCurve 1800-24G
Laptop: Dell Precision 5510 Printer: HP CP1515n || Phone: Huawei P30 || Other: Samsung Galaxy Tab 4 Pro 10.1 CM14 / Playstation 4 + G29 + 2TB Hybrid drive
Did anyone seriously believe the "Master" would let them get away with it? Meanwhile, the other player in the market has no such issues and that fact is not promoted often enough by the controlled media, including Hexus.
Yes, with AMD there has never been an attempt to inhibit the consumer with such trivial issues.
Well if we look back previous generations of processors have allowed bclk overclocking (nehalem architecture) which, while unsupported by Intel officially, many did. I fail to see how this is any different and not just blatant profiteering from Intel to force people to buy the K series of processors. If I'd purchased one of these boards then I would definitely want a refund. You can't market a product stating it can do something which people may base a purchasing decision on, then later remove it whilst fixing unrelated bugs.
Main PC: Asus Rampage IV Extreme / 3960X@4.5GHz / Antec H1200 Pro / 32GB DDR3-1866 Quad Channel / Sapphire Fury X / Areca 1680 / 850W EVGA SuperNOVA Gold 2 / Corsair 600T / 2x Dell 3007 / 4 x 250GB SSD + 2 x 80GB SSD / 4 x 1TB HDD (RAID 10) / Windows 10 Pro, Yosemite & Ubuntu
HTPC: AsRock Z77 Pro 4 / 3770K@4.2GHz / 24GB / GTX 1080 / SST-LC20 / Antec TP-550 / Hisense 65k5510 4K TV / HTC Vive / 2 x 240GB SSD + 12TB HDD Space / Race Seat / Logitech G29 / Win 10 Pro
HTPC2: Asus AM1I-A / 5150 / 4GB / Corsair Force 3 240GB / Silverstone SST-ML05B + ST30SF / Samsung UE60H6200 TV / Windows 10 Pro
Spare/Loaner: Gigabyte EX58-UD5 / i950 / 12GB / HD7870 / Corsair 300R / Silverpower 700W modular
NAS 1: HP N40L / 12GB ECC RAM / 2 x 3TB Arrays || NAS 2: Dell PowerEdge T110 II / 24GB ECC RAM / 2 x 3TB Hybrid arrays || Network:Buffalo WZR-1166DHP w/DD-WRT + HP ProCurve 1800-24G
Laptop: Dell Precision 5510 Printer: HP CP1515n || Phone: Huawei P30 || Other: Samsung Galaxy Tab 4 Pro 10.1 CM14 / Playstation 4 + G29 + 2TB Hybrid drive
Well, I suppose at the very least the "complex workload" bug will have been fixed. The one recently discovered by the Great Internet Mersenne Prime Search collective.
Going on the article that was fixed in the last BIOS, my Google-fu must be letting me down because i can't find any release note for any microcode updates.
I was just assuming "that" microcode update would be pushed out with the removal of BCLK overclocking. Stick'n'carrot'n'all that. I'm not sure Intel ever details what's in a microcode update. I'd wager most people wouldn't even know if and when the microcode of their processor was updated.
There are currently 1 users browsing this thread. (0 members and 1 guests)