BSOD - seemingly random

I have been bluescreening 1-2 times a day over the passed couple days, and there's no particular thing I can do that seems to make it happen.

I have attached all the necessary files.

Also, here are some specs:
Windows 7 Ultimate x64
Full retail version
All hardware is just over a year old, but was very new, high end hardware at the time.
I haven't re-installed the OS for about 8 months.

edit: Something else that may help, it usually says "MEMORY_MANAGEMENT" on the bluescreen, I don't know if this is the cause or what but it may help.

Thanks!

Device Concerns:

Code:

archlp	ROOT\LEGACY_ARCHLP\0000	This device is not present, is not working properly, or does not have all its drivers installed.
USB Input Device	USB\VID_0D8C&PID_013C&MI_03\8&18C6F28&0&0003	This device is disabled.

Were you aware of the above. If so, please explain your troubleshooting steps.
Check Device Manager for any problem devices or unknown devices and uninstall any devices that show problems: Start Menu -> Right click Computer -> Manage -> Device Manager from the list on the left.

Device Manager : Hidden Devices may also be needed.

Software Concerns:

Security Software: ??? Make sure to install security software. I recommend either of these:

• Microsoft Security Essentials - Free Antivirus for Windows coupled with Malwarebytes. Do not start the free trial of Malwarebytes. Just use the standalone version, update it, and scan your computer once a week with Malwarebytes and with Microsoft Security Essentials.
  
  
• Good and Free system security combination.

After installing your security software, update it, and then run full scans today with each program. Report back the results of the scans.



MSI Afterburner/RivaTuner/Kombustor are known to cause instability with systems. Please remove the software. Software overclocking does not provide reliable overclocking. Overclocking should be accomplished through the BIOS or through the graphics card manufacturer's software.

Analysis:

Crashes are pointing to memory problems or driver conflicts.

• If you are overclocking any hardware, please stop.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    Attachment 221750
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
  
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset
  -> Restart your computer.

3rd Party Drivers:

The following is for informational purposes only:

Code:

Afc.sys Tue Jul 11 23:48:20 2006 (44B48D24)
ManyCam_x64.sys Thu Mar 13 01:46:01 2008 (47D8DBB9)
GEARAspiWDM.sys Mon May 18 06:17:04 2009 (4A1151C0)
Tosrfhid.sys Tue May 19 19:23:51 2009 (4A135BA7)
tosrfbnp.sys Wed Jun 10 23:05:00 2009 (4A30907C)
tosporte.sys Tue Jun 16 04:48:47 2009 (4A37788F)
uxpatch.sys Sun Jul 12 23:09:18 2009 (4A5AC17E)
intelppm.sys Mon Jul 13 17:19:25 2009 (4A5BC0FD)
tosrfnds.sys Thu Jul 23 18:43:25 2009 (4A6903AD)
tosrfcom.sys Tue Jul 28 04:18:20 2009 (4A6ED06C)
xusb21.sys Thu Aug 13 16:10:17 2009 (4A848F49)
tosrfusb.sys Fri Sep 11 03:37:18 2009 (4AAA1A4E)
taphss.sys Tue Sep 15 13:58:23 2009 (4AAFF1DF)
tosrfbd.sys Wed Sep 23 22:57:27 2009 (4ABAFC37)
CM10864.sys Wed Nov 18 02:55:47 2009 (4B03C4A3)
tap0901.sys Fri Dec 11 16:48:03 2009 (4B22DA33)
amdxata.sys Fri Mar 19 10:18:18 2010 (4BA3A3CA)
SCDEmu.SYS Mon Apr 12 02:52:25 2010 (4BC2DF49)
npf.sys Fri Jun 25 10:50:58 2010 (4C24DE72)
e1q62x64.sys Thu Jul 8 16:07:00 2010 (4C364C04)
AsIO.sys Mon Aug 23 19:53:02 2010 (4C7325FE)
e1c62x64.sys Tue Sep 21 15:34:15 2010 (4C9924D7)
RzSynapse.sys Thu Oct 14 01:42:17 2010 (4CB6B459)
HECIx64.sys Tue Oct 19 17:33:43 2010 (4CBE2AD7)
Soluto.sys Mon Feb 14 05:25:50 2011 (4D591F4E)
hcwD1cap.sys Mon Jul 11 10:16:55 2011 (4E1B21F7)
hcwD1xcm.sys Mon Jul 11 10:18:04 2011 (4E1B223C)
hcwD1xcd.sys Mon Jul 11 10:18:07 2011 (4E1B223F)
cpuz135_x64.sys Wed Sep 21 02:23:41 2011 (4E799F0D)
aswFsBlk.SYS Tue Mar 6 17:01:31 2012 (4F56A55B)
aswMonFlt.sys Tue Mar 6 17:01:51 2012 (4F56A56F)
aswTdi.SYS Tue Mar 6 17:01:56 2012 (4F56A574)
aswrdr2.sys Tue Mar 6 17:02:19 2012 (4F56A58B)
aswSP.SYS Tue Mar 6 17:04:03 2012 (4F56A5F3)
aswSnx.SYS Tue Mar 6 17:04:05 2012 (4F56A5F5)
mbam.sys Tue Mar 20 10:04:48 2012 (4F68AAA0)
nvhda64v.sys Wed Apr 18 11:07:54 2012 (4F8EF4EA)
nvlddmkm.sys Tue May 15 01:35:36 2012 (4FB20748)
hssdrv6.sys Fri Jun 1 15:18:17 2012 (4FC93199)

Afc.sys
ManyCam_x64.sys
GEARAspiWDM.sys
Tosrfhid.sys
tosrfbnp.sys
tosporte.sys
uxpatch.sys
intelppm.sys
tosrfnds.sys
tosrfcom.sys
xusb21.sys
tosrfusb.sys
taphss.sys
tosrfbd.sys
CM10864.sys
tap0901.sys
amdxata.sys
SCDEmu.SYS
npf.sys
e1q62x64.sys
AsIO.sys
e1c62x64.sys
RzSynapse.sys
HECIx64.sys
Soluto.sys
hcwD1cap.sys - Hauppauge Colossus Capture Driver
hcwD1xcm.sys - Hauppauge Colossus XCode Driver
hcwD1xcd.sys - Hauppauge Colossus XCode Driver
cpuz135_x64.sys
aswFsBlk.SYS
aswMonFlt.sys
aswTdi.SYS
aswrdr2.sys
aswSP.SYS
aswSnx.SYS
mbam.sys
nvhda64v.sys
nvlddmkm.sys
hssdrv6.sys

Ubuntu is actually a good troubleshooting step. If you have the same problems there, it will indicate a hardware problem. If not, you may consider re-installing Windows cleanly. Damage to Windows files or registry files can cause freezes, as well.