OE at 0028:C02A0948 in VXD VWIN32

I searched google on this error but I couldn't find
anything. Please help. Thanks.

I searched google on this error but I couldn't find
anything.

You didn't find anything because there are many possible causes,
including defective RAM. Since you tiold nothing about the situations
in which this error occurs, I'll give you a very long list of
diagnostic steps. These apply to all kinds of problems, not only the
one you are having.

Troubleshooting should follow this logic:

1. Check Microsoft's web site to see whether they have created a
troubleshooter that fits your situation:
http://support.microsoft.com/support...fault.asp?FR=0

2. Think about things you have done that might be causing trouble.

3. Think about the pattern of errors or the lack of a pattern.

4. Check for a virus or a bad spot on the harddisk.

5. Eliminate badly fragmented files and temporary files.

6. If you have Win95, run RegClean. If you have Windows 98, run
ScanReg /fix.

7. Start Win95/98 in Safe Mode. If the trouble does not appear in Safe
Mode, then the trouble is caused by software conflicts or defects.
Investigate each of the functions that Safe Mode turns off.

8. If the trouble also occurs in Safe Mode, rename the current Windows
folder and reinstall Win95/98 into an empty folder. If the trouble
does not appear with a fresh installation, the trouble is caused by
something you have added to Win95/98 (but something that is not turned
off by Safe Mode).

9. If the trouble occurs even with a fresh install of Windows, the
trouble is arising in hardware.

First, some questions that may suggest a cause for the trouble:

When did the trouble start? What changes did you make to the system
that could have initiated this behavior?

When does the problem occur? Is it associated with a specific program?
You cannot be sure that the problem was caused by the program(s)
mentioned in an error message. Often, error messages simply cite the
program that has noticed the problem. In particular, error messages
often mention Windows components such as Krnl386 or MsgSrv32. It is
very unlikely that these have caused the trouble. One or another
Windows component is running most of the time. MsgSrv32 is a little
program that delivers error messages to the screen; when an error
message mentions MsgSrv32, it only indicates that the computer halted
while displaying an error message.

Did you install Win 95 over an earlier version of Windows (Win 3.1 or
WFWG), or did you install Win 95 to a clean directory?
Some 16-bit drivers for Win3 do not work properly with Win95/98, so
installing over Win3 can be a source of trouble.

Are you running any TSRs with it? What third-party device drivers are
you using? (Look at Config.sys, Autoexec.bat, System.ini, and the
LOAD= and RUN= lines in Win.ini.)

When do the errors occur? If they occur only when you run one
specific program, check the configuration of that program. Is it set
up correctly? Also, what drivers does that program use? If the
errors occur with many programs but in systematic patterns that you
can reproduce, then be suspicious of drivers that affect many programs
-- such as video software. If the errors seem to occur at random, so
that you cannot reproduce the errors consistently, then they are
probably caused by hardware. Software always behaves consistently,
whereas hardware is capable of randomness. In particular, defective
or inappropriate RAM chips can cause all sorts of errors in programs
of all types.

The following troubleshooting steps apply to diverse situations:

1. Check for a virus. Use at least two different up-to-date virus
checkers.

2. Run ScanDisk and have it do a thorough (surface) scan.

3. Open the folder that holds temporary files (usually
C:\Windows\Temp). Either delete its contents or move its contents to a
floppy disk.

4. Defragment the harddisk(s).

5. Does the problem occur in safe-mode? To get to Safe Mode, reboot
the computer and press F8 when you see "Starting Windows 95..." Choose
Safe Mode from the menu.

Safe Mode is intended for troubleshooting. It does the following:
(a) bypasses config.sys and autoexec.bat
(b) prevents programs from starting automatically because they are
listed in
win.ini or they are in the startup folder
(c) uses standard VGA video
(d) prevents a network from being started
(e) disables protected mode device drivers (which are listed in
Device Manager)
(f) bypasses the [boot] and [386Enh] sections of system.ini
For more details, see document 122051 in the Microsoft KnowledgeBase.

