BSOD on clean install, error 0x00000003b

I have been building and using computers for my entire life, so I feel comfortable in doing most things related to them. With my current PC (built in 2013, updated graphics and RAM 3 months ago), I have been having chronic bluescreens (roughly once an hour, does not matter what I am doing) for the past couple weeks, and prior to that it was at least once a week, if not once a day.

A clean Windows 7 install was overdue and I did one today. Reinstalled my basic programs (nothing nefarious or fishy, very vanilla stuff with correct install files) and I'm bluescreening again, at a rate of about once an hour.

I have done every RAM test I can get my hands on, and have had no issues reported. Please help me in sorting out this .dmp and .zip so that I can get back to using my computer without raging many times a day.

For starters you need to update to Service Pack 1 via Windows Updates.

Code:

Host Name:                 ANDREWSHELTON
OS Name:                   Microsoft Windows 7 Home Premium 
OS Version:                6.1.7600 N/A Build 7600
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Andrew Shelton
Registered Organization:   
Product ID:                00359-112-0000007-85599
Original Install Date:     6/2/2015, 9:34:30 AM
System Boot Time:          6/2/2015, 3:14:57 PM
System Manufacturer:       MSI
System Model:              MS-7821
System Type:               x64-based PC

You need to do that first then upload any subsequent BSODs. If it wasn't important I wouldn't ask for it.

UPDATE: Fresh dump with a BSOD on SP1, under the same circumstances as the previous ones (seemingly random). File attached to this post.


UPDATE2: Decided to read another post's advice and used verifier, and was in a BSOD boot loop without safe mode, so it is certainly a driver. Seeing as though I had to quit verifier to access my computer again, if someone could help me isolate which driver it is, that would be fantastic.