Exception 0E in Vredir error messages when you open network files

Article translations Article translations
Article ID: 293793 - View products that this article applies to.
This article was previously published under Q293793
This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
Expand all | Collapse all

On This Page

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 "More Information" 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 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 hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual 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
   ----------------------------------------------------------------------
   30-Mar-2001  10:05am  4.10.2230  165,461  Vredir.vxd  Windows 98 SE
   22-Mar-2001  17:02pm  4.90.3006  161,849  Vredir.vxd  Windows Me
				

Workaround

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
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 following article number to view the article in the Microsoft Knowledge Base:
129202 Explanation of opportunistic locking on Windows NT

Status

Microsoft has confirmed that this is 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. As of June 26 2001, information about the latest update to the Ifsmgr.vxd file is available in the following Microsoft Knowledge Base article:
273017 ScanDisk runs even though Windows shut down correctly
For additional information about Windows Millennium and the updated Directory Services Client, click the following article number to view the article in the Microsoft Knowledge Base:
276472 Directory Services Client is not included with Windows Me
For additional information about Windows 98 and Windows 98 Second Edition hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
206071 General information on Windows 98 and SE hotfixes
For additional information about Windows Me hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
295413 General information about Windows Millennium Edition hotfixes
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 293793 - Last Review: October 25, 2013 - Revision: 1.0
Applies to
  • Microsoft Windows 95
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbenv kbfix kbnetwork KB293793

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com