Annoyances.org
Home » Windows XP Discussion Forum » Message 1156913084 Search | Help | Home
  
Tip: Run a free scan for common Windows errors ad

re: I've encountered an error message '' 0x0000007e(0xc0000005,0x00000000,0xf96b487c,0xf96b457c)
Tuesday, August 29, 2006 at 9:44 pm
Windows XP Annoyances Discussion Forum
Posted by Tsvi Gold (1 messages posted)


My error message was similar: 
0x0000007E 0xC0000005 0xBA2224B0 0xF789DFC4 0xF789DCC0
but the source TURNED OUT TO BE a corrupted vsmon.exe file -- a Zone Alarm component 
had gotten corrupted.  This supports Microsoft's contention that a bad driver COULD 
cause the 0x0000007E error.
I had a new system-board installed and it had a bad NIC.  In addition, the WinXP 
event manager in safe mode indicated that vsmon.exe [Zone Alarm's "TrueVector Internet 
Monitor"] had exibited numerous failures prior to the time the system ultimately 
failed.  The driver had become corrupted.  Later, when it tried to run, the corrupted 
driver caused the BSOD, producing the above error.  I do not know the source of the 
corruption.  However, I ...
1.  Uninstalled the software that was using the corrupted driver (ZoneAlarm);
2.  Searched for and destroyed any registry keys referencing the offending driver 
(ZoneAlarm cleaned itself up nicely, leaving nothing to delete), and
3.  Rebooted Normally
The BSOD disappeared and I was back up in Normal Mode.  If you look at your Event 
Manager in Safe Mode [control panel -> administrative tools] for a few days PRIOR 
to system failure, you may show a bad driver failing DAYS before the system actually 
went down.  A previous post listed "VSO software" for a DVD burner being the culprit 
- ptapi.sys.  I suspect that the failure could result for ANY bad or corrupted driver. 
 
The Event Manager should indicate the origin of offending driver you need to remove 
or fix.  I hope that helps!




On Thursday, July 24, 2003 at 3:57 pm, djryan_08 wrote:
>July 25,2003 at 7:04 AM
>can some body post a reply on my problem...i've been struggling on it and i don't
>want to mess up my system...thank you in advance.....



Written in response to:
I've encountered an error message '' 0x0000007e(0xc0000005,0x00000000,0xf96b487c,0xf96b457c) (djryan_08: Thursday, July 24, 2003 at 3:57 pm)

There are presently no replies to this message.

All messages in this thread [show all]
-Question about 'What to do about error messages during Windows startup' (Leigh: Wed, Mar 5, 2003, 6:43 pm)
-re: Question about 'What to do about error messages during Windows startup' (Dan Sarandrea, MCSE: Thu, Mar 6, 2003, 3:54 pm)
-re: Question about 'What to do about error messages during Windows startup' (William A. Cornacchia: Thu, Jun 12, 2003, 9:50 am)
-I've encountered an error message '' 0x0000007e(0xc0000005,0x00000000,0xf96b487c,0xf96b457c) (djryan_08: Thu, Jul 24, 2003, 3:57 pm)
*re: I've encountered an error message '' 0x0000007e(0xc0000005,0x00000000,0xf96b487c,0xf96b457c) (BEBO: Thu, May 27, 2004, 4:35 am)
*re: I've encountered an error message '' 0x0000007e(0xc0000005,0x00000000,0xf96b487c,0xf96b457c) (Tsvi Gold: Tue, Aug 29, 2006, 9:44 pm)
*re: Question about 'What to do about error messages during Windows startup' (Terry Moon: Wed, Oct 19, 2005, 10:44 pm)
-re: Question about 'What to do about error messages during Windows startup' (p camplin: Thu, Nov 6, 2003, 5:03 am)
*re: Question about 'What to do about error messages during Windows startup' (James Cooper: Thu, Nov 27, 2003, 3:20 am)
*re: Question about 'What to do about error messages during Windows startup' (Jay Skulkan Bushwhacker: Sat, Mar 25, 2006, 11:06 am)
Return to the Windows XP Discussion Forum


All content at Annoyances.org is Copyright © 1995-2009 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.