Windows 7: Frequent crashes for the past 3 months

jai007 · 08 Mar 2012

Hi people,
I have facing this crashes for a past 3 months , i had windows 7 home premium 32 bit version which had the same problem now for time being i switched over to windows xp for trouble shooting but still the problem persists with random crashes

My specs are
AMD athlon II x2 @2.8Ghz
2*1GB transcend ddr2 ram
currently running windows xp sp2 professional 32 bit

posting my dump file along with this post , hoping for some valuable help . Really fed up because of this PC problem in the midst of my studies

Thanks in advance

writhziden · 08 Mar 2012

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\jai007\Windows_NT6_BSOD_jcgriff2\Mini030812-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Thu Mar  8 04:05:52.203 2012 (UTC - 7:00)
System Uptime: 0 days 0:20:13.778
Loading Kernel Symbols
...............................................................
.........................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {acc81a28, 0, b9dfc35c, 0}


Could not read faulting driver name
*** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys
Probably caused by : AVGIDSFilter.Sys ( AVGIDSFilter+730 )

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

0: 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: acc81a28, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: b9dfc35c, 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:  acc81a28 

FAULTING_IP: 
Ntfs!NtfsCommonRead+d2a
b9dfc35c 8b4328          mov     eax,dword ptr [ebx+28h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

LAST_CONTROL_TRANSFER:  from b9dfbfbf to b9dfc35c

STACK_TEXT:  
acc899ec b9dfbfbf acc89a00 88d41e00 00000001 Ntfs!NtfsCommonRead+0xd2a
acc89b9c 804eeeb1 8a556020 88d41e00 8a59aed8 Ntfs!NtfsFsdRead+0x22d
acc89bac b9e9d459 acc89bd8 804eeeb1 8a54a6e0 nt!IopfCallDriver+0x31
acc89bb4 804eeeb1 8a54a6e0 88d41e00 88d41fd8 sr!SrPassThrough+0x31
acc89bc4 b9eb2b2f 8928ec18 88d41e00 00000000 nt!IopfCallDriver+0x31
acc89bd8 b9eb2ffb acc89bf0 8a2cdcb8 8a5d5420 fltMgr!FltpPassThrough+0xf9
acc89c08 804eeeb1 89297490 88d41e00 8a4a2318 fltMgr!FltpDispatch+0xf3
acc89c18 ba4a8730 acc89c44 804eeeb1 8a3e1a40 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
acc89c20 804eeeb1 8a3e1a40 88d41e00 0001a400 AVGIDSFilter+0x730
acc89c30 804ef8a9 8a45a770 8a239350 8a239360 nt!IopfCallDriver+0x31
acc89c44 804ef8d1 8a3e1a40 8a23930b 8a239368 nt!IopPageReadInternal+0xf3
acc89c64 8051581e 8a2cdcb8 8a239388 8a239368 nt!IoPageRead+0x1b
acc89ce0 8051fbec e2124e58 75b7b161 c03adbd8 nt!MiDispatchFault+0x292
acc89d4c 80543568 00000008 75b7b161 00000001 nt!MmAccessFault+0x111c
acc89d4c 75b7b161 00000008 75b7b161 00000001 nt!KiTrap0E+0xd0
0052fff4 00000000 00000000 00000000 00000000 0x75b7b161


STACK_COMMAND:  kb

FOLLOWUP_IP: 
AVGIDSFilter+730
ba4a8730 ??              ???

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  AVGIDSFilter+730

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AVGIDSFilter

IMAGE_NAME:  AVGIDSFilter.Sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e1a29d0

FAILURE_BUCKET_ID:  0x50_AVGIDSFilter+730

BUCKET_ID:  0x50_AVGIDSFilter+730

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

This is SevenForums, and we are not exactly equipped to handle XP crashes, but this one was fairly straight forward. Your crash was caused by AVG. Did you have AVG installed on both 7 and XP during these crashes?

AVG is known to cause crashes on some systems. Recommend removing AVG with the AVG Remover and replace with either

Microsoft Security Essentials - Free Antivirus for Windows

or the

Good and Free system security combination.

Windows 7: Frequent crashes for the past 3 months

Frequent crashes for the past 3 months problems?