jester, I hope this solves your problem.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;189655
****************************quote***********************************
RESOLUTION
WARNING: Using Registry Editor incorrectly can cause serious problems
that may require you to reinstall your operating system. Microsoft
cannot guarantee that problems resulting from the incorrect use of
Registry Editor can be solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing
Keys And Values" Help topic in Registry Editor (Regedit.exe) or the
"Add and Delete Information in the Registry" and "Edit Registry Data"
Help topics in Regedt32.exe. Note that you should back up the registry
before you edit it.
To resolve this issue, disable the Symantec Symevnt.386 file. To do
so, follow these steps:
1. Use Registry Editor to delete the following registry key, if it exists:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\SymEvnt
2. Click Start, click Run, type sysedit, and then click OK.
3. On the Window menu, click System.ini.
4. On the Search menu, click Find.
5. In the Find box, type symevnt.386, and then press ENTER.
6. Place a semicolon (;) at the beginning of the line that contains "symevnt.386."
7. On the File menu, click Save, and then click Exit on the File menu.
8. Restart your computer.
9. After Setup has finished successfully, reinstall the Symantec
program. If the problem continues to occur, contact Symantec for
additional information.
****************************quote***********************************
Search strategy:
http://groups.google.com/groups?&q=Fatal+Exception+0028%3ABFF98DAE
Google! Groups often provides better answers to technical support
questions than general Google searches do. Chances are if you have a
question about something going wrong in Windows, it's happened to
someone else before, and there's a good chance that it's been asked
before. If you're lucky enough to find an answer there as well, it can
be a tremendous timesaver.
However, in this case, it merely confirmed the use of the more archaic
resource, the Microsoft Knowledgebase, which contains many errors and
is a good place to go to if you actually have an error code or a
specific MS-product bug:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;kbhowto
Thanks for your question, and thanks for choosing Google! Answers.
-- bookface-ga |