.NET Questions and Solutions

As a software engineer, I focus on .NET, especially asp.net, C#, WCF and so on, and I am also very interested in Search Engine Optimization.

Entries Tagged ‘DEL’

Fatal Exception 0E with Multiple MS-DOS Device Names in Path

Symptoms
If the last two or more components in a path match MS-DOS device names, you may receive an error message on a blue screen similar to the following example:

A fatal exception 0E has occurred at (address) in VXD (FSD) + (address). The current application will be terminated.
* Press any key to terminate the current application. * Press CTRL+ALT+DEL to restart your computer. You will lose any unsaved information in all applications.
Press any key to continue NOTE: The VXD in question is a File System Driver (FSD) from the list in the “More Information” section of this article.
If you do not restart your computer at this point, subsequent blue screen error messages occur and the computer does not shut down properly. It may be necessary to interrupt power to the computer to reset it successfully.
Alternatively, if your computer has a large amount of memory (for example, 192 MB), the mouse pointer may be displayed as an hourglass over the taskbar and you may be unable to run additional programs. The computer eventually becomes unresponsive to mouse and keyboard input.
Resolution
MS-DOS device names are reserved words and cannot be used as folder or file names. When parsing a reference to a file or folder, Windows correctly checks for the case in which a single MS-DOS device name is used in the path, and treats it as invalid. However, Windows does not check for the case in which the path includes multiple MS-DOS device names. When Windows attempts to interpret the device name as a file resource, it performs an illegal resource access operation that usually results in the computer becoming unresponsive.
Because you cannot create files or folders that contain MS-DOS device names, it is unusual for a user to try to gain access to one under normal circumstances. The chief threat posed by this vulnerability is that a malicious user can entice a user to attempt such an access. For example, if a Web site operator hosts a hyperlink that references such a path, when the user clicks the link, the computer may hang. Likewise, a Web page or HTML e-mail message that specifies a local file as the source of rendering information can cause the user’s computer to hang when it is displayed. If this happens, you can put the computer back into normal service by restarting it.

Exception 0E in Vredir.vxd during CoCreateInstanceEx() on remote DCOM server

Symptoms
If your network is set up as a workgroup, you have a drive mapped to a Microsoft Windows NT-based server, and you run a Distributed Component Object Model (DCOM) program that attempts to start a remote server component on the Windows NT-based server, you may receive one of the following error messages on a blue screen.
Windows 95, Windows 98, Windows 98 Second Edition:

Windows
A fatal exception 0E has occurred at 0028:???????? in VXD VREDIR(??)+ ????????. The current application will be terminated.
* Press any key to terminate the current application.
* Press CTRL+ALT+DEL again to restart your computer. You will lose any unsaved information on all applications.
Press any key to continue.Windows Millennium Edition (Me):

Windows
An error has occurred. To continue:
Press Enter to return to Windows, or Press CTRL+ALT+DEL to restart your computer. If you do this, you will lose any unsaved information in all open applications.
File Name: VREDIR(06) + 00006C54 Error: 0E : 0028 : C02D2770
Press any key to continue.If you press ENTER, CoCreateInstanceEx returns RPC_S_CALL_FAILED (0×800706BE). The program may display the following error message:

The remote procedure call failed.See the “More Information” section of this article for the error message values for various versions of the Vredir.vxd file.
Resolution
The redirector (Vredir.vxd) incorrectly references internal resource data for the mapped drive connection while setting up the connection that the DCOM Remote Procedure Call (RPC) traffic will use.