Windows 10: I think my Windows OS is interrupting a motherboard related update.

I have Windows OS and an MSI motherboard. In my MSI control center I was prompted for some new updates/installs available. After installing I had to restart the PC. Once restarted the system seems to freeze during this process, skipping my MSI reboot and taking me straight to the login screen to enter my PIN. I am able to enter my pin and view the Home Screen for just a second or two, however this process automatically starts over again. I have spoken with MSI support and they do believe that my Windows OS essentially is not liking the updates I have made. I have followed the steps on this inq

:)

 

I think my Windows OS is interrupting a motherboard related update.

I have Windows OS and an MSI motherboard. In my MSI control center I was prompted for some new updates/installs available. After installing I had to restart the PC. Once restarted the system seems to freeze during this process, skipping my MSI reboot and taking me straight to the login screen to enter my PIN. I am able to enter my pin and view the Home Screen for just a second or two, however this process automatically starts over again. I have spoken with MSI support and they do believe that my Windows OS essentially is not liking the updates I have made. I have followed the steps on this inquiry with no resolution.

Redirecting

Any ideas?

 

Is it plausible that an interrupted Windows update can cause the motherboard to fail?

(The answers given by others are, I think, wrong).

Although somewhat unlikely this is possible. Manufacturers can indeed get Windows to update firmware and UEFI during a Windows update, and if this process is interrupted you could indeed hose a motherboard.

See Update device firmware using Windows Update - Windows drivers | Microsoft Learn to read it "from the horses mouth"

 

Help with Hardware Interrupts

To use Krview, ignore any driver that is part of Windows or that is for the CPU idle thread.
inteppm is for the CPU idle thread, ignore it.
hal and ntkrnlpa are part of Windows, ignore them.
ati2mtag is the first one on the list that is elevated and relevant.
Find out what hardware interrupt it uses and then any device that shares this interrupt could be the problem. It might not be ati2mtag.
If its the video driver, can you use another card?
Putting the computer to sleep might reset things.