Successfully patched Z170X-UD5 TH CFG Lock (MSR Ex02)

[canyondust]

I’m wonder if the grub shell modifies the main bios but not the backup, and the save image saves from the backup?

 

[MAC_OS]

just checked your new updates bios on my board, extracted it and load UEFItool and see that nothing changed:
One Of: CFG Lock, VarStoreInfo (VarOffset/VarName): 0x4EF, VarStore: 0x1, QuestionId: 0x24C, Size: 1, Min: 0x0, Max

 

[iLikeHackintosh]

I hope it helps, If someone is more eager to know, whay those set_var_2 and set_var_3 were invented.

http://geek-mag.com/posts/258090/

Original article is Russian, linked on is English translation.

 

[canyondust]

just checked your new updates bios on my board, extracted it and load UEFItool and see that nothing changed:
One Of: CFG Lock, VarStoreInfo (VarOffset/VarName): 0x4EF, VarStore: 0x1, QuestionId: 0x24C, Size: 1, Min: 0x0, Max

Yep see my other posts for more info, or at least more conjecture.

 

[zipb]

So just updating to CanyonDust's modified BIOS will not do the trick? You need to do the patching yourself?

 

[canyondust]

So just updating to CanyonDust's modified BIOS will not do the trick? You need to do the patching yourself?

Yeah, I think you need to patch the variable right on the MB. My var is set to 0x0 but when I save the image it outputs 0x1. I think it might save the image from the backup, or that variable is stored in nvram. I don’t have the programming background to know for sure.

 

[MAC_OS]

ok, I ask agin how did you make your usb, which OS/Software you use: windows, Linux or Mac...etc and maybe is there some special on Bios settings before patching?

 

[zipb]

Yeah, I think you need to patch the variable right on the MB. My var is set to 0x0 but when I save the image it outputs 0x1. I think it might save the image from the backup, or that variable is stored in nvram. I don’t have the programming background to know for sure.

OK. My hack without this BIOS patch works fine overclocked, with no weird high temperatures etc and good geekbench scores. What will I be gaining performance/stability wise with this rather convoluted process? I like to tinker when I have the time, but always with a clear goal, ie measurable improvements.

 

[canyondust]

OK. My hack without this BIOS patch works fine overclocked, with no weird high temperatures etc and good geekbench scores. What will I be gaining performance/stability wise with this rather convoluted process? I like to tinker when I have the time, but always with a clear goal, ie measurable improvements.

To be honest I’m not sure what is gained. I only did it because it’s recommended by aptiomemoryfix, and I thought it might have other benefits regarding native power management or sleep..

 

[canyondust]

ok, I ask agin how did you make your usb, which OS/Software you use: windows, Linux or Mac...etc and maybe is there some special on Bios settings before patching?

The grub shell usb? I don’t remember how I made it, but it was likely a USB key formatted as fat-32, then replacing the bootx64.efi with the grub shell one.
It’s also possible I ran setup_var2 to do the actual patch but again I don’t remember.

Have a look at the 22g bios and let me know if you think there are potentially relevant settings you want me to check.