Still, it blames your Intel wireless card. Try disabling it in Device Manager, and see what happens.
NIS (especially older versions), is well known for causing BSODs in the BSOD-analyst community. Since it is surely monitoring all network activity, it would not surprise me at all if it were the case here.
Once you actually disable the Intel wireless card in Device Manager, or physically remove or turn off the card, the drivers should stop getting loaded. A reboot will likely be required after disabling it.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\DOCUME~1\JK\LOCALS~1\Temp\Temporary Directory 2 for Windows_NT6_BSOD_jcgriff2.zip\Windows_NT6_BSOD_jcgriff2\090310-30529-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e07000 PsLoadedModuleList = 0xfffff800`03044e50
Debug session time: Fri Sep 3 05:27:38.120 2010 (GMT-5)
System Uptime: 0 days 1:00:20.396
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {90, 2, 1, fffff88004676353}
Unable to load image \SystemRoot\system32\DRIVERS\e1k62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1k62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1k62x64.sys
Probably caused by : e1k62x64.sys ( e1k62x64+1b353 )
Followup: MachineOwner
---------