Looks like it may be a problem with your network adapter driver. Check the manufacturer's website for a Windows 7 compatible driver. You've also got an old version of secdrv.sys (seems to be related to something from MacroVision Safe Disck Copy Protection) I don't know if it's a hold over from the upgrade or not. Did you actually do an upgrade from Vista or did you choose to do a custom clean install? Anyway here's the info from the dump, hope this helps
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\JohnSmith\Desktop\New folder\Mini-Dump-Feb02=22729-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*c:\symbols*
Symbol information Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c06000 PsLoadedModuleList = 0xfffff800`02e43e50
Debug session time: Tue Feb 2 18:19:46.019 2010 (GMT-6)
System Uptime: 0 days 1:57:38.284
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800470ca20, fffff80000b9c518, fffffa800450c730}
*** 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
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800470ca20, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa800450c730, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa800450c730
DEVICE_OBJECT: fffffa80052f3050
DRIVER_OBJECT: fffffa8005372060
IMAGE_NAME: e1k62x64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b2131f1
MODULE_NAME: e1k62x64
FAULTING_MODULE: fffff8800486a000 e1k62x64
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002ce6e23 to fffff80002c77f00
STACK_TEXT:
fffff800`00b9c4c8 fffff800`02ce6e23 : 00000000`0000009f 00000000`00000003 fffffa80`0470ca20 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02c83fa6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
fffff800`00b9c570 fffff800`02c83326 : fffffa80`05d12c10 fffffa80`05d12c10 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02c83e7e : 00000010`6f10adfb fffff800`00b9cc58 00000000`0006e763 fffff800`02df3ee8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02c83697 : 00000004`47aa34c3 00000004`0006e763 00000004`47aa3481 00000000`00000062 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02c806fa : fffff800`02df0e80 fffff800`02dfec40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_IMAGE_e1k62x64.sys
BUCKET_ID: X64_0x9F_IMAGE_e1k62x64.sys
Followup: MachineOwner
---------