Event Viewer System Error

Hi All:

Anybody know what this is or how to fix it?

Event Type: Warning
Event Source: SNMP
Event Category: None
Event ID: 1101
Date: 2/20/2004
Time: 10:50:55 AM
User: N/A
Computer: CATASTROPHY
Description:
The SNMP Service is ignoring extension agent key SOFTWARE\Microsoft\IPXMibAgent\CurrentVersion because it is missing or misconfigured.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 02 00 00 00 ....


Any response is appreciated.

Martin

 

LOL!!



You named your computer "Catastrophy "????

Johanna
who knows just how you feel....

 

Thanks Arie: I'll try that and post back.

Johanna: Yes, Catastrophy. I was thinking of Train Wreck or something similar, but over time, Catastrophy suits this machine.

 

Jeez Arie, How did you get so smart? Deleted that key, the deletion fixed that system error, and also, fixed 4 more system errors I was going to post questions on separately.

Errors caused by machine trying to load software for hardware that had long been removed.

I can't imagine what one has to do with the other, but plainly it did.

So, thanks again, Windows BBS to the rescue again. Anybody who hasn't become a contributing member, it is the best $ I ever spent.

 

Arie, I patted us on the back too soon.

The errors in system event viewer for loading the software for hardware long since removed are back. One of which I tried to fix with a suggestion from Newt, but that error is still there. Something to do with UMAX scanner, for which I deleted all references to in registry. But still getting error. There are other scanner references in registry for scanners not attached to this machine.

Plus, now I have changed video cards but machine still trying to load some ATI stuff. Nothing of ATI left in drivers or programs that I can find. There are ATI entries in registry, I'm not comfortable working registry w/o explicit instruction.

Start a new post or add the additional errors here?

One per post or all together?

Appreciate all your help and help of others on this great board.

Martin

 

Put the errors in here. It's really an extension of the same issue for you.

And all in the same post is probably simpler and easier to manage.

 

OK, here goes:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 2/21/2004
Time: 7:39:34 PM
User: N/A
Computer: CATASTROPHY
Description:
The UDNT service failed to start due to the following error:
The system cannot find the device specified.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 2/21/2004
Time: 7:39:34 PM
User: N/A
Computer: CATASTROPHY
Description:
The ATI WDM TV Tuner service failed to start due to the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 2/21/2004
Time: 7:39:34 PM
User: N/A
Computer: CATASTROPHY
Description:
The ATI WDM TV Audio Crossbar service failed to start due to the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 2/21/2004
Time: 7:39:34 PM
User: N/A
Computer: CATASTROPHY
Description:
The ATI WDM Specialized MVD Codec service failed to start due to the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 2/21/2004
Time: 7:39:34 PM
User: N/A
Computer: CATASTROPHY
Description:
The ATI WDM Specialized PCD Codec service failed to start due to the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Then these two about 5 times each alternating:

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 2/21/2004
Time: 7:37:48 PM
User: N/A
Computer: CATASTROPHY
Description:
Application popup: : Machine Check: Regs

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 08 00 03 00 6c 00 ......l.
0008: 00 00 00 00 1a 00 00 40 .......@
0010: 00 00 00 00 1a 00 00 40 .......@
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 00 00 00 00 00 00 00 00 ........



Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 2/21/2004
Time: 7:37:48 PM
User: N/A
Computer: CATASTROPHY
Description:
Application popup: : Machine Check:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 38 00 03 00 9c 00 ..8...œ.
0008: 00 00 00 00 1a 00 00 40 .......@
0010: 03 00 00 00 1a 00 00 40 .......@
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 01 00 00 00 01 00 00 00 ........
0030: 5c ef 9c 18 dc f8 c3 01 \ïœ.ÜøÃ.
0038: 00 00 00 00 00 00 00 00 ........
0040: 03 00 00 00 00 00 00 00 ........
0048: df df 00 00 00 00 00 fc ßß.....ü
0050: e5 b2 40 c5 0e 00 00 00 Ã¥²@Ã…....
0058: 00 00 00 00 00 00 00 00 ........


Martin

 

Hi Martin. Sorry about the delay but I spent Saturday with honey do's and Sunday fishing. Whew but I do feel better.

Sound like you had some hardware undergo significant emotional events.

UDNT service should be from problems with a UMAX scanner and may or may not indicate a problem with the device. Sometimes it just barks at you. I'd remove it from device manager and from the PC, boot and shutdown with it missing, then hook it up and reload with the latest drivers you can find.

