Windows 95 Fatal Exception Errors


From: http://www.slip.net/~gregoryn/fatal.htm

Fatal Exception Error Using DHCP
"Fatal Exception 0D" Error Message Installing Program message:
"Fatal Exception 0E" Error Message When Running McAfee VirusScan
Fatal Exception Error Running Add New Hardware Wizard
"Exception 0E in VPOWERD" During First Boot
Fatal Exception in VMM(06) Caused by Damaged Registry
A Fatal Error Has Occurred in VxD VMCPD
Fatal Exception Error Accessing Windows NT Share From Windows 95
CD-ROM. "Fatal Exception 0E" May Occur During Critical Suspend
Fatal Exception in Msgsrv32.exe When You Quit Windows 95

What Are Windows 95/98 Fatal Exception Errors (scroll down for codes and fixes at bottom of page) When you attempt to start Windows or an application inside of Windows, you may encounter errors similar to the following:

A fatal exception <XY> has occurred at xxxx:xxxxxxxx

Fatal exception errors are codes returned by a program in the following cases:
- Access to an illegal instruction has been encountered
- Invalid data or code has been accessed
- The privilege level of an operation is invalid
When any of these occur, the processor returns an exception to the operating system, which in turn is handled as a Fatal Exception Error. In many cases the exception is nonrecoverable and the system must either be restarted or shutdown, depending upon the severity of the error.

In the following example of a Fatal Exception error
A fatal exception <XY> has occurred at xxxx:xxxxxxxx
the <XY> represents the actual processor exception from 00 to 0F. The xxxx:xxxxxxxx represents the enhanced instruction pointer to the code segment and the 8-bit address is the actual address where the exception occurred. Windows does not cause these errors, but has the exception handling routine for that particular processor exception, which displays the above message.

The following article details the processor exceptions and their meaning. For more information about troubleshooting strategies for Fatal Exception Errors, see the Knowledge Base articles listed at the end of this document.

MORE INFORMATION
The following are the processor exceptions and their definitions: 00: Divide Fault
The processor returns this exception when it encounters a divide fault. A divide fault occurs if division by zero is attempted or if the result of the operation does not fit in the destination operand.

02: NMI interrupt
Interrupt 2 is reserved for the hardware Non-Maskable-Interrupt condition. No exceptions trap through interrupt 2.

04: Overflow trap
The overflow trap occurs after an INTO instruction has executed and the 0F bit is set to 1.

05: Bounds Check Fault
The BOUND instruction compares the array index with an upper and lower bound. If the index is out of range, then the processor traps to interrupt 05.

06: Invalid Opcode fault
This error is returned if any one of the following conditions are true:
- The processor tries to decode a bit pattern that does not correspond to any legal computer instruction
- The processor attempts to execute an instruction that contains invalid operands
- The processor attempts to execute a protected-mode instruction while running in virtual 8086 mode.
- The processor tries to execute a LOCK prefix with an instruction that cannot be locked.

07: Coprocessor not available fault
This error occurs if the computer does not have a math coprocessor and the EM bit of register CR0 is set indicating that Numeric Data Processor emulation is being used. Each time a floating point operation is executed, an interrupt 07 occurs. This error also occurs when a math coprocessor is used and a task switch is executed. Interrupt 07 tells the processor that the current state of the coprocessor needs to be saved so that it can be used by another task.

08: Double Fault
Processing an exception sometimes triggers a second exception. In the event that this occurs, the processor will issue a interrupt 08 for a double fault.

09: Coprocessor Segment Overrun
This error occurs when a floating point instruction causes a memory access that runs beyond the end of the segment. If the starting address of the floating point operand is outside the segment, then a General Protection Fault occurs (interrupt 0D).

10 (0Ah): Invalid Task State Segment Fault
Because the Task State Segment contains a number of descriptors, any number of conditions may cause exception 0A. Typically, the processor can gather enough information from the Task State Segment to issue another fault pointing to the actual problem. See "Microsoft's Programming the 80386/80486 Guide" for more information.

11 (0Bh): Not Present Fault
The Not present interrupt allows the operating system to implement virtual memory through the segmentation mechanism. When a segment is marked as "not present", the segment is swapped out to disk. The interrupt 0B fault is triggered when an application needs access to the segment.

