Non-stop random BSOD's in a new build

Intro

I've been getting BSOD's at random since I built this system around two months ago. I've looked for help via friends, Reddit and my own technical knowledge but have so far not come up with a solution. I'm going crazy and desperate for a solution now - it's a brand new build that I should be enjoying, not wanting to throw out the window.

Specs

i5 6500
ASUS H110M-A (BIOS v503)
Corsair Vengeance 8GB DDR4
Samsung 850 Evo SSD WD 1TB HDD
MSI R9 380 4GB
Windows 10

What I've Tried

• Refresh Install
• Clean Install
• Installed all Windows Updates
• Installed latest GPU drivers
• Installed all current device drivers
• Memtest86 with One Pass (all clear)
• Memtest86 for 36 hours (all clear)
• Windows Memory Diagnostic (all clear)
• SFC (all clear)
• Switched ram from Slot 1 to Slot 2 (same result)

Additional Information

• I can't seem to find a trigger. I've had the BSOD's occur after booting, a few hours into using my PC, whilst gaming. An example would be today playing League of Legends I had about 3 BSOD's in 2 hours, yet I played The Division for an hour with no crashes.
• I don't know a lot about RAM but I'm using DDR4 2400mhz in a motherboard that only supports DDR4 2133mhz. Looking at the BIOS and it seems to display that information correctly so I don't know if there is an issue there.

axe0 said:

If you didn't perform MemTest86+, please run MemTest86+.


Please run CPU-Z | Softwares | CPUID, open it and make screenshots of the following tabs

• CPU
• Mainboard
• Memory
• SPD*
• Graphics

*SPD shows the details of each module, you can show the details by choosing different slots in the left upper corner.
Please make screenshots of each module.

Please post each screenshot in your next reply/replies.

The same device is giving WER's in 8 other reports, what device is this? I can't find it back in msinfo32.nfo.

Code:

15/03/2016 3:38 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: PnPRequestAdditionalSoftware
Response: Not available
Cab Id: 0

Problem signature:
P1: x64
P2: USB\VID_056A&PID_0302&REV_0100&MI_01
P3: 10.0.0.0
P4: 0409
P5: input.inf
P6: *
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_x64_a45b16bee463a1d692b25faf2e552567e5616a_00000000_01430133

Analysis symbol: 
Rechecking for solution: 0
Report Id: 33cc6699-da07-11e5-bd00-305a3a04f965
Report Status: 8192
Hashed bucket:

I'll post CPU-Z screenshots soon, just need a minute to take them all.

In the mean time, is there a way to further investigate what device is throwing WER's? You said you can't see it in msinfo32.nfo, so is there somewhere I can check?

Thanks

axe0 said:

I search msinfo32 for the vid and/or pid, I also checked manually but I couldn't find anything that compares with the vid

Code:

P2: USB\VID_056A&PID_0302&REV_0100&MI_01

Searching VID_056A in google shows it links to a WACOM tablet, which I have. But I haven't used it except for once and it's never plugged in. The BSOD"s occured before then too. Weird.

axe0 said:

Both SPD tabs are empty..

I know. They always have been. Cpuz is up to date and running in admin mode so I don't know what else to do.

axe0 said:

Please check in the BIOS for everything related to the memory and let me know it.

BIOS when on automatic defaults to 2133mhz with 15-15-15-36 @ 1.2v.
I changed it recently to 2133mhz with 14-16-16-31 @ 1.2v which was the manufacture tested setting (although they were at 2400mhz)

Photos of memory settings are attached.