I have a Windows Server 2003 that stops working randomly (displays image on monitor but is completely frozen), all I could found on the event log as causes were an error from atapi and a warning from msas2k3.
The event log entries are:
Event Type: Error Event Source: atapi
Event Category: None Event ID: 9
Date: 22-07-2009 Time: 16:13:33
User: N/A Computer: SERVER
Description: The device,
\Device\Ide\IdePort0, did not respond
within the timeout period.For more information, see Help and
Support Center at
http : // go.microsoft.com / fwlink / events.asp.
Data: 0000: 0f 00 10 00 01 00 64 00
……d. 0008: 00 00 00 00 09 00 04 c0
…….À 0010: 01 01 00 50 00 00 00 00
…P…. 0018: f8 06 20 00 00 00 00 00
ø. ….. 0020: 00 00 00 00 00 00 00 00
…….. 0028: 00 00 00 00 01 00 00 00
…….. 0030: 00 00 00 00 07 00 00 00
……..Event Type: Warning Event
Source: msas2k3 Event Category: None
Event ID: 129 Date: 22-07-2009
Time: 16:14:23 User: N/A
Computer: SERVER Description: Reset to
device, \Device\RaidPort0, was issued.For more information, see Help and
Support Center at
http : // go.microsoft.com / fwlink / events.asp.
Data: 0000: 0f 00 10 00 01 00 68 00
……h. 0008: 00 00 00 00 81 00 04 80
…… 0010: 04 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
…….. 0028: 00 00 00 00 00 00 00 00
…….. 0030: 01 00 00 00 81 00 04 80
……
Any hints?
Best Answer
I'm aware that this is an old question, but I've replaced many a burnt-out consumer motherboard for this when the user tries overclocking and manages to run the southbridge outside of spec. SATA controller pooches itself and starts to throw these errors.
I'd have a suspicious look at your RAID controller; all the drive-level redundancy in the world won't save you if the controller itself goes Tango Uniform.