Lỗi the bios in this system is not fully acpi

Khi tôi cài windows 7 cho laptop Asus E502M thì nhận được nội dung thông báo lỗi tại màn hình xanh chữ trắng huyền thoại. Trong đó có nội dung: The BIOS in this system is not fully ACPI compliant. Mời các bạn xem ảnh chụp màn hình của lỗi này.

Lỗi the bios in this system is not fully acpi
Hình 1. Lỗi “The BIOS in this system is not fully ACPI compliant”

2. Cách giải quyết

Để giải quyết lỗi này tôi đã thực hiện như sau:

Bước 1: Vào BIOS bằng cách bấm phím F2 khi khởi động lại máy.

Bước 2: Tại menu Advanced chỉnh thông số OS Version thành windows 7

Bước 3: Bấm phím F10 để lưu nội dung cài đặt lại và khởi động lại máy.

Hy vọng hữu ích với bạn!

Nosomovo

  • Asus E502M
  • BIOS
  • OS Version
  • phím F10
  • phím F2
  • The BIOS in this system is not fully ACPI compliant
  • windows 7

'' The BIOS in this system is not fully ACPI compliant '' is an error encountered when trying to install windows. Particularly, the error is known to appear during the file copying phase of windows installation. Thus, halting the installation process.

Now this error can appear regardless of the installation media (It can be CD/DVD drive or USB flash drive). Whether it is Windows XP, Windows 7 or Windows 10, you will be ended up with the exact same error. In the recent times, a lot of people tend to experience this blue screen error. Despite how frustrating it appears, it is relatively easy to fix this error.

In this article, I am going to tell you about Fix The BIOS in this System is Not Fully ACPI Compliant in Windows. If you have also experienced this error keep working with the fixes until the problem is resolved.

Let's get started,

1. Check RAM

This error BIOS is not fully compliant with ACPI can also be an indication of RAM failure. Or if it is not properly seated. Most issues related to the RAM is shown when using the system. To identify potential issues with the RAM, you can utilize the tool known as Memory Diagnostics. If possible, try the RAM in different slots.

2. Update BIOS

In most cases, the BIOS inconsistency has found to be the reason behind this error. There is also a chance for this error to appear if the BIOS on the system is outdated. Therefore, the BIOS will have problem working with ACPI. In this case, there is nothing that can be done except updating BIOS. However it is not an easy process since the procedure differs from motherboard to motherboard. The entire documentation on this procedure is available from the official website.

3. Restore BIOS

Despite of updating BIOS if the issue still persists, then you need to consider restoring BIOS. Restoring BIOS in essence means that to revert the BIOS back to its default settings. However, you should be aware that the newer systems use UEFI instead of BIOS. Whatever technology it is, revert back to its default values so that it will be compliant with ACPI.

4. Install Standard PC HAL

In some instances, the issue might be with the BIOS itself. Meaning, the BIOS isn't supported by the operating system. Thus, neither updating or restoring BIOS will work here. The only means to fix this issue is by setting up an ACPI compliant BIOS. Due to this, the standard PC HAL will be installed instead of ACPI HAL.

5. Change LPSS and SCC Configuration

Certain versions of windows use Windows Image Boot (WIMBoot) to install Windows operating systems. This saves significant amount of space in storage medium. Now this WIMBoot isn't compatible with all the drives. Especially, the traditional hard disk drives. If this is the case, you can fix this error by adjusting the LPSS & SCC configuration inside the BIOS settings.

The bios in this system is not fully ACPI compliant. Please contact your system vendor for an updated bios. If you are unable to obtain an updated bios or the latest bios supplied by your vendor is not ACPI compliant, you can turn off ACPI mode during text mode setup. To do this, simply press the F7 key when you are prompted to install storage drivers. The system will not notify you that the F7 key was pressed--it will silently disable ACPI and allow you to continue your installation."

The parameters Parameter1, Parameter2, Parameter3, and Parameter4 vary from computer to computer.

Cause

