Tip: Run a free scan for common Windows errors ad

re: Question about 'What to do about error messages during Windows startup' Thursday, March 6, 2003 at 3:54 pm Posted by Dan Sarandrea, MCSE (4310 messages posted) The blue screen of death has an error message on it, and this is usually the format: STOP: 0x0000007E (0xC0000005, 0x804E518E, 0xFC938104, 0xFC937E04) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Post your error message and then help will happen. You should repost with a new message as these get buried quickly. [Reply or follow-up to this message] re: Question about 'What to do about error messages during Windows startup' Thursday, June 12, 2003 at 9:50 am Posted by William A. Cornacchia (1 messages posted) lOn my Desktop I have an ICON Excite Home Page will it cause the ExShell to shout down my computer? On Thursday, March 6, 2003 at 3:54 pm, Dan Sarandrea, MCSE wrote: >The blue screen of death has an error message on it, and this is usually the format: > >STOP: 0x0000007E (0xC0000005, 0x804E518E, 0xFC938104, 0xFC937E04) >SYSTEM_THREAD_EXCEPTION_NOT_HANDLED > >Post your error message and then help will happen. > >You should repost with a new message as these get buried quickly. [Reply or follow-up to this message] I've encountered an error message '' 0x0000007e(0xc0000005,0x00000000,0xf96b487c,0xf96b457c) Thursday, July 24, 2003 at 3:57 pm Posted by djryan_08 (1 messages posted) 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..... On Thursday, June 12, 2003 at 9:50 am, William A. Cornacchia wrote: >lOn my Desktop I have an ICON Excite Home Page will it cause the ExShell to shout >down my computer? > > [Reply or follow-up to this message] re: Question about 'What to do about error messages during Windows startup' Thursday, November 6, 2003 at 5:03 am Posted by p camplin (1 messages posted) can you help me i have this blue screen of death my message is stop:0x0000007e(0x0000005,0x0001000d,0xf89a8924,0xf89a8624) heres hopeing campo On Thursday, March 6, 2003 at 3:54 pm, Dan Sarandrea, MCSE wrote: >The blue screen of death has an error message on it, and this is usually the format: > >STOP: 0x0000007E (0xC0000005, 0x804E518E, 0xFC938104, 0xFC937E04) >SYSTEM_THREAD_EXCEPTION_NOT_HANDLED > >Post your error message and then help will happen. > >You should repost with a new message as these get buried quickly. [Reply or follow-up to this message] re: Question about 'What to do about error messages during Windows startup' Thursday, November 27, 2003 at 3:20 am Posted by James Cooper (1 messages posted) I had this problem last night after installing a DVD burner. After many reboots I narrowed down the culprit to a VSO Software CD-ROM driver, ptapi.sys. Even though I had uninstalled the VSO software ages before, the driver was not uninstalled. If you have previously installed this software, remove %system%/drivers/ptapi.sys and remove all references to it from registry/CurrentControlSet/class/{CD/DVD Devices} as when the Add Hardware Wizard installs the device it looks here for what drivers to load for the device. Sorry, I can't remember the exact registry path (I was up late fixing it, shouldn't be too hard to find). Reboot and all should be fine (Well it was for me anyway!) On Thursday, November 6, 2003 at 5:03 am, p camplin wrote: >can you help me i have this blue screen of death my message is stop:0x0000007e(0x0000005,0x0001000d,0xf89a8924,0xf89a8624) >heres hopeing campo > > [Reply or follow-up to this message] re: I've encountered an error message '' 0x0000007e(0xc0000005,0x00000000,0xf96b487c,0xf96b457c) Thursday, May 27, 2004 at 4:35 am Posted by BEBO (1 messages posted) This is a new virus on the web. this virus have been released 4 or 5 days ago,, symantec is still working on a solution for this virus,, It affect the same way as the sasser. also i have noticed that this issue also bring some other problems like: The HuntBar IE toolbar (also called WinTools, does not require network connection). One of the Korgo variants, likely Korgo.C The Newgina password capture utility. Certain later NetSky variants. As you can see the virus is called W32.Korgo.c and the other is W32.Donk.Q,, this Donk.Q already have a removal tool on symantec. But we're still waiting for the Korgo. the only way stop by now is disconnecting the network cable. 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..... > [Reply or follow-up to this message] re: Question about 'What to do about error messages during Windows startup' Wednesday, October 19, 2005 at 10:44 pm Posted by Terry Moon (1 messages posted) I am recieving the error explorer.exe applicationfailed to initialize prpoerply (0cx0000005). my system will not load my desktop, but if I go to the task manager I can get around to the internet n order to send this email. Please HELP!!! On Thursday, June 12, 2003 at 9:50 am, William A. Cornacchia wrote: >lOn my Desktop I have an ICON Excite Home Page will it cause the ExShell to shout >down my computer? > > [Reply or follow-up to this message] re: Question about 'What to do about error messages during Windows startup' Saturday, March 25, 2006 at 11:06 am Posted by Jay Skulkan Bushwhacker (1 messages posted) Folks, I have been down a week and counting because of this problem. Any suggestion will be appreciated. Here is the entire BSOD. Maybe someone will find something here that I can't see, It is about four paragraphs long, but there doesn't ever seem to be any specific information about what is failing other than the long alphanumeric number that I shared last week. Here is the entire blue screen message: "A problem has been detected and windows has been shut down to prevent damage to your computer. If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps: Check to be sure you have adequate disk space. IF... a driver is identified in the stop message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove, or disable components, restart your computer, press F8 to select advanced startup options, and then select safe mode. Technical Information: *** STOP: 0x0000007E (0xC0000005, 0xF8CE64D0, 0xF9E67FEC, 0xF9E67CEC)" Forum. that's it! The screen is totally empty the rest of the way to the bottom. I did type in the STOP number wrong the first time. So I will google this number and see if it gives me any information that I didn't get the first time when I had several digits missing, or incorrect. >How am i supposed to fix my computer, if i can't get to windows? > [Reply or follow-up to this message] re: I've encountered an error message '' 0x0000007e(0xc0000005,0x00000000,0xf96b487c,0xf96b457c) Tuesday, August 29, 2006 at 9:44 pm 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..... [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows XP Discussion Forum