According to this, one of the drivers on your network stack is behaving badly (access violation in kernel mode referencing nonpaged pool memory == immediate bugcheck):
Code:
3: kd> .bugcheck
Bugcheck code 1000007E
Arguments c0000005 964cc0a3 baaa3a1c baaa3600
3: kd> kn
# ChildEBP RetAddr
00 baaa3b98 8b0308f7 athur+0x790a3
01 baaa3c50 82c1bfda ndis!ndisDereferenceULongRef+0x1f
02 baaa3c90 82ac41f9 nt!PspSystemThreadStartup+0x9e
03 00000000 00000000 nt!KiThreadStartup+0x19
3: kd> lmvm athur
start end module name
96453000 965d5000 athur T (no symbols)
Loaded symbol image file: athur.sys
Image path: \SystemRoot\system32\DRIVERS\athur.sys
Image name: athur.sys
Timestamp: Mon Oct 11 05:09:09 2010 (4CB2D435)
CheckSum: 00180865
ImageSize: 00182000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
The driver in question (athur.sys) is the Atheros extensible WiFi device driver, meaning it's likely you have an Atheros-based WiFi card in that system, which is odd for a desktop system:
Code:
3: kd> !sysinfo smbios
...
Vendor American Megatrends Inc.
BIOS Version A48F1P02
BIOS Starting Address Segment f000
BIOS Release Date 09/07/2011
...
Manufacturer Novatech Ltd
Product Name Desktop PC
Version V1.0
...
Manufacturer Foxconn
Product H67M-S/H67M-V/H67
I can't see anything about the global object table or device specific settings from a minidump, but if you've got a WiFi adapter in there, it's driver is behaving badly it would seem.
Quote