Downlooad and Install Dll Files: How to Fix Problem - A plethora of BSOD errors with no known cause?

A plethora of BSOD errors with no known cause

About a month ago, there was a power hiccup, and almost immediately afterward, my computer started throwing bluescreens left and right.
Seeing as I've only had this custom build for only a couple of months, the last thing I want it to be is a hardware
problem.
From what I can tell from the 34 dump files is that it mostly seems to be a software thing (at least I hope so).
Before I go and post all of them, I did a fresh install of the OS, and updated all of my drivers.
It's getting better now, but it still
goes off.
Memory diagnostic ran AND COMPLETED, but the system bluescreened on the restart, so I couldn't read the result.
After installing a new USB wireless adapter, I experienced a new error, although the frequency still remained the same.
I'm not sure which
dump files to upload (short of all of them), since the 10 since the clean install have about 4 different drivers as the cause, and the 24 beforehand have 10 different drivers listed, 3 of which overlap.
Which ones should I upload?

PC Timeline:

11 June - Power hiccup.
28 June - New USB Wireless adapter
30 June - Reinstall OS

Pre-reinstall crashers:
netr7364.sys x1
usbehci.sys x1
dxgmms1.sys x2
ntoskrnl.exe x9
atikmdag.sys x5
fltmgr.sys x1
tcpip.sys x1
rtwlanu.sys x2
ntfs.sys x1
wdf01000.sys x1

Post-reinstall crashers:
ntoskrnl.exe x6
win32k.sys x2
rtwlanu.sys x1
atikmdag.sys x1

Solutions to the Problem A plethora of BSOD errors with no known cause

Download SmartPCFixer to Fix It (Free)

Patrick,

I appreciate your help with my slew of errors, however due to some sort of horrific fate, my motherboard actually died the other day.
I popped my hard drive into my dinosaur, and it's been 2 days with no blue screen occurrences.
And given that the whole
series of errors actually started the day of the power surge, is it possible that a piece of hardware is to blame?

In semi-related news, installing the new PCIe adapter brought in 2 new errors!

Manually editing the Windows registry

Caution: Unless you an advanced PC user, please do not edit the Windows registry manually.

Because of this risk, we highly recommend using a trusted registry cleaner such as SmartPCFixer Using a registry cleaner automates the process of finding invalid registry entries, missing file references (like the one causing your MACHINE_CHECK_EXCEPTION error), and broken links within the registry. A backup is automatically created before each scan, with the ability to undo any changes in a single click, protecting you against the possibility of PC damage. The best part is that repairing registry errors can also dramatically improve system speed and performance.

Click the Start button.
Type "command" in the search box... DO NOT hit ENTER yet!
While holding CTRL-Shift on your keyboard, hit ENTER.
You will be prompted with a permission dialog box.
Click Yes.
A black box will open with a blinking cursor.
Type "regedit" and hit ENTER.
In the Registry Editor, select the Error 0x9C-related key (eg. Windows Operating System) you want to back up.
From the File menu, choose Export.
In the Save In list, select the folder where you want to save the Windows Operating System backup key.
In the File Name box, type a name for your backup file, such as "Windows Operating System Backup".
In the Export Range box, be sure that "Selected branch" is selected.
Click Save.
The file is then saved with a .reg file extension.
You now have a backup of your MACHINE_CHECK_EXCEPTION-related registry entry.

The next steps in manually editing your registry will not be discussed in this article due to the high risk of damaging your system. If you would like to learn more about manual registry editing, please see the links below.