Windows 7 64 bit - random BSOD

The BSOD points to memory corruption. This is most often corruption in virtual memory and is most often caused by a corrupted driver.

So, let's start with this:
Please remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:

Code:

ASACPI.sys   Sun Mar 27 22:30:36 2005 - a sure fire BSOD maker, this is the Asus ATK0110 ACPI Utility driver - http://www.carrona.org/dvrref.html#a
LMIRfsDriver.sys Mon Jul 14 12:26:56 2008 - RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport  Driver - http://www.carrona.org/dvrref.html#l
RaInfo.sys   Fri Jan 04 13:57:14 2008 - RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport  Driver - http://www.carrona.org/dvrref.html#r

Due to the presence of NTFS.SYS in the stack text, I'd also run this test:

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

And then these:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

BSOD is good! BSOD save hardware!
Seriously, Windows is constructed so that it will "fail fast". It does this so that your hardware will be saved - even at the cost of things like data loss, etc.

Because this problem is so vexing, let's be careful with how we proceed. Only change one thing at a time. Make a list of what's been tried - so we can see what's been done.

First, please continue with the driver replacement and the diagnostics that I asked for previously. They will give us a good look at the system - and we can compare the results with the info that you gave us previously. Also, the memory diagnostic is needed to confirm that the new RAM is good (not a likely problem, but it has been known to happen).

Personally, I'm concerned with the presence of NTFS.sys Most times this isn't an issue, but when it is the most common problem is a failing hard drive. Beyond that, there can be issues with the motherboard that affect the storage controllers. The errors caused by a failing hard drive can also make it seem as if there are memory problems.

A clean install would be OK at this point - but be sure to:
- wipe the drive first (KillDisk or DBan)
- Install Windows
- Install Windows Updates
- Check and install drivers
- Install Microsoft Security Essentials (for protection).

Then wait to see if it still BSOD's. If it does, then that will tend to confirm the hardware issue.

I can't give you a more direct link, but go here: ASUSTeK Computer Inc.-Support-

Select Motherboards, and you MB is in the Socket771 series.