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

[Maverick1234]

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

 

[Lutfij]

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;

How to repair Windows 11

The operating system is the most important software on your PC, so it's important to fix any OS-related errors as soon as you detect them.

www.xda-developers.com

assuming you're on Windows 11.

 

[Ralston18]

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]

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;

How to repair Windows 11

The operating system is the most important software on your PC, so it's important to fix any OS-related errors as soon as you detect them.

www.xda-developers.com

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]

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]

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]

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]

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.

 

[Maverick1234]

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.

I think Ik the reason why lmao. I was force shutting down my pc when I was trouble shooting it and when one time I was playing valorant when my system froze.

Andp it could also be when I was using my pc during a thunderstorm. My pc was sending a notif sound but there's no notif banner that tells what it is.

 

[Ralston18]

Forced shutdowns, power problems, etc. can all cause file corruption problems.

Take a look in the Notifications Center via "WIN" + "N" > Notifications settings > Get notifications from apps and other senders.

There are two settings: one for notification sound, one for notification display.

= = = =

Explore first, read carefully.

Make only one change at a time and keep notes regarding what was changed, the original setting, the new setting, and where the change was made.

 

[Maverick1234]

Forced shutdowns, power problems, etc. can all cause file corruption problems.

Take a look in the Notifications Center via "WIN" + "N" > Notifications settings > Get notifications from apps and other senders.

There are two settings: one for notification sound, one for notification display.

= = = =

Explore first, read carefully.

Make only one change at a time and keep notes regarding what was changed, the original setting, the new setting, and where the change was made.

Ok I checked notification settings and there is nothing out of ordinary.

Now, my main concern. Why does my windows search sometimes doesn't work? Why does it do that?

 

[Maverick1234]

O

Forced shutdowns, power problems, etc. can all cause file corruption problems.

Take a look in the Notifications Center via "WIN" + "N" > Notifications settings > Get notifications from apps and other senders.

There are two settings: one for notification sound, one for notification display.

= = = =

Explore first, read carefully.

Make only one change at a time and keep notes regarding what was changed, the original setting, the new setting, and where the change was made.

Oh and also, I checked reliability monitor and it says last night windows was not shut down properly.

Which is very odd because when I did shut it down last night, it did shut down. My pc turned off and my monitor turned off as well. Nothing out of the ordinary.

After that, I turned off my avr. Here's photo: https://gyazo.com/f74032d90f3af033479ad6d9c8fe82df

 

[Ralston18]

Appears to be improving.

Take a look at what happened on the 16th. Error, Warning, and Information.

Both in Reliability History and Event Viewer.

And it may prove easier if you clear all of the Event Viewer logs and only need to work through a couple of days worth of recent and curdrent entries.

 

[Maverick1234]

Here's the screenshot for the 16th: https://gyazo.com/af5a5a4944e9340cde4e2fae06955ffc https://gyazo.com/42425dda1ef03cbbc974d56bf4b51d04 https://gyazo.com/81684f39ee2cd7e44064848a6049d2de https://gyazo.com/1f7a2cd914d451e1cc101be18b3786a3

I think the "Stopped Working" is the result of my exiting the app from the hidden icons. I was trying to free up some memory as much as possible.

And ok, I'll clear event viewer logs.

 

[Maverick1234]

Appears to be improving.

Take a look at what happened on the 16th. Error, Warning, and Information.

Both in Reliability History and Event Viewer.

And it may prove easier if you clear all of the Event Viewer logs and only need to work through a couple of days worth of recent and curdrent entries.

Actually which ones do I clear? I cleared the application but I'm not sure if I should clear the security. https://gyazo.com/aa7df10abcdc8ce0cffc389331e408ee

 

[Maverick1234]

Appears to be improving.

Take a look at what happened on the 16th. Error, Warning, and Information.

Both in Reliability History and Event Viewer.

And it may prove easier if you clear all of the Event Viewer logs and only need to work through a couple of days worth of recent and curdrent entries.

Not sure if this is important, but could be that the reason why my windows doesn't shut down properly according to reliability history is because, even if my pc is off, the rgb lights of my headset is still on?

I'm sorry if this is statement is so dumb lol.

 

[Ralston18]

Not a dumb statement at all.

The headset rgb lights being on is certainly something I would question.

Make and model headset? How is the headset connected - what port?

Do you have a User Guide/Manual for the headset?

Is it a headset (earphones and microphone) or just headphones (ears only - no microphone)?

Any adapters/converters, extension cables being used?

What software (if any) is being used to control the rgb lights: colors, patterns, etc.?

If there is no identifiable reason for the rgb lights being on then the reason could be some misconnection by error of omission or commission.

And power is thus getting somewhere it should not be or maybe not getting where it should be.

 

[Ralston18]

I would not be that concerned about clearing the security logs.

Maybe just clear all but the last 30 days if you wish to retain some event histories.