This behavior can occur if Windows has detected that the BIOS in the computer is not fully compliant with Advanced Configuration and Power Interface (ACPI).

Resolution

To resolve this behavior, contact the manufacturer of your computer to obtain a BIOS that is fully ACPI compliant.

To work around this behavior, manually install the Standard PC hardware abstraction layer (HAL):

  1. Restart the computer to restart Setup.
  2. When Setup starts again, press F7 (not F6) when you see the "Press F6 if you need to install a third-party SCSI or RAID driver" screen.

Windows automatically disables the installation of the ACPI HAL and installs the Standard PC HAL.

More Information

The following information can help you debug a Stop 0x000000A5 error.

  • The cause of the Stop message is always errors in the ACPI BIOS. There is nothing that you can fix at the level of the operating system.
  • This Stop message can occur at other times. For example, you could receive this Stop error after you install Windows XP and later make a hardware change, such as adding a device. A computer that works properly with Microsoft Windows 98 may not work with Windows XP. Windows 98 does not necessarily use all of the ACPI functions that Windows XP uses. Windows 98 may allow workarounds that Windows XP cannot use because of its more stringent requirements for system stability).

The following information lists possible causes of the Stop 0x000000A5 error. To identify the cause of this Stop error, note Parameter1 and compare it to the numbers listed in the following paragraphs, to get a general idea of the problem.

The other parameters (arguments) are not discussed in this article. You can view these other arguments only by connecting the system to a kernel debugger. This article provides a description of the issues that this Stop error can involve, without requiring more advanced debugging. For more information, refer to Acpidbg.h.

(0x00000001, Parameter2, Parameter3, Parameter4):

This argument is defined as an ACPI root resources failure. More specifically, ACPI could not find the system control interrupt (SCI) vector in any of the resources that ACPI received at startup. SCI is a special interrupt type that provides a more efficient way to deal with problems that are normally handled by system management interrupts (SMI). If SCIs cannot be initialized, ACPI cannot function. This can occur if no entry for this IRQ is found in the list or if no IRQ resource list was found at all.

(0x00000002, Parameter2, Parameter3, Parameter4):

This error is defined as ACPI root PCI resource failure. To discover what current resources are being used by PCI devices, ACPI must be able to query the CRS descriptor in the ACPI namespace. This error occurs if the BIOS lacks a pointer to the list, or if the list is empty, or if the list contains errors or conflicts.

(0x00000003, Parameter2, Parameter3, Parameter4):

This error is defined as "ACPI failed must succeed method." This error occurs if ACPI cannot build a control method to reference the ACPI namespace. Other arguments for this error reference the ACPI object that was being run and the name of the control method. One greatly simplified explanation (which might not be completely accurate) is that the system cannot find a way to get to the ACPI tables that define the Plug and Play and Power Management capabilities of the system.

(0x00000004, Parameter2, Parameter3, Parameter4):

This error occurs because the system received some data type other than the expected integer as a package element when defining a _PRW method in the ACPI namespace. _PRW is only defined for systems that have the ability to wake the system from Sleep mode. Among other things, _PRW defines the lowest power system state that the system can enter and be able to wake up.

(0x00000005, Parameter2, Parameter3, Parameter4):

The _PRW referenced must contain at least two elements. When queried, the _PRW indicated that it was incomplete.

(0x00000006, Parameter2, Parameter3, Parameter4):

A power resource is named, but there is no information available in the namespace for this resource.

(0x00000007, Parameter2, Parameter3, Parameter4):

When the system referenced a method in the ACPI namespace, the system expected a data type of BUFFER but received some other data type.

(0x00000008, Parameter2, Parameter3, Parameter4):

The system expected a data type of INTEGER but received some other data type.

(0x00000009, Parameter2, Parameter3, Parameter4):

The system expected a data type of PACKAGE but received some other data type.

(0x0000000A, Parameter2, Parameter3, Parameter4):

The system expected a data type of STRING but received some other data type.

(0x0000000B, Parameter2, Parameter3, Parameter4):

