Posts: 22
Threads: 1
Joined: Jun 2019
Reputation:
0
06-16-2019, 12:12 PM
(This post was last modified: 06-16-2019, 12:31 PM by RocoCoco90.)
Ok I did everything you said and FPTw.exe -bios -f biosreg.bin has worked! I have attached the screenshot of the success.
https://ibb.co/jT1MzXN
Posts: 1,776
Threads: 0
Joined: Aug 2018
Reputation:
42
06-16-2019, 11:18 PM
(This post was last modified: 06-16-2019, 11:53 PM by Lost_N_BIOS.)
No problem about a delay in reply, I'm always behind too. Hope you are enjoying the new rads!
FPT Success!  Now I will make you unlocked BIOS, please wait
Quick test of a single setting change instead of BIOS unlock for now, flash this via >> FPTw.exe -bios -f OCPMTest.bin
http://s000.tinyupload.com/index.php?fil...4349238968
Do you get OverClocking Performance Menu now or no? If no, on your Main BIOS page, what does it show at the bottom for Access Level?
If yes, can you show me images of all the memory related settings you can see, so I can unhide any still missing (This is all you needed, correct?)
Posts: 22
Threads: 1
Joined: Jun 2019
Reputation:
0
06-17-2019, 06:54 AM
(This post was last modified: 04-29-2025, 05:15 AM by DeathBringer.)
(06-16-2019, 11:18 PM)Lost_N_BIOS Wrote: No problem about a delay in reply, I'm always behind too. Hope you are enjoying the new rads! 
FPT Success! Now I will make you unlocked BIOS, please wait
Quick test of a single setting change instead of BIOS unlock for now, flash this via >> FPTw.exe -bios -f OCPMTest.bin
http://s000.tinyupload.com/index.php?fil...4349238968
Do you get OverClocking Performance Menu now or no? If no, on your Main BIOS page, what does it show at the bottom for Access Level?
If yes, can you show me images of all the memory related settings you can see, so I can unhide any still missing (This is all you needed, correct?)
I am not sure I did it right, I flashed it through the Command Prompt in windows and rebooted into my bios and saw no change in the menu. Was I supposed to do it via the GRUB method booting from the USB? Also the access level in the Main bios page says Administrator. A;so I went back into windows and tried to reflash FPTw.exe -bios -f OCPMTest.bin thinking I might have done something wrong the first time and now I am getting the 167 error again.
Yes the new rads are great. I did my first ITX build in a NZXT H200I case that I modified. I have a 240 45mm rad in the front with 3 80cfm fans in push pull, and a rear 120 45mm with 1 80cfm fan. I delided my 9900k and replace the solder with liquid metal and am doing direct die cooling with der8auers OC frame in a fully custom loop. The other specs are 16gb of 4266 ram and a 2080ti also in that custom loop. I can post pictures once it's done, I'm still waiting on my powered RGB splitter because apparently you can't daisy chain RGB splitters off a mother board header.
Any idea why the FPTw.exe -bios -f OCPMTest.bin failed the second time?
Posts: 1,776
Threads: 0
Joined: Aug 2018
Reputation:
42
First, did you use Admin Command prompt? If not, then maybe didn't' flash, it must be administrator command prompt, not regular CMD prompt, or powershell.
If it doesn't show up after successful above flash method is used, then this is normal, as I mentioned that was only a test to see if a single settings change allowed it to show up or not, or if further edits are needed. Since you get error 167 again, sounds like you flashed it in properly, and this test failed. Thanks for letting me know 167 showed back up, I will attempt to set that to disabled on subsequent test files I send you.
Wow, that is a lot of rads! I used to WC, but only had one 240 on CPU, with 4 fans, and even with slower fans it got to be too loud for me so I went back to air.
I will make you new BIOS to test tonight, please wait and do nothing
Posts: 22
Threads: 1
Joined: Jun 2019
Reputation:
0
(06-21-2019, 01:39 PM)Lost_N_BIOS Wrote: First, did you use Admin Command prompt? If not, then maybe didn't' flash, it must be administrator command prompt, not regular CMD prompt, or powershell.
If it doesn't show up after successful above flash method is used, then this is normal, as I mentioned that was only a test to see if a single settings change allowed it to show up or not, or if further edits are needed. Since you get error 167 again, sounds like you flashed it in properly, and this test failed. Thanks for letting me know 167 showed back up, I will attempt to set that to disabled on subsequent test files I send you.
Wow, that is a lot of rads! I used to WC, but only had one 240 on CPU, with 4 fans, and even with slower fans it got to be too loud for me so I went back to air.
I will make you new BIOS to test tonight, please wait and do nothing 
I might not have used an administrator CP, Ok I will sit tight until you give further instruction.
Posts: 1,776
Threads: 0
Joined: Aug 2018
Reputation:
42
Always use Admin CMD prompt for FPT.
Please test changing this via grub / setup_var, so we can see if this is controlled by NVRAM or Setup instead of what AMIBCP changes
Then look in BIOS, do you see Overclocking Performance menu by itself as new menu, or inside Advanced, or still nothing?
setup_var 0x855 0x1
Posts: 22
Threads: 1
Joined: Jun 2019
Reputation:
0
(06-21-2019, 09:47 PM)Lost_N_BIOS Wrote: Always use Admin CMD prompt for FPT.
Please test changing this via grub / setup_var, so we can see if this is controlled by NVRAM or Setup instead of what AMIBCP changes
Then look in BIOS, do you see Overclocking Performance menu by itself as new menu, or inside Advanced, or still nothing?
setup_var 0x855 0x1
Nothing, didn't change anything.
Posts: 1,776
Threads: 0
Joined: Aug 2018
Reputation:
42
Thanks for checking! The problem here is, sometimes if you disable/enable in one thing, like AMIBCP, and it doesn't help then trying all other methods (setup, NVRAM, STDDegfaults etc) after that may fail due to the AMIBCP setting change conflict. So many test may be needed to solve this one, for that one menu alone.
Let me try changing all 5 instances in NVRAM/stddefault areas, this will be two tests, one with AMIBCP change also, and one without. Then if both those fail, I will redo same with setup module change too. then if none still work, I'll start at base BIOS again and add this menu entry to AMITSE instead. Maybe I'll send all these at once, make now, while it's fresh in my mind
I'm wanting to work on this first, because it's the harder part, since this is it's own submenu that isn't addressable in AMIBCP at the root level of setup, so we need to figure it out first. All the other hidden stuff in already visible menus is no problem, and or no problem to switch default advanced for the hidden one etc.
Posts: 22
Threads: 1
Joined: Jun 2019
Reputation:
0
(06-21-2019, 10:20 PM)Lost_N_BIOS Wrote: Thanks for checking! The problem here is, sometimes if you disable/enable in one thing, like AMIBCP, and it doesn't help then trying all other methods (setup, NVRAM, STDDegfaults etc) after that may fail due to the AMIBCP setting change conflict. So many test may be needed to solve this one, for that one menu alone.
Let me try changing all 5 instances in NVRAM/stddefault areas, this will be two tests, one with AMIBCP change also, and one without. Then if both those fail, I will redo same with setup module change too. then if none still work, I'll start at base BIOS again and add this menu entry to AMITSE instead. Maybe I'll send all these at once, make now, while it's fresh in my mind 
I'm wanting to work on this first, because it's the harder part, since this is it's own submenu that isn't addressable in AMIBCP at the root level of setup, so we need to figure it out first. All the other hidden stuff in already visible menus is no problem, and or no problem to switch default advanced for the hidden one etc.
No problem! I will be awake a few more hours so I will do my best to stay with you during the whole procedure.
Posts: 1,776
Threads: 0
Joined: Aug 2018
Reputation:
42
Hope you can make it  I'd nudge you if you were here and dozing off
Sorry so many test for this one thing, if you just wanted advanced swapped we'd be done
Will have package for you shortly, maybe 20 minutes or so.
|