Article ID: 329075 - View products that this article applies to.
This article was previously published under Q329075
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows registry
When you use dynamic disks, you may receive the following Dmio event log entries, which may lead to data corruption, database corruption, or file system corruption on one or more dynamic disk volumes, or may cause application failures:
Event Type: Information Event Source: dmio Event Category: None Event ID: 29 Date: MM/DD/YYYY Time: HH:MM:SS AM/PM User: N/A Computer: Computer_Name Description: dmio: Harddisk9 read error at block 445136247: status 0xC000009A Event Type: Warning Event Source: dmio Event Category: None Event ID: 35 Date: MM/DD/YYYY Time: HH:MM:SS AM/PM User: N/A Computer: Computer_Name Description: dmio: Disk Harddisk9 block 445136247 (mountpoint F:): Uncorrectable read error Event Type: Information Event Source: dmio Event Category: None Event ID: 30 Date: MM/DD/YYYY Time: HH:MM:SS AM/PM User: N/A Computer: Computer_Name Description: dmio: Harddisk2 write error at block 411779656: status 0xC000009A
This problem occurs because of a combination of conditions or factors, which include:
To resolve this problem, use one of the following methods:
Method 1: Modify the RegistryWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Reduce the concurrent I/O requests that are permitted by the mass storage controller. To do this, follow these steps:
(http://support.microsoft.com/kb/240314/ )INFO: Restriction on the Number of Concurrent I/O Requests Setting
Method 2: Modify the Boot.ini FileRemove the /3GB switch from the Boot.ini file, and then restart the computer.
Method 3: Use the /USERVA Switch in the Boot.ini File (Windows 2003 only)For more information about how to use the /USERVA switch in the Boot.ini file, click the following article number to view the article in the Microsoft Knowledge Base:
316739The following Windows 2003 fix may also impact PTE usage and help eliminate the errors:
(http://support.microsoft.com/kb/316739/ )How to Use the /USERVA Switch in the Boot.ini File to Tune /3GB Configurations
(http://support.microsoft.com/kb/831899/ )You receive a "stop 0x000000DA" error message on a blue screen after you enable PTE tracking on a Windows Server 2003-based node
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/247904/ )How to Configure the Paged Address Pool and System Page Table Entry Memory Areas
(http://support.microsoft.com/kb/274750/ )HOW TO: Configure Memory for More Than 2 GB in SQL Server
Article ID: 329075 - Last Review: October 30, 2006 - Revision: 7.3