12 (0Ch): Stack Fault
A Stack Fault occurs with error code 0 if an instruction refers to memory beyond the limit of the stack segment. If the operating system supports expand-down segments, increasing the size of the stack should alleviate the problem. Loading the Stack Segment with invalid descriptors will result in a general protection fault.

13 (0Dh): General Protection Fault
Any condition which is not covered by any of the other processor exceptions will result in a general protection fault. The exception indicates that this program has been corrupted in memory usually resulting in immediate termination of the application.

14 (0Eh): Page Fault
The Page Fault interrupt allows the operating system to implement virtual memory on a demand-paged basis. An interrupt 14 usually isissued whenever an access to a page directory entry or page table with the present bit set to 0 (Not present) occurs. The operating system makes the page present (usually retrieves the page from virtual memory) and re-issues the faulting instruction, which then can access the segment. A page fault also occurs when a paging protection rule is violated (when the retrieve fails, or data retrieved is invalid, or the code that issued the fault broke the protection rule for the processor). In these cases the operating system takes over for the appropriate action.

16 (10h): Coprocessor error Fault
This interrupt occurs when an unmasked floating-point exception has been signaled a previous instruction. (Because the 80386 does not have access to the Floating Point Unit, it checks the ERROR\ pin to test for this condition). This is also triggered by a WAIT instruction if the Emulate Math Coprocessor bit at CR0 is set.

17 (11h): Alignment Check Fault
This interrupt is only used on the 80486 CPUs. An interrupt 17 is issued when code executing at ring privilege 3 attempts to access a word operand that is not on an even-address boundary, a double-word operand that is not divisible by four, or a long real or temp real whose address is not divisible by eight. Alignment checking is disabled when the CPU is first powered up and is only enabled in protected mode.



Fatal Exception Error Using DHCP

SYMPTOMS
When you use Winipcfg.exe to release or renew IP addresses obtained using DHCP, or when you start Windows 95 with the network adapter configured to obtain IP addresses using DHCP, you may receive an error message similar to the following message on a blue screen:
Fatal exception 0E at 0028:C433442B in VXD octk16.sys (01) + 0000342B. This was called from 0028:C003C47C in VXD NDIS (01) + 00000D7C. It may be possible to continue normally.

CAUSE
When you are using the Windows 95 DHCP client, a buffer in memory used to send a DHCP message may be freed before the message has been completely sent. The error occurs when the network adapter driver attempts to access this buffer to send the information on the wire.

STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows 95. A fix to this problem is in development, but has not been regression tested and may be destabilizing in production environments. Microsoft does not recommend implementing this fix at this time. Contact Microsoft Technical Support for more information on the availability of this fix.

MORE INFORMATION
The fatal exception error typically occurs in the MAC driver, although it may also occur in NDIS itself. This symptom may occur more frequently with Token Ring adapters using locally administered addresses (LAAs), although it has been reported to occur with Ethernet adapters and without using LAAs. Fatal Exception Error When Starting an MS-DOS Session



BETA INFORMATION BETA INFORMATION BETA INFORMATION BETA
This article discusses a Beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice. No formal product support is available from Microsoft for this Beta product. For information about
obtaining support for a Beta release, please see the documentation included with the Beta product files, or check the Web location from which you downloaded the release.

SYMPTOMS
When you attempt to start an MS-DOS session in Windows 98, you may receive the following error message:
A Fatal Exception 0E has occurred at 0028:C02B1E2B in VXD VCOND(03) + 0000176F. The current application will be terminated.

CAUSE
This error message can occur if you are already running 64 MS-DOS sessions.

RESOLUTION
To work around this problem, quit one or more MS-DOS sessions before you start a new session. To do so, type "exit" (without quotation marks) at a command prompt, and then press ENTER.

STATUS
Microsoft has confirmed this to be a problem in Windows 98. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.



"Fatal Exception 0D" Error Message Installing Program message:

A Fatal Exception 0E has occurred at 0028:C02B1E2B in VXD VCOND(03) + 0000176F

