A variety of BSODs that I need help with

Specs:
Processor Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Memory (RAM) 4.00 GB
Graphics NVIDIA GeForce GTX 550 Ti
Gaming graphics 2815 MB Total available graphics memory
Primary hard disk 18GB Free (59GB Total)

Gigabyte P35-DS3L Mobo

Whocrashed Professional logs of problem:

http://pastebin.com/GGyTz3vH

Things I have done:

CHKDSK (while not in windows) - everything OK
memtest86 (no errors although I'm thinking about doing this again)
ALL drivers are updated (via windows update, not individually)
AV Scan - I have AVIRA premium w/ internet security
No Action Center things (other than backup system)
Reformatted (These are all the BSOD's since formatting)

actual minidump files from C:\Windows\Minidump

http://jsimz.com/Minidump.rar

Thanks a lot,

jsimz.

You should research the stop code(s) on the various BSOD's. That is what I would have to do for you.

No I reformatted because it was blue screening.

I don't really game anymore so desktop apps 95% of it

Not recently installed new RAM, its been in there a while

0 errors on small fft's.. testing blend now

since creating the thread I used driverscanner to get newest drivers, there were 3 I didn't have. since then i've had less blue screens but still happening

Can anyone post the BSOD Error Message/STOP code? I can't view most sites at work...

In the meantime, run memtest86 and check RAM.

I've ran memtest but yes I'm going to do it again

On Tue 2/14/2012 11:57:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021412-18564-01.dmp
uptime: 00:38:15
This was probably caused by the following module: netio.sys (NETIO+0x145E)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800173345E, 0xFFFFF880033AF998, 0xFFFFF880033AF1F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 2/14/2012 5:48:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021312-22588-01.dmp
uptime: 11:39:29
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800924EF40, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 2/9/2012 7:37:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020812-18486-01.dmp
uptime: 08:18:19
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xFC (0xFFFFF900C0613280, 0x87B0000019C55863, 0xFFFFF88008B0D240, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Your problems are almost identical to what I had a couple of weeks ago. Random BSOD's each one with a different "caused by the following module". However, mine mainly occured while running a game. I ran different programs to check the RAM and hard drive and both passed with no problems. When I ran Prime95 the Small FFT's test passed, BUT the Blend test failed, (I see you also had failures with this test). This suggested to me that it was something to do with the RAM and what I did was bump up the Northbridge voltage by its smallest increment, 0.025v. The Blend test still failed, but at a much later point in the test, so I increased it by another 0.025v. Ran the Blend test again with no failures, and my computer hasn't crashed since.

I'm not saying this is the solution to your problem, just that I had a similar problem and this is how I fixed it.