Question BSOD Issues... Commonly IRQL No Less Or Equal ntoskrnl....

[Bluescreener97]

Hey everyone... Not a big tech person and I'm at the point of frustration where i have no idea what's causing these BSOD I've tried numerous things on the web to solve the issues even did a complete reset with a new windows... but they keep happening i would really appreciate some help if possible to try and solve this issue. I will randomly blue screen or my pc will restart sometimes when I'm gaming.

I posted below what it's told me.... but ill also post the file here... https://www.mediafire.com/file/4x91ggf5w9hq8pn/091024-16234-01_-_Copy.zip/file

Would greatly appreciate any help as I'm stressed to the max here - i don't understand why this is happening like i even have BRAND new ram sticks in there fresh out of the box so it's not a Ram issue.
Will be logged in to check for replies...

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000020, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80479e78d01, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1890

Key : Analysis.Elapsed.mSec
Value: 5469

Key : Analysis.IO.Other.Mb
Value: 8

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 20

Key : Analysis.Init.CPU.mSec
Value: 265

Key : Analysis.Init.Elapsed.mSec
Value: 23423

Key : Analysis.Memory.CommitPeak.Mb
Value: 98

Key : Bugcheck.Code.LegacyAPI
Value: 0xa

Key : Bugcheck.Code.TargetModel
Value: 0xa

Key : Failure.Bucket
Value: AV_nt!MiInsertPageInFreeOrZeroedList

Key : Failure.Hash
Value: {779c7427-9286-2607-95ab-7b33d42c5f3a}

Key : Hypervisor.Enlightenments.ValueHex
Value: 1497cf94

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 1

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 4853999

Key : Hypervisor.Flags.ValueHex
Value: 4a10ef

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 3f7

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Version
Value: 10.0.22621.1


BUGCHECK_CODE: a

BUGCHECK_P1: 20

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff80479e78d01

FILE_IN_CAB: 091024-16234-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


FAULTING_THREAD: ffffcb84768d4040

