bluescreen aswMon2.SYS 4.6.763.0

[darkfader]

Just in case you haven't got this report yet, here's debuginfo from the minidump:

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: e5bc1000, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: ba7ede6a, If non-zero, the instruction address which referenced the bad memory
   address.
Arg4: 00000000, (reserved)

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** BLAHBLAH TEXT REMOVED FROM HERE ***
*************************************************************************

MODULE_NAME:  aswMon2

FAULTING_MODULE: 80800000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  43e493a7

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 e5bc1000

FAULTING_IP:
aswMon2+2e6a
ba7ede6a f3a5             rep     movsd

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0x50

LAST_CONTROL_TRANSFER:  from ba7f13dd to ba7ede6a

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
b9711710 ba7f13dd b97117d4 00000000 84fc1860 aswMon2+0x2e6a
b971180c ba7f154c 85101ad0 851018f8 b9711843 aswMon2+0x63dd
b9711844 ba7eb7b6 85cef558 001018f8 80828c95 aswMon2+0x654c
b9711864 b9583306 85140b10 85689940 8536d308 aswMon2+0x7b6
b9711a50 b958350d 8574c718 851018f8 80828c95 FILEM701+0x8306
b9711a70 80907bfa b9711c18 86b4f018 00000000 FILEM701+0x850d
b9711b58 80902fad 86b4f030 00000000 8521bc20 nt+0x107bfa
b9711bd8 80906a15 00000000 b9711c18 00000040 nt+0x102fad
b9711c2c 8090613b 00000000 00000000 00000001 nt+0x106a15
b9711ca8 8092b2c2 032ef750 00100001 032ef708 nt+0x10613b
b9711d04 8091bd30 032ef750 00100001 032ef708 nt+0x12b2c2
b9711d44 8082337b 032ef750 00100001 032ef708 nt+0x11bd30
b9711d64 7c82ed54 badb0d00 032ef6e4 00000000 nt+0x2337b
b9711d68 badb0d00 032ef6e4 00000000 00000000 0x7c82ed54
b9711d6c 032ef6e4 00000000 00000000 00000000 rdbss+0xed00
b9711d70 00000000 00000000 00000000 00000000 0x32ef6e4


FOLLOWUP_IP:
aswMon2+2e6a
ba7ede6a f3a5             rep     movsd

SYMBOL_STACK_INDEX:  0

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  aswMon2+2e6a

IMAGE_NAME:  aswMon2.SYS

STACK_COMMAND:  kb

BUCKET_ID:  WRONG_SYMBOLS

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

[Vlk]

Just in case you haven't got this report yet, here's debuginfo from the minidump:

THE minidump? Are you talking about some specific minidump we've been discussing already?

BTW can you please send the minidump to my email address?
I'll have a look at it.


BTW are you really talking about the Server Edition of avast?
I'm asking because the version number you specified (4.6.763.0) doesn't look like a Server Edition (the latest version of Server Edition is 4.6.566).


Thanks
Vlk

[darkfader]

Probably not the one you're discussing lately.
And that's the version of the sys file.
The program version is still 4.6.566.