According to your system you have Intel I211 Gigabit Network Controller drivers dated 25/2/20 version number 18.104.22.168 - only result i can find of these is in Chinese, and its on the intel site. Seems they had problems with the LAN not working with those drivers - link - and the current version of windows.
note: date above might be creation date, not actual driver date. That driver was signed by Microsoft in November last year
Issued by: Intel External Issuing CA 7B
Issued to: Intel(R) INTELND1820
Revocation Status: OK
Serial number: 560000077b478c76c9afcafcaf00000000077b
Signing time: Monday, November 25, 2019 8:22:00 AM
Valid from: 8/9/2018 to 8/8/2020
Issued by: Microsoft Windows PCA 2010
Issued to: Microsoft Windows Hardware Compatibility Publisher
Revocation Status: OK
Serial number: 330000061929b7720a7076e4b4000000000619
Signing time: Monday, December 2, 2019 5:53:44 PM
Valid from: 2/20/2019 to 7/31/2020
Error mentioned non paged pool. Nonpaged pool is kernel memory which can't be paged out into the pagefile when Windows runs out of free physical memory. Its in ram. While it is an IRQ error its also a page fault. Page faults are not errors - badly named actions. They are necessary for virtual memory systems. So try running this on your ssd and run benchmarks, check its smart score and see if you have any firmware updates - https://www.samsung.com/semiconductor/minisite/ssd/download/tools/ (you want samsung Magician)
windows sees storage as memory as its where the page file is. Not getting a dump file after DV could also mean its the ssd as its not going to record an error if its the cause. PSU being less known could have (Maybe) damaged other parts. That is risk of cheap PSU. I learned that long ago, killed a few hdd along way. I could be wrong, but I am leaning towards hardware cause as drivers usually not this hard to find.
slaps DV for not producing a dump. It could mean it isn't a driver error.
Do you get any errors in safe mode?
You replaced RAM & PSU so far? Ram is on motherboard list now.
Newest BIOS on motherboard. Newest LAN drivers (not going there again)
I have yet to try in safe mode, but it might be a bitch to test out, since I've had four days of no crashes at least twice. I'll try to leave the computer running in safe mode overnight and while at work after the weekend.
GPU is a PowerColor Red Dragon
Keyboard is a CM Storm Devastator
Mouse is a Logitech G502 Lightspeed (Wireless)
I have a Steelseries Arctis Pro Wireless headset.
My monitors USB-ports are also connected to the system. They aren't in use, though.
I have not actually run Memtest on these sticks. I'll run it overnight when I go to bed tomorrow.
Very small sample size, but errors in safe mode seemed to happen way faster, and while not doing anything with the PC.
Asked about GPU as was curious if was made by Asus. I heard they were problem cards.
Only asked about USB as my odd problem ended up being an old mouse, but I wasn't getting BSOD, you are. How old are they all?
3rd party drivers don't run in safe mode. So it removes software as generally windows built in drivers are rock solid (If you disregard the possibly buggy lan drivers)
which safe mode did you run? with or without networking?
Not sure why it would happen faster in safe mode... perhaps some of the AMD drivers slow down the error from happening in normal mode. Safe mode puts less stress on hardware, so its odd your PC crashes faster in it.
Please put new dumps into a new folder each time, or provide a link directly to the new dump file(s) each time. It makes it difficult for me to determine which files are old and which ones I've already done when they are all mixed up. Thanks.
My interpretation of that error is probably wrong... I saw an almost identical error yesterday and I thought at time it was GPU errors. A lot of your errors have made me look (every time) if it isn't an Nvidia GPU. As they look like the errors I see from Nvidia.
GPU drivers don't normally cause IRQ errors and yet I have seen a few recently. This error isn't pointing at a GPU driver.
I am probably reading this incorrectly - win32kbase!DirectComposition::CAnimationMarshaler::SetReferenceProperty
Direct Composition uses the GPU for flashy transitions but later on, the error itself happened in virtual memory.
How did memtest go? Did you run Prime 95 as it tests CPU & Memory (since the memory controller is on CPU)
only so many things deal with data. CPU, RAM, GPU ram (to a lesser degree), storage & PSU (cause it effects everything). I expect Dark Breeze didn't let you buy a cheap PSU so it shouldn't be it and you were having the errors before you swapped them.
I am planning on running Memtest tonight when I go to bed, and let it run until I get home from work tomorrow. Just to be sure since I see different recommendations in various places, but should I run Memtest86 or Memtest86+?
I ran Prime95 a while back on Darkbreezes recommendation, and it showed no errors. That was before the hardware changes, however. I'll run it tomorrow night before I go to bed.
He did not. As far as I understood, it's not top of the line, but should be solid.
Read below why I ask that, sorry for the wall of text, I have tried to make it easy to read, as I think it could be relevant.
I've been following this thread for a while, because it reminds me of a series of BSODs I had. But I wasn't too sure, I'm still not, if my experinces can actually contribute with anything.
But I'll try and share it anyways - it might be a bit long, but maybe it is easier to disregard if it sounds completely unlike what OP experiences, or maybe it sounds familiar and could be helpful - you never know.
I know OP has a Ryzen CPU, and mine is an Intel - but everything OP derscribes sounds very similar to what I experienced.
I built a completely new system, built from entirely new parts, except for the PSU, which was a 2 year old Corsair AX860 that didn't show any signs of being faulty with my previous build.
In the beginning I had a random BSOD here and there, but nothing that I really considered a problem, I felt it might be some driver issue - and there would be several days between the BSODs occuring.
But the BSODs kept comming, so after a while I did a clean re-install of Windows 10.
Still I had BSODs, so after a period of time with 4 complete re-installs, and several different driver version for various components, I felt there had to be something more seriously wrong.
The problem was, the BSODs primarily occured when I was away from the computer, or when it was under very light load. There were no real obvious indications to what it could be.
Some of the BSODs, but not all, shared the stop code 0x124 - which indicates hardware failure, but the dump files identified something new as the cause every time - which I later learned can point towards CPU error.
When analyzing the dump files, it pointed to every possible thing you can think of. Firefox, Samsungs NVMe drivers, ntoskrnl.exe, hal.dll, Nvidia drivers, LAN drivers... -and the list goes on and on.
I spent a lot of time chasing dead ends, trying different drivers for all the stuff the dump files indicated as the being the cause of the BSODs.
I finally realized, that when a certain file was singled out in the dump file, it actually never meant anything other than that program happened to be running at he time. (when it wasn't Firefox, it could be iTunes, VLC Player, Origin, explorer.exe or pretty much any program that happened to be running).
The most difficult bit was, that although some BSOD returned the same faulty items, most of them were completely random.
All stresstests and benchmarks passed error free.
I couldn't in any way provoke the BSODs while benchmarking, Prime95 both Small FTTs and Blend Test with or without AVX passed 12 hours of testing, OCCT ran for 20 hours error free, AIDA64 System Stability Test ran without problems for 12 hours.
Even Intel's own "Processor Diagnostic Tool" gave the CPU a "Pass" with no signs of error.
But I was beginning to suspect the CPU being faulty. But up to that point in time, I had only once in 20 years come across a faulty (factory new) CPU, so I was reluctant to conclude that it was a faulty CPU.
After 4 passes of MemTest86 it returned no errors. I bought the Pro version of MemTest86, which lets you run more than 4 passes, and after 8 passes I recieved a warning, but no errors.
Googling the warning, it was referred to as being something that could be ignored, a warning that can be the result of high frequency RAM, and isn't generally considered a big issue.
But I bought new RAM anyways, which didn't help.
Even a second set of new RAM didn't help.
Then I bought a new PSU, which didn't help.
So I bought a new motherboard, which didn't help either
I tried my previous graphics card, which didn't help.
I tried a different system drive, which didn't help.
Then I bought a dirt cheap 9th Gen i3 9100F CPU, and the errors went away.
Finally I contacted the store where I bought the CPU, and they recommeded RMA'ing it.
When I recieved a brand new CPU from Intel, no BSODs or errors ever returned, and it was almost as if it had only been a bad dream
I had kept all the new parts of the original setup, and I had the new parts bought for troubleshooting. So eventhough I was positive it was the CPU being faulty, I actually - out of my own curiosity - rebuilt the original setup, and the setup built from the troubleshooting parts, and both systems were stable as a rock, finally confirming that it actually WAS a faulty CPU, and nothing else.
I could have saved myself a lot of money for new hardware, if I had listened to my gut feeling concerning the faulty CPU instead of replacing so many things for no reson.
I'm sorry for how long my post is, I've tried to make it easily readable.
When I read this thread for the first time, I thought it might be a faulty CPU, but I have very little experience with Ryzen CPUs, so I decided I wouldn't be of much help.
But still, every time I return to this thread, it sound a lot like the process I went through with my faulty CPU.
It took me almost two months, from the first BSOD until I finally RMA'ed the CPU.
Although I couldn't identify 100% what was faulty on the CPU, everything pointed towards the integrated memory controller, but I can't say for sure.
What made this process so difficult, was that the system passed every single test designed to indentify instasbility or faulty hardware, with no hint of problems.
The best way to provoke the errors, was actually to leave the computer alone for a while.
So I might be completely wrong, but maybe you should consider if the CPU is the cause of all this.