Question Is this normal to have this much of errors and warnings in the event viewer.

Maverick1234

Reputable
Feb 20, 2021
119
2
4,585
I noticed that there is a lot of warnings and errors in my event viewer and I wanted to know if there's something I need to do or something that I need to fix to remove these. I went to the event viewer because sometimes my Windows Search doesn't work, but it's not all the time. I'd say about 3/10 times. But I still want to fix my Windows Search.

So while at it I hope someone can tell me a way to fix my Windows Search as well when sometimes I doesn't work and is just stuck in loading.

Here's the image: https://gyazo.com/c326f775b50440dd1788ff31fca77168
 
Last edited:

Lutfij

Titan
Moderator
When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.

Since you're on Windows, open up Device Manager and see if you have any items flagged with a yellow exclamation mark.

You might want to try and repair your OS using this tutorial;
assuming you're on Windows 11.
 

Ralston18

Titan
Moderator
Update your post to include full system hardware specs and OS information.

Check Update History for any failed or problem updates.

= = = =

Could be some buggy or corrupted files. Windows may be able to find and fix those problems.

Try running "dism" and "sfc /scannow".

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

Also look in Reliability History/Monitor. Much more end user friendly and the timeline formation may reveal some pattern.
 

Maverick1234

Reputable
Feb 20, 2021
119
2
4,585
When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.

Since you're on Windows, open up Device Manager and see if you have any items flagged with a yellow exclamation mark.

You might want to try and repair your OS using this tutorial;
assuming you're on Windows 11.
CPU: AMD Ryzen 5 5500
CPU cooler: AMD Wraith Stealth
Motherboard: Gigabyte GA-A520M-DS3H AC
Ram: Colorful Battle-Ax x2 8gb (16) 3200Mhz DDR4
SSD/HDD: Kingston 2.5 240GB SSD (Windows Drive) | WDC 3.5 1TB HDD
GPU: GTX 1050 TI
PSU: Corsair CX550 550W 80+ Bronze (Only about 4 weeks old)
Chassis: DeepCool Matrexx 55 mesh
OS: Windows 11 Pro (Unactivated)
Monitor: Nvision 1080p 75hz 22"

Nothing is marked with yellow exclamation mark. It only has those green leaves which indicated eco mode.
 

Maverick1234

Reputable
Feb 20, 2021
119
2
4,585
Update your post to include full system hardware specs and OS information.

Check Update History for any failed or problem updates.

= = = =

Could be some buggy or corrupted files. Windows may be able to find and fix those problems.

Try running "dism" and "sfc /scannow".

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

Also look in Reliability History/Monitor. Much more end user friendly and the timeline formation may reveal some pattern.
Ok so I ran both of these. The sfc scannow says that it fixed corrupted files and the second one says nothing was found. Photo: https://gyazo.com/e8dea9b1c54122eb6cfbd02366dee3d5

Now, I went to the reliability monitor and I saw 2 failed windows updates. But I'll send a photo here as well so you can check out the rest. Photo: https://gyazo.com/7e9fdb11ca54cde8087ccb2b4ba7b4bf
 

Ralston18

Titan
Moderator
Send photos for 13/07 and 14/07.

Adjust the Source column width so the full contents can be read.

Objective being to look at the critical errors (red circles) that occured.

And include a view of the technical details. (May or may not be helpful.)

Remember to check Update History as well.

[Note: 16/07 Warning appears to be "YourPhone" related - I am seeing the same failed update.]
 

Maverick1234

Reputable
Feb 20, 2021
119
2
4,585
Ok
Send photos for 13/07 and 14/07.

Adjust the Source column width so the full contents can be read.

Objective being to look at the critical errors (red circles) that occured.

And include a view of the technical details. (May or may not be helpful.)

Remember to check Update History as well.

[Note: 16/07 Warning appears to be "YourPhone" related - I am seeing the same failed update.]
Ok so here is 13/07: https://gyazo.com/f4e0e139acda1a4da45e351350435ec6 https://gyazo.com/a07514a3a18366c391e6447364cfcf06 https://gyazo.com/6c94b351b5aa848be1d6868ad766a8b5

And here is 14/07: https://gyazo.com/c0b65b431435bc5cb32adb794d96fa55 https://gyazo.com/864559138630fbb86ea2ca834f67cd91 https://gyazo.com/b038ac18a687b84fa1dae4b360e47cce
It does seem like Windows Search does not work sometimes, judging from the 14/07.

I also checked the update history and there is nothing out of the ordinary. Here's a ss: https://gyazo.com/e5ae8420cf1ba32a08c50d3271d2b456 https://gyazo.com/e049bad798f3a3bf6e270ec2f8596cfd https://gyazo.com/6a5100812359489274b719c50e0e277b https://gyazo.com/251c1af3557064dce25829b3b362a46b
 

Ralston18

Titan
Moderator
Improper shutdowns: Unless you were forced to power down one possibility is a loose connector.

4 week old PSU.

When the PSU was installed were only the cables that came with that PSU used?

Power down, unplug, open the case.

Clean out dust and debris.

Verify by sight and feel that all connectors, cards, RAM, jumpers, and case connections are fully and firmly in place. What might have seemed connected or in place may not have actually been so.

My other thought is that that 550 watt Corsair is not able to keep up with high power requirements and/or spikes.

Keep an eye on the errors and error patterns (if any).

If there are additional problems run "sfc /scannow" and "dism" again to fix new problems resulting from improper shutdowns.