MSPUB 2002 caused general protection fault; performed illega

[Larry1eprint]

•••
We are working in Windows 98 4.10.2222A;
Publisher 2002 PID No.: 54197-750-4398524-16750;
Publisher 2000 PID No. 50066-007-6917327-02803;
on a Compaq Presario 5868;
RAM, 128MB;
processor, AMD-K7 (tm) MMX, 3DNow;
speed, 650MH;
I am sending this from my Mac using Netscape 4.7.
•••

I trust that this is enough information to get help.

In Publisher 2002, we keep getting the message in a dialog box: "This program has performed an illegal operation and will be shut down…

The error dialog boxes started appearing after upgrading to 2002 (from version 2000) and attempting to open a client’s MS Publisher 2000 document, it read, “This program has performed an illegal operation and will be shut down. If the problem persists, contact the program vendor.”

Selecting the details button gave the following text:

MSPUB caused a general protection fault
in module 3DFX16V3.DRV at 0009:000002ce.
Registers:
EAX=0000bb28 CS=0397 EIP=000002ce EFLGS=00000246
EBX=006240b6 SS=3ccf ESP=0000ba08 EBP=0000ba22
ECX=00000004 DS=3ccf ES1=0000bb28 FS=374f
EDX=00013ccf ES=0000 ED1=00000000 GS=0000
Bytes at CS:EIP:
f3 66 a5 If 8b d8 8e c2 66 26 8b 47 14 c4 5e Oc
Stack dump:
83060427 0001bb28 318910ca bb3eOl6f OOOa4dIb 000007f4 ba3cOOOO 0387237f
bb281388 00003ccf 04270000 fbbe8306 30cb52bc 0458ba5a 000003ff bb280000

The above document opened with no hitches in our Publisher 2000, still on the hard drive.

We thought it was a damaged file, but of late with more Publisher documents from other clients, some saved with the Pack and Go feature, some not, we are getting similar error messages while doing a variety of other things in Publisher 2002, an example:

Clicking details, we got: MSpub Caused a general
protection fault in module 3DFX16U3.DRU at 00009.000002ce.

These messages happen while: trying to open a folder, searching for a file, opening a file, moving a text box one way in a document, choosing a new font, etc.

We uninstalled and reinstalled the program several times. We left the older MS Publisher 2000 installed on the hard drive during these trials. Now we have uninstalled 2002 and gone back to using 2000 which opens all the publisher files without incident that would not work correctly in 2002.

What's the problem with Publisher 2002? Thanks for any help you can offer.

 

[Guest_imported]

When working with Microsoft Office XP or Publisher 2000 you may recieve the error
WINWORD(or other Office product)caused a general protection fault
in module 3DFX16V3.DRV at 0009:000002ce.
Registers:
EAX=0000bb28 CS=0397 EIP=000002ce EFLGS=00000246
EBX=006240b6 SS=3ccf ESP=0000ba08 EBP=0000ba22
ECX=00000004 DS=3ccf ES1=0000bb28 FS=374f
EDX=00013ccf ES=0000 ED1=00000000 GS=0000
Bytes at CS:EIP:
f3 66 a5 If 8b d8 8e c2 66 26 8b 47 14 c4 5e Oc
Stack dump:
83060427 0001bb28 318910ca bb3eOl6f OOOa4dIb 000007f4 ba3cOOOO 0387237f
bb281388 00003ccf 04270000 fbbe8306 30cb52bc 0458ba5a 000003ff bb280000

This problem is caused because of a conflict with 3dfx display adapter drivers if you have a vodoo 3 or velocity 100/200 card as well as others. If you update these drivers everything sould work great. You can go to

http://www.voodoofiles.com/3201

for the update file I used.

 

[Larry1eprint]

Thanks for your suggestion for solving our “general protection fault” error. We are experiencing it with MS Publisher 2002, though.

I tried downloading the 3dfx display adapter driver from the Voodoo web site you mentioned. When the compressed downloaded file was unzipped though, I had some 20 files of various types. Did I down load the right stuff? The list of contents is as follows:

readme.txt 3KB Text Document 11 /13/00 11:15 AM
manifest. txt 1KB Text Document 11 A 0/00 2:55 PM
stbaud32.dIl 36KB Application Extension 11/10/00 2:51 PM
stbmiway.exe 54KB Application 11/10/00 2:51 PM
vcapdey.dll 40KB Application Extension 11/10/00 2:51 PM
VTV.inf 9KB Setup Information 11/10/00 2:51 PM
Bt848ybi.386 13KB Virtual device driver 11 A OJOO 2:51 PM
Btcc.dll 84KB Application Extension 11/10/00 2:51 PM
btddi.dll 45KB Application Extension 11 A 0/00 2:51 PM
Btpcivid.vxd 1OOKB Virtual device driver 11 il 0/00 2:51 PM
Btutill 6. dll 17KB Application Extension 11/10/00 2:51 PM
btutil32.dll 36KB Application Extension 11/10/00 2:51 PM
Btvcap16.dll 5KB Application Extension 11/10/00 2:51 PM
Btvid.drv 75KB Device driver 11/10/00 2:51 PM
Btvid_16.dll 12KB Application Extension 11/10/00 2:51 PM
Btvid_32.dII 52KB Application Extension 11/10/00 2:51 PM
Btyiddlg.dll 54KB Application Extension 11/10/00 2:51 PM
Btvvc32.drv 62KB Device driver 11/10/00 2:51 PM
BtVVC32.inf 3KB Setup Information 11/10/00 2:51 PM
grappler.dU 94KB Application Extension 11/10/00 2:51 PM


Looks like a bit more than just a display driver, in fact there are two drivers listed!

Although I may have the right stuff, I didn’t want to run the driver updater in Windows without first saving the current driver version in case the update really gives us worse problems--so we could revert back.

We are not advanced Windows users, so not real sure as what to do. Please advise. Thanks.