PDA

View Full Version : ACPI bios is trying to write to a illegal I/O port address 0xcfc in the protected ran


sofokles
05-02-2005, 08:14 PM
I get an error code in event list that I dont understand or know what to do with. I've been reading several chapters of the excellent guide, but there are so many sub pages/topics referenced that I just keep loosing track of time and and purpose and all of a sudden another day is gone and the problem not fixed.

I'm on a Asus A7V, bios rev 1.04, duron 650 @650 cooled by Silver Arctic copper silent, 512 Mb ram,a floppy, cd-rom, 30 and 89 Gb WD EIDE on separate IDE slots, a msi nVidia GeForce 2 graphic card, a soundblaster 5.1 platinum live using kx drivers, and a Realtec network adapter. XP-pro SP1.

The error messages are milliseconds ahead of system hang and they read

1. ACPI bios is trying to write to a illegal I/O port address 0xcfc in the protected range 0xcf8-0xcff

2. ACPI bios is trying to read from a illegal I/O port address 0xcfc in the protected range 0xcf8-0xcff

How do I go ahead to figure this out ? It's got something to do with multimedia, I suspect, but I'm in no way sure.

All help greatly appreciated.

PrntRhd
05-02-2005, 11:03 PM
A Google search had loads of HP Pavillion XT983 (1.4GHz AMD) owners howling about this, seems Microsoft says it is a BIOS issue, and HP had not new BIOS updates to fix it.

sofokles
05-03-2005, 05:03 AM
Well, I'm not on a HP ( I have an HP scanner though and it sucks). In my mobo's manual, which I have read, ACPI is only mentioned in the glossary, I have turned the power management Off in Bios.

Is there a way to find exactly what triggers the ACPI request ?

And is it possible to find out why this particular range is protected, and perhaps move/readdress it ?

ski
05-03-2005, 12:45 PM
It may be caused by bad RAM.
D/L and run memtest86 to check the memory.
Be sure to run the test with only one module installed at a time.

If the RAM is ok, then did you try updating the BIOS?

If so, then it's also possible that a MS security update is the cause.

sofokles
05-03-2005, 01:46 PM
Ram is fine, tested OK.

I had problems updating bios as XP pro have problems formatting floppies in fat 16 and the old bios had problems reading system floppy disks in fat 32. Then I remembered that laptop from the stone age, used that for formatting purposes, and were then able to update bios. Problem seems to be solved for now, but i haven't connected all the peripherals yet.

However as I'm like a sponge for knowledge I'd much appreciate if someone could answer the questions in my last post. My computer is a guinea pig and toy and if it dies, so be it, as long as I learn something from it. :D