Discussion Locked

OE at 0137:BFF9A3C0

0 helpful
27 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We get this error from different users several times a day (of course this is a "Blue Screen of Death" scenario. We have tried several unsuccessful attempts to correct it but nothing has seemed to work. We are using Win95 with Novell Client 2.5 & 3.1, GroupWise 5.5.2, Corel8, DocsOpen and IE4.0 as the main programs. The problem seems to be very random and we haven't been able to narrow it down to any app or function. Any ideas?

27 replies

by nicholas paras

99% of the time this error is due to a memory malfunction. Memory is a very sensitive piece of equipment. If you put memory of 2 different types (EDO mixed with non-EDO). This will not show up in the initial on start memory test but it is a problemand memory causes very disturbing conflicts, sometimes not even allowing windows itself to start. Try adding memory of one type, or replace one of you memory chips if they are of the same access time and type.
Hope this helps,
regards, NICHOLAS.

by zogware

Maybe you use overclocked processor. Check processor unit, or if you use non PC100 memory for frequency bus >66Mhz. Check you hardware.

by gerriep

More specific information is needed to analyse your problem. After the blue screen, do you get any "program caused illegal operation" type message with a "details" button? If so, post this so I can have a look at it.
The only advice at this stage is to disable any sort of power saving you might have.
IE4.0 can also cause similar problems as well as certain VGA cards. These would produce an "invalid page fault" error once you press a key (from blue screen) and it returns you to Windows.

by jgajeski

the fact that you are using 2 different clients on the same network is scary! this could be an even bigger problem. the 2 clients could be conflicting with one another. try getting all workstations using the same 3.10 client and get the latest patch from novell for that client. also, you might be using cheap memory instead of some high quality viking memory. all of the previous postings that have some memory resolutions are all valid things to try.

by rindi1

From your info it's difficult to diagnose your problem. Are you using a virus scanner? if so, which one? Look in your registry under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VXD\Symevnt.
If this key exists, save it then delete it. Reboot your system and test it to see if the problem still exists.

by proe

I have a very similar environment sans the Groupwise, DocsOpen, and IE4. This problem appears when our users are in Corel WordPerfect Suite 8. It is somewhat random, but from experience I think it often occurs when the user has first entered WordPerfect and accesses File, Open while the program is still loading (hard drive still making noise!), Corel's knowledge base has a number of suggestions for this error--do a search in it for their suggestions. I believe some of their solutions include replacing the video and printer drivers and disabling the enhanced file dialog box. I just tell my users to be a little more patient!

by wholzem1

Be it an Exception error, a Fatal Exception Error, Invalid Page Fault, or Illegal Operation, if the address that it occurs at is 0137, it's a very good bet that it has something to do with the video card and/or it's drivers.

So check to make surethatyou have the correct driver installed, and the correct monitor chosen.

If not, correct it. Also check with the OEM to see if an updated driver is available.

Other things to check include any display or font settings in the applications involved. Anything display related.

Occasionally a printer driver problem may be involved. The biggest indicator for printer problems would be GDI.EXE (Graphic & Display Interface) being involved. But even then, the video driver is a better bet thanthe printer driver.

by wholzem1

There is an update to shell32.dll that corrects this problem. You need to contact Microsoft Tech Support, and allow the Support Engineer to poke and prod enough to gather the information that the escalation engineers need to ensure that there aren'tother issues involved.

This issue is resolved in Windows 98.

by ericg4679

All fatal exception errors follow the example "A fatal exception has occurred at xxxx:xxxxxxxx" the representing the actual processor exception. 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. By using the Windows 95 device manager you can lookup the 8-bit memory address and determine which device is using it.

by duster52

A couple of questions which may help. Does the problem always happen on the same computers? Does the problem follow users from one computer to another? Do you know which applications are open when the abend happens? Is there any similarity between the computers that have the problem: same vendor, brand, memory, hard drive, video card, etc.? This may help you isolate the problem.

The only issue with different clients is the interaction with those clients and a particular application. Having different clients on a Novell network with not cause any problem.

by jesselou

configure correctly your network connection and your ie4.0.try to reinstall ie4.0 in full.then download the msdun13.exe which is an upgrade to your win95 dialup network similar to that of win98.this may correct your integration with novell client 2.5.reconfigure your tcp/ip under dial up
network.

by tathtar

Refer back to answer #1, we had 37 PC's which exibited this problem, it seems the users them selves had upgraded thier PC's memory, and had ordered non-EDO memory, the first 2 banks had EDO, and the Last 2 now had non EDO. When we took all the chipsout and put only EDO or NON EDO in a machine the problem stopped happening in ALL 37 Pc's we had the exact error address you have.

I hope this helps

This discussion is closed to new replies.