Identifying Reason for Hardware Crash

[eAndy]

I'm experiencing system reboots in Windows Server 2000 and Windows Server
2003.

The server just stops and restarts.

I'm pretty sure its a hardware problem.

Can you identify specific articles/resources that can be used to identify
and resolve the problem?

(I've gone through the clean the machine, re-seat cards and simple stuff)

thanks

[eAndy]

No. It appears the machine just reboots vs. a BSD.

I am getting a number of these:

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.

Any way to identify which device its accessing?



"Oli Restorick [MVP]" > wrote in message
...
> Does the event log indicate that a minidump has been generated? If so,
> there are resources on the Microsoft sire for interpreting the crash
dumps.
>
> Oli
>
> "eAndy" > wrote in message
> ...
> > I'm experiencing system reboots in Windows Server 2000 and Windows
Server
> > 2003.
> >
> > The server just stops and restarts.
> >
> > I'm pretty sure its a hardware problem.
> >
> > Can you identify specific articles/resources that can be used to
identify
> > and resolve the problem?
> >
> > (I've gone through the clean the machine, re-seat cards and simple
stuff)
> >
> > thanks
> >
> >
>
>

[eAndy]

Found this.

http://support.microsoft.com/default.aspx?scid=kb;en-us;283649&sd=ee

Seems that a PCI card may not be working properly. I say that as it has
worked fine for 3 years and just now started misbehaving.

Thanks

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.

"Oli Restorick [MVP]" > wrote in message
...
> Does the event log indicate that a minidump has been generated? If so,
> there are resources on the Microsoft sire for interpreting the crash
dumps.
>
> Oli
>
> "eAndy" > wrote in message
> ...
> > I'm experiencing system reboots in Windows Server 2000 and Windows
Server
> > 2003.
> >
> > The server just stops and restarts.
> >
> > I'm pretty sure its a hardware problem.
> >
> > Can you identify specific articles/resources that can be used to
identify
> > and resolve the problem?
> >
> > (I've gone through the clean the machine, re-seat cards and simple
stuff)
> >
> > thanks
> >
> >
>
>

[Ivan Sheng]

Hello eAndy,

This behavior may occur if your computer's basic input/output system (BIOS)
tries to write to a port in ACPI Machine Language (AML). This attempt
causes Windows Server 2003 to prevent all access to that port.

To resolve this issue, contact your computer manufacturer or the BIOS
vendor for possible updates to your computer BIOS. For more information,
you can refer to these 2 articles

Error Message: ACPI BIOS Is Attempting to Write to an Illegal IO Port
WGID:493
ID: 317513.KB.EN-US
http://support.microsoft.com/default.aspx?scid=KB;EN-US;317513

Error Message: ACPI BIOS Is Attempting to Write to Illegal IO Port WGID:358
ID: 283649.KB.EN-US
http://support.microsoft.com/default.aspx?scid=KB;EN-US;283649

Please let me know if you have any questions.

Ivan Sheng
Microsoft Online Partner Support
MCSD,MCSE4,2000,MCDBA,CCNA,ASE
Get Secure! ¨C www.microsoft.com/security

This posting is provided ¡°as is¡± with no warranties and confers no rights.

[Oli Restorick [MVP]]

Does the event log indicate that a minidump has been generated? If so,
there are resources on the Microsoft sire for interpreting the crash dumps.

Oli

"eAndy" > wrote in message
...
> I'm experiencing system reboots in Windows Server 2000 and Windows Server
> 2003.
>
> The server just stops and restarts.
>
> I'm pretty sure its a hardware problem.
>
> Can you identify specific articles/resources that can be used to identify
> and resolve the problem?
>
> (I've gone through the clean the machine, re-seat cards and simple stuff)
>
> thanks
>
>