kwwerror2215ca02e3
New member
- Joined
- Aug 11, 2026
- Messages
- 2
Hi,
I'm having an issue with my MSI A520M-A PRO (MS-7C96) motherboard after disabling Secure Boot.
System specs:
- Motherboard: MSI A520M-A PRO (MS-7C96), BIOS version 1.K0 (dated 02.09.2025)
- CPU: AMD Ryzen 5 5600 (6-core)
- RAM: 16 GB
- OS: Windows 11 Pro, version 25H2 (build 26200.8875)
- Boot mode: UEFI, GPT disk
What I did:
1. Entered BIOS setup
2. Disabled Secure Boot
3. Saved and exited (F10)
What happened:
The system started rebooting - fans, RGB, and the monitor flickered on for about a second, then everything went dark. The monitor reported "No signal" and stayed that way. The system did not reach POST/BIOS screen or Windows at all.
What fixed it:
Clearing CMOS (jumper) brought the system back to normal - it booted fine afterward with default settings (Secure Boot back to its default state).
Questions:
1. Is this a known issue with this board's BIOS handling of Secure Boot NVRAM variables?
2. Would updating to the latest BIOS version resolve this before I try disabling Secure Boot again?
3. Any recommended steps to safely disable Secure Boot on this board without risking another no-signal freeze?
Thanks in advance for any help!
I'm having an issue with my MSI A520M-A PRO (MS-7C96) motherboard after disabling Secure Boot.
System specs:
- Motherboard: MSI A520M-A PRO (MS-7C96), BIOS version 1.K0 (dated 02.09.2025)
- CPU: AMD Ryzen 5 5600 (6-core)
- RAM: 16 GB
- OS: Windows 11 Pro, version 25H2 (build 26200.8875)
- Boot mode: UEFI, GPT disk
What I did:
1. Entered BIOS setup
2. Disabled Secure Boot
3. Saved and exited (F10)
What happened:
The system started rebooting - fans, RGB, and the monitor flickered on for about a second, then everything went dark. The monitor reported "No signal" and stayed that way. The system did not reach POST/BIOS screen or Windows at all.
What fixed it:
Clearing CMOS (jumper) brought the system back to normal - it booted fine afterward with default settings (Secure Boot back to its default state).
Questions:
1. Is this a known issue with this board's BIOS handling of Secure Boot NVRAM variables?
2. Would updating to the latest BIOS version resolve this before I try disabling Secure Boot again?
3. Any recommended steps to safely disable Secure Boot on this board without risking another no-signal freeze?
Thanks in advance for any help!