Thousands of Event ID 7000 ???

[cognus]

wondering if any of you can clue me where to start looking for a cause of a LOT of repetitive errors, seemingly coming at the tick of the clock - in other words the system is generating the same error dozens of times per second. All of the errors I've looked at so far, with just a few exceptions [about as many as on a "healthy" windows 8 system] seem to be Event ID 7000. These errors go back to mid-February and have continued until now. The system would run, but slow. Checking install log, back in February, Silverlight plus C++ runtime were installed. nothing else. I don't know if that is related to the errors, but it is what it is.

Secondly: from what I have read here and many other places around the web the Windows 8.1 'refresh' function is not advisable. what I see is that it provides no assurance of a clean install, can damage apps and files, and the user applications, customizations, personalizations will need to be reinstalled. to me, that sounds like a leading indicator for doing a clean install period, from scratch. correct?

thank you
c

 

[cognus]

p.s. the system is a lenovo Z510, win 8.1 pro, x64. malware free.

 

[Clintlgm]

https://technet.microsoft.com/en-us/library/cc756344(v=ws.10).aspx

 

[cognus]

Just in case someone searches this topic and lands here:
- going back to the date range from which the errors began, we find only a few things new/installed, all of which came through windows updates
- in this case, something updating in Office 2010 called for Silverlight plus several C++ related packages. These did not install correctly, as it turns out, and can neither be repaired nor uninstalled
- Windows had file system damage that I repaired via chkdsk
- Windows has file troubles turned up by scannow , some of which it could not correct [see cbs.log]
- There was evidence that when "shut down" is invoked, Windows 8 frequently landed in a zombie state [I have no idea what to call it] that shows up as a "low power state" in the error logs when it should have been shutdown completely. Suspicion that it is hung during shutdown by a poorly managed connection to a peripheral [this one has several - a scanner, printer, card reader]. "Shut down" did not mean "shut down".

The errors ceased after the file system repairs. the problems with botched silverlight remain but it is non-lethal at the present. future will install windows 10.

 

[Clintlgm]

Just in case someone searches this topic and lands here:
- going back to the date range from which the errors began, we find only a few things new/installed, all of which came through windows updates
- in this case, something updating in Office 2010 called for Silverlight plus several C++ related packages. These did not install correctly, as it turns out, and can neither be repaired nor uninstalled
- Windows had file system damage that I repaired via chkdsk
- Windows has file troubles turned up by scannow , some of which it could not correct [see cbs.log]
- There was evidence that when "shut down" is invoked, Windows 8 frequently landed in a zombie state [I have no idea what to call it] that shows up as a "low power state" in the error logs when it should have been shutdown completely. Suspicion that it is hung during shutdown by a poorly managed connection to a peripheral [this one has several - a scanner, printer, card reader]. "Shut down" did not mean "shut down".

The errors ceased after the file system repairs. the problems with botched silverlight remain but it is non-lethal at the present. future will install windows 10.

Yep looks like a clean install is in order. You are aware that shut down in windows 8 goes into hybrid shut down. Similar to Hibernate this is default. I have been using Classic Shell for so long now I don't remember how to get a complete shut down in windows 8