SYMPTOMS
When you are installing any program that uses the Windows Install Wizard or the InstallShield installation program, you may receive the following error message: A Fatal Exception Error 0D has occurred in VxD VMM(01) + 00001840

CAUSE
This error can occur if you have Stacker version 4.1 installed on your computer.

RESOLUTION
To resolve this issue, use either of the following methods:
Contact Stac Electronics for a possible fix. Disable 32-bit disk access for all drives. To do this, perform the following steps:
1. In Control Panel, double-click System.
2. On the Performance tab, click File System.
3. On the Troubleshooting tab, click the Disable All 32-Bit Protect- Mode Drivers check box to select it.
4. Click OK.

MORE INFORMATION
The third-party product discussed in this article is manufactured by a vendor independent of Microsoft; we make no warranty, implied or other- wise, regarding this product's performance or reliability. Fatal Exception Error Starting Windows 95 error message: WINDOWS This program has caused a Fatal Exception 0D at 00457:000040B1 and will be terminated



Last reviewed: February 11, 1998 Article ID: Q133440
********************************************************************
BETA INFORMATION BETA INFORMATION BETA INFORMATION BETA

SYMPTOMS
When you start Windows 95, you may receive a blue error screen with the following error message: WINDOWS This program has caused a Fatal Exception 0D at 00457:000040B1 and will be terminated. Pressing any key causes the screen to turn black and the computer to stop responding (hang).

CAUSE
This problem can occur if you are using Adobe Type Manager with certain display drivers and the Hardware Acceleration setting is not set to Full.

RESOLUTION
Set the Hardware Acceleration setting to Full. To do so, follow these steps:
1.Restart your computer. When you see the "Starting Windows 95" message, press the F8 key, and then choose Safe Mode from the Startup menu.
2.Click the Start button, point to Settings, then click Control Panel.
3.Double-click the System icon.
4.On the Performance tab, click the Graphics button.
5.Move the Hardware Acceleration slider all the way to the right (to the Full setting).
6.Click OK. When you are prompted to restart your computer, click Yes.

MORE INFORMATION
The third-party product discussed in this article is manufactured by a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability. "Fatal Exception OE" Error Message When You Start Windows 95 error message: A Fatal Exception 0E has occurred at 0137: . The current application will be terminated.



Last reviewed: March 20, 1998 Article ID: Q179347 The information in this article applies to: Microsoft Windows 95

SYMPTOMS
When you start Windows 95, you may receive the following error message: A Fatal Exception 0E has occurred at 0137:<address>. The current application will be terminated. If you press a key to continue, one of the following symptoms may occur: You receive the following error message: A Fatal Exception 0C has occurred at 0137:<address>. The current application will be terminated. Your computer is restarted.
NOTE: This error message also occurs in Safe mode.

CAUSE
This behavior can occur if the Advapi32.dll file located in the Windows\System folder is missing or damaged.

RESOLUTION
To resolve this behavior, follow these steps:
1.Rename the Advapi32.dll file (if it exists). To do so, follow these steps:
a. Click Start, point to Find, and then click Files Or Folders.
b. In the Named box, type "advapi32.dll" (without quotation marks), and then click Find Now.
c. If the Advapi32.dll file is found, right-click it, and then click Rename. If the Advapi32.dll file is not found, skip to step E.
d. Type a new name for the Advapi32.dll file (such as Advapi32.xxx), and then press ENTER.
e. Close the Find window.
2.Extract a new copy of the Advapi32.dll file from your original Windows 95 disks or CD-ROM. The Advapi32.dll file is located in the following locations: - The Win95_11.cab cabinet file on the Windows 95 CD-ROM. - The Win95_17.cab cabinet file on the Windows 95 OEM Service Release 2 (OSR2) CD-ROM. - The Win95_11.cab cabinet file on disk 11 of the original Windows 95 DMF floppy disks. - The Win95_18.cab cabinet file on disk 18 of the original Windows 95 non-DMF floppy disks.
For information about using the Extract tool, type "extract" (without quotation marks) at a command
prompt, or see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q129605
TITLE : How to Extract Original Compressed Windows Files

3.Restart your computer.



"Fatal Exception 0E" Error Message When Running McAfee VirusScan