The others are probably video issues if you run an ATI card of some sort. Otherwise I'm not sure what it would be. Again, remove the video card from device manager, reboot, and try with a complet new install of all the various drivers.

Probably an excellent idea to run the registry cleaner of your choice while you have the scanner removed and the software part of the video card removed.

 

Hey Newt, thanks for the response, and don't apologize for gone fishin.

Problem is, I do not have or have I ever had a UMAX scanner. Prior to the current HP 2200C scanner that is usb, I had an older HP scanner, the only two I ever had.

I do remember sometime in the hazy past getting some online info/advice to install some UMAX drivers, and I think I did.

The other problem is I did have a ATI card, but it has been removed and replaced.

I had run RegSeeker and deleted all references to ATI, and also deleted all ATI installed programs & drivers.

In the meantime this machine has developed some other and much more serious problems. Right now I'm online but can't get network connections in control panel to open. If I had not gotten an auto update notification from MSFT I would not have even known I was connected.

I'm going to try to deal with that problem first, some kind of file/registry corruption.

I'll try to get back to you on this though.

Thanks

Martin

 

Martin - the ATI errors all make sense then. Service trying to start and not finding the files it needs to run. Other than slowing things down at startup time, probably harmless but annoying. Check your Services and any that look ATIish should be set to disabled so they won't even try to start. Same with the UDNT one.

The 'application popup' items are listed as informational so maybe not an issue. Some searching turned up other folks getting the same pair of errors but since they were all listed because they were odd messages on systems having problems, hard to say much about them. One fella did get them stopped by
start~run~sfc /purgecache followed by (with the install CD in place) start~run~sfc /scannow
but another with pretty much the same event log message pair tried and they continued. Not much help I'm afraid.

 

Hey Newt: Thanks for sticking with me on this one. There is so many failures and so much stuff gone wrong, I don't expect to get bailed out, but I could use some sympathy and the knowledge that I'm not alone. Anyhow:

I disabled ATI services, cannot find any reference in services to UDNT, just errors in service control manager event viewer.

Still getting ATI errors.

I am really sorry I ever looked at the event viewer.

It turns out that those reported errors are the least of this machines problems.

I have major computer/program problems over the last two days, and have run sfc /scannow with CD twice. I have made no progress with any of it. I don't want to clear the cache as it may contain some of the updates I don't want to erase because I won't know they were erased, but who knows???

I have in the past used PC Pitstop, they can scan this machine from afar and tell just about everything except the color of my eyes. But the Great Computer Software Design People at MSFT can't tell what updates are on this machine?? What ****!!!

Have had several blue screen shutdowns, several NT authority.sys shutdowns, program failures and myriad other problems.

I have used all the worm removal tools supplied by MSFT and Norton, seem to have made a little progress with NT Authority, (no shutdowns since yesterday evening) but had my last blue screen late this afternoon when I tried to start Drive Image 7.

Even though I had the classic viral symptons, all virus scans, with latest updates, and worm removal tools from Symantec and MSFT report no infection.

In the meantime, getting program errors in Powerquest's Drive Image 7, (now owned by Symantec) who you either pay $30.00 or wait 4-5 days (they say, but who knows?) for email response for program support. My backups went down the tubes along with Drive Image. So much for backing up your system.

Event Viewer Application says:

