1. Did you try to fix it with DBCC CHECKDB with REPAIR_REBUILD option. Please read the recommendation to run a dbcc checkdb from BOL.

2. If this does not solve only one...

Wanted to know if AUTOGROW option is enabled ??

check this KB http://support.microsoft.com/kb/317375/en-us

Minaz

Check if any trigger is getting fired. !!

I am not sure if the Replication is causing the issue. You should have good backup plan. That will solve the issue.

Please follow these links for more info:

http://support.microsoft.com/kb/272318/en-us

As SQLBill, try to recycle the log.

 What is the total server memory ? What is the max / min SQL server memory?

is there /3GB is enabled in the Boot.ini ?

You need to do a fresh installation and rebuild the cluster.

Minaz

What is memory configuration of the SQL Server. ?

1. Check if there is fragmentaion of the virtual memory then defrag it.

2. Check the output of the DBCC MEMORYSTATUS shown where...

C:\WINDOWS\Minidump\Mini070307-05.dmp. did you checked this dump file?

Minaz

As you have mentioned you are in RTM version, I would suggest it will be better if you apply SP2.

Minaz

Thanks Sugesh I learned about the SP.

Apart from this there is a good KB :

http://support.microsoft.com/kb/314546/en-us

http://support.microsoft.com/kb/246133/en-us

http://support.microsoft.com/kb/137983/en-us

Event ID 824 is similar to the 823 error message which is related to problem in the I/O subsystem, such as a failing disk drive, disk firmware problems, faulty device...

Michael has explained well about blocking and I have found some good KB which will also help you to understand blocking and how to troubleshoot it.

http://support.microsoft.com/kb/224453/en-us

Minaz

Hey this error itself says that network address is the problem.

1. Did you check the SQL server is listening on 1433 port.

2. Enable the TCP/IP protocol ->  Client Configuration dialog...

Review the following links for more info:

http://msdn2.microsoft.com/en-us/library/ms151247.aspx

Minaz Amin