Last reviewed: December 4, 1997 Article ID: Q177672 The information in this article applies to:
Microsoft Windows 95 Microsoft Windows 95 OEM Service Release version 2

SYMPTOMS
When McAfee VirusScan95 with VShield scanning software detects a virus on your computer, you may receive the following error message: A fatal exception 0E has occurred at 0028:C0003C72 in VXD VMM(01) + 00002C72. The current application will be terminated.
NOTE: In addition to this error message, your computer may stop responding (hang) or restart when a virus is detected.

CAUSE
This behavior can occur if your video adapter uses the Tseng Labs ET6000 chip set.

RESOLUTION
Upgrade to Release 6, version 4.03.4800 or later of the Tseng Labs ET6000 video adapter driver for Windows 95. To obtain this driver, contact Tseng Labs.

MORE INFORMATION
When McAfee VirusScan95 detects a virus, it switches to MS-DOS mode. The video adapter drivers for the Tseng Labs ET6000 chip set do not handle this change correctly.

The third-party products discussed in this article are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability. Fatal Exception Error or Computer Hangs with Incoming Fax



Last reviewed: November 19, 1997 Article ID: Q176942 The information in this article applies to: Microsoft Windows 95

SYMPTOMS
If a fax is received by your computer while it is processing another fax, you may receive a fatal exception error message, and your computer may stop responding (hang).

RESOLUTION
To work around this issue, follow these steps:
1.Click Start, point to Settings, click Control Panel, and then double- click Mail And Fax.
2.In the list of installed information services, click Microsoft Fax, and then click Properties.
3.Click the Modem tab, click the modem you are using to receive incoming faxes, and then click Properties.
4.Click Answer After <n> Rings.
5.Change the value in the Answer After <n> Rings box to the number of rings you want Microsoft Fax to wait before the fax modem answers the call.
6.Click OK, click OK, click OK, and then close Control Panel.

MORE INFORMATION
For additional information about troubleshooting Microsoft Fax, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q152196 TITLE : How to Install and Use Microsoft Fax Fatal Exception Error When Opening or Closing Control Panel



Last reviewed: February 26, 1998 Article ID: Q175211 The information in this article applies to: Microsoft Windows 95

SYMPTOMS
If you have installed a scanner on your computer, the following symptoms may occur: When you attempt to open or close Control Panel, you may receive the following error message: A fatal exception OE has occurred at 0028:C029F7A1 in VXD IFSMGR(04) + 0000D4F1. The current application will be terminated.
After receiving this error message, you can still use Control Panel, but the Speaker icon may no longer appear on the taskbar. This behavior may also occur in Safe mode.
- When you start Windows 95, you may receive the following error message: A fatal exception OE has occurred at 028:C0282dB0 in VxD IFSMGR(03) + 0000 CF7C The current application will be terminated.

CAUSE
This behavior can occur if the Vhpscand.vxd file is located in the Windows\System folder instead of the Windows\System\Iosubsys folder.

RESOLUTION
To resolve this behavior, follow these steps:
1.Click Start, point to Programs, and then click Windows Explorer.
2.On the Tools menu, point to Find, and then click Files Or Folders.
3.In the Named box, type "vhpscand.vxd" (without quotation marks), and then click Find Now.
4.If the Vhpscand.vxd file is located in the Windows\System folder, right-click the Vhpscand.vxd file, and then click Cut.
5.Right-click the Windows\System\Iosubsys folder, and then click Paste.
6.Restart your computer.

MORE INFORMATION
The third-party product discussed in this article is manufactured by a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability. Fatal Exception Error Opening Gaming Devices Tool
Last reviewed: April 8, 1997 Article ID: Q165049 The information in this article applies to: Microsoft SideWinder game pad version 1.0 Microsoft SideWinder 3D Pro version 1.0

SYMPTOMS
When you open the Gaming Devices tool in Windows 95 Control Panel, you may receive the following error message: A Fatal Exception Error 0E occurred at 0028:58C10F3F
NOTE: This behavior occurs with both the Microsoft SideWinder Gaming Devices software version 1.0 (originally included with Microsoft SideWinder game pad version 1.0) and the Microsoft SideWinder Gaming Devices software version 1.5.

