Z390 Extreme4 BIOS 2.02 Windows error
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=10182
Printed Date: 05 Aug 2025 at 2:01pm Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Z390 Extreme4 BIOS 2.02 Windows error
Posted By: darylzero
Subject: Z390 Extreme4 BIOS 2.02 Windows error
Date Posted: 16 Nov 2018 at 4:47am
I just updated the BIOS to ver 2.02 and now in the Windows 10 Event viewer I get this error:
"AMLI: ACPI BIOS is attempting to write to an illegal IO port address (0x74), which lies in the 0x74 - 0x76 protected address range. This could lead to system instability. Please contact your system vendor for technical assistance."
|
Replies:
Posted By: darylzero
Date Posted: 16 Nov 2018 at 6:36am
This happens after every reboot
|
Posted By: darylzero
Date Posted: 17 Nov 2018 at 2:14am
So does ASRock tech support not look at their own Technical Support Forum???
|
Posted By: Xaltar
Date Posted: 17 Nov 2018 at 2:43am
The "Technical Support" forum is a place for users to attempt to assist one another, this is a community forum. If no other member knows how to help then sadly posts go unanswered. If you are looking for an answer from ASRock you need to open a support ticket with ASRock. I provided a link in your other post.
ASRock Tech Support does post here fairly often these days however they operate within a limited time frame so they can't get to every post. The fact that they have a presence here at all is a vast improvement over most manufacturer forums.
-------------
|
Posted By: DavidDane
Date Posted: 31 Jan 2019 at 1:32pm
Yeah, I am getting the exact same error on Windows 10 Pro 64bit running the latest bios. Driving me crazy. I've been troubleshooting it for about 2 weeks now with no solution. I've tried different bios settings and the factory defaults, but nothing has fixed it yet. ASRock Tech Support on the phone doesn't know how to resolve it either. Anyone have any solutions? Can we get some kind of an update here on what the issue might be?
|
|