Help! Coincidence or Virus or ???

[Rl'Halsinor]

I think a clean install would be a good idea. Did you scroll down the link I provided and read fully about your particular Stop Error? It can be software as well. Have you done Memtest on your memory?

 

[Redrobes]

The System Event Notification service depends on the COM+ Event System service which failed to start because of the following error:
No attempts to start the service have been made since the last boot.

This means that your event log is switched off so its not going to report any errors like your STOP problem until its switched on.

It appears as though you have a number of services disabled. You should go to your administration tools / services and look at what you have enabled (Auto / Manual - Started/Running) and disabled. Particularly check the System Even Notification service - which appears to be on BUT it depends on other services. Look at the dependancy list and ensure that they are on and that their dependants are on too (i.e. the COM+ service). Basically most services should be running though a few should be off if you dont use certain features (universal plug and play, remote login, etc being a couple for an example).

Once you have your event log running then get a BSOD and then reboot and see who is causing it. It could be dodgy memory which would mean anything could cause it but if the app is the same over many reboots then look at that one closely.

Two seperate machines starting to cause the same BSOD at the same time ? Extremely unlikely to be a hardware issue like RAM.

 

[greymist]

Rl'Halsinor wrote: I think a clean install would be a good idea. Did you scroll down the link I provided and read fully about your particular Stop Error? It can be software as well. Have you done Memtest on your memory?

I did read the link you posted, that page is a copy of the MS KB, and the only software issues they mention are: Stop 0x7F messages can occur after installing incompatible applications, drivers, or system services.Pretty generic info! Nothing was recently installed on the XP box, and only 7Zip on the 2000 box, and that was over a week prior to the BSODs.

I didn't run Memtest as I used it a few months back, both sticks in the XP box were tested, and the stick in the 2000 box is only a few months old. But if these BSODs reappear I will be dragging out Memtest!

Redrobes wrote: This means that your event log is switched off so its not going to report any errors like your STOP problem until its switched on.

I think I turned some services off when I was experiencing some issues with memory (which were eventually solved with the new stick of RAM noted above). I will have to go back in and figure out which ones I should switch on, in case this issue comes back.

Both machines have been running since yesterday without a hitch, hopefully that will continue!

Thanks for everyone for their responses and help.

 

[Ralts Bloodthorne]

I had this hit the other day.

I booted up with logging on, and found the driver that was the problem. For me, it was my video card, totally corrupted.

Here's the rub. I didn't install a new driver, and there were 12 copies of that damn driver in my driver's directory.

Start it up with logging on, write down which drivers were loaded, then check them in safe mode.

Hopefully this will help you.

 

[tkkonirc]

Redrobes, I just checked out the Event Viewer...mostly gibberish to me. Things like this after each reboot:



Rl'Halsinor, I did write down the STOP numbers: 0x0000007F. The four numbers in the parentheses that followed were all 0's, and the problem is described as an Unexpected Kernel Mode Trap. The MS KB indicates that this is usually a hardware issue.

I did manage to get both PCs working today! On the XP machine I simply restored to a point earlier than yesterday's restore, and it worked. On the Win2000 box I am still confused why it is working.

When I rebooted the W2000 box, it would get further into the startup than the XP box. My wallpaper would appear, the Quick Launch bar would populate, my desktop icons would appear, and the system tray would start to fill, then BSOD. I figured that something that was auto-starting was causing the problem. I used Mike Lin's Startup to kill Wallmaster and Stickies, and a few other things, and it booted!

I immediately ran BitDefender's rootkit detector which found nothing. I then ran rootkit revealer, and I got another BSOD. I rebooted and it started fine. I wonder if there is a rootkit on this machine which is evading detection?

I think I will have to reinstall Windows on the 2000 machine for sure, as it has not been done for at least 2 years, maybe 3. The XP box, I will jeep my fingers crossed that it was a bad download on my wife's part, and that it does not happen again!!

I received BSOD & STOP: 0x0000007F on my XP Pro SP2 today after applying the latest critical update. Could not login to my normal XP account, as it would crash/reboot after it loaded the first few startup items. So I logged on as administrator and received the "recovered from a critical error" notice. I looked at the .dmp file referenced in the technical details and wallmast.exe was the culprit. I uninstalled wallmaster (v. 2) filesize (3978kb) and rebooted. I mention the filesize of wallmaster because on the wallmaster website, they have version 2.0 as only 1142 kb <shrugs> . Anyway, after rebooting, I was able to successfully login to my user account. I tried reinstalling wallmaster just to be sure, and it immediately crashed/rebooted. I can only guess that a new windows update interferes with it? Anyway, that was my solution. I'm not sure what needs to be done on 2000, but try uninstalling wallmaster! Hope this helps. I don't even play D&D but HAD to post after fighting this error for 4 hours today.

 

[greymist]

Warlord Ralts wrote: I booted up with logging on, and found the driver that was the problem.

I didn't think it could be a driver, as I have not changed any in recent memory, but given what happened to you, I will keep it it in mind if the BSOD returns.

tkkonirc wrote: I looked at the .dmp file referenced in the technical details and wallmast.exe was the culprit.

Interesting. I have not started up Wallmaster on either machine since I got them running, and I guess I won't bother. Time to find a new wallpaper changer!

Thanks for the tips.

 

[Plane Sailing]

Nothing was recently installed on the XP box, and only 7Zip on the 2000 box, and that was over a week prior to the BSODs.

Do you have Windows Update set to automatically download and apply fixes? That has been a problem for some people in the past, when a windows update has been quietly applied behind the scenes and suddenly everything starts breaking.

Have you tried using an older system restore point (say from a few weeks ago?).

 

[greymist]

Plane Sailing wrote:Do you have Windows Update set to automatically download and apply fixes?

Not on the 2000 machine, but I think on the XP machine it got turned on somehow. BUt I have switched it off again!

I got the XP machine running by going to a previous restore point, no such thing on 2000, but as I noted, it is running now.

 

[tkkonirc]

Finally solved my BSOD/Reboot errors. I use AVG antivirus and it has been reported that the newest update (build 407) is causing these errors.

From the AVG forum "The new update causes this when certain EXEs are run or even scanned. One app that causes it without question is Wallmaster 2.4e"

Even after uninstalling wallmaster, I was still getting reboots once my system went idle (either with a screensaver or monitor power off after x number of minutes). Then I would get a dump file on reboot pointing to svchost.exe.

My daughter's computer is currently running AVG with the 407 update and her computer is having NO problems with it.

I uninstalled AVG last night and I have not had ANY more reboots or BSOD.

I'm not sure how limited this problem is, but hopefully AVG will fix it. Until then, I've switched to AVAST! antivirus sofware.

http://forum.grisoft.cz/freeforum/read.php?2,77597,77719#msg-77719
http://forum.grisoft.cz/freeforum/read.php?1,77700,77700#msg-77700
http://forum.grisoft.cz/freeforum/read.php?2,77503,77668#msg-77668

 

[greymist]

tkkonirc wrote: From the AVG forum "The new update causes this when certain EXEs are run or even scanned. One app that causes it without question is Wallmaster 2.4e"

This makes total sense for both of my machines. Both have AVG running with automatic updating, so they likely updated to the "bad" version, and it interacted with Wallmaster.

Mystery solved!