CAUSE
This behavior can occur if the game port is in conflict with another device.

RESOLUTION
Use Device Manager to determine whether another device is in conflict with the game port. If Device Manager reports that there is a problem with the configuration of the game port, reconfigure the game port so that it uses resources that are not already in use by another device.

If the game port is on a Plug and Play device and is in conflict with another device, you must disable the device before attempting to change the resource settings. To do so, follow these steps:

1.In Control Panel, double-click System, click the Device Manager tab, double-click Sound, Video And Game Controllers, and then double-click Gameport Joystick.
2.In the Gameport Joystick Properties dialog box, click the General tab, click the Original Configuration check box to clear it, and then click OK.
For information about using Device Manager to troubleshoot device conflicts, see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q133240 TITLE: Troubleshooting Device Conflicts with Device Manager "Exception 0E" Using MSNDS Over Dial-Up Connection



Last reviewed: March 17, 1998 Article ID: Q163673 The information in this article applies to: Microsoft Windows 95 Microsoft Windows 95 OEM Service Release versions 1, 2, 2.1

SYMPTOMS
When you are using the Microsoft Client for NetWare Networks with the Microsoft Service for NetWare Directory Services (MSNDS) to connect to a NetWare network over a dial-up connection, a "Fatal Exception Error 0E" (Invalid Page Fault) error message may occur when you are browsing or connecting to NetWare resources. This symptom has been observed primarily when a Windows 95 client makes a Dial-Up Networking connection to a Novell NetWare Connect version 2.028 PPP server.

CAUSE
When you connect to certain Dial-Up Networking servers, the MSNDS client redirector may time out and resend a packet after freeing a network buffer needed to transmit the packet. When the Dial-Up Adapter driver attempts to access this buffer to retransmit the packet, an Invalid Page Fault error occurs.

STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows 95. A fix to this problem is in development, but has not been regression tested and may be destabilizing in production environments. Microsoft does not recommend implementing this fix at this time. Contact Microsoft Technical Support for more information about the availability of this fix.

MORE INFORMATION
Currently, this symptom has not been reported to occur with the Microsoft Client for NetWare networks (Bindery version) without the Microsoft Service for NetWare Directory Services (MSNDS) installed.
"Fatal Exception Error" with Iomega IDE Zip Drives



Last reviewed: March 17, 1998 Article ID: Q160800 The information in this article applies to: Microsoft Windows 95 Microsoft Windows 95 OEM Service Release version 2

SYMPTOMS
When you are using an Intel motherboard with an AMI/Intel BIOS or an Iomega IDE Zip drive installed on the secondary IDE channel, you may receive a "Fatal Exception Error" error message when you start the computer without a disk in the Zip drive or you eject the disk from the Zip drive.

CAUSE
This problem can occur if the following conditions exist: The computer has an IDE removable drive that uses Media Status Notification (the Iomega IDE Zip drive is one such drive). The computer's BIOS unmasks the PIC for the IRQ on the controller on which the drive is located. The drive is accessed with no disk in the drive. The BIOS touches the Alt Status register when an interrupt is vectored to it. When these conditions exist, an interrupt may be reflected to the BIOS, which can cause a fault.

STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows 95. An update to address this problem is now available, but is not fully regression tested and should be applied only to computers experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft does not recommend implementing this update at this time. This issue is resolved by the following updated files for Windows 95:
Esdi_506.pdr version 4.00.956 (dated 5/14/96) and later Voltrack.vxd version 4.00.954 (dated 3/6/96) and later
To install this update, follow these steps:
1.Download the Remideup.exe file from the online service listed below to an empty folder.
2.In My Computer or Windows Explorer, double-click the Remideup.exe file you downloaded in step 1.
3.Follow the instructions on the screen.
The following file(s) are available for download from the Microsoft Software Library: ~ remideup.exe (size: 147096 bytes)
For more information about downloading files from the Microsoft Software Library, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q119591 TITLE : How to Obtain Microsoft Support Files from Online Services

The following files are installed by Remideup.exe:

