STOP:0x000000D1

DRIVER_IRQL_NOT_LESS_OR_EQUAL
fakeRAID 1
http://www.techspot.com/community/topics/stop-error-0x000000d1-driver-irql.130858/
1. How is the pagefile currently set at?
 Start - Control Panel - System - Advanced - Click 'settings' under the Performance Category. Select - Select Advanced - Under the Virtual Memory category, see what your page filing size is.
2. If you are comfortable with getting into your BIOS, select the default settings. This is in case your RAM voltages/timing have been changed as this can cause problems related to this one.
3. Your system may be overheating. Download speedfan and monitor your computer temps, see if it fluctuates when you are doing your usual routine on the machine.
HWiNFO64
windows-memory-diagnostics-tool
Download and run Video Memory Stress Test
0x00000000d1 ahcix64.sys
http://www.sevenforums.com/bsod-help-support/207847-bsod-when-opening-firefox-error-0x000000d1-3.html
If the RAID controller is still showing as the issue,  updatd it to the latest version of the drivers available.
You should use your extra 600 GB drive as a backup drive after disabling the RAID controller. If you want help with backing up your system, see Backup Complete Computer - Create an Image Backup and Imaging with free Macrium (I use the second one myself as it is an easier interface and less likely to be corrupted).
================
Download MBRCheck to your desktop

• Double click MBRCheck.exe to run (vista and Win 7 right click and select Run as Administrator)
• It will show a Black screen with some information that will contain either the below line if no problem is found:
  • Done! Press ENTER to exit...
• Or you will see more information like below if a problem is found:
  • Found non-standard or infected MBR.
  • Enter 'Y' and hit ENTER for more options, or 'N' to exit:
• Either way, just choose to exit the program at this point since we want to see only the scan results to begin with.
• MBRCheck will create a log named similar to MBRCheck_07.16.10_00.32.33.txt which is random based on date and time.

http://forums.majorgeeks.com/showthread.php?s=f7da067b7c37221b386e9b0510a55ffb&t=240720&page=2 
IF one of the drives is faulty, you can copy the drive data to another drive (same make/model, otherwise the RAID might not work) using something like Roadkil's Raw Copy and swap out the drives. If you don't have a spare drive, obviously get one and do the data copy before sending the faulty drive in.
-------------------------------
Memory crops up in both; let's assume it could be Virtual Memory = page file and get that removed, set it to zero then reboot. Then set it for 4092MB min. and max. This should at least allow the creation of a minidump, assuming that the services needed to create it are loaded when it BSOD's
-------------------------------
So I was going to update his RAID drivers because it looks like his system is using that Microsoft one instead of the Asus one, but whenever I try to get it to update with the Asus RAID driver I downloaded, the update screen gets pissy at me and says, basically, "cut it out, that driver is already updated," even though the file I'm trying to give it is completely different.
When looking at the "volumes" tab under the driver information, it's all blank.
Apparently the RAID is using two driver files I've never heard of involved in a RAID. disk.sys and partmgr.sys.
I realize the drivers for Asus are from last year. But I don't think I care how recent the Microsoft one is. I have a bad feeling that the computer is trying to run the wrong driver or even two at the same time for the RAID. Since it won't allow me to update the ahcix64s.sys file, which is the old version from April off of the Asus disk, I can't even determine if the update can fix the problem.
----------------------------------
FltMgr.sys is a “system” file used by Windows to help control various aspects of your hard drives & files. Its official name is the “Microsoft Filesystem Filter Manager” and its main duty in the operating system is make sure that the data written to the hard drive is correct and not corrupted. The fltmgr.sys error is caused when Windows cannot read or process files that are on the hard drive, usually because the File System Manager is damaged or unreadable. If this is the case, it can cause hard drives to stop working and the blue screen to appear.
http://forums.majorgeeks.com/showthread.php?t=240720&page=4