Windows 10: Attached file "Administrative Events" shows many problems

My Windows 10 was installed on top of Windows 7 and, since then, I have been trying to correct the many little glitches I've run across. Not always successful. This view of my AdmiAttachment 119945nistrative Events is typical and not normal - but I don't know where to go from here.

:)

 

" SOFTWARE UPDATE FAILED "

SO HERE'S THE LINK TO THAT PIC

http://i26.tinypic.com/2ihbdco.jpg

CAN U PLZ CHECK IT ACTUALLY I HAVE USED THE NOKIA SOFTWARE UPDATER B4 ... BUT I DONT KNW WHY I M GETTING THIS ERROR NOW

 

" SOFTWARE UPDATE FAILED "

i have installed windows xp sp2

previously i was using windows media center i thought i might b facing this probs due to that but then i changed it to windows xp ! n moreover i have also shown to nokia service center executives but they were not having the latest updates available ......
my pc suite is showing that new update version of firmware is available but i cudnt download it

oh gawd wat to do ?

i tried in another pc then again i got an error u need to have minimum 256 ram

please cant it b rectified ? there must b any solution to this probs please help me guyz

god bless all of u thanx

 

Hi,
1. Event ID 153- might indicate a failing disk.

Start by downloading and running Crystal Diskinfo (free) - gives a quick report + SMART params.

Recommend you organise the report by clicking on the tabs to find the most frequently occurring Error Event id's and look them up.

2. Event id 3104
Event 3104 Errors Since Anniversary Upgrade

3. Tools
You may find this free tool helpful




or this (Event log explorer)

 

These results look to me - do you agree? My hard drive is an SSD (don't know if that matters). I downloaded the two tools you recommended - but I have never tried to solve event problems. Perhaps you could tell me what to do with the tools I now have?

I sorted these by Error ID

 

FYI: I looked up Error 1000 in Google - but not sure what to do.

 

Ok, disk is good.. now run two basic routine checks before worrying about event ids, as problems with these could give rise to all sorts of issues:

1. File system
From an admin command prompt
[Windows key + X, click command prompt (admin)]
chkdsk C: /F
Your PC will need to restart.
Make sure the result is clear or fixed- else do not proceed.
Post back the result, which you can get after a restart as follows:
How do I see the results of a CHKDSK that ran on boot? - Ask Leo!

2. System files integrity check
Again from an admin command prompt run
sfc /scannow
and report the result that appears on the screen. (This takes a few minutes).

Explorer could be crashing because of an installed program... do the above before anything else.

By the way, do you have a full backup of your data?

 

I ran both chkdsk and sfc - no problems - and, yes, I have a full backup of my data. I use images to back up everything daily. Where to now?

 

Excellent so far... tomorrow now..

 

Hi, first- expectations. It's most likely not going to be possible to resolve all major errors reported where there is no apparent failure at the user level. These reports are poorly supported - clicking on the link here now gives nothing useful:



(Thanks MS!)

Resolving any one will most likely take time, experimentation and research and may not lead to success.
That you have upgraded from Win 7 could lead to inherited issues, whether from the OS or older installed programs you've retained.

Could you post a view like this which gives a good summary:




Mine's a clean Win 10 install on a 1 year-old laptop. If I expand the Error set, I can immediately see most are listed as 1 Event ID.



Expanding those shows not all originate in exactly the same way.

But at a practical level, I'm not aware of these. Quickly searching for information on this doesn't appear to offer any obvious resolution. SFC /SCANNOW ran successfully and fixed minor problems.

So much for an example, and that may well be nothing new.

===============================================
So, are you aware of anything that fails at a user level, if so what? Or does everything appear to work, and you're simply concerned about the number of reports?

Now, turning to Event ID 1000.
First try to identify the most common cause. For this you need to look through the detail of a lot of the event id 1000 reports.
Here this is associated with a WPS Office program:




A broader approach.
You'll note that events can be listed for the last hour.
Take a screenshot of what you have now in normal mode.
Now boot to Safe Mode, leave that for an hour, and see what is recorded.
Take a screenshot, and pick out any significant repeated failures.

Repeat after a clean boot.

What we want to know is whether installed programs are significantly contributing to error reports.

Once you have something to focus on, you can create a custom view- a bit tricky, but it creates a special view added to the list on the left:

 

Good morning - from Texas. You've obviously put a lot of work into your morning post (yeah Patriots!!!). I'd like to learn how to analyze these errors - never gotten in to it before. Not feeling well right now - but I'll re-read your post a little later and see what I can do. I hope you stay with me as I (slowly) do what you tell me too. Yes, thanks MS. Thank you very much for the help!

 

An example where a solution is feasible:
I was looking at my event ids 100016. These are well-known, and a solution is listed here and there, however in some instances it is not given accurately. I have several occurring each day, perhaps after each time I log on, for example.

Here is just one place where @lx07 has provided a script to help with part of the solution - changing permissions in the registry, so that a change can be made elsewhere:
Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

You will get some idea how complex and time consuming this can be.

In this instance it appears this is a Windows issue- not a 3rd party program.

 

Hello again! Because of the apparent complexity of the solution(s), I've decided to go ahead with a clean install. Thanks for trying to help - but I just don't have the expertise or time to track down these errors.

 

Yep, good idea. Bear in mind you shouldn't expect a completely clean event log. You might consider a refresh or reset.