File name Version Date/Time Size Destination folder
---------------------
Esdi_506.pdr 4.00.1116 8/25/97 11:16a 24,426 Windows\System\Iosubsys
Voltrack.vxd 4.00.954 3/6/96 9:54a 18,518 Windows\System\Iosubsys

NOTE: The Voltrack.vxd file is installed on Windows 95 computers only. This file is not installed on computers running OSR2.



Fatal Exception Error Running Add New Hardware Wizard

Last reviewed: March 29, 1997 Article ID: Q166047 The information in this article applies to: Microsoft Windows 95

SYMPTOMS
After you install the Hewlett-Packard (HP) OfficeJet Series 300 printer driver and Device Manager software, any attempt to detect new hardware using the Add New Hardware Wizard may cause a fatal exception error 06, 0E, 0C, or 0D.

CAUSE
The HP OfficeJet Series 300 Device Manager contends with Windows 95 for control of Plug and Play.

RESOLUTION
Start the Close Program dialog box by pressing CTRL+ALT+DELETE. Click HPOJDMAN in the list of tasks, and then click End Task.

STATUS
Contact Hewlett-Packard Technical Support for more information.

MORE INFORMATION
The problem occurs only when the HP OfficeJet Series 300 Device Manager (Hpodjman.exe) is running. The HP installation process sets up a shortcut in the Startup folder that runs "Hpojdman.exe /AUTOPROMPT." This causes Hpojdman.exe to run in the background. The third-party product discussed in this article is manufactured by a vendor independent of Microsoft; we make no warranty, implied or other- wise, regarding this product's performance or reliability.



"Exception 0E in VPOWERD" During First Boot

Last reviewed: March 17, 1998 Article ID: Q153395 95 WINDOWS kbhw kbpolicy
The information in this article applies to: Microsoft Windows 95

SYMPTOMS
VPOWERD may cause a page fault (Fatal Exception error 0E) on the first reboot during Windows 95 Setup on certain computer models that support advanced power management (APM).

RESOLUTION
To work around this problem, use one of the following methods:
Disable the APM feature during Windows 95 Setup.
- If you are not using an automated Setup, click the Custom button in the Setup Options screen, and then click the Advanced Power Management check box to clear it in the Computer Settings screen.
- If you are using an automated Setup, add the following line to the [System] section of the Msbatch.inf file:
"Power"="No APM" (include the quotation marks)
This method disables all APM functionality in Windows 95.
You may be able to resolve this issue by upgrading the computer's BIOS. Contact the computer's manufacturer for information about a possible BIOS upgrade.



Fatal Exception in VMM(06) Caused by Damaged Registry

Last reviewed: October 30, 1996 Article ID: Q145836 The information in this article applies to: Microsoft Windows 95

SYMPTOMS
You may receive either of the following error messages in Windows 95: Windows Networking The following error occurred while loading the device driver Vnetsup. Error 6107: Could Not Setup Instance Data A fatal exception 0E has occurred at 0028:xxxxxxxx in VxD VMM(06) + xxxxxxxx
While the exception number may vary, 0E is the most common.

CAUSE
This error message can occur when Windows 95 encounters a problem while processing the system registry. If this error message occurs, the registry may be damaged.

RESOLUTION
To resolve this problem, restore your registry files from a backup.



A Fatal Error Has Occurred in VxD VMCPD

Last reviewed: July 17, 1996 Article ID: Q136255 The information in this article applies to: Microsoft Windows 95

SYMPTOMS
After you install Windows 95, you may see the following error message on a blue screen the first time the computer restarts:
Windows: A fatal error 0D has occurred at 0028:xxxxxxxx in VXD VMCPD(01) + 000026B. The current application will be terminated. If you press any key, you see the same error message. If you press CTRL+ALT+DEL to restart the computer, the same error message occurs. You can start Windows 95 using Safe mode.

CAUSE
This problem can occur on computers using a Cyrix 486DLC processor and a Cyrix FastMath coprocessor. Some computers with this processor and coprocessor are not compatible with Windows 95.

