Author Topic: BSOD in aswSP.sys  (Read 2814 times)

0 Members and 1 Guest are viewing this topic.

tamras

  • Guest
BSOD in aswSP.sys
« on: August 03, 2011, 09:09:47 AM »
I have a Windows XP SP3 system with avast free installed.  Today, it updated the program to 6.0.1203.  This evening it blue-screened in aswSP.sys.  I have a minidump which shows the following:
*******************************************************************************
*                                                                             *
*                        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: 00000025, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: b0c47c73, address which referenced memory

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


WRITE_ADDRESS:  00000025

CURRENT_IRQL:  2

FAULTING_IP:
aswSP+1fc73
b0c47c73 f00fc111        lock xadd dword ptr [ecx],edx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  AvastSvc.exe

LAST_CONTROL_TRANSFER:  from b0c47e57 to b0c47c73

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
ae075af0 b0c47e57 0000001d 8920f2a8 88bce008 aswSP+0x1fc73
ae075b04 b0c46dc0 b0c6bf68 1ec1cdc8 00000000 aswSP+0x1fe57
ae075b44 b0c470ff 00000012 8a92c388 88c7cd70 aswSP+0x1edc0
ae075b60 804ef19f 8a92c388 88c7cd70 8a8b2818 aswSP+0x1f0ff
ae075b70 b9ee5bbf 00000000 892bfdb8 ae075bc8 nt!IopfCallDriver+0x31
ae075b80 804ef19f 8a8f9480 88c7cd70 8a5eb590 sr!SrCleanup+0xb3
ae075b90 b9d1e2d7 804ef19f 8a5a9ed0 88c7cd70 nt!IopfCallDriver+0x31
ae075bc8 b9ef706b ae075be8 8a6dd4a8 00000000 OsaFsLoc+0x12d7
ae075c00 804ef19f 8a6dd4a8 88c7cd70 88c7cffc fltmgr!FltpDispatch+0x11f
ae075c10 ae467be7 8a756de8 8a71c4d8 88c7cd80 nt!IopfCallDriver+0x31
ae075c34 ae461a34 8a6eea00 88c7cd70 ae075c84 aswMon2+0x6be7
ae075c44 804ef19f 8a6eea00 88c7cd70 88c7cd70 aswMon2+0xa34
ae075c54 80583979 8a756dd0 00000038 8a966900 nt!IopfCallDriver+0x31
ae075c84 805bca4e 8a6e42a0 8a6eea00 00120189 nt!IopCloseFile+0x26b
ae075cb8 805bc377 8a6e42a0 00000001 8a966900 nt!ObpDecrementHandleCount+0xd8
ae075ce0 805bc415 e1a4f368 8a756de8 00000f3c nt!ObpCloseHandleTableEntry+0x14d
ae075d28 805bc54d 00000f3c 00000001 00000000 nt!ObpCloseHandle+0x87
ae075d3c b0c39bc9 00000f3c ae075d64 033d50c4 nt!NtClose+0x1d
ae075d58 8054167c 00000f3c 033d50c4 7c90e514 aswSP+0x11bc9
ae075d58 7c90e514 00000f3c 033d50c4 7c90e514 nt!KiFastCallEntry+0xfc
033d50c4 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

FOLLOWUP_IP:
aswSP+1fc73
b0c47c73 f00fc111        lock xadd dword ptr [ecx],edx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  aswSP+1fc73

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSP

IMAGE_NAME:  aswSP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4e11a5be

FAILURE_BUCKET_ID:  0xD1_W_aswSP+1fc73

BUCKET_ID:  0xD1_W_aswSP+1fc73

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

Cheers,
Tamra

Offline pk

  • Avast team
  • Super Poster
  • *
  • Posts: 2078
Re: BSOD in aswSP.sys
« Reply #1 on: August 03, 2011, 12:17:33 PM »
type: aswsp!LockItem+0x1f crash

unfortunately, this bsod will not get fixed - see this thread: http://forum.avast.com/index.php?topic=81278.msg664526#msg664526 (BarbaBookie msg + vlk reply)

bibik

  • Guest
Re: BSOD in aswSP.sys
« Reply #2 on: September 15, 2011, 01:27:04 PM »
I'm also having BSOD caused by aswsp.sys on both computers running Windows XP SP3. >:(
New Avast free version 6.0.1289 did not solve the problem
Will it be fixed any time soon? 
Many thanks.

ady4um

  • Guest
Re: BSOD in aswSP.sys
« Reply #3 on: September 15, 2011, 03:15:46 PM »
@bibik,

Your BSOD might be different from the one presented above in the OP. Please open a separate topic and report all your details: OS, SP, x32 / x64, memory dump, additional info...

If you have a mini memory dump, you could also use BlueScreenView to get more info and post it in your new topic (not here, unless you already KNOW that it is EXACTLY the same BSOD, in which case you already have your answer).