BSOD - Most likely RAM issue

Yes, one error on memtest86+ is too many, when memtest86+ freezes it is not a good sign.

Let's look at your RAM and memory controller settings first, sometimes adjusting the settings will make it stable.
These are important, post these voltage settings in your next post so we can proceed.
Check the CPU Over Voltage, Memory Over Voltage, (CPU/NB Voltage should be) VDDNB Over Voltage settings, and post them here.
In BIOS, Advanced > Jumper Free Configuration.

If you are having any problems finding these voltage settings, let me know.

Did you get a chance to get the 'warm' voltage settings?
Speed Fan is showing some strange 5v readings, check it with HWiNFO64, open the 'Sensors' tab.
Let HWiNFO64 run at cold idle and then when it warms up open your game to put some stress on the system, when through post the screen shot.

POsting this weird distortion as well.
I can still move my mouse around but it's stuck on the loading wheel.
Then the background went black and it's on screenshot 2.
As soon as I closed these windows, I blue screened.
Now I've been running memtest86+ since I blue screened with no errors.

Go to your BIOS and get/post the, DRAM frequency and VDDNB Over Voltage, if no voltage number is shown then change it to 'Manual' to get the reading.
Are you selecting 'Exit and Save Changes' after changing BIOS settings?
Confirm your DRAM Voltage is 1.80v.
Your previous BIOS screen shot is showing 'Memory Over Voltage' is on 'Auto'.

Change your 'CPU Over Voltage' to +0.005v.


The various issues you are having may indicate the PSU voltage is not sufficiently stable, we may need to come back to this.

Can you confirm what you changed and to what setting (voltage, etc.) amount.

Three of your crashes were:

Code:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION  
Usual causes:  System service, Device driver, graphics driver, ?memory
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
IMAGE_NAME:  memory_corruption

These all look like they are caused by memory corruption.
The RAM settings should take care of these.

Code:

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003714100
GetUlongFromAddress: unable to read from fffff800037141c0
 fffff6ff30000008 Nonpaged pool
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_0xA_nt!MiObtainSystemCacheView+186

Looks like the same cause as above.

Drivers that need updating:

Code:

AtiPcie  AtiPcie.sys  Tue May 05 23:00:22 2009

Make sure you have the latest Asus Chipset driver.

Code:

GEARAspiWDM GEARAspiWDM.sys Mon May 18 20:17:04 2009

Uninstall iTunes and get the latest version. This driver is known to cause crashes with Win7.

Code:

mcdbus   mcdbus.sys   Tue Feb 24 18:34:07 2009

Uninstall MagicISO and install the latest version. This driver is out of date.

If the LGVirHid.sys driver was implicated in a crash somewhere, it is likely the result of the crash and not the cause.

Let us know if you get any more crashes.