Modifing a CpuSmm store value using CpuSetup on accident (not issue)

[ElephantTweakerdeblaterSAK]

I know this may not be the best place to put it , I used your old grub efi, I am going to switch to the new one. I was able to modify lots of bios settings with it but particularly I tried to disable smm stuff and it said successful. But in bios it didn't change, I realized that I wrote down the wrong var store , I put CpuSetup instead of CpuSmm for the var store. I had realized that today. Did I mess anything up , as my PC was never bricked and I've updated my bois firmware multiple times since then. I also have taken out cmos lots of times since then.
These are the things I tried to disable with it SMM MSR Save State Enable | VarStore: CpuSmm | VarOffset: 0x0 | Size: 0x1     Disabled: 0x0     Enabled: 0x1                                                                                                                         CPU SMM Enhancement SMM Code Access Check | VarStore: CpuSmm | VarOffset: 0x1 | Size: 0x1     Disabled: 0x0     Enabled: 0x1                                                                                                                         CPU SMM Enhancement SMM Use Delay Indication | VarStore: CpuSmm | VarOffset: 0x2 | Size: 0x1     Disabled: 0x0     Enabled: 0x1                                                                                                                         CPU SMM Enhancement SMM Use Block Indication | VarStore: CpuSmm | VarOffset: 0x3 | Size: 0x1     Disabled: 0x0     Enabled: 0x1                                                                                                                         CPU SMM Enhancement SMM Use SMM en-US Indication | VarStore: CpuSmm | VarOffset: 0x4 | Size: 0x1     Disabled: 0x0     Enabled: 0x1                                                                                                                         CPU SMM Enhancement DGR+NR11 / NR10 Support | VarStore: CpuSmm | VarOffset: 0x6 | Size: 0x1     NR10: 0x0     DGR_NR11: 0x1 . These settings are visible in my bios anyways , also it didn't touch them as it wasn't the right Var store. Is everything okay. I have anxiety. Thank you.

[ElephantTweakerdeblaterSAK]

I know this may not be the best place to put it , I used your old grub efi, I am going to switch to the new one. I was able to modify lots of bios settings with it but particularly I tried to disable smm stuff and it said successful. But in bios it didn't change, I realized that I wrote down the wrong var store , I put CpuSetup instead of CpuSmm for the var store. I had realized that today. Did I mess anything up , as my PC was never bricked and I've updated my bois firmware multiple times since then. I also have taken out cmos lots of times since then. These are the things I tried to disable with it SMM MSR Save State Enable | VarStore: CpuSmm | VarOffset: 0x0 | Size: 0x1     Disabled: 0x0     Enabled: 0x1                                                                                                                         CPU SMM Enhancement SMM Code Access Check | VarStore: CpuSmm | VarOffset: 0x1 | Size: 0x1     Disabled: 0x0     Enabled: 0x1                                                                                                                         CPU SMM Enhancement SMM Use Delay Indication | VarStore: CpuSmm | VarOffset: 0x2 | Size: 0x1     Disabled: 0x0     Enabled: 0x1                                                                                                                         CPU SMM Enhancement SMM Use Block Indication | VarStore: CpuSmm | VarOffset: 0x3 | Size: 0x1     Disabled: 0x0     Enabled: 0x1                                                                                                                         CPU SMM Enhancement SMM Use SMM en-US Indication | VarStore: CpuSmm | VarOffset: 0x4 | Size: 0x1     Disabled: 0x0     Enabled: 0x1                                                                                                                         CPU SMM Enhancement DGR+NR11 / NR10 Support | VarStore: CpuSmm | VarOffset: 0x6 | Size: 0x1     NR10: 0x0     DGR_NR11: 0x1 . These settings are visible in my bios anyways , also it didn't touch them as it wasn't the right Var store. Is everything okay. I have anxiety. Thank you.

I've touched them many times since then in the bios and it's been fine.

[ElephantTweakerdeblaterSAK]

@datasone

[datasone]

What's the corresponding values with these VarOffsets in CpuSetup? You can use that to confirm which settings are touched.

Though I think the low addresses in CpuSetup are often not used to store settings, that may be why it doesn't affect much on your PC.

[ElephantTweakerdeblaterSAK]

What's the corresponding values with these VarOffsets in CpuSetup? You can use that to confirm which settings are touched.

Though I think the low addresses in CpuSetup are often not used to store settings, that may be why it doesn't affect much on your PC.

