Try this [win7, but it's pretty much the same for all windows OS]StartRight click computer >properties> Advanced system settings. Advanced tab, in the startup and recovery section click settings button. Under the System failure section uncheck Automatically restart. Reboot, next time you BSOD it will not restart windows, make a note of the code and then restart manually via the computer button.

Ahhh, thanks!

Here are the four diffirent stop codes I've seen in the last 10 mins. I get these between 0 and 3 minutes after the ststem starts up. My computer is completely unusable.KERNEL_DATA_INPAGE_ERROR0X0000007AKERNEL_STACK_INPAGE_ERROR0X00000077PROCESS_INITIALIZATION_FAILED0X0000006B{NO ERROR NAME}0X000000F4

Here are the four diffirent stop codes I've seen in the last 10 mins. I get these between 0 and 3 minutes after the ststem starts up. My computer is completely unusable.KERNEL_DATA_INPAGE_ERROR0X0000007AKERNEL_STACK_INPAGE_ERROR0X00000077PROCESS_INITIALIZATION_FAILED0X0000006B{NO ERROR NAME}0X000000F4

A quick search on Microsoft's site regarding KERNEL_DATA_INPAGE_ERROR 0X0000007A brought up the following quote:

The error code KERNEL_DATA_INPAGE_ERROR STOP: 0x0000007A states that the requested page of kernel data from the paging file could not be read into memory. It appears that there are some issues with the hard disk. Use check disk command for any errors on hard disk - Warning: Microsoft does not recommend interrupting the CHKDSK process. Microsoft does not guarantee the integrity of the disk if the CHKDSK program is interrupted. For safety you can back up your data before using the check disk command. Use the check disk commands as follows: 1. Click Start. 2. In search window type 'cmd' and ENTER. Right click and select 'Run as administrator'. 3. Type at the command prompt CHKDSK /P and press ENTER to scan the disk. 4. Then type CHKDSK C: /F /R and press ENTER to repair corrupt sectors, if there are any. NOTE: The root drive has to be C: and the command may schedule a task at the system startup, if it does, then press Y to schedule a task and restart the computer to perform chkdsk.Once chkdsk completes, boot to the desktop and then check.

Give it a shot....It also brought up this link. (summary: This issue can occur if a requested page of kernel data could not be read from the paging file into memory, or the master boot record is infected with a virus.) Follow the link and try the recommendations.

I already ran chkdsk from Command Prompt and it came back with no errors. If I move my HDD to my crappy Dell work computer, I can boot fine and receive no BSODs or stop errors. The problem is that the hardware in my work computer is just for normal computing and could never run FSX or media editing aplications like my personal PC can. It is all very strange. The errors point to the HDD, but when I connect it to my work computer, I receive no errors when I run chkdsk, (I cant run this on my personal computer because I get a blue screen before it completes.), and I can boot an run everything fine.ARRRGGGG!

If I move my HDD to my crappy Dell work computer, I can boot fine and receive no BSODs or stop errors. The problem is that the hardware in my work computer is just for normal computing and could never run FSX or media editing aplications like my personal PC can. ARRRGGGG!

You moved your main drive to a different PC? That can *seriously* screw with drivers. Not to mention product activation should an addon need it...Before buying new hardware, i would take an image of your drive, and reinstall Windows. This smells like a driver problem for sure.

+1 to that. That can ruin and overwrite tons of important data. The registry gets hosed also. Your chipset drivers, etc... Everything.

I'm pretty sure it's your RAM now. I had this very issue with a bad stick. You will get all sorts of disk errors as Windows will cache systems files into your RAM and the problem arises when it can't retrieve the data. I had to run diagnostics on each RAM stick individually until I found the dodgy one. It's a bit of a hassle, but, once that stick is taken out you'll be stable again but at a lower RAM speed as Double or Triple speed will not be enabled.Also, I have moved system drives to other computers, for diagnostics, and they have been fine. As the drive wont be the boot drive [as directed by the bios] the computer won't read the reg / boot entries on the newly added drive.BUT, it's always wise to have back-ups in this situation.

Thanks everybody. I'll see about my memory now.