It looks like Avast is causing the problem. Uninstall completely and download a fresh copy, or install Microsoft Security Essentials instead.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp6_Minidump.zip\040910-10982-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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`01c58000 PsLoadedModuleList = 0xfffff800`01e95e50
Debug session time: Fri Apr 9 12:28:21.091 2010 (GMT-4)
System Uptime: 0 days 2:30:17.230
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
......
Unable to load image aswMonFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800d13b69b, fffff88002174a98, fffff880021742f0}
Probably caused by : aswMonFlt.sys ( aswMonFlt+569b )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800d13b69b, The address that the exception occurred at
Arg3: fffff88002174a98, Exception Record Address
Arg4: fffff880021742f0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
aswMonFlt+569b
fffff880`0d13b69b 49396a20 cmp qword ptr [r10+20h],rbp
EXCEPTION_RECORD: fffff88002174a98 -- (.exr 0xfffff88002174a98)
ExceptionAddress: fffff8800d13b69b (aswMonFlt+0x000000000000569b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880021742f0 -- (.cxr 0xfffff880021742f0)
rax=ffebfffffffffffb rbx=0000000000003080 rcx=fffff8800d148b00
rdx=0000000000000000 rsi=fffff8a010a00000 rdi=fffff8a00130d258
rip=fffff8800d13b69b rsp=fffff88002174cd0 rbp=01cad7e885d0ad21
r8=0000000000000000 r9=000000000000744b r10=ff5ff8a0109fffd8
r11=0000000000004000 r12=fffff8a0012d3000 r13=fffff8a00e5da000
r14=0000000000000000 r15=fffff88001e61f40
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
aswMonFlt+0x569b:
fffff880`0d13b69b 49396a20 cmp qword ptr [r10+20h],rbp ds:002b:ff5ff8a0`109ffff8=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001f000e0
ffffffffffffffff
FOLLOWUP_IP:
aswMonFlt+569b
fffff880`0d13b69b 49396a20 cmp qword ptr [r10+20h],rbp
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88001e61f40 to fffff8800d13b69b
STACK_TEXT:
fffff880`02174cd0 fffff880`01e61f40 : 00000000`00000000 fffff880`0d13b920 00000000`00000000 00000000`00000000 : aswMonFlt+0x569b
fffff880`02174cd8 00000000`00000000 : fffff880`0d13b920 00000000`00000000 00000000`00000000 fffff880`0d13b920 : 0xfffff880`01e61f40
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: aswMonFlt+569b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: aswMonFlt
IMAGE_NAME: aswMonFlt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b0c7123
STACK_COMMAND: .cxr 0xfffff880021742f0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_aswMonFlt+569b
BUCKET_ID: X64_0x7E_aswMonFlt+569b
Followup: MachineOwner
---------