Hi kelvin and welcome to the forum. I looked at your two most recent dumps. The third dump is from last October.
Bugcheck 50, PAGE_FAULT_IN_NONPAGED_AREA. Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.
This dump blames AsDsm.sys, Asus Data Security Manager Drive, and shows AVG was involved in the crash.
Bugcheck C2, BAD_POOL_CALLER. Usual causes: Device driver, ?Memory
This dump blames a Windows system driver, which is highly unlikely to be the real cause. Something else is causing a conflict.
1. Update this driver through the link provided; it is slightly out of date.2. Uninstall AVG using this removal tool: Tool (64 bit). If you have Identity protection installed, remove it with this tool: Tool. Though your version of AVG is up todate, AVG is know to cuase problems on some Win 7 systems. Download and install Microsoft Security Essentials in its place. Once your system is stable, you can try AVG again.
3. Update your OS by installing Service Pack 1: http://windows.microsoft.com/en-US/w...ice-pack-1-sp1
Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02e10000 PsLoadedModuleList = 0xfffff800`0304de50
Debug session time: Sat Apr 23 21:39:29.538 2011 (GMT-4)
System Uptime: 2 days 2:15:57.161
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a003c76000, 1, fffff880011ed363, 0}
Unable to load image \SystemRoot\System32\Drivers\AsDsm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AsDsm.sys
*** ERROR: Module load completed but symbols could not be loaded for AsDsm.sys
Could not read faulting driver name
Probably caused by : AsDsm.sys ( AsDsm+2363 )
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: fffff8a003c76000, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff880011ed363, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b80e0
fffff8a003c76000
FAULTING_IP:
AsDsm+2363
fffff880`011ed363 488901 mov qword ptr [rcx],rax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: AVGIDSAgent.ex
CURRENT_IRQL: 0
TRAP_FRAME: fffff880087ba3a0 -- (.trap 0xfffff880087ba3a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0031006500700069 rbx=0000000000000000 rcx=fffff8a003c76000
rdx=000001e007d49424 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880011ed363 rsp=fffff880087ba538 rbp=fffffa800b9bf024
r8=000000000000000c r9=0000000000000001 r10=0070005f00340036
r11=fffff8a003c75c00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
AsDsm+0x2363:
fffff880`011ed363 488901 mov qword ptr [rcx],rax ds:bae0:fffff8a0`03c76000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002f00f14 to fffff80002e80740
STACK_TEXT:
fffff880`087ba238 fffff800`02f00f14 : 00000000`00000050 fffff8a0`03c76000 00000000`00000001 fffff880`087ba3a0 : nt!KeBugCheckEx
fffff880`087ba240 fffff800`02e7e82e : 00000000`00000001 fffff8a0`00081ad0 fffffa80`04b54b00 fffffa80`0b08bae0 : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`087ba3a0 fffff880`011ed363 : fffff880`011ec724 00000000`0000074d fffff8a0`00081ad0 fffffa80`04b549c0 : nt!KiPageFault+0x16e
fffff880`087ba538 fffff880`011ec724 : 00000000`0000074d fffff8a0`00081ad0 fffffa80`04b549c0 00000000`000007ff : AsDsm+0x2363
fffff880`087ba540 00000000`0000074d : fffff8a0`00081ad0 fffffa80`04b549c0 00000000`000007ff fffff880`011ef140 : AsDsm+0x1724
fffff880`087ba548 fffff8a0`00081ad0 : fffffa80`04b549c0 00000000`000007ff fffff880`011ef140 fffff880`087ba5a0 : 0x74d
fffff880`087ba550 fffffa80`04b549c0 : 00000000`000007ff fffff880`011ef140 fffff880`087ba5a0 fffff880`011ef1c0 : 0xfffff8a0`00081ad0
fffff880`087ba558 00000000`000007ff : fffff880`011ef140 fffff880`087ba5a0 fffff880`011ef1c0 00000000`00000000 : 0xfffffa80`04b549c0
fffff880`087ba560 fffff880`011ef140 : fffff880`087ba5a0 fffff880`011ef1c0 00000000`00000000 fffffa80`0b08bae0 : 0x7ff
fffff880`087ba568 fffff880`087ba5a0 : fffff880`011ef1c0 00000000`00000000 fffffa80`0b08bae0 fffffa80`04b549c0 : AsDsm+0x4140
fffff880`087ba570 fffff880`011ef1c0 : 00000000`00000000 fffffa80`0b08bae0 fffffa80`04b549c0 fffffa80`04b54b10 : 0xfffff880`087ba5a0
fffff880`087ba578 00000000`00000000 : fffffa80`0b08bae0 fffffa80`04b549c0 fffffa80`04b54b10 fffff880`011f29ff : AsDsm+0x41c0
STACK_COMMAND: kb
FOLLOWUP_IP:
AsDsm+2363
fffff880`011ed363 488901 mov qword ptr [rcx],rax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: AsDsm+2363
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AsDsm
IMAGE_NAME: AsDsm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49950fc2
FAILURE_BUCKET_ID: X64_0x50_AsDsm+2363
BUCKET_ID: X64_0x50_AsDsm+2363
Followup: MachineOwner
---------
Debug session time: Tue Mar 29 18:51:31.886 2011 (GMT-4)
System Uptime: 1 days 5:39:57.493
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, 1097, 61004200, 200001}
Probably caused by : win32k.sys ( win32k!RFONTOBJ::vDeleteRFONT+353 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 0000000061004200, Memory contents of the pool block
Arg4: 0000000000200001, Address of the block of pool being deallocated
Debugging Details:
------------------
BUGCHECK_STR: 0xc2_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: aim.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002e0760e to fffff80002cd4740
STACK_TEXT:
fffff880`07349f78 fffff800`02e0760e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`61004200 : nt!KeBugCheckEx
fffff880`07349f80 fffff960`00291597 : 00000000`00000001 fffffa80`06c9b8a0 fffff880`20626747 fffff880`00000001 : nt!ExDeferredFreePool+0x11eb
fffff880`0734a030 fffff960`000b7ad3 : fffff900`c00bf010 fffff900`c1fcc010 fffff900`c008a010 fffff960`00262888 : win32k!RFONTOBJ::vDeleteRFONT+0x353
fffff880`0734a0a0 fffff960`000b7507 : fffff900`c077eca0 fffff880`0734a140 fffff900`c077eca0 00000000`62010eaa : win32k!RFONTOBJ::bMakeInactiveHelper+0x427
fffff880`0734a120 fffff960`001061b5 : fffff880`0734a300 fffff880`0734a300 00000000`62010eaa 00000000`00000001 : win32k!RFONTOBJ::vMakeInactive+0xa3
fffff880`0734a1c0 fffff960`0023c991 : fffff880`0734a300 00000000`00000000 00000000`00000000 fffff900`c1fdc010 : win32k!XDCOBJ::bCleanDC+0x36d
fffff880`0734a280 fffff960`001076e2 : fffff880`0734a300 00000000`00000000 fffff900`00000000 00000000`00000000 : win32k!bDeleteDCInternalWorker+0x29
fffff880`0734a2e0 fffff960`000c6778 : 00000000`62010eaa fffff880`0734a3e0 00000000`00000000 fffff960`000baf94 : win32k!bDeleteDCInternal+0x56
fffff880`0734a330 fffff800`02cd3993 : fffffa80`04d5db60 fffff880`00000001 00000000`00000001 00000000`00000001 : win32k!NtGdiDeleteObjectApp+0x120
fffff880`0734a360 00000000`749b2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008dd18 fffff800`02ccc080 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x749b2dd9
fffff880`0734a740 fffff880`0734a758 : fffffa80`04d5db60 00000000`00000000 fffff960`00000018 00000000`00000000 : nt!KiCallUserMode
fffff880`0734a748 fffffa80`04d5db60 : 00000000`00000000 fffff960`00000018 00000000`00000000 fffff880`0734adb0 : 0xfffff880`0734a758
fffff880`0734a750 00000000`00000000 : fffff960`00000018 00000000`00000000 fffff880`0734adb0 0020002c`00220077 : 0xfffffa80`04d5db60
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!RFONTOBJ::vDeleteRFONT+353
fffff960`00291597 488bcb mov rcx,rbx
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: win32k!RFONTOBJ::vDeleteRFONT+353
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d23ecb0
FAILURE_BUCKET_ID: X64_0xc2_7_win32k!RFONTOBJ::vDeleteRFONT+353
BUCKET_ID: X64_0xc2_7_win32k!RFONTOBJ::vDeleteRFONT+353
Followup: MachineOwner
---------
Quote