Event Type: Information
Event Source: V2i Protector
Event Category: None
Event ID: 0
Date: 2/24/2004
Time: 4:19:54 PM
User: N/A
Computer: CATASTROPHY
Description:
The description for Event ID ( 0 ) in Source ( V2i Protector ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: An error occurred while starting V2i Protector service. The following component is not installed correctly: PowerQuest.Notify..

V2i Protector is an itregal part of Drive Image, although I don't know it's function, Drive Image will not run without it. Uninstall and reinstall of the program is no help, same error. I also don't know why the reference to the remote computer other than the program has the ability to back up to a network drive.

System Restore as usual is of no help, I think it was put on the system as a joke. No matter which restore point is used, message is it did not work. On this machine at least, it has always failed in a crisis. Reminds me of when I had GoBack Deluxe 3 on this system. After a crash it always reported no restore points due to massive hard drive activity. Such ****.

Of some concern to me now is this service error:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 2/24/2004
Time: 11:22:05 PM
User: N/A
Computer: CATASTROPHY
Description:
The IPv6 Internet Connection Firewall service terminated with service-specific error 2147952447 (0x8007273F).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Of course, as usual, the link is no help. What unmitigated gall to put a link in the error message as that one, and then when you get to the site it says so sorry, no more information, but follow this other link and we will tell you how to send us $35.00 and then maybe we will help you. If we can't, we will keep your $35.00 and tell you to start over again. If you do start over you probably won't have any problems until you install a program and actually use your machine. More ****.

Here is the one that really frosts me. IEEE 1394 Open Host Controller. For reasons I cannot fathom, MSFT loads firewire as a network connection. The drivers are written and published by MSFT. Contained on the XP Home CD. Device continues to fail, device cannot start, code 10. Reinstall drivers from XP Home CD, get message: Drivers not WHQL Certified. Install at your own risk. Install drivers anyhow, device works for a while then fails again. Same routine gets it working again. More ****. And, I did send $35.00 on this one to MSFT who in effect tell me it is my fault for having a firewire card in the machine. And they did keep my $35.00 More and more ****.

Now, to add insult to injury, I cannot backup my financials to CD. "Device not accessable ". More ****. It appears the UDF Packet writing program has also gone south. Uninstall and reinstall of Pinnacle's Instant Write CD/DVD UDF program returns Windows error message: "IWUINSTALL.exe has encountered an error and needs to close. We are sorry for......." Of course, then the install program continues and installs a program that will not work. More and more and more ****.

&*%$#*&^%@#$!

Network connections also failed, but after two hours I have it working again.

Standard advice for a machine in this condition is format and reinstall. But all that seems to do is extend the time between crashes. I am determined to ferret out and solve these problems.
If I can't, I'll get Pro and start clean. I will not do another install of Home. But I am not about to surrender.

In case anybody from MSFT reads this, this is to let you know that you have failed miserably in building customer loyalty. I paid $200. for your program and (before I found this board) have sent you over $500. for paid support at $35.00 a pop, and still have a system that does not work. If I ever get the chance to escape from your clutches, I'll be gone so fast you won't be able to see me leave.

Martin

 

Martin - don't sugar coat your feelings. Tell us what you really think.

Seriously, I don't blame you for being more than a little angry. What a mess.

At this point, we have heard hoof beats and looked all over the place for horses. None found so it's beginning to seem like you may be hearing a Zebra herd or possibly a Yak herd.

I've sorta lost track so some of the below may be things you've already done and told us about. If so, still can't hurt to do them again.

I would certainly turn off any feature that could be storing bad stuff and putting it back without warning. System restore, indexing, hibernation, suspend, and any other similar items. Leave them all disabled until you get things fixed and then turn back on any that you really want. Indexing is one I would never have active.

It could easily be a hardware problem of some sort. Heat maybe or a bad spot on a memory stick. I'd try running for a few days with the case removed and a floor fan blowing on the system. Maybe also swapping out a memory stick if you have two and either one is large enough to keep your system running. One of the hardware experts can probably point you to a utility that can do diagnostics on the mother board and other associated hardware components.

Your registry could be damaged. Not the most likely suspect since you say your problems have survived at least one clean reinstall of the OS. But it certainly can't hurt and especially with the phantom ATI and UMAX stuff. RegSeeker is reliable on XP. Nice too in that it will not only 'clean' but can search for specific items and allow removal.

I certainly like my XP-pro and think you'd be happy with it but at this point, I'd be reluctant to load another OS on a machine that is behaving so badly.

 

Hey Newt, appreciate the comeback. Never was much good at sugar coating. I am even more AARRRRGHED!! than I was when I wrote the last post.

Spent most of the day on the 'phone with MSFT support, as after two blue screens the system would not boot, not even in safe mode One positive note was I was able to get in under an old case number, so the non help was free this time.

To make a long story short, after 3 hours on the 'phone, the machine would still not boot.

I was finally able to get DI7 to boot from CD and restore the Windows Folder, even though when I tried to restore the 'c' drive, it told me the backup was corrupt???? The backup was on a DVD-R that DI7 told me was successful when it was made. More ****.

As an off topic, I cleaned the CD with toothpaste to get that far. Funny the coincidence with and inspiration from last night. You listening Johanna?

The MSFT tech spent all that time trying to get the machine to do a repair install, which it refused to do. I spent the afternoon typing in lines renaming and copying system files, all to no avail.
no matter what, on boot, the system said NTLDR missing.

After restoring the Windows folder I was able to get the machine to boot by changing the boot order in System BIOS, for some reason, the boot order has to be set to SCSI instead of HD 0 where it was set since install. Go Figure.

On top of that, DI7 still refuses to make new backups, so I'm waiting to hear from Symantec, only 4 days left to wait. They are certainly endearing themselves to me. If I remember correctly that program cost $70. Too bad it is no %$&^#good. My advice is do not shop Symantec. I got the virus/worm while an up to date to the minute copy of Norton AntiVirus was running on this system.

As a matter of fact, the way I feel now, if anybody asked me if they should buy a computer, I would tell them to forget it and get on with their normal life which I no longer have. I just got an error bing in the background while typing this, god knows what's wrong now.

So, now the plan is this: Hobble along with what I got until I scrap together enough money to buy Pro, do a format and clean install, and $%#$&*^ it better work.

I'm not even going to look in event viewer if I can help it.

Martin

 

Martin - I now think I have spotted an albino Yak running rapidly across the landscape.

Give a try at the hardware things if you can. Since no body jumped in with a link to a nifty and free diagnostic package, you might post a request for info in the hardware section. Some regulars there never look at XP or if they do, not at topics that sound software-ish.

 

Hey Newt: Nah, that was'nt an albino Yak, it was a Mastedon. Cloned by this machine during a blue screen, 'cause the beast had been frozen in the blue ice of my desktop.

I have only had 2 blue screens and one NT Authority shut down since my last post. And that is real progress. I got the &^*%$& thing to boot. Like I said, I am not surrendering!!!!

Both blue screens came after running checkdisk from management program. One of the blue screens had ATI in its error message.

Following your advice, I shut down system restore and indexing. I have run all of the Blaster and it's varients removal tools, scanned for virus with updated defs again, all report clean.

I fired up RegSeeker an deleted all ATI references after specific search. Seems like machine breathed a sigh of relief and has been perking along like a new clean install ever since.

And this is on a system restored by a faulty DI7 program! (which still refuses to run, except when booted from CD) Maybe one of these days Symantec will respond to my email, maybe.

At this point, I really think (delusional?) I am over the hump, but it is cautious optimisim.

What more can I say but Thanks for your support (sympathy?) A little bit of humor goes a long way.

Yak Yak Yak

Martin

 

Martin now, while everything is running like it is supposed to, and you are thinking of it, set a restore point.

If I were you, I would burn everything of value to cd, reformat and reinstall XP. Or, after yesterday, I might drive my truck over the whole thing, a few satisfying times.

I applaud your determination, perseverance and humor, despite the catastrophe! (Yes, pun intended! ) I am a bit concerned about your assumption that Microsoft or Symantec will provide useful tech support.... There are some good medicines available now for people who suffer from delusional thinking....

I am almost done with my "care free computer" post. I got the nails out of my arm yesterday- and it feels much much better. (The true test will be if I can move the trackball back on the right side, again!)

For a laugh, go here and click on the "Welcome to the Internet Help Desk ", turn up the sound, and sit back.

Now, excuse me, I have to go threaten a couple of children with bodily harm and other dire consequences. Children, darn it, do not come with power buttons, or even a mute switch. The only tech support available is my sister, if I can hear her over her three kids in the background. It is no wonder I find less frustration in computers- they can be rebooted, reformatted, or run over with the truck. Even duct tape is illegal with kids...sigh..

Johanna

 

Hi Arie: Thanks for the interest.

This board has two RAID connectors running on High Point RAID drivers in addition to the IDE connectors. When doing a repair install or system restore with DI 7, I have to load the High Point drivers using F6 + floppy install of High Point drivers or those programs cannot see drives on RAID connectors.

Boot drive, 0, is on RAID controller. I am not using a RAID array, using drives attached to RAID controller as IDE drives.

Up until now, BIOS boot order in MOBO has been Drive 0, (after floppy and CD) and RAID controller BIOS boot order Drive 0. Those settings have worked for this MOBO since installed.

Being unable to boot, in desperation, sort of "what else could go wrong?" experiment, set boot order in MOBO to SCSI. Much to my surprise, Windows booted.

Have been using those setting ever since.

Windows install program and DI 7 restore program sees the RAID 0 drive as the "D" drive, even though after booting it is in fact the "C" drive. There is a HDD attached to IDE controller as a Master on IDE Channel 1.

Although Windows install program recognizes the "D" drive as drive 0, channel 0, with a windows OS, it refuses to allow a repair, wants to wipe the drive. The MSFT tech spent about 3 hours on the phone with me trying to get Windows to do a repair install on this drive, he finally surrendered.

I have no idea what use this information would be to anybody, but since you asked.......

Martin