Windows 10: SYSTEM_SERVICE_EXCEPTION Among Others, Constant BSOD. Desperate

I have been receiving this BSOD since about the second week of successfully building my computer, almost a year ago. The drivers that caused the error always vary, but ntoskrnl.exe was the most recent offender. Though my computer crashes usually with SYSTEM_SERVICE_EXCEPTION, I also frequently see IRQL_NOT_LESS_OR_EQUAL, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, or KMODE EXCEPTION NOT HANDLED. I have tried:
-DISM Clean up
-Reinstalling Windows 10
-Check & Repair Disk
-Updating video drivers (though the problem continued through multiple graphics cards)
-Removing all USB devices except mouse and keyboard
-Driver Verifier
- Updating BIOS
-Updating most drivers
-Memtest (8 passes with 0 errors)

This has caused me stress like nothing else. The BSOD seems to happen frequently when playing video games, but by no means exclusively. I have tried for months to fix it. I am beginning to suspect a hardware problem, though I'm reluctant to accept this as I have gone through 2 faulty PSUs already and one mobo and cpu (though those were my fault) and don't want to throw anymore money down the drain.

Can anyone help me?
Link to my lasted minidump: Free File Hosting - Online Storage; Upload Mp3, Videos, Music. Backup Files

Also: After Win10 completes its "gathering info and then we'll restart", it restarts and almost immediately after boot I will BSOD again. This will continue repeatedly if I keep letting the computer restart itself. However, if I hard shut down the computer and then turn it back on, the BSODs will temporarily stop. I think this is a clue as to what is causing this problem.

:)

 

SYSTEM_SERVICE_EXCEPTION (among other things)

Hey,

I've never posted here before, so I apologize if I'm making any common mistakes. I'm aware that this is a fairly common issue, but I wasn't able to find any instructions that weren't specific to an individual.

I built my computer a couple months ago, and it normally runs really well, but every once in a while I get a blue screen and have to restart the computer. It's inconvenient but not super frequent so I've just been living with it, but it's starting to get pretty
old. There are three or four normal error messages I get on the crash screen, SYSTEM_SERVICE_EXCEPTION being the most recent, and they all seem to be related to bad drivers. I can't remember the other errors off the top of my head, but if you need them I can
probably find them in my search history.

I followed
these instructions to run Driver Verifier, and
these instructions to compile the information it appeared you would need from me.

Here is (hopefully) a link to my three most recent DMPs (compressed) and the output of MSinfo:

Shared items 7-22-2016 (2)

Also, the summary of my specs as generated by Speccy:

Summary

Operating System

Windows 10 Home 64-bit

CPU

Intel Core i3 @ 3.70GHz 25 °C

Skylake 14nm Technology

RAM

8.00GB Dual-Channel Unknown @ 1333MHz (15-17-17-35)

Motherboard

ASRock Z170M Pro4S (CPUSocket) 32 °C

Graphics

ASUS VS239 (1920x1080@60Hz)

4096MB ATI AMD Radeon R9 380 Series (ASUStek Computer Inc) 39 °C

Storage

223GB Crucial CT240BX200SSD1 (SSD) 29 °C

Optical Drives

No optical disk drives detected

Audio

AMD High Definition Audio Device

Thanks in advance, friendos.

 

SYSTEM_SERVICE_EXCEPTION (among other things)

How to Uninstall AMD Catalyst™ Drivers on Windows® 8.1 and Windows® 10 Based Systems

How-To Uninstall AMD Catalyst Drivers From A Windows Based System

 

Hi usermx,

Welcome to the 10forums *Smile

Is this before, after or at the time of Windows loading (circling dots)?

Could you upload the chkdsk log please *Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums

 

After the time of Windows loading.
Attachment 103985

 

Please run following command in admin command prompt
chkdsk C: /r

You'll be asked to schedule it on a reboot, because the partition needs to be unmounted for the chkdsk to run. Press Y when requested and reboot.

 

Here are the results.

Attachment 104101

 

Have crashes occured while driver verifier was enabled? If so, do you remember what error code was disabled and any driver (if any)?
What settings were enabled with driver verifier?

 

I'm not sure I remember, but I can run it again.

 

Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Been running driver verifier and have BSOD'd three times, all in a row. After the first, they only stopped when I hard shut down, as I mentioned before. The first was SYSTEM SERVICE EXCEPTION (ntoskrnl.exe), then K MODE EXCEPTION (ntfs.sys), and then K MODE again (ntoskrnl.exe). Don't know if driver verifier triggered these, but they happened when they usually do: a few hours into a gaming session. It also sounded like my fans were working very hard, but I don't think my temps ever got too high.

Thank you for your continued help.

 

Upload a new zip from the DM Log Collector.

 

Attachment 104124

Here you go.

 

The crashes present haven't been caused by driver verifier, keep it running.

If you are using a program like Ccleaner please stop using it while troubleshooting.
This because programs like Ccleaner remove dump files that are needed to troubleshoot.
Or configure Ccleaner to not remove dump files:

 

Will do. What do I do next? Wait for driver verifier to crash?