Various BSOD errors when doing certain tasks on Steam

Hello,
I keep getting the BSOD when, as of now, verifying the integrity of a game cache on Steam, or downloading on Steam. It doesn't always happen, but it happens more often than not when verifying integrity and occasionally when downloading. I get multiple different BSOD errors, which I find unusual.
A few dump logs:


On Thu 7/12/2012 5:19:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071212-24882-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFFA9007580990, 0x2, 0x0, 0xFFFFF8000318231F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 7/12/2012 2:04:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071112-28735-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x871D0)
Bugcheck code: 0x19 (0x3, 0xFFFFF88003C96540, 0xFFFFF88003C96540, 0xFFEFF88003C96540)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
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 Wed 7/11/2012 9:52:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071112-26566-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000320A9BC, 0xFFFFF8800950E590, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Wed 7/11/2012 9:52:13 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: mpfilter.sys (MpFilter+0x172E2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000320A9BC, 0xFFFFF8800950E590, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\mpfilter.sys
product: Microsoft Malware Protection
company: Microsoft Corporation
description: Microsoft antimalware file system filter driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.

A few of my specs (I'm not good at saying these, if I need more, please tell me so.)
OS: Windows 7 Home Premium x64
CPU: Intel Core i5-3570k Ivy Bridge
GPU: EVGA GeForce GTX 570
RAM: Corsair 8 GB 1600 Mhz Vengeance

The whole computer, hardware, OS and everything is only about a month old. This is a full retail version of Windows 7, which has not been re-installed.

Software Concerns:

Code:

Start Menu\Programs\ASRock Utility\AsrAppCharger

Please remove any ASRock utilities. They are not necessary for the functionality of your system and may degrade performance. USB fast charging utilities are especially problematic since they put the USB ports in an unnatural power state that may lead to instability, crashes, or blue screens.

Analysis:

Your crashes included a wide variety of BugCheck codes. This generally means a hardware issue is at fault. Run some hardware checks.

• If you are overclocking any hardware, please stop.
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!
  
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

OK, so I've removed the utility like you said so. I haven't done all of the tests yet, because I'm going to bed now. But these are the results of the tests so far:
SeaTools: Passed all the tests.
FurMark: I managed to maintain a constant temperature of about 73 degrees C. Nothing strange with the graphics.
GPU Memory Stress test: Went through the test 7 times. I didn't record the results of the first test but the second time, I had 4899 errors, third, I had 4763, fourth I had 128, fifth I had 8854, sixth I had 126, seventh I had 128.

That sounds pretty conclusive that your graphics card memory is either bad or you should at the very least contact NVIDIA to determine what they recommend.

I still have not performed every hardware test yet, I haven't had much time lately, and it's not that much of a problem (I can still play most of my games and I can do almost everything else normally), but I have determined it's not an issue with overheating by doing one of those tasks while monitoring temperatures. Something came to mind though: I cheaped out on one piece of hardware: the Wi-Fi card. Does that ever cause BSoD errors? This is what I'm using, by the way: Newegg.com - Rosewill RNX-N300 Wireless N Adapter IEEE 802.11b/g/n PCI (1T2R) Up to 300Mbps download and 150 Mbps upload Data Rates/ WPA/WPA2 (AES, 64,128-WEP with shared-key authentication) Cisco CCS V1.0, V2.0 and V3

Wireless cards may cause crashes if they are faulty. I do not know if they can also cause crashes if they are cheaply made, but I wouldn't doubt it. However, none of your crashes even vaguely resemble network issues. They are mostly indicating file system or memory issues. I suspect there may be a faulty memory module involved, but the diagnostics would need to be finished to find out. Prime95 and Memtest86+ specifically test those the best.

OK, I finally got around to Prime95, but not Memtest86+, I'll do that soon, and these are the results:
For Small FFTs and In-Place Large FFTs, the whole test went for 2 hours without error. However, for Blend, as soon as I started the test, Worker #1 and #3 displayed "FATAL ERROR: Rounding was 0.5, expected less than 0.4."

Alright, I figured out that the problem was one faulty memory module. Going to RMA my RAM. Thanks for your help.