Random BSOD's random error codes

Absolutely. Sorry to see that happened, though. Is the motherboard still under warranty?

I think it is, I got it in 2010, but I'm upgrading to a z77 mobo pretty soon, so it doesn't really bother me much, just so nice to have a definite solution to the blue screens.

Glad you found a solution, as well. May I ask how you tested the lane/slot to make sure it was the motherboard and not the card?

I have another pci-e slot on the board, it runs at 8x, the card puts video in through that slot, both do actually, but not the other lane. Another note, I had a single BSOD last night, but I'm suspecting that my USB ports are now going bad as well, seems the motherboard is on a downward spiral.

What leads you to suspect the USB ports? Mind uploading the dumps for a second opinion?

Here are my two latest, the one from the 27th, and strangely, I have a dump file from 1 minute before I logged into Windows.

Crashes actually indicate RAM or drivers as the likely culprit(s)...

• 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 214232
  • 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.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  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.

I actually have run memtest, I get a a large number of errors in dual channel mode, but in single channel mode, both sticks run clean.

Have you tried running with one stick at a time to see if the problems persist? Having both sticks in may cause problems due to a bad module. Testing them individually may not find the bad section in the module, but testing them as dual channel does check the area of the module that is faulty.

Yes, I've tested them singly in all 4 slots and they both tested clean and free of errors. The only time I get memtest errors is in dual channel mode.