Windows 7: BSOD - Win7 when watching flash - NIC??

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\New folder\112410-33259-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;srv*e:\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`02c67000 PsLoadedModuleList = 0xfffff800`02ea4e50
Debug session time: Wed Nov 24 10:01:19.684 2010 (GMT-5)
System Uptime: 0 days 0:39:19.307
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {90, 2, 1, fffff8800467e353}

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
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000090, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800467e353, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0f0e0
 0000000000000090 

CURRENT_IRQL:  2

FAULTING_IP: 
e1k62x64+1b353
fffff880`0467e353 48899090000000  mov     qword ptr [rax+90h],rdx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800886b850 -- (.trap 0xfffff8800886b850)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8005af26b0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800467e353 rsp=fffff8800886b9e0 rbp=00000000000001bc
 r8=fffffa8007cc9700  r9=0000000000000000 r10=fffffa80084e40e0
r11=000000000000fffb r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
e1k62x64+0x1b353:
fffff880`0467e353 48899090000000  mov     qword ptr [rax+90h],rdx ds:00000000`00000090=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cd6ca9 to fffff80002cd7740

STACK_TEXT:  
fffff880`0886b708 fffff800`02cd6ca9 : 00000000`0000000a 00000000`00000090 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0886b710 fffff800`02cd5920 : 00000000`00000000 00000000`00000000 fffffa80`08b46000 00000000`000000a4 : nt!KiBugCheckDispatch+0x69
fffff880`0886b850 fffff880`0467e353 : fffffa80`085fe410 fffffa80`08ba5fa8 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x260
fffff880`0886b9e0 fffffa80`085fe410 : fffffa80`08ba5fa8 00000000`00000000 00000000`00000001 00000000`00000000 : e1k62x64+0x1b353
fffff880`0886b9e8 fffffa80`08ba5fa8 : 00000000`00000000 00000000`00000001 00000000`00000000 fffff880`046864f4 : 0xfffffa80`085fe410
fffff880`0886b9f0 00000000`00000000 : 00000000`00000001 00000000`00000000 fffff880`046864f4 00000000`00000000 : 0xfffffa80`08ba5fa8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
e1k62x64+1b353
fffff880`0467e353 48899090000000  mov     qword ptr [rax+90h],rdx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  e1k62x64+1b353

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e1k62x64

IMAGE_NAME:  e1k62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bbae4c3

FAILURE_BUCKET_ID:  X64_0xD1_e1k62x64+1b353

BUCKET_ID:  X64_0xD1_e1k62x64+1b353

Followup: MachineOwner
---------