Frequent sequence of blue screens, crashes

This is probably going to be a long one but here I go. I'm going to list everything that happened since the problems arose

My computer has been running on Windows 7 Ultimate x64 for about three years with no issues. Last week I decided to install Windows 8 Pro x64 on my build, and the installation went smoothly, as well as the installation of the latest catalyst beta drivers. When I tried to install Mumble, I ran into what seemed to be a common error in 2012, the "A referral was returned from the server" error. I attempted follow the advice on the wiki, which says to right click on the installation file, select digital signatures and then details. When I click details however, it would seem as if explorer.exe would crash and then restart. Following from there I decided to just reinstall Windows 8 again.

On the reinstall I was able to install Mumble, so I continued to launch Dota 2 and started a game. Within 3 minutes of the game starting the game crashed with no error message, and when I tried to start it again, I blue screened with a "PAGE_FAULT_IN_NONPAGED_AREA" error. I decided to try other games, and I was perfectly fine(even going so far as being able to play Transistor in one five hour sitting). Afterwards I played through some youtube videos and I blue screened again. I decided that since my blue screens were caused from things that involve my GPU, I went and downgraded to the 14.4 drivers. Same issue. I tried sfc /scannow, there were errors but sfc couldn't fix them. I ran it two more times and the same message appeared. So I tried to boot into safe mode and do it, thinking that it would have a better chance of fixing any problems. From here my memory is a bit fuzzy on the exact sequence of events, but essentially when I started up my computer Windows 8 refused to start up, saying "the header checksum does not match the computer checksum". So once again I resorted to reinstalling Windows 8, but when I booted from my disc the same error came up, even when changing the boot order in my mobo.

By this point I thought my hard drive bad sectors or something of the sort, so I booted into Gparted from my USB, and I was going to format the computer and try installing windows 8 again. When I started it up however, it said "Xz-compressed data is corrupt". I ran the memtest included in Gparted, and I was getting a painfully high number of failures on Test 7, but the version of memtest that comes with Gparted is supposedly bugged as other users on various forums noted the same thing. I tried to install Windows 8 once again, with another DVD, and I was able to get the files copied and was in the personalize process of the installation, when once again I blue screened, except this time with "NTFS_FILE_SYSTEM". So from here I assumed it was my RAM that was faulty, and I bought another set of ram: Team Vulcan 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model TLD38G1600HC9DC01 - Newegg.com

When it arrived, I replaced my previous set of ram(GeIL Value PLUS 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model GVP34GB1600C9DC - Newegg.com) and I decided to just continue with the Windows 8 installed before. Everything was fine, I went through about 50 turns in Civilization V without blue screening...and I tried running Dota 2 again later on that night. The game froze as soon as my match started but I could still hear audio and click on the screen(I heard the sound of the menu transitions). I figure this was an issue with either the game or my driver installation, because a reinstall of my GPU drivers fixed the problem. I started a game with bots, went for about 10 minutes and no blue screens, start a real match...multiple crashes with no errors, sometimes it would blue screen me with the error "IRQL_NOT_LESS_OR_EQUAL". I ran chkdsk, sfc /scannow, and went back to the 13.12 catalyst drivers; no go. This is the current state of my computer. I'm all out of options, and my usually go-to fixer of reinstalling the OS(which I do quite a bit, now thinking back on it!) hasn't worked. Using BlueScreenView, everytime I blue screen ntoskrnl.exe is at the end of the stack. Everything inside is safely in place, the only thing I can maybe think of now is either:

1) The RAM I ordered came DOA, or
2) My hard drive is faulty

And I can't prove either because I don't have a second computer to try either component. Any help is tremendously appreciated.

I've recently tried installing Windows 7 again, upon the expanding windows files set it says "Windows can not be installed because some files are missing or corrupt". I'm currently trying to prepare a DVD and seeing if that works, because I'm using a USB at the moment. My Windows 8 install is now gone and my hard drive is formatted.

Summary: Thought 4GB ram went bad, bought 8GB ram, same blue screen problems. Only happens when watching videos or Dota 2, haven't tried many other games but Civilization V and Transistor worked.

Yes, I've been switching back and forth between the beta and latest stable release with the same issue. When I tried the 13.12 driver I was completely stumped, because that was the last driver I used on windows 7 and I was fine then.