WRITE_ADDRESS: fffff8047a91c470: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000000020

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: fffff008e1a07550 -- (.trap 0xfffff008e1a07550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8047a86b9c0 rbx=0000000000000000 rcx=0000003fffffffff
rdx=00000000001d8c0a rsi=0000000000000000 rdi=0000000000000000
rip=fffff80479e78d01 rsp=fffff008e1a076e0 rbp=ffffcb847668d970
r8=aaaaaaaaaaaaaaab r9=00000000004cd20a r10=ffff91000e6761e0
r11=ffffff0000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiInsertPageInFreeOrZeroedList+0x1021:
fffff804`79e78d01 44896f20 mov dword ptr [rdi+20h],r13d ds:00000000`00000020=????????
Resetting default scope

STACK_TEXT:
fffff008`e1a07408 fffff804`7a02bf29 : 00000000`0000000a 00000000`00000020 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff008`e1a07410 fffff804`7a027389 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff008`e1a07550 fffff804`79e78d01 : aaaaaaaa`aaaaaaab ffff9100`1854f1f0 ffffcb84`7668d970 fffff804`7a86afc0 : nt!KiPageFault+0x489
fffff008`e1a076e0 fffff804`79e75525 : 00000000`0081c50a 00000000`00001000 00000000`00000000 ffffc534`00000001 : nt!MiInsertPageInFreeOrZeroedList+0x1021
fffff008`e1a07830 fffff804`79e7487e : ffffffff`ffffffff 00000000`00000001 ffffffff`ffffffff fffff804`7a86afc0 : nt!MiZeroPage+0x4c5
fffff008`e1a07a50 fffff804`79f8fc0f : ffffcb84`766ea050 ffffcb84`00000003 00000000`00000000 00000000`00000000 : nt!MiZeroLocalPages+0xcce
fffff008`e1a07b60 fffff804`79f54d47 : ffffcb84`768d4040 00000000`00000080 fffff804`79f8faa0 00000000`00000000 : nt!MiZeroNodePages+0x16f
fffff008`e1a07bb0 fffff804`7a01b114 : ffff8080`69c51180 ffffcb84`768d4040 fffff804`79f54cf0 00000000`00000000 : nt!PspSystemThreadStartup+0x57
fffff008`e1a07c00 00000000`00000000 : fffff008`e1a08000 fffff008`e1a01000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: nt!MiInsertPageInFreeOrZeroedList+1021

MODULE_NAME: nt

IMAGE_VERSION: 10.0.22621.4111

STACK_COMMAND: .process /r /p 0xffffcb847673e040; .thread 0xffffcb84768d4040 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 1021

FAILURE_BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {779c7427-9286-2607-95ab-7b33d42c5f3a}

Followup: MachineOwner

 

[Ralston18]

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

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how full?

= = = =

New RAM does not eliminate there being a memory problem. Unsupported RAM, mismatched RAM, and misconfigured RAM all cause problems. Some motherboards require that the first physically installed RAM be placed in a specific RAM slot. (Commonly DIMMA2.)

If the system boots immediately look in Reliability History/Monitor. Reliability History/Monitor may be capturing some error codes, warnings, or even informational events just before or at the time of the BSOD's.

There are other similar tools but Reliability History/Monitor is end user friendly and presents a timeline format that can reveal patterns.

Any given entry can be clicked for more detailed information about what happened. The details may or may not be helpful.

 

[Bluescreener97]

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

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how full?

= = = =

New RAM does not eliminate there being a memory problem. Unsupported RAM, mismatched RAM, and misconfigured RAM all cause problems. Some motherboards require that the first physically installed RAM be placed in a specific RAM slot. (Commonly DIMMA2.)

If the system boots immediately look in Reliability History/Monitor. Reliability History/Monitor may be capturing some error codes, warnings, or even informational events just before or at the time of the BSOD's.

There are other similar tools but Reliability History/Monitor is end user friendly and presents a timeline format that can reveal patterns.

Any given entry can be clicked for more detailed information about what happened. The details may or may not be helpful.

This pc was prebuilt and i purchased it and was all brand new parts i have a SSD not a HDD
OS: Windows 11 pro
PSU: Rosewill 650W
Motherboard: B450 Gaming Plus Max
CPU: AMD Ryzen 5 5500
GPU: NVIDIA GeForce RTX 3060 TI
RAM: Corsair Vengeance RBG Pro 32GB

My Local disk says 299GB free out of 476gb

 

[Bluescreener97]

samsung mzvlb512hajq-000l7 is my Disk

 

[Ralston18]

Look for error codes etc. in Reliability History/Monitor.

Also use Event Viewer.

Use both tools but not at the same time.

Event Viewer is not as end user friendly. Requires more time and effort to navigate and understand.

To help:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

Remember that you can open the tool windows and take screenshots of what is being shown.

Simply expand the window so all can be seen and click whatever error or other entry (or entries) that catch your attention.

Take a screenshot and post the screenshot here via imgur (www.imgur.com).

Especially if you find red circles and yellow triangles in Reliability History/Monitor.

 

[Bluescreener97]

yea that's a bit of an issue as there's many lol... also the link you provided doesn't work i just had a quick look.

https://imgur.com/a/pKYi8pE

View: https://imgur.com/a/pKYi8pE


Here's the link... i mean im not sure which is best to show? but i see a few of those kernel related thing like kernel power etc do i have to fix wattage or something on my system? or im confused what's going on... i posted a few random time bits through out the day

 

[Bluescreener97]

Look for error codes etc. in Reliability History/Monitor.

Also use Event Viewer.

Use both tools but not at the same time.

Event Viewer is not as end user friendly. Requires more time and effort to navigate and understand.

To help:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

Remember that you can open the tool windows and take screenshots of what is being shown.

Simply expand the window so all can be seen and click whatever error or other entry (or entries) that catch your attention.

Take a screenshot and post the screenshot here via imgur (www.imgur.com).

Especially if you find red circles and yellow triangles in Reliability History/Monitor.

Not sure if the pics i sent just now will help but if you need specifics let me know..

 

[Bluescreener97]

https://imgur.com/a/pKYi8pE

View: https://imgur.com/a/pKYi8pE


Added another image but with the Reliability monitor

 

[ubuysa]

It's unwise to make a diagnosis based on only one dump, but that one looks to point at a possible RAM issue. What speed are you clocking your RAM at? Is that RAM on the QVL for the CPU and motherboard?

 

[Ralston18]

The many errors etc. listed began on August 25th per the Reliability Monitor timeline. Select that date and take a closer look at what all happened. Then work through the following days noting both the number of errors and the details of those errors. Determine if there is some constant error throughout.

Are you aware of any software installs, updates, or other changes at that time? Hardware perhaps?

In any case, my thought is that some file was buggy or corrupted. Note that critical errors occur mainly in Application failures. Forced shutdows may have made matters worse. And thus problems in other failure categories.

Run "dism" and "sfc /scannow" - Windows may be able to find and fix its' corrupted files.

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

The objective simply being to eliminate corrupted files as a culprit.

= = = =

The PSU could be a suspect as well

How old is that Roswell PSU? Increasing numbers of errors and varying errors is a sign of a faltering and failing PSU. May be at or near its' designed in EOL (End of Life).

Do you have access to another known working PSU to swap in for testing purposes? Remember to use only the cables that come with the test PSU.

= = = =

Note: If possible, ensure that all importand data is backed up at least 2 x to locations away from the computer in question. Verify that the backups are recoverable and readable.

 

[Bluescreener97]

It's unwise to make a diagnosis based on only one dump, but that one looks to point at a possible RAM issue. What speed are you clocking your RAM at? Is that RAM on the QVL for the CPU and motherboard?

task manager says my ram speed is 2133 MHz is that bad or good?.. im also not sure what QVL means like i have my ram in both the red slots and not the black slots on my motherboard it would have to be on QVL (i just checked what QVL means) cause this is prebuilt they should know what they are doing

 

[Bluescreener97]

The many errors etc. listed began on August 25th per the Reliability Monitor timeline. Select that date and take a closer look at what all happened. Then work through the following days noting both the number of errors and the details of those errors. Determine if there is some constant error throughout.

Are you aware of any software installs, updates, or other changes at that time? Hardware perhaps?

In any case, my thought is that some file was buggy or corrupted. Note that critical errors occur mainly in Application failures. Forced shutdows may have made matters worse. And thus problems in other failure categories.

Run "dism" and "sfc /scannow" - Windows may be able to find and fix its' corrupted files.

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

The objective simply being to eliminate corrupted files as a culprit.

= = = =

The PSU could be a suspect as well

How old is that Roswell PSU? Increasing numbers of errors and varying errors is a sign of a faltering and failing PSU. May be at or near its' designed in EOL (End of Life).

Do you have access to another known working PSU to swap in for testing purposes? Remember to use only the cables that come with the test PSU.

= = = =

Note: If possible, ensure that all importand data is backed up at least 2 x to locations away from the computer in question. Verify that the backups are recoverable and readable.

just a lot of "Riotclientservices.exe stopped working" as well as "ALPBCSVC.exe stopped working" and "windows failed to start cause of missing system files happened on the 10th?" I've done all the DISM commands and SFC command so many times like it hasn't done anything to help my pc.... i don't have access to another PSU as that's just $ is it 100% my PSU ? cause i don't wanna buy a psu then come to figure out im blue screening again... the only blue screens i seen so far is the IRQL no less or equal ntoskrnl so far so is a PSU causing that? i also don't know how old that PSU is as this was a Pre-built i bought off a guy who owns a shop im also not sure what PSU is even compatible

 

[Bluescreener97]

https://imgur.com/a/RV1MgzT

View: https://imgur.com/a/RV1MgzT


Could this mean anything? im looking through my AIDA64 and im not sure if that means my PSU but it's not showing any details on it?

 

[Ralston18]

Disable or, if necessary, uninstall those non-Windows apps, etc. that stop working.

For example: "Riotclientservices.exe" and "ALPBCSVC.exe".

There may be other reasons for them to stop working but just getting them out of the way will simplify matters.

 

[Bluescreener97]

...? i dont know what ALPBCSVC is but Riotclient is a game I've been playing since 2014 im not sure how that would be an issue

 

[Bluescreener97]

Disable or, if necessary, uninstall those non-Windows apps, etc. that stop working.

For example: "Riotclientservices.exe" and "ALPBCSVC.exe".

There may be other reasons for them to stop working but just getting them out of the way will simplify matters.

Do you think it's a PSU issue? cause if it is id need to go out and buy it today as i have not much time this week. I'm not sure what PSU would even fit as i have a mini tower and well I'm not even sure how to even get TOO the psu lol... its in a weird caged area in the case. Maybe i could have something underclocked or overclocked in my system? im not sure

 

[Bluescreener97]

https://imgur.com/a/irQDjlR

View: https://imgur.com/a/irQDjlR


im also getting a lot of 131 it seems but I'm not sure what that is.. so far i haven't gotten a blue screen in like atleast 10+ hours like sometimes ill go a bit without blue screening which i dont understand but when i do bluescreen its a loop for a bit

 

[Ralston18]

Interesting.

I found this rather lengthy link:

DeviceSetupManager, 131

What is posted in the link is a good match to the problems you describe.

At the end of the link is an Answer wth this:

Here are two things you can try:

1. Disable metadata staging:

• Windows Settings > System > About > Advanced System Settings > Select the Hardware tab > Click the Device Installation Settings button.
• In the pop-up box that appears, you can change it from Yes (recommended) to No (device may not function as expected).

There is a second solution presented. However, that solution requires a registry edit which should be a very last resort only after a full system backup including the registry itself.

At best just check the current Windows Settings and post what is found in the Hardware tab.

Mine is set to "Yes". Just look for now. Do not change.

Scan through the replies and read what others have posted.

= = = =

Games can get corrupted. As can any app, utility, service, process, etc..

And there can be domino effects from a failure that, in turn, results in other errors and problems.

I would disable Riotclient just as a matter of elimination.

As for ALPBCSVC.exe I found the following link:

https://windowsbulletin.com/files/exe/d-link-corporation/alpbcsvc-module/alpbcsvc-exe

Read only. Do not download any offered files. Simply check where ALPBCSV.exe is located. Post accordingly.

Although the PSU may be a concern I am not sure that the PSU is the root of it all.

Especially where the errors seem to be fairly constant.

= = = =

Since the system has not blue screened for awhile I have three suggestions:

1) Clear all of the Event Viewer logs. Clearing the logs will make it easier to note additional and/or new errors that occur.

