Bluescreen, unscertainty.

Avast Free Antivirus / Premium Security
1

I’ve recently been getting bluescreens, originally I thought it had to do with me trying to get rid of old ATI drivers since I got a new Nvidia GPU but only earlier this morning did I take it upon myself to look through the dump file.

I was a bit confused when it said "Process_name: avast.setup

Though the way it’s worded it makes me think that this is just telling me avast isn’t allowing me to see the debug and thus giving me info about that, but I am uncertain about it so here is the log and maybe someone can be of a some help.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e0207482, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8bdd5203, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from 83780718
Unable to read MiSystemVaType memory at 83760180
 e0207482 

FAULTING_IP: 
aswSP+2c203
8bdd5203 0fb74e18        movzx   ecx,word ptr [esi+18h]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  avast.setup

CURRENT_IRQL:  0

TRAP_FRAME:  8a227614 -- (.trap 0xffffffff8a227614)
ErrCode = 00000000
eax=00000000 ebx=e020746a ecx=89441008 edx=00000000 esi=e020746a edi=00000034
eip=8bdd5203 esp=8a227688 ebp=8a2277f0 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
aswSP+0x2c203:
8bdd5203 0fb74e18        movzx   ecx,word ptr [esi+18h]   ds:0023:e0207482=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8365e5d8 to 8369da23

STACK_TEXT:  
8a2275fc 8365e5d8 00000000 e0207482 00000000 nt!MmAccessFault+0x106
8a2275fc 8bdd5203 00000000 e0207482 00000000 nt!KiTrap0E+0xdc
WARNING: Stack unwind information not available. Following frames may be wrong.
8a2277f0 8bdb6db8 e020746a 00000000 89441008 aswSP+0x2c203
8a22784c 8bdb7ad5 e020746a 8a227880 8a227a70 aswSP+0xddb8
8a22789c 8bdbb24a c46c93b8 8a227908 01fcfc22 aswSP+0xead5
8a2278fc 838b6978 00000000 0000001d 8a22799c aswSP+0x1224a
8a227970 83856fd1 0000001d bd1e2488 918aa900 nt!CmpCallCallBacks+0x336
8a2279b8 8384ff6e 0000001d ad3026d0 8a227a70 nt!CmPostCallbackNotification+0x55
8a227b48 838395f3 8cc0aaf8 85de4980 85f2ca90 nt!CmpParseKey+0x14b2
8a227bc4 8385f7b9 00000000 8a227c18 00000040 nt!ObpLookupObjectName+0x4fa
8a227c20 83856f04 0012df6c 85de4980 8a227d01 nt!ObOpenObjectByName+0x165
8a227d00 83851c57 0012e05c 00020019 0012df6c nt!CmOpenKey+0x1f4
8a227d1c 8365b3ea 0012e05c 00020019 0012df6c nt!NtOpenKeyEx+0x18
8a227d1c 76e16344 0012e05c 00020019 0012df6c nt!KiFastCallEntry+0x12a
0012dfac 00000000 00000000 00000000 00000000 0x76e16344


STACK_COMMAND:  kb

FOLLOWUP_IP: 
aswSP+2c203
8bdd5203 0fb74e18        movzx   ecx,word ptr [esi+18h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  aswSP+2c203

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSP

IMAGE_NAME:  aswSP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4d65202b

FAILURE_BUCKET_ID:  0x50_aswSP+2c203

BUCKET_ID:  0x50_aswSP+2c203

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

Here is the dump file if anyone wants to take a look for themselves.

http://www.mediafire.com/file/aeer8c2uoubrfwh/092511-31403-01.dmp

2

Hi Rainbow Dash,

I’m just a forum member, but I’ve done alot of Avast installations and I’ve seen BSOD’s from Avast before.

What Operating System do you run?

What you can try is disabling Auto-Sandboxing temporarily and see if you notice any change.

Regards,
Hellion

EDIT: Disregard my OS Question, I can see you are running VISTA from the data provided.

3

Hi!
Try update to newer version. This should help.

4

Updating to the newer program version could be tricky, if avast.setup is part of the problem. You could download the latest version from Avast’s website and run it, instead of trying to update from inside the main GUI of Avast.

5

Windows 7, 32bit actually, I wonder why it says vista. :x
and it seems I already had sandboxing turned off already, though now I’m curious why that might have caused issues?

I was able to update it through the built in updater, and I have yet to have the issue so I think that may have done the trick, maybe there was something conflicting with it and the newer nvidia driver I had, since it only ever did this when I was A. watching videos in SMplayer, B. On youtube, or C. playing a game.

Hopefully that did the trick but I’ll post back if it happens again :x