UPDATE: Here is the error message from the system log.
Log Name: System
Date: 10/18/2013 6:12:31 AM
Event ID: 7
Task Category: None
The device, \Device\Harddisk0\DR0, has a bad block.
<Provider Name="disk" />
<TimeCreated SystemTime="2013-10-18T10:12:31.771Z" />
Our theory is that the bad block is in the logical drive, not the physical drive. We have done the chkdsk and found no errors. We have seen this same error on a set of mirrors drives using RAID 1. We first replaced drive 0 of the pair, it was rebuilt but the error continued. So we moved the drive taken from drive 0 and installed it as Drive 1. Once it was rebuilt, the error continued.
Windows writes event about bad block in two cases: in case the verify read returns different from what should be written (applicable only for certain operations) and in case that system cannot complete read at all. You are likely faced with RAID 5 'write hole' trouble, when because of wrong data or parity chunk controller takes a lot of time in hopeless data block reconstruction. The solution is a full backup and full array recreation.
About RAID Web Console: check that its system service is running and allowed in Windows Firewall.
Our best recommendation is running the Intel System Information Retrieval Utility (sysinfo) For UEFI and sending the logs to your local support group for further assistance: