![]() |
Troubleshoot Windows Fatal Exception Errors |
Trying to run memory with the wrong BIOS wait-state settings can also generate such errors. To rule out this possibility, go into your system's CMOS setup program and choose the default wait-state settings, or experiment with different settings.
Microsoft has documented numerous Fatal Exception error problems and solutions in its online Knowledgebase.
If your problem isn't listed in the Knowledgebase, read:
Troubleshooting Windows 95 Startup Problems and Error Messages Q136337
An extensive step-by-step troubleshooting guide to Windows 95 start-up
problems, including the Fatal Exception errors.
How to Determine a Device
Driver's Source
Read
Up on Fatal Windows Errors
Here are some of the more common errors
Wavetable audio/CMOS setting clash Q129777
Diamond Viper video board drivers Q131743
Adobe Type Manager/video board driver clash Q133440
ATI Mach32 ISA settingsQ139771
Clash with Windows for Workgroups TCP/IP files Q140903
Fatal Exception in VMM(06) Caused by Damaged Registry Q145836 VMM Number may vary.
VPOWERD power management bug Q153395
Fatal Exception
Error Using DHCP Q158713
Q171353
Computer
with Ultra DMA IDE Controller May Hang
Q161642
Auto Insert
Notification May Prevent Automatic Suspend
Q154976
Error
Message Running Jet Database Engine Stress Test
Q154436
Errors
Accessing Hard Disk with Spin-Down Enabled
Q154435
Windows
95 IDE Support for SMART, DMA, and ATAPI Tape Drives
Q153471
Problems
with Removable IDE Drives in Windows 95
"Fatal
Exception 0D" Error Message Installing Program Q162390
Q177222
NetWare
Printers or Volumes Unavailable in Windows 95
Q165402
Windows
95 Update to Encrypt Passwords in Memory
Q160897
NWRedir Reports Incorrect Free Space If Limited by Admin
Q160824
MSNDS
Drops Connections to More Than Eight Servers
Q158058
MSNDS Client Does
Not Prompt to Log On
Q153470
Incorrect
Error Code Returned for Locked Files
Q152186
Possible Network Data Corruption If Locking Not Used
Q151912
NWRedir
Returns Cached File Size Information
Q149606
Fatal
Exception 0E in VNETBIOS Using NetWare Login Script
Q147838
Cannot
Access Folders with Long File Names on NetWare Servers
Q143282
No Documents
Appear in the File Open Dialog Box
Q139747
MS-DOS-Based
Program Reports Not Enough NetWare Server Space
Q136303
Connecting
to Schedule+ 1.0 Calendar File Drops Connections
Windows
95 Update Version Information
Identifying
Windows 95 Updates
The
Windows 95 Update Information Tool (Qfecheck.exe)
Installing
Windows 95 Updates on a Single Computer
Uninstalling
Windows 95 Updates on a Single Computer
Installing
Windows 95 Updates Using Server-Based Setup
Obtaining
Windows 95 Updates
Knowledge
Base Query Tips
Windows 95 Update Version Information
The version numbers of the original retail and OEM release of Windows 95 and the OEM Service Releases are listed below. In general, files included with the indicated release of Windows 95 have the indicated version stamp.
Release
Version File dates
----------------------------------------------------------
Windows 95 retail & OEM 4.00.950
7/11/95
OEM Service Release 1 4.00.950
12/31/95
OEM Service Release 2 4.00.1111*
8/24/96
OEM Service Release 2.1 4.03.1212-1214* 8/24/96-8/27/97
OEM Service Release 2.5 4.03.1214*
8/24/96-11/18/97
Fatal
Exception Error Running Add New Hardware Wizard Q166047
1.The device driver name may suggest the name of the program that installed it. For example, CCVKD is the virtual keyboard device driver installed by Carbon Copy. Virtual devices often begin with the letter "V" and end in the letter "D." For example, VNAVD is the Norton Anti- Virus device driver.
If you are successful in identifying the source of the driver, remove the corresponding program.
2.The device driver name may begin with the letters "NW," suggesting that it may be a Novell NetWare networking driver. Other clues that may identify a driver as network-related are the presence of the letters "NDIS," "NET," or "SERVER."
3.If you are unable to identify the program or component that installed the driver, search the [386Enh] section of the System.ini file for a line with the following form
Device=<DeviceName>.386
where <DeviceName> is the name of the device driver, possibly with a path, or possibly with a slightly modified name. For example:
Device=ccvkd.386
4.If the driver that needs to be replaced is one of the Windows 95 standard drivers, run Windows 95 Setup again, and choose to verify the installation.
The following table lists virtual device drivers you may encounter.
Legend:
# - Indicates a standard Windows 95 driver.
! - Indicates a standard Windows 95 driver that may have been replaced by a third-party product.
$ - Indicates a driver provided by a third-party manufacturer.
3.0 - Indicates a driver from Windows 3.0.
3.1, 3.11 - Indicates device drivers that have been superseded by drivers in Windows 95
ID Driver
No. Name Driver Description
-----------------------------------------------------------------------
# 0001 VMM
Virtual Machine Manager
# 0002 DEBUG
WDEB386 Kernel Debugger
! 0003 VPICD
Virtual Programmable Interrupt Controller Device
# 0004 VDMAD
Virtual Direct Memory Access Device
! 0005 VTD
Virtual Timer Device
# 0006 V86MMGR Virtual
8086-mode Memory Manager
# 0007 PAGESWAP Demand Paging
Swap Device
# 0008 PARITY
Parity-checking Device
# 0009 REBOOT
System Reboot Device
! 000A VDD
Virtual Display Device
# 000B VSD
Virtual Sound Device
! 000C VMD
Virtual Mouse Device
! 000D VKD
Virtual Keyboard Device
! 000E VCD
Virtual Communications Device
! 000F VPD
Virtual Printer Device
3.1 0010 BLOCKDEV Block Device Driver
# 0010 IOS
Input/Output Supervisor
# 0011 VMCPD
Virtual Math Coprocessor Device
# 0012 EBIOS
PS/2 Extended BIOS Device Driver
# 0013 BIOSXLAT BIOS Translation
Device Driver
# 0014 VNETBIOS Virtual NetBIOS
Device Driver
# 0015 DOSMGR
MS-DOS Device Driver
# 0017 SHELL
Shell Interface Device
# 0018 VMPOLL
Virtual Machine Polling Detection Device
! 3.1 001A DOSNET MS-DOS Network Interface
Driver - This driver is often replaced by third-party network drivers
! 001B VFD
Virtual Floppy Device
$! 001C LOADHI EMM386
Memory Manager Driver - This driver is often replaced by third-party
memory managers
# 0020 INT13
Fixed Disk Interrupt Driver
! 3.1 0021 PAGEFILE Paging File Device - This driver
is often replaced by RAM-doubling software
0022 SCSI
SCSI Device
0023 MCA_POS
MCA_POS Device
0024 SCSIFD
SCSI FastDisk Device
0025 VPEND
Pen Device
3.1 0026 APM
Advanced Power Management Device
# 0026 VPOWERD Virtual
Advanced Power Management Device
# 0027 VXDLDR
VxD Loader device
# 0028 NDIS
NDIS wrapper
# 002A VWIN32
Windows 95 Win32 Support Driver
# 002B VCOMM
Windows 95 Communications Device Driver
# 002C SPOOLER Print
Spooler
3.1 002D WIN32S WIN32S Driver
3.11 0031 VNB
NetBEUI Driver from Windows for Workgroups
3.11 0032 SERVER NetBEUI Driver
from Windows for Workgroups
# 0033 CONFIGMG Plug and
Play Configuration Manager
3.1 0034 DWCFGMG Configuration
Manager for Windows 3.1 and MS-DOS
# 0035 SCSIPORT I/O Subsystem
Miniport Loader/Driver
# 0036 VFBACKUP Helper Driver
for Backup Applications
# 0037 ENABLE
Accessibility Driver
# 0038 VCOND
Virtual Console Device for WIN32 Console Subsystem
# 003C ISAPNP
ISA Plug and Play Enumerator
# 003D BIOS
BIOS Plug and Play Enumerator
# 003E WINSOCK Windows
Network Sockets
# 003F WSIPX
Windows Network Sockets for IPX
# 0040 IFSMGR
Installable File System Manager
# 0041 VCDFSD
CD-ROM File System Driver
# 0042 MRCI32
Microsoft Real-time Compression Driver
# 0043 PCI
PCI Plug and Play Enumerator
# 0045 EISA
EISA Plug and Play Enumerator
# 011F VFLATD
Linear Frame Buffer Video Driver
# 0442 VTDAPI
Multimedia Timer Services Driver
3.0 0444 VADMAD Auto-initialize
DMA
! 0445 VSBD
Sound Blaster (Windows Resource Kit) [ASCII 150] This driver
is often replaced by third-party sound drivers
# 0460 UNIMODEM Universal
Modem Driver
# 0480 VNETSUP Network
Support Driver
# 0481 VREDIR
Network Redirector
# 0483 VSHARE
File Sharing Support Driver
3.11 0484
Old IFSMGR from Windows for Workgroups
# 0486 VFAT
32-bit File System Driver
# 0487 NWLINK
32-bit IPX/SPX-compatible Protocol
# 0488 VTDI
TCP/IP Driver
# 0489 VIP
TCP/IP Driver
# 048A VTCP
TCP/IP Driver
# 048B VCACHE
Cache Manager
# 048C VUDP
User Datagram Protocol Driver
# 048E NWREDIR Windows
95 NetWare-compatible Redirector
# 0491 FILESEC File
Security Driver
# 0492 NWSERVER Windows 95
NetWare-compatible File Server
# 049B VNBT
NetBIOS Transport for TCP/IP