@lowrck - Since you used NVFlash yes, that means vBIOS is on it’s own chip and not inside BIOS
Yes, if no error on #2, then unlocked now / all good and you can now flash in mod BIOS 
Thanks for zip And you’re welcome!!! 
Here is your unlocked BIOS, flash it back via >> FPTw.exe -bios -f biosmodm.bin
https://ufile.io/ngpt7d3n
*** WARNING - To ANYONE with laptop and unlocked BIOS!!!
DO NOT try to enable this graphics card or disable that card, switch cards etc. Otherwise you will end up with no display output (ie black screen) and no way to recover except by blind flash or with flash programmer.
You can change graphics related settings, like changing memory sizes, or core speeds etc, just don’t try to disable one card or change which is main etc.
Additionally, be very careful when trying to undervolt CPU, you can leave BIOS unbootable due to CPU voltage too low (Sometimes even 0.05 is too much)
WARNING *** - This BIOS is user specific! If you are not user lowrck at Win-RAID.com forum, DO NOT USE THIS BIOS!!
If you do, and you are not lowrck, then you will loose your serial, UUID, OG NVRAM, and possibly LAN MAC ID as well.
You have been warned!!!
to help user out my cheap 2666 ddr4 kit if fully stable with 1.25V @ 3473 mhz (21-22-20-48) CR1 to be more stable and reach max speed up the uncore 100 is too low i wil recommend uncore + 118-125mv and put it in CR2 if cant pass these speed …
Put 13265 in REFI (or try to max it out 65635) to ease the overclocking and 674 the other parameter (forgot the name 470 before)
And if you undervolt too much on the cpu cache (me -175m vs 170mv for me max) DDR4 will be unstable too do ALL of you tests first with -125mv on both VID and cache before undervolting them !
@Lost_N_BIOS @saltinbank Thanks for the helpful advice but I’m afraid its a bust. I’ve tried all frequencies above 2666 at stock or with increased voltages and higher timings but it seems like it just wouldn’t work. It might be possible that it’s my ram or is there something in memory settings that’s preventing it from clocking higher? I tried clocking to 2400 and works just fine so i guess I’m out of ideas
@moonzz - Could just be poor performing default memory, not all will OC the same. You’ll have to pick up some new better memory, then you should have much better luck.
Or, you can run 2400-2666 with tighter timings. Be careful and work your way down slow, too tight and you might get stuck unbootable with no way to recover
@Lost_N_BIOS Yeah i suppose it could be bad luck with the ram. Thanks for all the help anyway i really appreciate it 
In any case if i do set a bad ram timing it auto resets to default so i guess I’m good in that sense. Got a good Cl 15-15-15-39 timing at 2666 so I’m set 
@moonzz - You may just need to keep trying, possibly just one setting too low or not high enough, that’s holding you back.
CL15 @ 2666 is pretty good, what was default? Did you try 14-15-15-38?
@Lost_N_BIOS I’ll keep trying and keep you posted maybe I’ll eventually get it.
The default was Cl 19-19-19-43. Yeah i tried but it seems Cl14 is too low as it makes windows crash when i login but on more tweaking 15-15-15-35 has been working smoothly.
Yes, maybe CL14 is too low, you could maybe try 14-16-15/16-38, but that would probably be counterproductive
intel is back :acer bios 1.12 is the one to go
Summary:
Potential security vulnerabilities in BIOS firmware for multiple Intel Platforms may allow escalation of privilege, denial of service and/or information disclosure. Intel is releasing BIOS updates to mitigate these potential vulnerabilities.
Vulnerability Details:
CVEID: CVE-2020-24457
Description: Logic error in BIOS firmware for 8th, 9th and 10th Generation Intel(R) Core™ Processors may allow an unauthenticated user to potentially enable escalation of privilege, denial of service and/or information disclosure via physical access.
CVSS Base Score: 7.6 High
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CVEID: CVE-2020-0571
Description: Improper conditions check in BIOS firmware for 8th Generation Intel(R) Core™ Processors and Intel(R) Pentium(R) Silver Processor Series may allow an authenticated user to potentially enable information disclosure via local access.
CVSS Base Score: 5.5 Medium
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Affected Products:
8th Generation Intel® Core™ Processor
9th Generation Intel® Core™ Processor
10th Generation Intel® Core™ i7 Processor
Intel® Pentium® Silver Processor Series
Recommendations:
Intel recommends that users of above Intel® products update to the latest BIOS version provided by the system manufacturer that addresses these issues.
Acknowledgements:
These issues were found internally by Intel.
Intel, and nearly the entire technology industry, follows a disclosure practice called Coordinated Disclosure, under which a cybersecurity vulnerability is generally publicly disclosed only after mitigations are available.
Summary:
Potential security vulnerability in Intel® Active Management Technology (AMT), and Intel® Standard Manageability (ISM) may allow escalation of privilege. Intel is releasing firmware updates to mitigate this potential vulnerability.
Vulnerability Details:
CVEID: CVE-2020-8758
Description: Improper buffer restrictions in network subsystem in provisioned Intel(R) AMT and Intel(R) ISM versions before 11.8.79, 11.12.79, 11.22.79, 12.0.68 and 14.0.39 may allow an unauthenticated user to potentially enable escalation of privilege via network access. On un-provisioned systems, an authenticated user may potentially enable escalation of privilege via local access.
CVSS Vector (Provisioned, unauthenticated, network):
CVSS Base Score: 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS Vector (Un-provisioned, authenticated, local):
CVSS Base Score: 7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Products:
Intel® AMT and Intel® ISM versions before 11.8.79, 11.12.79, 11.22.79, 12.0.68 and 14.0.39.
Note: Firmware versions of Intel® AMT 3.x thru 10.x are no longer supported, thus were not assessed for the vulnerabilities/CVEs listed in this Advisory. There is no new release planned for these versions.
Recommendations:
Intel recommends that users of Intel® AMT and Intel® ISM update to the latest version provided by the system manufacturer that addresses these issues.
Acknowledgements:
This issue was found internally by Intel employees. Intel would like to thank Yaakov Cohen, Yocheved Butterman and Yossef Kuszer.
Intel, and nearly the entire technology industry, follows a disclosure practice called Coordinated Disclosure, under which a cybersecurity vulnerability is generally publicly disclosed only after mitigations are available.
Revision History
Revision Date Description
1.0 09/08/2020 Initial Release
@saltinbank - I see "via physical access & via local access" - That means the asshat would have to be sitting at your system, or on your router, to gain access - so really nothing to worry about for general users
ok ive done the job updating CSME and the PMC to up to date ver !
thanks mate !
One another question ? i saw that manufacter mode was enabled by default so i closed it with the command : FPTW64.exe -CLOSEMNF - strange behavior on acer’s laptops ?!
like at the end of this article : http://blog.ptsecurity.com/2018/10/intel…de-macbook.html
and one more thing when Acer on his website talked about “microcode update” it means bios related update or PMC/CMSE counterpart ?
And i saw that BOOT GUARD is disable in FIT when i merge CSME & PMC it says BG is disabled warning ! look for OEM key signing so i have check and KEY is erased : 000000000000000000 do you know how to fix this ?
Boot Guard protects the uefi against Boot/Rootkits right ?
thanks in advance mate !
@saltinbank - Sorry, I can’t comment on Manufacture mode enabled by default, I think MANY systems are like that (ie what you seen was normal).
I often see ManufacturingMode “Enabled” and End of Manufacturing Enabled = No - I just checked my current Z390 system and see this same thing too.
You’ll have to ask @plutomaniac to confirm
"Microcode Update" means just that, update of CPU microcodes, but MANY/ALL manufacturers give VERY short change logs, maybe you get lucky and they mention 2-3 things, but in reality almost all BIOS updates will have many behind the scene changes, fixes, updates etc.
Do you have a previous backup of FD/ME, or full BIOS, so I can look and answer you about Boot Guard?
Boot Guard protects against many things, including Mod BIOS usually, so this is not something you want enabled, and hopefully it’s not, I assume not or key would be burned into your PCH and we’d never be able to do menu mod BIOS on this model (usually this means no menu mod, but not always).
I checked two other users who’ve sent me full BIOS dumps for this model and Boot Guard is not enabled at ME FW side, and OEM key hash is 00’s. And it’s definitely not enabled at PCH side because of how many mod BIOS I’ve done for users on this model.
And I see no Boot Guard or other related entries in FIT table either, so yeah, it’s never enabled for this model
Is this your first time messing with FITc to build/clean/UPD ME FW? If yes, that may be the normal warning message, I’d have to see the exact message you see to be sure, but when it’s set to Disabled and Profile_0 as it is on this model then you do get a normal warning on build of outimage
You can disable the warning in settings I think, Yes, right under generate intermediate files. But as mentioned, it’s normal to see “a message” about boot guard when you build and it’s disabled
ok love you buddy thanks for quick answering …
do wan’t to bother you it will be ok thanks mate really appreciate the effort you put …
but yeah i think i have erased OEM KEY SIGNING upgrading the first the CMSE and tha PMC : but guess what i dont care just wanna know if it is a normal fact or on my behalf …
@saltinbank - 
Thanks
It’s never a bother!! If you need something done, please feel free to let me know, anytime!
All that stuff you mentioned does not apply, was not originally in, your BIOS by default. You did not erase or remove anything
still tweaking … 2nd place WR if the turbo could hit 4.5 ghz as intel said (no way under 2004) i got the WR for sure …
-----------------------------
@LOST : do you the technique to change QPI on our 9750H (locked)
look this one prema mod : https://valid.x86.fr/1k8ktf QPI running @ 102 mhz o
@saltinbank - Nice!!
What do you see in ICC section of BIOS? You may be able to change Bclk there.
Have you looked with throttlestop, it can change Bclk on some systems.
Last resort would be ME FW mod and increase the spread % Do you have flash programmer, I forget?
What bclk do you see in CPU-z?
Hi @Lost_N_BIOS ,
can you please check my modified vars (had error 167) if the changes I made ok to flash it in?
--------------------------
Hi @airstars , thank you for your PM. Here are my original vars. Dump with ver. 100.00.16.08 stuck on parsing variable information.
H2OUVE_100.0.9.2.rar (61.4 KB)
vars.rar (88 KB)
Hey @Lost_N_BIOS , I’m Interested in unlocking my bios for the ph315-52, Would you mind helping me out if you have the time. I’m on the newest firmware. Thanks
vars.zip (34.2 KB)