Did this error message appear after your comp suddenly restarted or STOP message? That file contains data that WinXP collected when your comp crashed (is used to report back to Microsoft for troubleshooting).
Open your Event viewer (type <b>eventvwr.msc</b> in Run command) to see what application caused it crash.
Good or Bad have no meaning at all, depends on what your point of view is.
ACPI bios is attemping to read from an illeagl IO port address (oxcfc) which lies in the Oxcf8-Oxcff protected address range. This could lead to system instability.
I had other errors like a few system errors but this ACPI error was the most. Any ideas on what caused this?
Also you were right the computer would just suddenly restart most of the time no warning, but sometimes give the blue screen. This happened suddenly had no problems before.
System is Asus A7v not sure which bios 1004b I think. I need to update bios do you think this would help?
Also tried the first suggestion delete temp files, etc. didn't seem to help.
This is what I did before my problem started; I installed battlefield 1942, played it decided I needed a flight stick to fly, bought one, hooked it up to the usb port which to my knowledge has never been used before.
So it is possible that using the usb port(with the current bios version) caused this problem?
Thanks for the info!
If the error didn't occur until you connected the joystick, then yes, that's probably the source of the problem. However, from the information I've found about the error around the 'Net, a BIOS flash seems to be the consensus opinion for a "fix", which is the same thing that Microsoft recommends.
Check out the search:
<A HREF="http://www.google.com/search?as_q=ACPI+bios+is+attempting+to+read+from+an+illegal+IO&num=100&hl=en&ie=UTF-8&oe=UTF-8&btnG=Google+Search&as_epq=&as_oq=&as_eq=&lr=&as_ft=i&as_filetype=&as_qdr=all&as_occt=any&as_dt=i&as_sitesearch=&safe=images" target="_new">ACPI bios is attemping to read from an illegal IO port address</A>
I think your choices are to either try the flash to attempt to correct the error, or to switch the power management type in the BIOS from ACPI to APM, which would require a fresh installation of Windows. This would allow you to select a standard HAL at the beginning of Windows Setup. You should also change the APIC controller in the BIOS to PIC (if listed as an option in your current BIOS version) when switching to APM. This will eliminate virtual IRQ's. Not every BIOS fully supports an APIC controller, and this can lead to inexplicable device conflicts that are not visible in the Device Manager.
<A HREF="http://www.anandtech.com/guides/viewfaq.html?i=47" target="_new">Correct procedure to change your system from the ACPI Hardware Abstraction Layer to the Standard PC/APM HAL</A>
This might be the best choice in the long run, if the BIOS flash doesn't fix the problem. An APIC controller really isn't needed anyway, not unless you have a dual-processor system.
I had to change the IRQ controller type on my main Intel rig to PIC in order to achieve stability when installing new devices (such as a USB joystick) although it wasn't necessary in this situation to switch the power management type to APM. (A PIC controller can function with ACPI.) In layman's terms, I just needed to keep the APIC-incompatible BIOS version from interfering with the way Windows handles the IRQ address assignments, and remove the virtual IRQ gateway. Sticking with the actual hardware IRQ addresses made all the difference for my system.
Comment: A BIOS flash didn't change a thing on my system.
In any case, changing the IRQ controller type means at least running a repair of the OS from the Recovery Console on the Windows CD. But switching the power management type really needs a fresh install of Windows, so you can load the Standard HAL.
Afterwards, Windows might develop a minor <A HREF="http://www.experts-exchange.com/Operating_Systems/Q_20234461.html" target="_new">shutdown issue</A>, which would require enabling APM in the APM or Power Options tab in the Control Panel.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.