BSOD When Downloading Large Files From Browser

Here's what I found via BlueScreenView...

The 7/8/2014 1:01:31 AM minidump shows the following filenames in red:
athrx.sys
ndis.sys
ntoskrnl.exe
tcpip.sys

^ I've done some searching and it seems this is related to LAN/Wifi drivers.

The 7/8/2014 1:13:07 AM show the following filename in red:
ntoskrnl.exe

^ This could be related to a myriad of different things.

Mind you, when I did a clean install of Windows 7 64bit a few months back, I never bothered to install any third party drivers as Windows took care of most of that.

Any help on pin-pointing the problem would be greatly appreciated. I've gone ahead and attached the minidump files, SF Diagnostic Tool zip file, as well as the BlueScreenView screenshots.

*Note, my laptop is not overclocked and is not overheating.

System Info:
OS Name: Microsoft Windows 7 Home Premium
OS Version: 6.1.7601 Service Pack 1 Build 7601
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
System Manufacturer: Acer
System Model: Aspire 5532
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: AMD64 Family 15 Model 124 Stepping 2 AuthenticAMD ~1600 Mhz
BIOS Version: Acer V1.09, 11/30/2009
Total Physical Memory: 2,812 MB
Available Physical Memory: 888 MB
Virtual Memory: Max Size: 5,622 MB
Virtual Memory: Available: 3,019 MB
Virtual Memory: In Use: 2,603 MB

Code:

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 82b3b943, address which referenced memory

Bug Check 0xC5: DRIVER_CORRUPTED_EXPOOL (Windows Debuggers)

The kernel attempted to access pageable memory (or perhaps completely invalid memory) when the IRQL was too high. The ultimate cause of this problem is almost certainly a driver that has corrupted the system pool.

If you get no help from that try enabling Driver Verifier,

   Information

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode

I ran Verifier for a good 23 hours to see if I could force a BSOD, but so far, everything has been okay. Ran several CPU intensive apps, still nothing.

Will report back if I do receive a BSOD.

Attachment 325778After almost a week of no BSOD's, I finally received one. I've provided a dm log. Any help would be greatly appreciated!

EDIT: Checked out the .dmp file myself and found that I needed to update my Aethors Wireless LAN driver. I will report back if I experience any BSOD's but i'm calling this one solved.