RESOLUTION
To work around this problem, disable support for the coprocessor in Windows 95. To do so, follow these steps:
1.Restart your computer. When you see the "Starting Windows 95" message, press the F8 key, and then choose Safe Mode from the Startup menu.
2.Click the Start button, point to Settings, and then click Control Panel.
3.Double-click the System icon.
4.On the Device Manager tab, double-click the System Devices branch.
5.Click Numeric Data Processor, and then click Properties.
6.On the Settings tab, click the "Never use the numeric data processor" check box to select it, and then click OK.
7.When you are prompted to restart your computer, do so.

MORE INFORMATION
Vmcpd.vxd controls the floating-point operations in Windows 95.



Fatal Exception Error Accessing Windows NT Share From Windows 95

Last reviewed: February 27, 1998 Article ID: Q181866 The information in this article applies to:
Microsoft Windows 95 Microsoft Windows NT Server version 4.0 Microsoft Windows NT Workstation version 4.0

SYMPTOMS
When you attempt to open a file or folder on Windows NT shared network drive that is on a NTFS partition, you may receive the following error message:
A Fatal Exception 0E has occurred at 0028:C0231810 in VXD VMM(0D) + 00001810.
The current Application will be terminated.

CAUSE
This behavior can occur if both of the following conditions exist: The file or folder you are attempting to open has a long file name. You have disabled short file name (standard 8.3 naming) creation on the Windows NT computer.

RESOLUTION
To resolve this issue, obtain and install Microsoft Windows 95 Service Pack 1. For information about Windows 95 Service Pack 1, please see the following article in the Microsoft Knowledge Base: ARTICLE-ID: Q142794 TITLE : Availability of Microsoft Windows 95 Service Pack 1

MORE INFORMATION
This behavior can also occur if the networking components have been removed and reinstalled on a computer that has Windows 95 Service Pack 1 installed. Reinstalling the networking components from the Windows 95 CD-ROM overwrites the Windows 95 Service Pack 1 version of the networking files. You should reinstall Windows 95 Service Pack 1 after installing network files from the Windows 95



CD-ROM. "Fatal Exception 0E" May Occur During Critical Suspend

Last reviewed: March 17, 1998 Article ID: Q162211 The information in this article applies to: Microsoft Windows 95 Microsoft Windows 95 OEM Service Release version 1

SYMPTOMS
On a computer equipped with advanced power management (APM), a "Fatal Exception 0E" error may occur in VPOWERD if a critical suspend occurs while the computer is already in the process of suspending normally.

CAUSE
The Windows 95 power-management driver does not properly handle a new critical suspend request while it is processing a normal suspend request.

STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows 95. An update to address this problem is in development, but has not been regression tested and may be destabilizing in production environments. Microsoft does not recommend implementing this update at this time. Contact Microsoft Technical Support for more information about the availability of this update.

MORE INFORMATION
This issue may occur if you manually suspend the computer when the computer's battery is critically low. Under such conditions, the low- battery condition could cause a critical suspend request to be issued by the computer's BIOS. If a critical suspend request is issued while Windows 95 is already processing the normal suspend request, the problem can occur.



Fatal Exception in Msgsrv32.exe When You Quit Windows 95

Last reviewed: March 16, 1998 Article ID: Q182567 The information in this article applies to:Microsoft Windows 95

SYMPTOMS
When you quit Windows 95, you may receive a fatal exception error message that references the Msgsrv32.exe file.

CAUSE
This behavior can occur if you have the Autodesk AutoCad Release 14 program installed on your computer, and the Graphics Display Interface (GDI) handle table has become damaged.

RESOLUTION
To work around this issue, remove the Microsoft Find Fast shortcut from the StartUp folder. To do so, use the following steps:
1.Right-click the desktop, click New, and then click Folder.
2.Type "Disabled StartUp shortcuts" (without quotation marks), and then press ENTER.
3.Click Start, point to Find, and then click Files Or Folders.
4.In the Named box, type "startup" (without quotation marks), and then click the Advanced tab.
5.In the Of Type box, click Folder, and then click Find Now.
6.Double-click the StartUp folder (after you verify it is in the Windows\Start Menu\Programs folder), right click the Microsoft Find Fast shortcut, and then click Cut.
7.Quit the Find Files Or Folders tool, right-click the Disabled StartUp Shortcuts folder, and then click Paste.
8.Restart your computer. 


  • Back To The Top    • Back To Home