SQL Server data corruption when a memory range is accessed by the SetFileIoOverlappedRange function and an I/O operation in Windows Vista, in Windows Server 2008, in Windows 7, or in Windows Server 2008 R2
You have a computer that is running one of the following operating systems:
Windows Vista
Windows Server 2008
Windows 7
Windows Server 2008 R2
The SetFileIoOverlappedRange function is called when another I/O operation is using the memory range that is specified in the SetFileIoOverlappedRange function.
For example, you create a new database in SQL Server, and you enable the Lock Pages in Memory permission in the database.
In this scenario, data corruption occurs in the first byte of a memory page in the specified memory range.
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Prerequisites
To apply this update, you must be running one of the following operating systems:
Windows Vista Service Pack 2 (SP2)
Windows Server 2008 Service Pack 2 (SP2)
Windows 7
Windows 7 Service Pack 1 (SP1)
Windows Server 2008 R2
Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest Windows Vista service pack
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for Windows Server 2008
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information
To apply this update, you do not have to make any changes to the registry.
Restart requirement
You must restart the computer after you apply this update.
Update replacement information
This update does not replace a previously released update.
File information
The global version of this update installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Collapse this tableExpand this table
Version
Product
SR_Level
Service branch
6.0.600
2
.
18xxx
Windows Vista and Windows Server 2008
SP2
GDR
6.0.600
2
.
22xxx
Windows Vista and Windows Server 2008
SP2
LDR
GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Ntkrnlpa.exe
6.0.6002.18595
3,602,816
06-Mar-2012
06:39
x86
Ntoskrnl.exe
6.0.6002.18595
3,550,080
06-Mar-2012
06:39
x86
Ntkrnlpa.exe
6.0.6002.22811
3,603,840
06-Mar-2012
06:39
x86
Ntoskrnl.exe
6.0.6002.22811
3,552,640
06-Mar-2012
06:39
x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Ntoskrnl.exe
6.0.6002.18595
4,699,520
06-Mar-2012
06:44
x64
Ntoskrnl.exe
6.0.6002.22811
4,687,744
06-Mar-2012
06:44
x64
For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Ntoskrnl.exe
6.0.6002.18595
9,475,456
06-Mar-2012
06:29
IA-64
Ntoskrnl.exe
6.0.6002.22811
9,468,288
06-Mar-2012
06:29
IA-64
Windows 7 and Windows Server 2008 R2 file information notes
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Collapse this tableExpand this table
Version
Product
Milestone
Service branch
6.1.760
0.16xxx
Windows 7 and Windows Server 2008 R2
RTM
GDR
6.1.760
0.21xxx
Windows 7 and Windows Server 2008 R2
RTM
LDR
6.1.760
1.17xxx
Windows 7 and Windows Server 2008 R2
SP1
GDR
6.1.760
1.21xxx
Windows 7 and Windows Server 2008 R2
SP1
LDR
GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Ntkrnlpa.exe
6.1.7600.16973
3,958,128
06-Mar-2012
05:59
x86
Ntoskrnl.exe
6.1.7600.16973
3,902,320
06-Mar-2012
05:59
x86
Ntkrnlpa.exe
6.1.7600.21163
3,971,440
06-Mar-2012
05:59
x86
Ntoskrnl.exe
6.1.7600.21163
3,915,632
06-Mar-2012
05:59
x86
Ntkrnlpa.exe
6.1.7601.17790
3,968,368
06-Mar-2012
05:59
x86
Ntoskrnl.exe
6.1.7601.17790
3,913,072
06-Mar-2012
05:59
x86
Ntkrnlpa.exe
6.1.7601.21936
3,972,464
06-Mar-2012
05:41
x86
Ntoskrnl.exe
6.1.7601.21936
3,916,656
06-Mar-2012
05:41
x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Ntoskrnl.exe
6.1.7600.16973
5,504,880
06-Mar-2012
06:43
x64
Ntoskrnl.exe
6.1.7600.21163
5,473,136
06-Mar-2012
06:51
x64
Ntoskrnl.exe
6.1.7601.17790
5,559,152
06-Mar-2012
06:53
x64
Ntoskrnl.exe
6.1.7601.21936
5,561,200
06-Mar-2012
06:30
x64
Ntkrnlpa.exe
6.1.7600.16973
3,958,128
06-Mar-2012
05:59
x86
Ntoskrnl.exe
6.1.7600.16973
3,902,320
06-Mar-2012
05:59
x86
Ntkrnlpa.exe
6.1.7600.21163
3,971,440
06-Mar-2012
05:59
x86
Ntoskrnl.exe
6.1.7600.21163
3,915,632
06-Mar-2012
05:59
x86
Ntkrnlpa.exe
6.1.7601.17790
3,968,368
06-Mar-2012
05:59
x86
Ntoskrnl.exe
6.1.7601.17790
3,913,072
06-Mar-2012
05:59
x86
Ntkrnlpa.exe
6.1.7601.21936
3,972,464
06-Mar-2012
05:41
x86
Ntoskrnl.exe
6.1.7601.21936
3,916,656
06-Mar-2012
05:41
x86
For all supported IA-64-based versions of Windows Server 2008 R2
Method 1: Reset Windows Update components and then try updating your computer
To reset the Windows Update components automatically, click the
Fix it
button or link. Click
Run
in the
File Download
dialog box, and then follow the steps in the Fix it wizard.
Note this Fix it Solution has two modes Default and Aggressive. You should run the Fix it solution in Default mode and determine whether it resolves your problem with Windows Update before you ru it in Aggressive mode.
Note this wizard may be in English only; however, the automatic fix also works for other language versions of Windows.
Note if you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.
For more information about how to reset Windows Update components, visit the following Microsoft Website:
Method 2: Manually download the update from the download link and then install it in clean boot mode
We suggest you to install the updates in clean boot mode to avoid the interruption of non-Microsoft programs. To enter clean boot mode on a computer, follow these steps:
Click Start, type msconfig in the Start Search box, and then press ENTER.
If you are prompted for an administrator password or for confirmation, type the password or click Continue.
On the General tab, click Selective Startup.
Under Selective Startup, clear the Load Startup Items check box.
Click the Services tab, click to select the Hide All Microsoft Services check box, and then click Disable All.
Click OK.
When you are prompted, click Restart.
Try update your computer again.
For more information about this method, visit the following Microsoft Website:
331796
Perform a clean startup to determine whether background programs are interfering with your game or program
Additional file information
Additional file information for Windows Vista and for Windows Server 2008
Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
Back to the top
