I also have the same problem, here is the
!analyse -v from windbg
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: 80000003, The exception code that was not handled
Arg2: 90bac966, The address that the exception occurred at
Arg3: 8078add0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
FAULTING_IP:
aswSP+4966
90bac966 cc int 3
TRAP_FRAME: 8078add0 -- (.trap 0xffffffff8078add0)
ErrCode = 00000000
eax=8650e258 ebx=00000000 ecx=889b1000 edx=00000002 esi=889b10d0 edi=889b1143
eip=90bac967 esp=8078ae44 ebp=8078ae44 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000202
aswSP+0x4967:
90bac967 56 push esi
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 830d008c to 830f9f1c
STACK_TEXT:
8078a944 830d008c 0000008e 80000003 90bac966 nt!KeBugCheckEx+0x1e
8078ad60 83059df6 8078ad7c 00000000 8078add0 nt!KiDispatchException+0x1ac
8078adc8 8305a698 8078ae44 90bac967 badb0d00 nt!CommonDispatchException+0x4a
8078adc8 90bac967 8078ae44 90bac967 badb0d00 nt!KiTrap03+0xb8
WARNING: Stack unwind information not available. Following frames may be wrong.
8078ae44 83093933 00000000 889b10d0 8650e258 aswSP+0x4967
8078ae8c 8ae7d9f9 85828d20 8078aeac 8ae7da17 nt!IopfCompleteRequest+0x128
8078ae98 8ae7da17 889b10d0 00000000 c0000185 storport!RaidCompleteRequestEx+0x1c
8078aeac 8ae8cc2e 889b10d0 c0000185 889b10d0 storport!RaidCompleteRequest+0x12
8078aeec 8ae8ce79 85828d20 8675d008 8583a9d8 storport!RaUnitAsyncError+0x196
8078af20 8ae7e31e 85828d20 8583a994 88831dcc storport!RaidUnitCompleteRequest+0x11f
8078af48 830931b5 8583a994 8583a920 00000000 storport!RaidpAdapterDpcRoutine+0x51
8078afa4 83093018 83145d20 88831d48 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 830927dc 9e587ce4 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 9e587ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
830927dc 00000000 0000001a 00d6850f bb830000 0x9e587ce4
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
aswSP+4966
90bac966 cc int 3
SYMBOL_NAME: aswSP+4966
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: aswSP
IMAGE_NAME: aswSP.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4f56a5d9
FAILURE_BUCKET_ID: 0x8E_aswSP+4966
BUCKET_ID: 0x8E_aswSP+4966
Followup: MachineOwner
---------
However, I wasn't running a game when it crashed, I had just started up Spyware Doctor to scan my system. A reboot and I was able to scan with Spyware dr. just fine. I'm running Windows 7 32bit. Avast is completely up to date as of 4-15-2012