Test the HD with maker's Hard Drive Diagnostic Procedure extended CD scan.

I'd test the RAM - Test with Memtest86+ for 7 passes or overnight to stress it. The tutorial shows how to do the job completely.

Compare the install you have with the perfect install in Clean Reinstall - Factory OEM Windows 7 especially how drivers are best handled in Win7, the tools and methods which work best in tens of thousands of installs we've helped with here since Win7 beta.

What drivers did WIn7 want after install when you enabled Device Installation Settings then ran all Important and Optional Windows Updates, with reboots, until there are no more offered? This is different than XP so gets users in trouble when they use older methods. OEM drivers are vetted in MS Hardware labs before loading into Updates.

It's been 3 days since I installed windows 7 and everything had been going good. SeaTools reported nothing wrong with my hard drive, and after updating the only drivers Windows wanted to install were my Razer Deathadder drivers. I have played several hours of Fallout: New Vegas, Civilization V and Team Fortress 2. The blue screens went down dramatically and only happened on a regular basis when playing Dota 2, but even then it wasn't reporting the blue screens as my power supply went off before it could finish. I checked my temperatures and my CPU was running at 72 Celsius on idle, so I went in and reapplied thermal paste, as well as moving the RAM sticks over to the other color on my motherboard for good measure. All of the blue screens that were reported was caused by the AMD graphics driver. I'm running on 13.12, which was the last stable version for me when my computer wasn't acting like this. There are other users on the AMD/Firefox forums who are having the same blue screens as me, but they have the latest drivers, 14.4, installed and switching back to 13.12 seemed to fix their problem completely, but not for me. I had been building a collection of blue screens before posting again because I was getting them less regularly, but then last night happened.

I blue screened last night and decided to run driver verifier to try to check it, following the instructions on this site. When I restarted I noticed I couldn't boot: the mouse cursor would appear on a black screen, and I could move the cursor around for about 5 seconds before it seemed to froze. So I went into safe mode and disabled it. I'm not sure if that was necessary information, but I'm just going to supply everything I've done.

I continued on and didn't get any blue screens until a game of Civilization V. After around turn 100 the game crashed, and immediately after Mumble crashed as well. I decided this would be a good break point for the night so I went to get something to eat, and when I came back I noticed that my computer was on a blue screen, but it was frozen and not completing the dump log. I restarted the computer, checked BlueScreenView, and was shocked when I realized that in the course of the 30 minutes I had been away from my computer, 5 blue screens happened back to back! So I decided to collect all of the dump files with the forum's dump/system info collection tool, and a message came up saying "Windows DOM server has closed and the computer needs to be restarted". I had to restart my computer around 10 times before I was not only allowed to boot into Windows(it was blue screening on startup), but also given enough time in Windows where I could run the collection tool and upload the zip file online, so I could post it. I ran memtest immediately after. I'm just waking up now, and memtest went through 4 passes, with all of the errors(9000+) on test 8. Attached it my collection of dumps, but it doesn't have some of the earlier ones as I was in such a panic I tried keeping all the files on my desktop, as when the DOM server crashed or something else the tool would get rid of the files it already obtained by deleting the folder.

EDIT: I should probably say that at the moment I can't boot into Windows at all. I booted into startup repair but noticed neither my mouse or keyboard were working, so I restarted my computer and tried running it again but it wouldn't let me. When I rebooted again a message appears saying "The file is possibly corrupt. The file header checksum does not match the computed checksum."

While you wait for BSOD analysis isolate the problem RAM stick or slot as shown in RAM - Test with Memtest86+.

Try running without the known-bad stick. Check slots for debris. Swap slots to test again per tutorial.

Code:

BugCheck 50, {ffffffffffffffff, 1, fffff88002d868aa, 0}

This bugcheck indicates a page fault in non paged memory has occurred, more specifically invalid memory was referenced.

Looking at the address being referenced I can see that it's completely invalid (1st parameter).

Unfortunately due to the nature of this dump file (minidump) I cannot check the page table entries although I find it unnecessary as it's pretty clear bad RAM is the cause.

Again with the other bugcheck I see this.

Code:

X64_0x7E_BAD_IP_nt!CmpDoCreate+e7

A bad instruction pointer, more evidence for bad RAM.