2) Continue to watch.

3) Post as necessary.

 

[Bluescreener97]

Interesting.

I found this rather lengthy link:

DeviceSetupManager, 131

What is posted in the link is a good match to the problems you describe.

At the end of the link is an Answer wth this:

Here are two things you can try:

1. Disable metadata staging:

• Windows Settings > System > About > Advanced System Settings > Select the Hardware tab > Click the Device Installation Settings button.
• In the pop-up box that appears, you can change it from Yes (recommended) to No (device may not function as expected).

There is a second solution presented. However, that solution requires a registry edit which should be a very last resort only after a full system backup including the registry itself.

At best just check the current Windows Settings and post what is found in the Hardware tab.

Mine is set to "Yes". Just look for now. Do not change.

Scan through the replies and read what others have posted.

= = = =

Games can get corrupted. As can any app, utility, service, process, etc..

And there can be domino effects from a failure that, in turn, results in other errors and problems.

I would disable Riotclient just as a matter of elimination.

As for ALPBCSVC.exe I found the following link:

https://windowsbulletin.com/files/exe/d-link-corporation/alpbcsvc-module/alpbcsvc-exe

Read only. Do not download any offered files. Simply check where ALPBCSV.exe is located. Post accordingly.

Although the PSU may be a concern I am not sure that the PSU is the root of it all.

