Hello ryanmPITH, welcome to Seven Forums. I will try to help you if I can. I have not looked at all of your Dump files but did look at the last 8 or 9. They mostly had different errors and listed different causes, which I will show you below.
Code:
BugCheck 19, {3, fffffa801c750e40, fffffa801c750e40, 726f70726f636e49}
*** WARNING: Unable to verify timestamp for e1e6232e.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6232e.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c96 )
Code:
e1e6232e
start end module name
fffff880`0798f000 fffff880`079db000 e1e6232e T (no symbols)
Loaded symbol image file: e1e6232e.sys
Image path: \SystemRoot\system32\DRIVERS\e1e6232e.sys
Image name: e1e6232e.sys
Timestamp: Tue Oct 30 04:19:42 2012 (508F9BAE)
CheckSum: 0004CD07
ImageSize: 0004C000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Which is your Intel(R) PRO/1000 PCI Express Network Connection Driver and can be updated from http://downloadcenter.intel.com/Default.aspx
Code:
e1c62x64
start end module name
fffff880`08600000 fffff880`0865b000 e1c62x64 T (no symbols)
Loaded symbol image file: e1c62x64.sys
Image path: \SystemRoot\system32\DRIVERS\e1c62x64.sys
Image name: e1c62x64.sys
Timestamp: Wed Jan 11 14:30:54 2012 (4F0DF17E)
CheckSum: 0005BBF4
ImageSize: 0005B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Which is your Intel(R) 82579V Gigabit Network Connection driver
Code:
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80003381c9f, fffff8800d27ab50, 0}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
Followup: MachineOwner
Code:
nvlddmkm
start end module name
fffff880`08608000 fffff880`090a6000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Sat Dec 29 00:47:52 2012 (50DE9218)
CheckSum: 00A7F96C
ImageSize: 00A9E000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Which of course is your graphics card drivers
Code:
AvidFos
start end module name
fffff880`0e2d0000 fffff880`0e384000 AvidFos T (no symbols)
Loaded symbol image file: AvidFos.SYS
Image path: \SystemRoot\System32\Drivers\AvidFos.SYS
Image name: AvidFos.SYS
Timestamp: Mon Dec 10 23:55:11 2012 (50C6CABF)
CheckSum: 000A9792
ImageSize: 000B4000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
There was one other one which I found an Avid PDF about but little else, in a quick search.
I think you can see they were mostly different stop codes and different drivers.
I may suggest you update the 2 Intel Network drivers since they were mentioned twice. The fact that we are getting different stop codes and different reasons leads me to believe the one which says Memory Corruption. Ofthen memory corruption will cause exactly that. So, I'm going to suggest you run memtest86+ first. Due to the reason I mentioned as well as the fact that memory corruption can make everything we get in the debugger not correct, I would do that first. This will tell you how to do it. I know what a pain it can be, I've been there myself too many times. But, I think it is necessary.
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 8 complete passes 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.
If you don't understand the instructions or have any questions, don't hesitate to ask. I don't mind explaining myself at all or the instructions. I realize the time this test takes, and can appreciate you not wanting to take the time, but I really think this is needed. It has to run a minimum of 8 passes all at one time, more is better. That is what it takes for a complete test.