cancel
Showing results for 
Search instead for 
Did you mean: 

Z790 MAXIMUS HERO - AI OC issues

Smexhy
Level 8
Hello, I noticed, that after updating to the latest BIOS listed on the website - https://rog.asus.com/motherboards/rog-maximus/rog-maximus-z790-hero-model/helpdesk_bios/ 0703 AI OC function is having issues with chromium and electron apps. They tend to crash randomly. The apps I am talking about are Discord, League of Legends client or NZXT cam or anything else in electron. Google Chrome tabs can crash randomly as well. In gaming though there aren't such problems. When I disable AI OC and put it on auto, everything works great with those apps again, that's how I know it's because of it.

The BIOS version 0502 worked fine with AI OC enabled. CPU is water-cooled and have more than enough room and other fans to keep everything cool, it's definitely not about temperatures. Those crashes are happening when the CPU is basically idle too, no high temps, no high usage, nothing running in background that would put the CPU into stress. I am currently using test BIOS 0031 version from Shamino here on the forum, although it's much better, it still randomly crashes, just less.

Intel ME firmware and driver is also installed to the latest one that I could find on Asus website for this motherboard with the rest of the drivers, windows 11 updates etc. all done

Do asus need to optimize this AI OC feature for new boards with the update, or is there something else I am missing?

Thank you.
2 REPLIES 2

Smexhy
Level 8
I just want to add that the error that appears in those crashes and sometimes even game crashes now is this one below. It's pretty random and after each restart it's either less or more common (probably due to how the AI OC changes values by itself).

EXCEPTION_ACCESS_VIOLATION

I am going to try the latest bios posted here - 0803 and perhaps it's going to be a bit better, hopefully. Otherwise AI OC feature won't be of much use until fixed.

UPDATE: Sadly bios update didn't help, got blue screen on desktop 3 mins after login to windows 😕

Same problem here.  Still have found no way to avoid it.