When will Pentium OC on Win 10 back? (H81M-HDSR2.0
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=707
Printed Date: 21 May 2024 at 6:09am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: When will Pentium OC on Win 10 back? (H81M-HDSR2.0
Posted By: griggsck
Subject: When will Pentium OC on Win 10 back? (H81M-HDSR2.0
Date Posted: 25 Aug 2015 at 6:19pm
|
So Asrock has to update the microcode for Windows 10, but it disabled Non-Z OC for the Pentium in the progress. My question is, when will it be back, it's almost a month since Windows 10 release. Or is the Non-Z OC gone forever? Mobo: |
Replies:
Posted By: Xaltar
Date Posted: 25 Aug 2015 at 7:55pm
| The fact that intel and MS went to such lengths to ensure the feature was disabled likely means that it won't be for some time yet, at least until Intel's current gen sales go up. There are a number of workarounds available though, google the issue and you should be able to find a way around it. There is even a thread here on the ASRock forums about how to get it to work. |
Posted By: parsec
Date Posted: 31 Aug 2015 at 12:39pm
I'm sorry but you don't understand why your board and some (not all) other ASRock board's have a CPU microcode update. Also, I don't see Windows 10 or any version of Windows mentioned in the description of these BIOS updates. Why do you think they are related to Windows 10? As Xaltar described above, Intel has made sure the non-Z OC is gone forever, as much as they can control that, with the help of MS. A recent Windows update will cause any board with a non-Z OC capable BIOS installed to no longer boot. The BIOS updates with the new microcode fixes that problem, by removing the non-Z OC capability. Windows 10 users will have quite a challenge using workarounds to keep the non-Z OC working, since Win 10 does not let you select the updates being installed, or when they are installed. Non-Z OC should never have existed at all IMO. One mother board manufacture started it (not ASRock) and the others had to join them or appear inferior and lose sales. Boards like the H81M-HDSR2.0 are not designed for over clocking, the CPU VRM stage is not built to the level/spec that Intel requires for 'Z' chipset boards. Among other reasons, Intel does not want non-Z OC to exist, since they do not want to be in the situation that AMD found itself in, with the FX-9000 series processors. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
griggsck wrote:Posted By: Sarnyai1982
Date Posted: 30 Nov 2015 at 7:30pm
|
I understand what he's on about. Prior to the BIOS update required for Microcode 19 to allow Windows 10 update... Non-Z OC was an option available in the BIOS GUI. Since then it has disappeared, but now we can use Windows 10... But its annoying, i have an Intel G3258 - its purpose was an anniversary chip for the pentium brand and comes with the unlocked multiplyer - if they didnt want us to 'play' around with it... why bother releasing it only to be shutdown... The Non-Z OC was such as easy function to use. Into BIOS --> select GHZ and done & considering I decided to invest in the Corsair H55 Water Cooler (Noctua HSF i wanted was out of stock) I figured I could play around with it. Which I did... 3.2ghz stock, to 4ghz idling at around 28 degree's... slick as far as i'm concerned... now back to 3.2ghz... oh well...
------------- http://valid.x86.fr/blhhla" rel="nofollow"> 
|
Posted By: wardog
Date Posted: 30 Nov 2015 at 10:12pm
Ohhoho no they don't: https://support.microsoft.com/en-us/kb/3073930 And the below page has some more interesting Windows Update nuggets, the above being one of 'em: http://www.howtogeek.com/223864/how-to-uninstall-and-block-updates-and-drivers-on-windows-10/ < id="kpm_plugin" ="application/x-KPMPlugin">
< id="kpm_plugin" ="application/x-KPMPlugin">
|
Posted By: Xaltar
Date Posted: 30 Nov 2015 at 10:38pm
| That is useful info Wardog, thanks for posting it. The problem with the update in question is that it is part of the retail Win 10 package. In order to uninstall and prevent the offending update you would need the BIOS update (though on some board simply setting factory defaults for the BIOS is enough) then uninstall and prevent it coming back. It may well be possible and if so it would be preferable to renaming system DLL files as you would have to for the more common workaround. |