Can you elaborate. From what I'm understanding of what you said you think that I edited CpuSetup settings correctly . What I'm saying is when I tried to use the syntax of applying many settings a long time ago I used the wrong var store which means those values weren't modified but I'm scared it changed stuff. If you change settings with the wrong var store that those settings do not exist in. Does it make glitch values stored in a secret place which not even a cmos reset plus bios update can fix or does cmos reset the whole motherboard and the bios update removes these values if they are even written. Sorry for my English it happens when I'm nervous and don't know how to write correctly.

[ElephantTweakerdeblaterSAK]

What's the corresponding values with these VarOffsets in CpuSetup? You can use that to confirm which settings are touched.

Though I think the low addresses in CpuSetup are often not used to store settings, that may be why it doesn't affect much on your PC.

I didn't edit it though, I edited basically a value I was supposed to edit in the different var store. But I edited it in CpuSetup which is not the var store in which the setting is stored in . Is it even changing anything at all?

[ElephantTweakerdeblaterSAK]

What's the corresponding values with these VarOffsets in CpuSetup? You can use that to confirm which settings are touched.

Though I think the low addresses in CpuSetup are often not used to store settings, that may be why it doesn't affect much on your PC.

Ohh okay , I realized I messed up I see what you wrote now. I did realize that is not just these settings. Do you have a definitive answer if resetting the cmos does revert everything or no.

[ElephantTweakerdeblaterSAK]

I thought I miscommunicated, I guess I did not read properly, so sorry.

[ElephantTweakerdeblaterSAK]

I will check these specific values , I just hope that I could completely revert anything possible just with cmos battery removal plus bios update.

[ElephantTweakerdeblaterSAK]

Honestly based on what I'm seeing one value I put here because of using the wrong var store ended up modifying peci . Shouldn't all settings modified even ones with that don't change anything be completely reset and cleared or no?.

[datasone]

What's the corresponding values with these VarOffsets in CpuSetup? You can use that to confirm which settings are touched.
Though I think the low addresses in CpuSetup are often not used to store settings, that may be why it doesn't affect much on your PC.

Ohh okay , I realized I messed up I see what you wrote now. I did realize that is not just these settings. Do you have a definitive answer if resetting the cmos does revert everything or no.

It's heavily implementation-dependent, but for these varstore used for setting items I think a reset will do the work.

About "implementation-dependent": the varstores are just like configuration files, so it's up to BIOS code to decide whether to read it and how to interpret and apply the values, as well as what to do while resetting CMOS. But most modern UEFI BIOS should handle this correctly (i.e. overwriting changed values with preset).
In your case about PCIe settings, there may be possibilities that BIOS just ignores it or the changed settings doesn't effect your current system setup (e.g. the corresponding PCIe slot or feature is not in use). So it doesn't brick or do any damage to your system.

[ElephantTweakerdeblaterSAK]

What's the corresponding values with these VarOffsets in CpuSetup? You can use that to confirm which settings are touched.
Though I think the low addresses in CpuSetup are often not used to store settings, that may be why it doesn't affect much on your PC.

Ohh okay , I realized I messed up I see what you wrote now. I did realize that is not just these settings. Do you have a definitive answer if resetting the cmos does revert everything or no.

It's heavily implementation-dependent, but for these varstore used for setting items I think a reset will do the work.

About "implementation-dependent": the varstores are just like configuration files, so it's up to BIOS code to decide whether to read it and how to interpret and apply the values, as well as what to do while resetting CMOS. But most modern UEFI BIOS should handle this correctly (i.e. overwriting changed values with preset). In your case about PCIe settings, there may be possibilities that BIOS just ignores it or the changed settings doesn't effect your current system setup (e.g. the corresponding PCIe slot or feature is not in use). So it doesn't brick or do any damage to your system.

Thanks so much for the reply, I have said these aren't the only settings as I realized even more var stores were wrongly used. I also updated firmware. And I fully took out cmos. If I did all this can I verify that it is fully stock. I want my tests as accurate as possible as I test tweaks ,I would like to ensure that I have a clean slate for testing. If it doesn't clear after all this how can we verify if everything is stock. As isn't the bios files that you get have all values set from that file. I mean any visible settings I think appears reset.

[ElephantTweakerdeblaterSAK]

Another example of me using the wrong var store was for a EC notification, cs pl1 limit, cs pl1 value, Intel rmt state, hw notification and lots of pep settings

[ElephantTweakerdeblaterSAK]

I can't remember all I don't think. Hopefully that's all.

[ElephantTweakerdeblaterSAK]

Intel ready mode technology I think too.

[ElephantTweakerdeblaterSAK]

Using their real vars , not all work. I'm assuming some are locked in my machine. As some fail.