Gigabyte motherboard boot loop, no further details
Gigabyte motherboard boot loop, no further details
Your Gigabyte H110M-DS2V is experiencing a boot loop after enabling Secure Boot in BIOS. The issue persists even after changing RAM, processor, and clearing CMOS. Please let me know if you need further assistance.
If you alter the secure boot configuration while the system already has an operating system, it may trigger an issue. Restore it to its original state.
Windows handles secure boot fully, regardless of whether it's enabled or disabled—it doesn't matter. Clarifying language helps avoid misunderstandings. Correcting someone who isn't fluent in English can come across as rude or dismissive. He mentioned resetting the CMOS but the problem continues, suggesting the root cause isn't related to CMOS settings. Confirm if the CMOS reset was done correctly and whether any other UEFI changes were made during secure boot adjustments. Explain what you mean by "stuck in a boot loop"—are you encountering any specific error messages or visual cues? Do you notice anything on the screen at all?
I don't agree with that, correcting someone who isn't native can come across as rude. He speaks English more clearly than your language. 2) That's not true; secure boot won't cause a boot loop under any circumstances. It won't happen at all. As I mentioned before, Windows doesn't depend on secure boot being active or inactive—it works perfectly in both cases and the settings can be changed during installation. 3) Avoid sharing false information; people won't point it out. Still impressive to call me the Greatest Of All Time!
1) understand that you can differ. your thoughts are valid even if you're mistaken.
2) altering secure boot configurations on a current Windows setup may cause issues.
3) revert to the original version of your system.
They provided evidence supporting the claim. Microsoft emphasizes that Windows Certified Boards on the X86 platform need secure boot functionality enabled for certification. This approach could prevent systems from starting if users disable secure boot, and they also warn that disabling it followed by software installation might lock users out of re-enabling it later. You can find more details here: https://docs.microsoft.com/en-us/windows...ecure-boot
Sir, please accept my apologies for the poor English. Also, thank you for letting me know. 1. Yes, I'm certain the CMOS has been reset. 2. I only modified the Secure Boot Mode to Enable; nothing else changed. 3. I can't see anything on the display since this is the first post.