Event ID: 4 ACPI BIOS

[toolman59]

The following error is a permanent entry in the event viewer

Event Type: Error
Event Source: ACPI
Event Category: None
Event ID: 4
Date: 14/11/2004
Time: 17:56:26
User: N/A
Computer: NOVATECH
Description:
AMLI: ACPI BIOS is attempting to read from an illegal IO port address (0x71), which lies in the 0x70 - 0x71 protected address range. This could lead to system instability. Please contact your system vendor for technical assistance.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Data:
0000: 00 00 00 00 04 00 52 00 ......R.
0008: 00 00 00 00 04 00 05 c0 .......À
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

This is reported in a clean install of XP Home with SP2 and updates.
The hardware setup is on a Maxtor 200GB HD via a Promise Ultra ATA 133 with the original 40GB HD also on this controller. The 200GB is reported as DMA6 and the 40GB DMA5.

Am I right in thinking that the above fault is related to the promise controller which has the lastest bios upgrade available?

How do I get rid of this problem?

Thanks

Toolman59

 

[micker377]

Is it possible to run the system off the native IDE ports and do without the Promise board? If so, it would narrow down the problem. (Could also be a memory problem).

 

[Freestone]

This is caused by your PC BIOS. You should see if there is a BIOS upgrade available for you motherboard.

Refer to these links for more information:

http://www.jsiinc.com/SUBJ/tip4500/rh4563.htm

http://support.microsoft.com/kb/q283649/

 

[toolman59]

micker377 and Freestone thank you for your help.
I have read the articles from the links, it would appear that this is a basic Windows XP reponse to the BIOS.
The latest BIOS upgrade for my system was issued in 2002, and is the one installed on my system. So until the MoBo people re-issue the BIOS code, I will ignore the Event viewer error reports.

It would appear that I was wrong in thinking that the Promise BIOS might be the culprit.

Toolman59