This widget could not be displayed.
This widget could not be displayed.
cancel
Showing results for 
Search instead for 
Did you mean: 

Current Windows Update causing "CPU Over Temperature Error" on boot

clsmooth
Star II

I just kicked off the latest Windows 11 update on my PN53.  Upon restart, partway through the bootup screen with the Asus logo, the screen would flash back to the AMD bootup info screen, but with the error "CPU Over Temperature Error! Press F1 to run SETUP".  Thing is, my CPU wasn't overheating, and could hear the fan running.  Log into BIOS and the CPU temp & fan speed are at normal, expected levels for just sitting there.

With the help of chat, this appear to be a false alarm error, where something in the BIOS or sensor calibration gets tripped after the update.

While in the BIOS -> Monitor tab -> CPU temp -> Enter -> Disable

My PN53 continued booting after this.  I'm gonna keep an eye on it.  After a few more normal restarts that I do, I'll see if everything's normal and re-enable the CPU temp trigger in the BIOS again and see what happens.

1 ACCEPTED SOLUTION

Accepted Solutions

agomes
Star I

Same thing has been happening for me for the last, what? 20 windows updates? Going to bios and exiting does the trick. It only happens after Windows Update reboots.

View solution in original post

10 REPLIES 10

123praveen
Star I

It could be due to usage of unknown online tools and websites. I suggest you stop using unreliable tools such as ytmp3 downloaders, insta viewers, etc, and use only safe downloader. Use a device cleaner to clean malware and restart the system.

No such sites in my case, and regularly run a scanner.  First time it happened to me in about 2 years of ownership now (at least I was able to resolve this one 🙄 ).  Thanks for checking.

I forgot to add this one to the list https://youtubeshortstomp3.com/

That's a really clever diagnostic process you went through with your PN53! It's a perfect example of how a modern tech problem often requires a bit of old-school troubleshooting to find a workaround. Navigating those BIOS settings to bypass a false sensor reading is similar to the process of finding the right my universal remote codes —sometimes you have to dig into the system's core programming to get everything working in harmony again. Great job figuring it out, and I hope a future BIOS update permanently resolves the calibration for you!