Windows 10: Can't pinpoint the cause of BSODs

My computer has been getting a lot of bluescreens from day 1, and I can't really seem to pinpoint the problemAs far as I know, all my drivers are up to date so I don't know what the problem isHere are all my minidump fileshttps://www.mediafire.com/file/k62k2fygv8kdecf/Minidump.zip/filefor some reason I can't upload the memory dump file, it just says "cannot read file" when I try it on google drive

:)

 

Random BSODs with new build, unable to pinpoint cause

I've attached the memtest results. They show no errors. So far I haven't had a crash since disabling the a-xmp profile but to be fair I haven't been at the pc much since then. Time will tell...

 

ntoskrnl.exe and amdppm.sys causing BSODs

@xcraft02 I can see you are now following zbook's advice so I will step away and let him continue. I'll be available if he needs me. Having too many people advise you is counterproductive as we all have different methods. I was hoping to explore the possible causes step by step so that the primary cause for your BSOD would be found. Now that you are making multiple changes at a time it will be difficult to pinpoint the actual cause. In the end it is important that you are free of the BSOD crashes, knowing why they happened is useful for others and for future improvements but not essential.

 

Pinpointing Faulty Driver Causing Memory BSODs

Hello!

Wanted to get some advice on pinpointing which driver is faulty on my machine. I recently built a desktop, installed Windows 10 on it (specs are in the OneDrive folder linked below).

I keep running into BSODs while using the machine after powering it on- it typically happens while I'm playing Overwatch.

At first, they varied widely- I got errors like:

• kmode exception not handled
• driver_irql not less or equal
• driver overran stack buffer
• attempted execute of noexecute memory

After doing some reading, I realized it was a memory issue, and using the Windows Debugging Tool I found that they were probably caused by wdf01000.sys, but wasn't able to go farther than that. I messaged the MS support, they recommended reinstalling Windows-
I did, and it was fine for a while.

Now it's starting to come back... but I would get an error saying "memory management" as soon as the lock screen appeared. I ran the Windows memory diagnostic, but that came out clean.

I enabled the Driver Verifier for all non-Windows driver and went through the "clean boot" procedure (went into system configuration, disabled all non-Windows services from startup and disabled everything under startup in task manager). Now everything is
fine- but when I power down my computer, it shows me a BSOD with an error code, "driver verifier found faulty driver" - but it won't tell me which one. As of now, I have a working desktop with a faulty driver currently disabled lurking somewhere...

After going through this clean boot process, I noticed that as soon as I started my keyboard software (Logitech Gaming Software 8.91), I'd get a BSOD with the error "system exception thread not handled"- so I uninstalled that, but the Driver Verifier is
still showing the BSOD when I power down.

So: I am relatively sure that one of my drivers is faulty, cause the RAM test came out clean. I want to pinpoint which driver is causing these crashes, but I don't know how other than enabling them upon startup one at a time.

Followed the procedures mentioned in
these
posts,
here is a OneDrive link with three most recent minidumps, output of MSInfo, and specs from AIDA64:

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Any tips on where to start? Thanks for the help in advance!