Event ID: 9, 11 and 57. Hardware or software issue?

This all started about a weak ago. My girlfriend was using the pc when it froze, mouse didn't respond, same for ctrl+alt+del, it froze dead, the only solution was to reboot. After the restart I went to event viewer to see what caused the freeze, around that time there was an error with EventID: 9, which said:
Log Name: System
Source: iaStor
Date: 06/03/2013 14:25:31
Event ID: 9
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Sanja-PC
Description:
The device, \Device\Ide\iaStor0, did not respond within the timeout period.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="iaStor" />
<EventID Qualifiers="49156">9</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-03-06T12:25:31.131854700Z" />
<EventRecordID>161357</EventRecordID>
<Channel>System</Channel>
<Computer>Sanja-PC</Computer>
<Security />
</System>
<EventData>
<Data>\Device\Ide\iaStor0</Data>
<Binary>0F0028000100000000000000090004C011111111090004C0000000000000000067452301EFCDAB89010000000000CCCC2800B0CD4C03200000000000000000000C000000EB23DDE90C000000EB23DDE9</Binary>
</EventData>
</Event>

Spending some time with google I found out that it could be related to Intel Rapid Storage Technology drivers. I tried disabling "link power management", some people on the web mentioned that it could help, to no avail... So in the end I decided to uninstall IRST drivers. It couldn't get any worse...
It helped, there were no more errors with EventID: 9.
But after couple of days a new problem appeared. I was still checking Event viewer now and then to see if the previous error would make it's reappearance and I saw four errors with EventID: 11, all of which said:
Log Name: System
Source: atapi
Date: 16/03/2013 12:49:15
Event ID: 11
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Sanja-PC
Description:
The driver detected a controller error on \Device\Ide\IdePort4.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="atapi" />
<EventID Qualifiers="49156">11</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-03-16T10:49:15.025151300Z" />
<EventRecordID>169036</EventRecordID>
<Channel>System</Channel>
<Computer>Sanja-PC</Computer>
<Security />
</System>
<EventData>
<Data>\Device\Ide\IdePort4</Data>
<Binary>0000100001000000000000000B0004C002000000850100C00000000000000000000000000000000003000000000000000000000004100000</Binary>
</EventData>
</Event>

So, naturally I went to the internet to find out what's causing it, as it turns out it can be a myriad of things, ranging from a driver error to faulty motherboard sata controller.
Since I don't have another hard drive, or another motherboard my hardware trouble shooting was, lets say, lacking. I've tried changing sata ports and sata cables, without any result. The things that I did find out were:
It seems to appear when hdd is under heavy load, like, when running an antivirus check, or scanning for errors on the drive. During which, sometimes, appears a warning with EventID: 57:
Log Name: System
Source: Ntfs
Date: 16/03/2013 17:22:24
Event ID: 57
Task Category: (2)
Level: Warning
Keywords: Classic
User: N/A
Computer: Sanja-PC
Description:
The system failed to flush data to the transaction log. Corruption may occur.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Ntfs" />
<EventID Qualifiers="32772">57</EventID>
<Level>3</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-03-16T15:22:24.668975200Z" />
<EventRecordID>169875</EventRecordID>
<Channel>System</Channel>
<Computer>Sanja-PC</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Binary>0000000001000000020000003900048000000000850100C000000000000000000000000000000000</Binary>
</EventData>
</Event>


Funny thing is, the system never froze again after that incident, which happened about a weak ago. The system seems to run stable. What got me worried is the number of unstable sectors that appeared in a short amount of time, in about a day it got from 9 to 18. And the number of errors with EventId: 11, at the moment there's 55 of them sitting in my event log. So I'm starting to think it's most likely a hardware issue, but which is it hard drive or motherboard? Oh, and I've ran HD Tune's Error scan, it found out that there's 2 damaged blocks.
My system specs:
Motherboard: Asus p8z68 pro/gen 3
CPU: Intel Core i5 2500k
HDD: Samsung HD103SJ
RAM: kingston hyperx 4gb/4gb ddr 3
GPU: ATI Radeon HD 5670 (ya, it's pretty outdated)
No cd/dvd drives, or external hard drives.
1 answer Last reply
More about event hardware software issue
  1. I tend to see those first two errors often on external hard drives, especially when under a heavy load like a virus scan or a backup. Most times I just think it's a miscommunication between the sata controller and the bridge chip used in the enclosure. A reboot (especially a cold boot) usually fixes it.
Ask a new question

Read More

Hardware Event Id Software Windows 7