hi every one I am satish I am a tech support engg
sledgus said:
I have been having trouble starting up windows XP. Everytime i start up XP, it always freezes. I would do something as simple as try to open My Computer, or internet explorer, and it would freeze, or take a lifetime to open.
I am also unable to install any programs, as I keep getting Error 1117 I/O error. I have ran HDD tests, and everything points to the HDD being fine. My main suspicion is that I have RAM problems??
I have done 2 complete formats, and fresh installs of windows XP profesional, and that didnt help!
Does anyone know what could be the problem?
If you receive the following error message, it might indicate that Microsoft SQL Server 2000 has detected hardware or system problems when it was reading from or writing to database files:
Error 823
I/O error <error> detected during <operation> at offset <offset> in file '<file>'
The format of the error message is slightly different in Microsoft SQL Server 2005 and Microsoft SQL Server 7.0. However, the same concepts and discussions also apply to SQL Server 2005 and SQL Server 7.0.
For more information about the various parts of this message, such as <error> and <operation>, and for more information about the use of Microsoft Windows API calls that are made by SQL Server 2000
TRY THIS:---------------------------
SQL Server 2000 raises the error that is mentioned in the "Symptoms" section of this article if the following conditions are true: • Operating system error: A read Windows API call or a write Windows API call is not successful, and SQL Server encounters an operating system error that is related to the Windows API call. The following error message is an example of an 823 error for an operating system:
2003-07-28 09:01:27.38 spid75 Error: 823, Severity: 24,
State: 2
2003-07-28 09:01:27.38 spid75 I/O error 1117 (The request could not be performed because of an I/O device error.) detected during read at offset 0x0000002d460000 in file 'e:\program files\Microsoft SQL Server\mssql\data\mydb.MDF'
Except for the operating system error 6 (“The handle is invalid”), operating system errors that are reported for 823 errors are likely related to an underlying system problem or hardware problem. If an operating system error occurs, even if the DBCC CHECKDB statement does not report a problem, you may have to work with your hardware vendor, system administrator, or Microsoft Product Support Services to resolve this problem.
Note You may or may not see errors from the DBCC CHECKDB statement on the database that is associated with the file in the error message. You can run the DBCC CHECKDB statement when you see an 823 error. If the DBCC CHECKDB statement does not report any errors, you probably have an intermittent system problem or a disk problem.
• I/O logical check failure: If a read Windows API call or a write Windows API call for a database file is successful, but specific logical checks on the data are not successful (a torn page, for example), an 823 error is raised. The following error message is an example of an 823 error for an I/O logical check failure:
2003-09-05 16:51:18.90 spid17 Error: 823, Severity: 24,
State: 2
2003-09-05 16:51:18.90 spid17 I/O error (torn page) detected during read at offset 0x00000094004000 in file 'F:\SQLData\mydb.MDF'..
To resolve this problem, first run the DBCC CHECKDB statement on the database that is associated with the file in the error message. If the DBCC CHECKDB statement reports errors, correct those errors before you troubleshoot this problem. If the problem persists even after the DBCC CHECKDB errors have been corrected, or if the DBCC CHECKDB statement does not report any errors, review the Microsoft Windows NT system event log for any system errors or disk-related errors. You can also contact your hardware vendor to run any appropriate diagnostics.