If Safe Mode makes the problem go away, you should try tests from the
list below to pin down the cause of the problem. For more elaborate
instructions, see document 156126 in the KnowledgeBase, which explains
how to do troubleshooting in Safe Mode.

With Windows 98, you can use MSConfig to help you run the tests below.
With Windows 95, you can use Startup Manager or Startup Cop. Startup
Manager is a freeware program, similar to the Msconfig utility that
ships in Windows 98. It can make troubleshooting easier by removing
and restoring items from the Windows startup.

http://members.aye.net/cgi-bin/dfs_c...startupmanager

Also, Startup Cop can disable items loading at Windows startup and it
is freeware. You can download Startup Cop from:

http://www.zdnet.com/downloads/stori...0,,77594,.html

6. Change the video driver to Microsoft's Standard Display Adapter
(VGA). Restart Windows and test.

7. Rename the Config.sys and Autoexec.bat to Config.sss and
Autoexec.bbb, or edit them so that the only things loading are
absolutely necessary for the computer to run. The latter items might
be a SCSI driver for the harddrive, or disk management software for an
EIDE drive. Deactivate EVERYTHING else by putting REM in front of
that line. Reboot the computer and test.

8. Remove EVERYTHING from the Start Menu/Startup folder by dragging
their icons onto the desktop. Also disable or uninstall all utilities
that are running TSR (such as Norton Navigator, SoftRam or Macafee
AV). Restart Windows and test.

9. Rename the Win.ini and System.ini to Win.iii and System.iii. Then
make a copy of System.cb and name it System.ini. Do not rename
System.cb itself. Edit the new System.ini as follows: Add
device=*vmd
to the [386Enh] section, and add
drivers=mmsystem.dll
mouse.drv=mouse.drv
to the [boot] section. Restart Windows. You probably will have no
mouse so you'll have to use keystrokes to do the following. Go into
Device Manager and select the mouse (which will have a yellow
exclamation point). Click "Remove." Again, restart Windows. Windows
should find the mouse and install software for it. Test.

10. Rename the current Windows folder (directory). Then install
Win95/98 to a new, empty folder. Test. If problem does not occur, it
was caused by something in the old installation. I recommend that you
keep this new installation and reinstall your Windows applications.

The following articles explain how to install into a new folder:

How to Reinstall Windows 95 to a New Folder [142096]
http://support.microsoft.com/support...s/142/0/96.asp

How to Install Windows 98 to a New Folder [193902]
http://support.microsoft.com/support...s/193/9/02.asp

When you reinstall applications, install Windows applications that
were written for Win95/98 or WinNT but do not install older
applications that were written for Windows 3.x. Install only one
application at a time and test the system thoroughly before installing
another application. Before you install and application, make a system
snapshot with a program such as ConfigSafe; this will allow you to
revert to the previous situation if (when) you install an application
that causes trouble. With Win98, it is also possible to run "ScanReg
/Backup" before you install an application, which allows you to
restore the Registry if (when) you install an application that causes
trouble. However, it is safer to make a complete system backup and
recovery with ConfigSafe or a similar product.

11. If the problem occurs with a clean boot and a clean install, then
you need to look at the hardware configuration. Here are some of the
more common hardware issues:
CMOS virus protection, shadowing, or caching
Bad or incompatible RAM
Improperly configured harddrives
Hardware peripherals in which the I/O address steps on something
else

To test the RAM, you can download a test program from
www.simmtester.com. You put it on a floppy disk that you boot in order
to run it. It runs a cycle of several differently patterned tests
over and over.

You can also use RAMDrive to test the reliability of your RAM chips.
However, RAMDrive can exclude no more than 32MB so it cannot test
large amounts of memory. For instructions, see document 142546 in the
KnowledgeBase.

It's quite a program of tests! I certainly do hope it helps.


Bill Starbuck (MVP)