Clean Boot Your Computer
Because there are many conditions that can cause a fatal exception error, the first step in resolving the issue is to narrow the focus. To narrow the focus, try a "clean boot" of your computer.
Clean-boot troubleshooting refers to methods of reducing problems that may occur because of your computer's environment. Many problems occur because of conflicting drivers, terminate-and-stay-resident programs (TSRs), and other settings that are loaded when your computer starts. For additional information about how to clean-boot your computer, click the following article numbers to view the articles in the Microsoft Knowledge Base:
http://support.microsoft.com/kb/150314
How to perform a clean boot in Windows 95
The following steps can help you to determine if the problem that you are experiencing is due to the real-mode configuration of your computer. This could include drivers that are loaded from your Config.sys and Autoexec.bat files.
Restart your computer. When the Starting Windows 95 dialog box is displayed, press F8, and then choose Step-By-Step Confirmation from the Startup menu.
When you are prompted, load the following items (if you are prompted to load any other items, press N):
Dblspace driver.
Himem.sys.
Ifshlp.sys.
Dblbuff.sys.
Load the Windows 95 graphical user interface (GUI), choosing to load all Windows drivers.
NOTE: Windows 95 does not require the Config.sys and Autoexec.bat files, but some tools installed on the computer may require them. You should never rename the Config.sys and Autoexec.bat files until you perform a successful interactive boot to verify that they are not needed.
If the clean boot of your real-mode configuration eliminates the issue, isolate the conflict with a terminate-and-stay-resident (TSR) or real-mode device driver using the Step-By-Step Confirmation function.
Load Windows 95 by booting to a command prompt and starting Windows 95 by typing win, holding down the SHIFT key for the duration of the boot. This prevents any programs from loading automatically at startup.
If the issue is resolved by preventing programs from loading at startup, investigate the following possible sources.
The Winstart.bat File
The Winstart.bat file is used to load TSRs that are required for Windows-based programs and are not needed in MS-DOS sessions.
For additional information the Winstart.bat file, click the article number below to view the article in the Microsoft Knowledge Base:
Some TSRs Moved from Autoexec.bat to Winstart.bat During Setup
134402:
http://support.microsoft.com/kb/134402/EN-US
The Startup Group
If the issue is resolved by bypassing the Startup group, remove each of the programs from the Startup group individually to isolate the program that is causing the problem.
The Run Key in the Registry
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
How to back up and restore the registry in Windows:
322756
http://support.microsoft.com/kb/322756
You can prevent programs from loading by removing the program's string from the following registry keys:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ RunServicesOnce
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ RunOnce\Setup
Programs may also be loading from the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
The Win.ini File
The "load=" and "run=" lines in the [Windows] section of the file can start programs automatically. See the following section for more information.
Test Windows Configuration Files
To test the Windows configuration files, use the following steps:
Boot to a command prompt.
Rename the Win.ini file by typing the following command:
ren c:\windows\win.ini *.bak
Start Windows 95 by typing win. If this procedure corrects the problem, ensure that the "load=" and "run=" lines in the [Windows] section of the Win.ini file are either blank or preceded with a semicolon (;) to prevent the items from loading.
Rename the System.ini file by typing the following command:
ren c:\windows\system.ini *.bak
Windows 95 requires a System.ini file to load the GUI. Replace the original file by typing the following command:
copy c:\windows\system.cb c:\windows\system.ini
NOTE: Starting Windows 95 with the System.cb file does not load a driver for the mouse. Edit the new System.ini file, adding the following lines:
[386Enh]
mouse=*vmouse, msmouse.vxd
[boot]
drivers=mmsystem.dll
mouse.drv=mouse.drv
Start Windows 95 by typing win at the command prompt. If replacing the original System.ini file with the System.cb file corrects the issue, the problem most likely resides with either the [boot] or [386Enh] sections of the original System.ini file. Restore the original file to troubleshoot it.
To isolate the cause of the problem, place a semicolon (;) at the beginning of a line to prevent the item from loading.
For additional information about the System.ini file and its default entries, click the article number below to view the article in the Microsoft Knowledge Base:
Creating a New System.ini File Without Third-Party Drivers:
140441
http://support.microsoft.com/kb/140441/EN-US
Protected-Mode Device Drivers
http://support.microsoft.com/kb/243039