Random BSODs, New Computer Build, minidumps included

My computer is at the repair shop. I will take a look at the files as soon as I can.

Upload a screenshot of your hard disk using crystal disk info and summary tab using speccy:

• CrystalDiskInfo - Software - Crystal Dew World
• Speccy - System Information - Free Download
• Screenshots and Files - Upload and Post in Seven Forums

Make a hard drive test from the hard drive manufacturers website.

• Hard Drive Diagnostic Procedure

Driver Verifier

Use verifier for 36 hours. Then send us the BSOD reports

Driver Verifier
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because [/B][B]Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable

Till the next blue screen.

The dumps of 11th & 13th come with BCC 109.

Code:

STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTION  
Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

Code:

BugCheck 109, {a3a039d89e8a6558, b3b7465ef10734ae, fffff80003000e40, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
............
BugCheck 109, {a3a039d89ee8564f, b3b7465ef166254d, fffff80002fd4510, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!_imp_NtOpenSymbolicLinkObject+8 )
............
BugCheck 109, {a3a039d89edf272a, b3b7465ef15cf628, fffff80002fda510, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!_imp_NtOpenSymbolicLinkObject+8 )

After verifier I would suggest that you test ram sticks individually.

Weird thing is it's crashing on MSE itself

There's nothing specific in the dumps

Will wait for the results on memtest.

Sometimes memtest doesn't find errors.
How many sticks do you have?

Test them manually, without memtest.

Insert one stick and see how the computer performs.
Do the same with others.

Edit: It's crashing on MSE. Have you overclocked any of your hardware?