I looked at each bugcheck memory dump
overall, I would remove the nvidia shadow play software first then
look down the list below for more potential hints to apply fixes.
just as a guess, I would uninstall your irirun webcam software.
you could install microsoft autoruns64 and just disable these two drivers and see if you still get memory corruptions.
Autoruns for Windows - Sysinternals | Microsoft Learn
iriuna0.sys Thu Oct 22 08:22:10 2020
iriunvid.sys Thu Aug 11 11:26:38 2022
System Uptime: 0 days 13:05:14.398
I only looked at two dumps but the problem looks like what you would expect with a bad driver.
try removing the software or disabling the two drivers and reboot.
you might have to uninstall a chrome extension.
looks like the problem takes many hours to hit. you might try to cause the problem faster by putting the machine thru quick sleep/wake cycles.
if you still get bugchecks with the drivers removed. I can try and look at the other memory dumps or tell you how to isolate the problem.
second bugcheck was fast (58seconds) and the calling process was
Logitech G HUB
access violation and stack corruption.
drivers look current (sept 2 2022)
make sure the calling software was updated and maybe look for firmware updates for the logitech devices.
third bugcheck was a system process making a call but getting a access violation. address looks like a valid kernel address but was invalid.
4th bugcheck was due to cpu 4 hanging.
the timeout was very short which means it is most likely one core waiting on another core . can not debug with a minidump. a kernel dump would be required to figure out the problem. Sometimes happens when one core attempts to install some driver while another core attempts to use the driver but the install does not complete. generally, would show up in windows control panel device manager as a failed install (yellow caution symbol)
can also happen with certain programs not working correctly.
both causes would require a kernel dump to debug.
5th bugcheck was a bad pool header
some driver screwed up. it requested kernel memory, made changes outside to the assigned area and corrupted the data structure. Later the system attempted to clean up the freed structures and found it was corrupted and called a bugcheck.
most likely just a driver bug but this is the same method that malware can use to infect so a bugcheck was called.
debugging / isolation of this would involve running verifier to get the system to bugcheck at the time of the corruption rather than when the system cleans up the corrupted structure.
6th bugcheck stack overflow while running chrome.
(I would disable chrome extensions)
buffer has structures before and after where the data should be. if these structures are modified then the buffer overflowed and a bugcheck is called. this can be a method of attack on the system.
system canceled a timer just before the overflow. I do not see the common modified windows files that indicate malware.
bogus kernel address used. looks like a bad timer was bing inserted into a timer table.
this is nvidia shadow play. I would disable this unless you actually are using it. It could be the cause of all of these bugchecks.
driver issue, I can not tell which driver but I can see it is being called by a user mode service. Might be the shadow play software. Not sure:.
steam running, watchdog timeout problem.
this would require a kernel dump to debug but the timeout value
it looks like there is only one DPC and it has been there for
1222 Min 40 Sec 125.00 mSec
it looks like a network timer function.
it could be this driver:
rt640x64.sys Sun Apr 24 23:19:49 2022
but more likely it is the nvidia shadow play software messing up the network timer.