Especially where the errors seem to be fairly constant.

= = = =

Since the system has not blue screened for awhile I have three suggestions:

1) Clear all of the Event Viewer logs. Clearing the logs will make it easier to note additional and/or new errors that occur.

2) Continue to watch.

3) Post as necessary.

Appreciate the info here so far... without you guys id be a sitting duck lol... I tried looking for a "clear log" on the administrative events but there seems to not be one... it only works for windows logs. What info in the hardware area do you need? im just trying to make this pc work so i can game without problems.. if the 2nd solution can fix it im all for it

 

[Bluescreener97]

Appreciate the info here so far... without you guys id be a sitting duck lol... I tried looking for a "clear log" on the administrative events but there seems to not be one... it only works for windows logs. What info in the hardware area do you need? im just trying to make this pc work so i can game without problems.. if the 2nd solution can fix it im all for it

also as for the ALPBCSVC thing that's my D-Link USB wifi

 

[Ralston18]

Run Event Viewer as admin.

Then you should be able to select and clear the various logs.

https://superuser.com/questions/1073509/clearing-administrative-events-log-in-windows10

= = = =

If you have a D-Link USB wifi then I would expect that ALPBCSVC is legitimate.

 

[Bluescreener97]

Run Event Viewer as admin.

Then you should be able to select and clear the various logs.

