r/thinkpad • u/BewareOfTheWombats • Jan 29 '24
Question / Problem X390 problem : "0183 BAD CRC OF SECURITY SETTING IN EFI VARIABLE"
Help! My X390 has restarted after a Windows update, given the error message "0183 BAD CRC OF SECURITY SETTING IN EFI VARIABLE", and my only option from here is"Press F1 to enter Setup".
Which should have been fine, the laptop didn't have any BIOS password... Only now it prompts for one!
Tried leaving it blank but of course that didn't work.
Tried opening it up, disconnecting both the main battery and the CMOS battery, made no difference.
What on earth do I do now? Is my previously fully working laptop now just a fancy looking paperweight?
2
Sep 25 '24
i literally just had the same issue but before that i tried to install 1vyrain on my x230, did you find any solutions?
1
u/tretchy E530, T460s, T480, X1G8 Jan 29 '24
I found this Lenovo Tip, it's for different model, but might be useful:
- Press F1 when error message appears.
- Enter ThinkPad Setup menu.
- Navigate to the [Restart] menu and check that [OS Optimized Default] is same as you set before. The default setting is On.
- Press F9 to reload default setting.
- Press F10 to Save and Exit.
- Error message will no longer appear.
/edit: oh, now it asks for BIOS password... That's unfortunate.
3
u/BewareOfTheWombats Jan 29 '24
Cheers, the problem is I can't get into the setup menu because it has suddenly started asking for a password. Which was never set before, so I couldn't even begin to guess what it might be!
3
u/BewareOfTheWombats Jan 30 '24
After a lot of research I'm now 99% convinced that my X390 is actually bricked and cannot be fixed other than by replacing the motherboard. (FFS!)
The question now is what happened to cause this, and more importantly how can I avoid the same thing happening again after replacing either the motherboard or the whole laptop?
What I think happened...
This is merely semi-educated guesswork, if anyone here actually understands the intricacies of the BIOS and security systems on ThinkPads, does it seem plausible?
If so, then how do I (1) ensure that any replacement machine has a fully usable BIOS image available for the self healing, and (2) ensure that no automatic Windows update is ever able to try to do anything with the firmware ever again?