[VirGnarus]

It looks like you're using the onboard network controller. The reason I mention this is because every single crash points blame on your network controller drivers. I notice your drivers for it are pretty outdated (July 2010) but it did seem like you tried to update em (older crashdumps show it being Nov 2009). Are there no drivers newer than this?

I've done some googling, and found a few others that had the exact same scenario - same crashdumps and everything. They found the network adapter itself was faulty, and by replacing it it turned out good. The problem you have is that if this is onboard, then you will have to end up replacing the whole board. It may be possible to purchase a cheap network card and use that to resolve the issue, but being onboard and having problems can be signs of a motherboard that generally has suffered in the manufacturing process. This could result in other problems occurring in the future.

Given the very consistent behavior, I personally don't think it's hardware. However, it's rather certain the drivers for that network controller aren't up to snuff, and if updating it any further isn't going to resolve things, then it's faulty hardware of a long-standing bug in the drivers, which will require you to get a replacement for either the mobo or a purchase a separate network card.

There is the small chance something else is interfering with the network drivers. You can determine by running Driver Verifier and let it crash a few more times. If it still blames your card's drivers, then my original diagnosis still stands.

 

[VirGnarus]

You manually install the drivers using the files present. You first have to uninstall the drivers you already have, then type "hdwwiz" in your Start menu to find the Add Hardware Device Wizard. Use that to discover your network controller, then manually tell it to look at the folder with the driver files inside it that you retrieved. Let it do its thing and then restart and it should be fine.

If this in itself does not work, then update BIOS and entire motherboard chipset drivers. If this still does not work, then replace the motherboard.

Btw, have you tried running Driver Verifier yet?

 

[VirGnarus]

Driver Verifier is just an extra set of checks Windows does on drivers you selected to ensure they're running ok. If a driver fails any of these checks, it will BSOD. Let DV run in the background while you use your computer normally, and if any BSODs do occur send the resulting crashdumps to us.

As this seems to confirm moreso, the network controller on your motherboard is to blame. Whether it's the drivers or the chip itself, I don't know. The only way to determine this is to send us a kernel dump (which are massive) and hopefully through long, thorough analysis the bug in the driver is found, or through replacing the motherboard and testing it on a new board.