Hello tizbad2k, I will try to help you with this problem. For Some reason the files you uploaded did not all come through. Please re run the BSOD posting instructions (Blue Screen of Death (BSOD) Posting Instructions) and use #2 this time and click the 'Grab All' button and give it long enough to do it's collection. Sometimes it can take a few minutes.
You are correct that all the dumps are a different Stop code. One thing I noticed was in all the dumps, there were references to the file system and I/O procedures. That leads me to believe there may be problems with your hard drives. Please run check disk Disk Check on your mechanical drives and make sure your OCZ SSD's firmware is up to date.
Also please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
Several reasons were given in your dump files. I only had time to look at the last 5 or 6 right now,
Code:
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffff8a01b1ef010, fffff8a01b1ef010, fffff8a01047fbe0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cbb )
Followup: Pool_corruption
Code:
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffff8a00e8831a0, fffff8a00e883360, 51c0202}
GetPointerFromAddress: unable to read from fffff800030c7100
GetUlongFromAddress: unable to read from fffff800030c71c0
Probably caused by : fltmgr.sys ( fltmgr!DoFreeContextMemory+6b )
Code:
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a014967b60, 1, fffff880012ae9ab, 0}
Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!NtfsFullDeleteLcb+bb )
Followup: MachineOwner
These last 2 relate directly to your hard drive or the file system, and the first one can. However, the one that is concerning me most is the next one. It can cause any type of error at any time, and you having a different error each time is indicative of this error. Until we rule out the next error, none of the information in the dump files id reliable.
Code:
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {2, 2e24e, 127fff, 1}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8d )
Followup: MachineOwner
In order to rule this out you will need to test it, and it will take a lot of time.
Please Run Memtest86+
Information
Please download from this site only
http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip
Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for a minimum of 8 complete passes all at the same time or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask