BSOD's while gaming, most prevalent error code, 0x0000001a

Msinfo32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter > Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post. Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "msinfo32 /nfo %USERPROFILE%\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back. Then zip up the .nfo file and upload/attach the .zip file with your next post.

systeminfo:
Please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "systeminfo.exe >%USERPROFILE%\Desktop\systeminfo.txt" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the syteminfo.txt file. If you have difficulties with making this work, please post back. Then zip up the .txt file and upload/attach the .zip file with your next post.

Memtest86+

Run Memtest86+ for at least 8-10 passes. It may take up to 20 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. How to Test and Diagnose RAM Issues with Memtest86+

   Note

Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.

   Tip

Do this test overnight.

Thanks for the response. I've attached the files. Also, should I try booting without my gfx card? If I still get blue screens, would that rule out faulty hardware?

Yes, you can try that.

Start up

Keep less stuff at the start-up. Only anti-virus, this helps avoid driver conflicts and improves time to log in to windows.
Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista
How to Change, Add, or Remove Startup Programs in Windows 7

Overclocking
If you are overclocking any hardware, STOP. Reset any changed values back to default.

Code:

Start Menu\Programs\ASUS	Public:Start Menu\Programs\ASUS	Public
Start Menu\Programs\ASUS\AI Suite II	Public:Start Menu\Programs\ASUS\AI Suite II	Public

   Warning

This is overclocking software and can lead to system instability and BSOD's. Please reset all components to their stock speeds and then remove the software.

Two threads that were solved by removing the software:
Recurring BSODs before/after startup
Windows 7 32bit freezes at random

   Note

Revo Uninstaller
Download and install Revo Uninstaller free from here: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).

Will wait for an update, good luck :)

All of them indicate memory corruption:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800a934688, fffff8800a933ee0, fffff80003244f0b}

Probably caused by : memory_corruption ( nt!MmPurgeSection+4eb )

Followup: MachineOwner
---------

Have you followed part 3 of the tutorial?

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa800313c8c0, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

Followup: MachineOwner
---------

If yes, I would check how a different set of ram sticks work on the computer. (compatible with your mobo)

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {28, 2, 0, fffff8000330bd80}

Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )

Followup: MachineOwner
---------

Alrighty