Windows 10: 3 Day old Win 10 Install 400+ Errors in Event Viewer

Title about sums it up. Fresh windows 10 Professional 64bit install. I installed the GPU Tweak II software for my GTX 980 ti which required a system restart to complete. While restarting, an error message popped up (one of the 0x08xxxxxxxx type of errors) but then dissappeared almost immediately as the system completed restarting so I didn't get to read it. I opened Windows Event Viewer to see if I could find the error and observed having 420 errors in the last 3 days. There's obviously too much to paste and include here so was looking for advice on where/how to get help. Honestly this is the first time I've opened the event viewer in any version of windows so idk how to read the errors and all of my attempts to google them have gotten me either outdated info or none at all *Confused if there's a known forum for Error log help or if anyone here could help, just let me know how to go about sharing the event logs or what info specifically from the errors you would need. The only response I've gotten elsewhere on the issue was that I could probably ignore the errors, however I have been experiencing occasional 5-15 second hangs in Windows 10 even when not doing much (for example, when opening a settings window or even clicking the start menu button) so am concerned some of the errors could be related to system instability. Thanks in advance if anyone can help!

:)

 

Cannot update Windows 10

I had a heck of a time upgrading to Win 10 from Win 8.1 but finally after several days got it to install.

Since then I have tried several times to upgrade to the current version. I am using an HP P7-1451 desktop with 16G of RAM. I kept getting this error message "failed in SAFE_OS phase during APPLY_IMAGE operation." The HD was almost 3 years old and had some
900 bad sectors. I ran defragger and got it down to 400 bad sectors. Still would not upgrade. Cloned the old HD with Macrium Reflect (disregarding bad sectors) and installed the new HD. No bad sectors on it. Defragged it down to 25 fragmented files and tried
to upgrade. Same error message.

Any ideas on what's causing this?

Thanks

 

Eventid 134 time service

If you have no other symptoms other than what you are seeing by manually looking in the event viewer I would say that you actually don't have a real problem at all and what you are seeing there are just normal for the beast. It is very common to see random
errors or warnings in the event viewer on all devices. Are you getting any pop-up error notifications on the desktop as well? If not then don't stress-out on what you are seeing when looking in the Event Viewer.

For example, the below snapshot is of the event viewer summery of a 3 day old upgrade type installation of Windows 10 v.1709 (the Fall Creators Update) (upgraded to from v.1703) that performs and functions very quite well (it's also quite fast, perhaps even
faster than v.1703).





Again, for what it's worth,

-Richard

 

There are 4 categories

Critical
Error
Warning
Information

Are all yours in the category 'Error' ??

 

Thanks for the reply. I have 1 critical, 425 error, 1,539 warning, & 4,308 information. The one critical was for an improper shutdown 3 days ago, so I don't think that one needs to be worried about, though I can't recall any improper shutdown occuring.

 

I assume the above numbers are for the 7 day period. They are a bit high but nothing to really worry about. I only watch the 'critical'. If there are a lot of those, then you need to investigate.

 

They are for the 7 day period (which is a 3day period since its only been that long since install). The ones I seem to be getting the most from the error category (numerous times per hour) are:

Log Name: Microsoft-Windows-DeviceSetupManager/Admin
Source: Microsoft-Windows-DeviceSetupManager
Date: 3/5/2016 7:21:25 PM
Event ID: 131
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Description:
Metadata staging failed, result={EBF5A0A0-1DD1-11B2-A90F-20AA4B937D52} for container '0x80070490'

-------------------------------------------------------------------------------------------------------------------------

Log Name: Application
Source: Microsoft-Windows-CAPI2
Date: 3/5/2016 7:21:10 PM
Event ID: 513
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Description:
Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.

Details:
AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol.

System Error:
Access is denied.

----------------------------------------------------------------------------------------------------------------

Log Name: Microsoft-Windows-DeviceSetupManager/Admin
Source: Microsoft-Windows-DeviceSetupManager
Date: 3/5/2016 7:21:25 PM
Event ID: 131
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Description:
Metadata staging failed, result={00000000-0000-0000-FFFF-FFFFFFFFFFFF} for container '0x80072EFE'

---------------------------------------------------------------------------------------------------------------

Log Name: System
Source: storahci
Date: 3/5/2016 5:31:46 PM
Event ID: 129
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Description:
Reset to device, \Device\RaidPort0, was issued.

Those seem to be the main repeat offenders

 

If you are only getting it because of that tweaking software, then remove it. Something with it that Windows 10 does not like, if it is the root of the problem.

 

Hey, thanks for the response. Unfortunately the Tweaking software is not the issue, the errors have been spamming since installing the OS on 3/2, I didn't install that software until 3/5. I also didn't see anywhere that any of the errors or warnings pointed towards that software whereas others mentioned the program ect at fault.

 

Drivers like the Intel RAID is known to cause problems, same as the NVidia drivers.

Always work backwards to what was installed after, to what was installed when this problem started popping up.

If you are pulling the info from the Dump Log, WhoCrashed is easy to help diagnose.