It sounds like one of the filters from the network manager is still active. Download the 64-bit version of the killer cleaner found at Driver Downloads | Qualcomm Atheros, Inc. and the latest drivers for e2200/wireless-N 1102 (64-bit).
Manually uninstall the drivers I had you install. Reboot.
Run the killer cleaner. Reboot.
Install the latest drivers. Reboot.
Uninstall the latest drivers from the Uninstall Programs in your control panel. Reboot.
Run the kill cleaner again. Reboot.
Install the drivers I had you manually install.
I realize that it's a pain, but wireless-N driver is causing the crash. This is usually because one of the filters installed by Killer Network Manager is still left behind.
I still haven't had any crashes for a while now. However, I will never say never.
ectech - FFFFFFF9 is the standard IRQ to be used for the Qualcomm Atheros Wireless-N 1102. I'm pretty sure it's a virtual device that is sharing the same hardware along with the Qualcomm Atheros e2200. Which is why, both wired or wireless will cause the same issues when put under high load.
My personal opinion is that it is a design flaw either in the driver or the device itself. To make it worse, Bigfoot (the original design manufacturer) was acquired by Qualcomm and has since shut down the website as of the 1/1/2014. This is why killergaming.com has been down for the past week. Hopefully, Qualcomm provides a fix.
What I have noticed is that the driver wants to manage the Windows TCP/IP stack for all applications. So programs that have their own process management for network activity seem to be at higher risk in causing a problem with the drivers. A perfect example of this is either chrome.exe or steam.exe. Both of which use an internal task management and memory system that split the multiple downloads into separate tasks (in the case of chrome) or threads (in the case of steam). Which would explain a lot of the wacky BSODs I used to get (KERNEL_SECURITY_CHECK_FAILURE, DRIVER_IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, IRQL_NOT_LESS_OR_EQUAL) all of which would point to either the killer drivers themselves or the tcpip.sys.
It's actually a common theme with various MSI laptops once you start putting them through their paces. You can try RMA'ing the laptop, but since it's intermittent and usually happens only when the NIC or WLAN is put under heavy load - I think you will get the laptop or replacement in the same condition.
Because this laptop cost me $2600 - if it happens again to myself, I will be removing (or disabling) the onboard LAN/WLAN and installing my own. I really don't want to be reduced down to a USB wireless network adapter.