Microsoft KB Archive/293793

{|
 * width="100%"|

Exception 0E in Vredir Error Messages When You Open Network Files

 * }

Q293793

-

The information in this article applies to:


 * Microsoft Windows 95
 * Microsoft Windows 98
 * Microsoft Windows 98 Second Edition
 * Microsoft Windows Millennium Edition

-

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the &quot;Restoring the Registry&quot; Help topic in Regedit.exe or the &quot;Restoring a Registry Key&quot; Help topic in Regedt32.exe.

SYMPTOMS
When you open several files that are stored in a shared folder on a network, your computer may generate one of following error messages on a blue screen, you may be unable to continue normally, and you may receive more error messages on blue screens if you attempt to continue.

NOTE: The following sample error messages may apply if no updates to the Ifsmgr.vxd file have been applied to your computer. For more information about updates to the Ifsmgr.vxd file, please see the &quot;More Information&quot; section of this article.

Windows Millennium Edition (Me)
Windows

An exception 0E has occurred at 0028:???????? in VxD VREDIR(01) +

????????. This was called from 0028:C0033AE8 in VxD IFSMGR(01) +

00001098. It may be possible to continue normally.


 * Press any key to attempt to continue.


 * Press CTRL+ALT+DEL to restart your computer. You will

lose any unsaved information in all applications.

Press any key to continue

Windows 98 Second Edition
Windows

An exception 0E has occurred at 0028:???????? in VxD VREDIR(01) +

????????. This was called from 0028:C0034A74 in VxD IFSMGR(01) +

00001094. It may be possible to continue normally.


 * Press and key to attempt to continue.


 * Press CTRL+ALT+DEL to restart your computer. You will

lose any unsaved information in all applications.

Press any key to continue

Windows 98
Windows

An exception 0E has occurred at 0028:???????? in VxD VREDIR(01) +

????????. This was called from 0028:C0034184 in VxD IFSMGR(01) +

00001094. It may be possible to continue normally.


 * Press and key to attempt to continue.


 * Press CTRL+ALT+DEL to restart your computer. You will

lose any unsaved information in all applications.

Press any key to continue

The following list provides information about the values that should appear in place of the question marks in the preceding sample error messages. Note that only the original (and latest) versions of the redirector file (Vredir.vxd) are documented. Exception address values may vary on your computer if you have installed updates that are not listed. Also, the list is not guaranteed to be comprehensive, as not all redirector updates have been exhaustively tested for this problem. However, fault addresses tend to be near those that are documented:

Blue Screen Address Information            Product           Update/Add-On -- 0028:C0066326 in VxD VREDIR(01) + 0000459A Windows Me        none 0028:C006693E in VxD VREDIR(01) + 00004BB2 Windows Me        Q284084 0028:C0077F0B in VxD VREDIR(01) + 00004A57 Windows 98 SE     none 0028:C0078167 in VxD VREDIR(01) + 00004CA7 Windows 98 SE     Q278558 0028:C0076EE1 in VxD VREDIR(01) + 00004479 Windows 98        none 0028:C007758F in VxD VREDIR(01) + 00004B27 Windows 98        Q278558 0028:C0078167 in VxD VREDIR(01) + 00004CA7 Windows 95/98/Me  DSClient 0028:C0075065 in VxD VREDIR(01) + 00004689 Windows 95/98/Me  DSClient

In the preceding table, Windows 98 SE is used to represent Microsoft Windows 98 Second Edition, and DSClient is used to represent Directory Services Client. NOTE: The problem that is described in this article has not been tested with Microsoft Windows 95. Note that the Directory Services Client can be installed on a Windows 95-based computer.

CAUSE
This problem can occur because when files are repeatedly opened and closed by using identical share modes, the redirector (Vredir.vxd) loses track of internal file-tracking structures, and erroneously schedules system events to close and deallocate file structures that have already been processed.

RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article and should be applied only to systems experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/directory/overview.asp

NOTE: In special cases, charges that are normally incurred for support calls may be canceled, if a Microsoft Support Professional determines that a specific update will resolve your problem. Normal support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

  Date           Time     Version    Size     File name   Operating System March/30/2001 10:05am  4.10.2230  165,461  Vredir.vxd  Windows 98 Second Edition March/22/2001 05:02pm  4.90.3006  161,849  Vredir.vxd  Windows Me IMPORTANT: The update that is described in this article supercedes the update that is described in the following Microsoft Knowledge Base article:

"Q278558 Mapped Drive Access Denied to Windows 2000-Based Server"

WORKAROUND
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the &quot;Changing Keys and Values&quot; Help topic in Registry Editor (Regedit.exe) or the &quot;Add and Delete Information in the Registry&quot; and &quot;Edit Registry Data&quot; Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD).

To work around this problem, disable opportunistic locking on the server by setting the server 'EnableOplocks' registry value to '0' (zero). For additional information about this topic, click the article number below to view the article in the Microsoft Knowledge Base:

"Q129202 PC Ext: Explanation of Opportunistic Locking on Windows NT"

STATUS
Microsoft has confirmed this to be a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION
This problem has been observed to occur when Microsoft Office 2000, and Microsoft Office XP programs are in use, where the network files exist on a Windows 2000 server folder that is shared under more than one name. For additional information about Vredir.vxd updates, click the article numbers below to view the articles in the Microsoft Knowledge Base:

"Q284084 Workgroups Missing from Network Neighborhood with Multiple Protocols Installed on Windows Me" "Q278558 Mapped Drive Access Denied to Windows 2000-Based Server" As of June 26 2001, information about the latest update to the Ifsmgr.vxd file is available in the following Microsoft Knowledge Base article:

"Q273017 ScanDisk Runs Even Though Windows Shut Down Correctly" For additional information about the Directory Services Client, click the article numbers below to view the articles in the Microsoft Knowledge Base:

"Q283261 Version Conflicts with the Directory Service Client Version of Windows 95 and Windows 98 System Files" "Q276472 Directory Services Client Is Not Included with Windows Me" Additional query words:

Keywords : kbenv kbnetwork kbtool kbWinME

Issue type : kbbug

Technology : kbWinMEsearch kbWin95search kbWin98search kbWin98SEsearch kbZNotKeyword3 kbWin98 kbWinME kbWin98SE