You have a computer that is running Windows Server 2008 or Windows Vista. When you unmount a volume, delete a snapshot or try to fail over a disk on which snapshots are saved to another Cluster node, you receive the following Stop error message:

0×000000D6 (parameter1, parameter2, parameter3, parameter4)
DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION

Notes:

• The four parameters in this error message vary, depending on the computer’s configuration.
• Not all “0×000000D6″ Stop errors are caused by this problem.

After you create a mirrored volume on a computer that is running Windows Server 2008 or Windows Vista, you unexpectedly receive the following Stop error message:

Stop 0×0000000a (parameter1, parameter2, parameter3, parameter4)
IRQL_NOT_LESS_OR_EQUAL

Note: The parameters of the error message depend on the configuration of the computer.

Consider the following scenario:

• You create a volume on a computer that is running Windows Vista or Windows Server 2008. The size of the volume is a multiple of 8 gigabytes (GB). For example, the size of the volume is 8,192 megabyte (MB), 16,384 MB, or 32,768 MB.
  Note: 1 GB equals 1,024 MB.
• You extend the size of the volume by using the Disk Management tool or by using the Diskpart.exe utility.
• You run the ChkDsk.exe utility on the volume in read-only mode.
  Note: If you do not specify a switch when you run the ChkDsk.exe utility, the ChkDsk.exe utility runs in read-only mode

In this scenario, you receive the following error message:

The Volume Bitmap is incorrect.
Windows found problems with the file system.

Additionally, if you restore data that was backed up on the system, the restore operation may not finish successfully.

Consider the following scenario:

• You create a folder on a NT file system (NTFS) volume on a computer that is running Windows Server 2008 or Windows Vista.
• You configure this folder as a reparse point or as a mount point for volumes that are added.
• A formatted volume is mounted on the folder.

In this scenario under a stress situation, you receive the following message in a message dialog box when the volume is mounted to the reparse point or mount point:

You need to format the disk in drive before you can use it.
Do you want to format it?

In the message dialog box, if you click the Format disk button, the wrong volume is formatted. For example, you mount a volume on the “E:\mount” folder, and then you receive the message mentioned in this “Symptoms” section. If you click the Format disk button, volume E instead of the mounted volume is formatted.

On a computer that is running Windows Vista Tablet PC, you use a tablet pen to click the Sound icon in the notification area. However, when you click Mixer, Volume Mixer does not open. In this scenario, you must click Mixer several times to open Volume Mixer.

This problem also occurs when you use a mouse to open Volume Mixer.

You record audio by using the Sound Recorder application and a microphone in Windows Vista and windows XP. Even though the input volume settings are the same, when you play back the audio files, the volume of the audio file recorded in Windows vista may be lower than that in windows XP.

The Sound Volume Mixer (SndVol.exe) window may not open when clicking the Mixer HotLink button on a Windows Vista-based computer that has touch screen capabilities.

You have a volume mount point on a network share. In Windows Vista or in Windows Server 2008, when you call the GetVolumePathNameW function on the UNC path of the volume mount point to retrieve the specified mount point path, the function returns only the path of the network share. However, you expect the function to return the mount point path.

In Windows XP or Windows Server 2003, the mount path is returned as expected.

For example, you have a network share whose UNC path is \\Server\Share. In the network share, you have a volume mount point that has the UNC path \\Server\Share\MountDrive. When you pass the UNC path \\Server\Share\MountDrive\SubDir to the GetVolumePathNameW function to retrieve the mount point path, the function returns \\Server\Share. In Windows XP and Windows Server 2003, the function returns \\Server\Share\MountDrive.

In Windows Server 2008-based or Windows Vista Service Pack 1 (SP1)-based systems, if the system partition is a mirrored volume, and a system-critical issue occurs, the following behavior occurs:

• A blue screen is not displayed.
• A memory dump file is not generated.

Additionally, the following event is logged in the System log:

Log Name: System
Source: volmgr
Event ID: 45
Task Category: None
Level: Error
Keywords: Classic
Description:
The system could not successfully load the crash dump driver. 

On a Windows Server 2008 or Windows Vista Service Pack 1 (SP1)-based computer, you create some snapshots of a volume on the computer. You open the Properties dialog box of a shared folder on this volume, and then you click the Previous Versions tab. When you do this, lots of paged pool memory is suddenly consumed. This may cause a severe lack of paged pool memory on this volume.

Note: Windows Server 2003 or Windows XP-based computers that have hotfix 903234 installed do not encounter this problem.