XP error report - post bsod

[Retruglot]

I consistently get the following error in XP...

Event Type: Error
Event Source: ACPI
Event Category: None
Event ID: 5
Date: 1/5/2002
Time: 9:34:00 AM
User: N/A
Computer: xxxxxxxxxx [removed by Ret]
Description:
AMLI: ACPI BIOS is attempting to write to an illegal IO port address (0xcf8), which lies in the 0xcf8 - 0xcff 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 05 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 ........


Event Type: Error
Event Source: ACPI
Event Category: None
Event ID: 5
Date: 1/5/2002
Time: 9:34:00 AM
User: N/A
Computer: xxxxxxxxxx [removed by Ret]
Description:
AMLI: ACPI BIOS is attempting to write to an illegal IO port address (0x70), 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 05 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 ........


Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 1/5/2002
Time: 9:35:06 AM
User: N/A
Computer: xxxxxxxxxx [removed by Ret]
Description:
Error code 0000000a, parameter1 00000004, parameter2 00000002, parameter3 00000000, parameter4 804f1a9e.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 30 0000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 34 2c 20 000004,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 34 66 00, 804f
0050: 31 61 39 65 1a9e


Now, this looks like a harddrive controller problem to me (although that is a wild guess on my part). And since I AM the "system vendor" I'm leaning on you guys/gals to provide some intellectual resource. I'm getting ready to do a Seatools test on the drive, but wonder if you folks know if you can update/flash/patch (whatever) the firmware on a harddrive? I've never heard of doing this, but then again, I've not heard of doing a lot of things...

Anybody got any ideas?


Thanks,
Ret

 

[labdog]

you can update your hd firmware from your constructor site.
but it can be not exist for your specific hd.


if you know you don't know, the way could be more easy.

 

[Retruglot]

Looks like flashing the BIOS solved the above problem... now I just get one error in Event Viewer:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 1/5/2002
Time: 1:10:02 PM
User: N/A
Computer: xxxxxxxxxx
Description:
Error code 0000000a, parameter1 00000004, parameter2 00000002, parameter3 00000000, parameter4 804f1a9e.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 30 0000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 34 2c 20 000004,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 34 66 00, 804f
0050: 31 61 39 65 1a9e


Any ideas?

I have found the Event Viewer a pretty handy tool.. it seems to log all "Events" (go figure) and provides me an option to see what the heck happened. Now if I could only figure out what this [-peep-] means!! (something else I didn't have in 98SE - Event Viewer) Anywayz...


Ret

 

[Retruglot]

Incase it is any use to you, I seem to have overcome this latest error by uninstalling the video drivers... (Nvidia GeForce 256)... XP automatically reinstalled them (the exact same drivers), but I've rebooted a coupla times and the error has ceased... (it used to come up after every boot and eventually bomb the system).


Thanks,
Ret


Oh yea,
And labdog, there if you 3 jutts, ok?