An _EJD string referenced a nonexistent object. The _EJD object defines objects that are dependent on a specific ejection device. For example, if you have an add-in adapter in a docking station and you attempt to eject the laptop computer, ACPI references this namespace to determine whether the dependent adapter in the docking station supports the ejection. This error occurs because there is no object to define the name referenced in the _EJD string.

(0x0000000C, Parameter2, Parameter3, Parameter4):

The namespace defines support for docking but lacks enough information to implement it. This can be because it is not properly defined or because there are duplicate services defined.

(0x0000000D, Parameter2, Parameter3, Parameter4):

There are many objects that must be defined in the ACPI namespace, and one or more of these was not found. This error generally occurs if either the _HID or _ADR object is missing. An _ADR is used to define the address of a device on its parent bus. The _ADR is a static address that defines slot numbers for devices that reside on any number of bus types, including EISA, floppy, IDE controller, IDE channel, PCI, PCMCIA, and CardBus. The _HID contains objects that supply the operating system with Plug and Play hardware ID for a device. Technically, these objects are optional, but they absolutely must be present to describe any device that is enumerated by an ACPI driver.

(0x0000000E, Parameter2, Parameter3, Parameter4):

This error occurs because the system could not find a required method or object in the namespace for a power resource. These are anything other than a "device." If the BIOS does not supply either an ON, OFF, or STA for a power resource, the system stops with this error.

(0x0000000F, Parameter2, Parameter3, Parameter4):

This occurs when a Plug and Play resource descriptor is smaller than its defined size, indicating that the descriptor is either incomplete or corrupted. Resource descriptors describe the system resources that the computer is using, can use, or wants to use. Each descriptor entry has a predefined size, which must match the data returned.

(0x000000010, Parameter2, Parameter3, Parameter4):

When a system transitions from one power state to another, the system compares the states that are supported system-wide to those supported by the individual devices in the system. This error occurs if Power Resource maps to a nonexistent system-wide resource. You can use a kernel debugger to view the specifics of this error, including the system power state that is causing the problem.

(0x000000011, Parameter2, Parameter3, Parameter4):

The system cannot enter ACPI mode. There are many reasons for this, including:

  • The system cannot initialize the AML interpreter.
  • The system cannot find the Root System Description table.
  • The system cannot allocate a critical driver.
  • The system cannot load the Root System Description table.
  • The system cannot load device descriptor blocks.
  • The system cannot connect an interrupt vector.
  • The SCI_EN (system control interrupt enable request) cannot be set (see 0x00000001).
  • The ACPI Table checksum is incorrect.

ACPI is a hierarchical arrangement of tables, each one building upon the next to define the complete capabilities of the system and of every device in the system. ACPI starts by looking for the Root System Description table, which points to the next table, which points to the next table, and so on. Usually, the 0x000000011 error occurs because these tables are damaged or missing.

(0x000000012, Parameter2, Parameter3, Parameter4):

ACPI is expecting a Power Resource Object that it cannot find. You can view the error through a kernel debugger to see what the exact object is.

(0x00002001, Parameter2, Parameter3, Parameter4):

ACPI tried to evaluate the control method for a specific type of Programmable Interrupt Controller and did not succeed.

(0x00010001, Parameter2, Parameter3, Parameter4):

ACPI tried to perform interrupt routing and did not succeed. This error is usually due to a damaged interrupt routing table.

(0x00010002, Parameter2, Parameter3, Parameter4):

ACPI could not find a link node that is referenced in the interrupt routing table.

(0x00010003, Parameter2, Parameter3, Parameter4):

A device is present in the system, but there is no entry for the device in the IRQ routing table.

(0x00010005, Parameter2, Parameter3, Parameter4):

This error relates to the rules about how a PCI routing table is written. To prevent ambiguity, the device number must be specified in the table but the function number must not. To this end, the function field must be set to all F's. This error occurs when a function number is not all F's.

(0x00010006, Parameter2, Parameter3, Parameter4):

ACPI must able to disabling a link node to reprogram it. This error occurs if ACPI cannot disable a link node.