Windows Crash

Avast Free Antivirus / Premium Security
1

Good morning,

Lately my system is experiencing frequent crashes. I’m currently running a Win XP Pro SP2 machine with a P4 2.40GHz processor and 1.5Gb of RAM and Avast 4.7 Home edition.

Following is the minidump. Although the offending process is mediaserver.exe, it has a reference to avast and I was wondering if anybody would be able to help me.

Thanks in advance.

  •                                                                         *

  •                    Bugcheck Analysis                                    *

  •                                                                         *

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {a3ab38b3, 0, 804f3e24, 0}

Could not read faulting driver name
Unable to load image aswMon2.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
Probably caused by : aswMon2.SYS ( aswMon2+6a93 )

Followup: MachineOwner

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: a3ab38b3, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 804f3e24, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

Debugging Details:

Could not read faulting driver name

READ_ADDRESS: a3ab38b3

FAULTING_IP:
nt!MmUnmapViewInSystemCache+55
804f3e24 8b30 mov esi,dword ptr [eax]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: MediaServer.exe

LAST_CONTROL_TRANSFER: from 80566678 to 804f3e24

STACK_TEXT:
af58ca68 80566678 ffff0000 b7204c0d 00000000 nt!MmUnmapViewInSystemCache+0x55
af58ca80 80519e91 898fb5a8 f7b553ac 00000000 nt!CcUnmapVacb+0x2a
af58cb08 804f451d 88591550 004ac02a 00000000 nt!CcGetVacbMiss+0x1eb
af58cb40 80578c2a 00591550 004ac02a 00000000 nt!CcGetVirtualAddress+0x94
af58cbdc f7b72cc8 885059e0 004ac02a 00000080 nt!CcFastCopyRead+0x279
af58cc34 f746f9a2 885059e0 af58ccc8 00000080 Ntfs!NtfsCopyReadA+0x1bf
af58cc5c af841a93 885059e0 af58ccc8 00008000 sr!SrFastIoRead+0x40
WARNING: Stack unwind information not available. Following frames may be wrong.
af58cc8c 80571373 885059e0 af58ccc8 00008000 aswMon2+0x6a93
af58cd38 804de7ec 00000304 00000000 00000000 nt!NtReadFile+0x2d5
af58cd38 7c90eb94 00000304 00000000 00000000 nt!KiFastCallEntry+0xf8
0185c8ec 00000000 00000000 00000000 00000000 0x7c90eb94

STACK_COMMAND: kb

FOLLOWUP_IP:
aswMon2+6a93
af841a93 ?? ???

SYMBOL_STACK_INDEX: 7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: aswMon2

IMAGE_NAME: aswMon2.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4501a829

SYMBOL_NAME: aswMon2+6a93

FAILURE_BUCKET_ID: 0x50_aswMon2+6a93

BUCKET_ID: 0x50_aswMon2+6a93

Followup: MachineOwner

2

The aswMon2 function on the stack is just the filter passthrough routine, so I wouldn’t say the problem has anything to do with it (even though the only way to be really sure is to uninstall avast and see if the problem stops happening).

What I’d suggest is try to run a memory test on your machine.

If you have a CD burner, the best way is to download, burn and boot from the MemTest86+ CD http://www.memtest.org (or I think there’s a version that filts on a floppy as well).

It’s free and works extremely well.

Let it run overnight and see if it reports any problems.

Thanks
Vlk

3

Thanks Vlk,

Reading another post online I saw that the problem could be related to my media server (TVersity). Apparently installing Windows Media Player 11 the issue could possibly be solved.

Will try installing WMP11 and running memtest as well.

Will keep you posted and thanks again for the suggestion.

4

Vlk you were right.

Faulty Ram is the cause of my crashes. Luckyly Kingston offers a lifetime warranty :slight_smile:

Thanks for your help.

Marc