https://superuser.com/questions/1073509/clearing-administrative-events-log-in-windows10

= = = =

If you have a D-Link USB wifi then I would expect that ALPBCSVC is legitimate.

Tried running as admin still wont let me.... but will notify you guys of any more blue screens if it pops up today/tmrw i wish i knew the exact root of the problem cause i mean this PC costed nearly 1000$ i cant just exactly go buy a new one.

 

[Ralston18]

Do you even see the Clear Logs options in Event Viewer?

Just continue to watch or check Reliability History/Monitor and Event Viewer for new entries.

Especially if another BSOD occurs. Look for error codes.

 

[Bluescreener97]

Do you even see the Clear Logs options in Event Viewer?

Just continue to watch or check Reliability History/Monitor and Event Viewer for new entries.

Especially if another BSOD occurs. Look for error codes.

like when i click the tab it doesn't show the option only for the other folders it does

 

[Ralston18]

As I understand it, the Administrative logs are a compilation of other Event Viewer logs.

The Administrative Events log is described as " Critical, Error, and Warning events from all administrative logs."

If you clear out the other logs that should empty the administrative entries.

Look at the menu choices via Windows logs. You should be able to select each log and clear it accordingly.

However, while/when I did so on my computer I noted that the entries in Administrative Events dropped from almost 8,000 to 5,000.

And some number of those errors were DeviceManagerSetup and 131 generated since I turned on my computer this morning

Interestingly, I have thus far not confirmed where all those Administrative Events are being kept - if there even is a specific folder or file.

I found this via Powershell's Get-EventLog cmdlet:

PS C:\WINDOWS\system32> Get-EventLog -list

Max(K) Retain OverflowAction Entries Log
------ ------ -------------- ------- ---
20,480 0 OverwriteAsNeeded 6 Application
512 7 OverwriteOlder 0 Dell
20,480 0 OverwriteAsNeeded 0 HardwareEvents
512 7 OverwriteOlder 0 Internet Explorer
20,480 0 OverwriteAsNeeded 0 Key Management Service
128 0 OverwriteAsNeeded 2,729 OAlerts
512 7 OverwriteOlder 3,574 OneApp_IGCC
5,056 7 OverwriteOlder 0 PRTG Network Monitor
20,480 0 OverwriteAsNeeded 77 Security
20,480 0 OverwriteAsNeeded 4 System
15,360 0 OverwriteAsNeeded 10,909 Windows PowerShell

I am going to do a bit more research and test some Event Viewer cmdlets. I have not really worked with Get-EventLog all that much (full disclosure) so I will see what more I can find and learn.

In the meantime someone else may be able add some ideas and suggestions to help as well.

If anything just continue to look through Event Viewer your logs and see what else can be found.

Do not get pulled into downloading any apps or utilities proporting to clean things up. That may not end well.