BugCheck 1000000A, {0, 1c, 0, 804dcbc6}
Probably caused by : avg7rsxp.sys ( avg7rsxp+1ff5 )
<<---- AVG
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 0000001c, IRQL
<<-----Clock Level IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 804dcbc6, address which referenced memory
STACK_TEXT:
a47247b4 804f65e7 8864d020 89bfca00 89bfca00 nt!ExRaiseStatus+0x2c
a47247d4 8058371a 89bfca00 a47247f0 00000000 nt!CcSetDirtyInMask+0xb4
a4724818 8057544c 886ecf68 00000001 00000002 nt!CmpFindSecurityCellCacheIndex+0xca
a472490c 805114c7 886ecf68 00000000 00000001 nt!CmpCompareNewValueDataAgainstKCBCache+0x68
a4724954 805bae64 886ecf68 00000000 00000000 nt!Ke386SetIOPL+0x61
a4724968 ba520ff5 88653410 00000000 01000000 nt!NtFreeVirtualMemory+0x3ee
WARNING: Stack unwind information not available. Following frames may be wrong.
a47249c4 ba5213de 88653410 88ce2008 89aa7bc8 avg7rsxp+0x1ff5
a47249f0 ba5206ab 89adf448 88653410 f79cd436 avg7rsxp+0x23de
a4724b04 8056c063 89b3f900 00000000 88d8e7e0 avg7rsxp+0x16ab
a4724b7c 8056f2a8 00000000 a4724bbc 00000040 nt!CmpQuerySecurityDescriptorInfo+0x1d
a4724bd0 8057d2e2 00000000 00000000 00002001 nt!ObQueryDeviceMapInformation+0x79
a4724c4c 8057d3b1 0012d7fc 00100020 0012d7b4 nt!NtReplyPort+0x254
a4724ca8 8057d55f 0012d7fc 00100020 0012d7b4 nt!SeCaptureSecurityQos+0x7a
a4724ce8 b6ca5dcb 0012d7fc 00100020 0012d7b4 nt!NtQueryInformationProcess+0xa86
a4724d44 804dd99e 0012d7fc 00100020 0012d7b4 vsdatant+0x2fdcb
a4724d48 0012d7fc 00100020 0012d7b4 0012d7d4 nt!ZwQueryEvent+0x13
a4724d64 7c90eb94 badb0d00 0012d788 00000000 0x12d7fc
a4724d68 badb0d00 0012d788 00000000 00000000 0x7c90eb94
a4724d6c 0012d788 00000000 00000000 00000000 0xbadb0d00
a4724d70 00000000 00000000 00000000 00000000 0x12d788
lmvm avg7rsxp
start end module name
ba51f000 ba525c80 avg7rsxp T (no symbols)
Loaded symbol image file: avg7rsxp.sys
Image path: avg7rsxp.sys
Image name: avg7rsxp.sys
Timestamp: Tue Jan 30 20:38:42 2007 (45BF5F7A)
<<-----Updated , Look For Any Recent Updates
CheckSum: 0000C1DC
ImageSize: 00006C80
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
System Crash With "Bugcheck 1A" With "IRQL" x'1c' Which Is "Clock Level IRQL" Is Also The Symptom Of Hardware Error
==================================================================
BugCheck 1000000A, {ffe00000, ff, 0, 806fff71}
Probably caused by : intelppm.sys ( intelppm!AcpiC1Idle+12 )
<<--- http://www.file.net/process/intelppm.sys.html
lmvm intelppm
start end module name
f7697000 f769fd00 intelppm M (pdb symbols) C:\Symbols\sys\intelppm.pdb
Loaded symbol image file: intelppm.sys
Image path: intelppm.sys
Image name: intelppm.sys
Timestamp: Wed Aug 04 11:29:19 2004 (41107B37)
<<---- 3 Years Behind
CheckSum: 0000B22F
ImageSize: 00008D00
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
==================================================================
BugCheck 1000000A, {ffca3874, 1c, 0, 8050184f}
Probably caused by : memory_corruption ( nt!MiGatherMappedPages+15c )
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffca3874, memory referenced
Arg2: 0000001c, IRQL
<<-----Clock Level IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8050184f, address which referenced memory
==================================================================
BugCheck 1000000A, {55ba14, 1c, 0, 8050184f}
Probably caused by : vsdatant.sys ( vsdatant+1641 )
<<----Zonelarm
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0055ba14, memory referenced
Arg2: 0000001c, IRQL
<<-----Clock Level IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8050184f, address which referenced memory
lmvm vsdatant
start end module name
b6923000 b6982160 vsdatant T (no symbols)
Loaded symbol image file: vsdatant.sys
Image path: vsdatant.sys
Image name: vsdatant.sys
Timestamp: Fri Sep 07 03:21:38 2007 (46E0766A)
<<---- Updated
CheckSum: 00061E1E
ImageSize: 0005F160
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
==================================================================
BugCheck 1000000A, {2732c0, 1c, 0, 805021af}
Probably caused by : vsdatant.sys ( vsdatant+32e12 )
<<----Zonelarm
STACK_TEXT:
b6382bbc 8050240d 00000001 b6382bd8 00000001 nt!IopFreeIrpAndMdls+0x25
b6382be8 804fcdf0 e289c840 893a5b60 893a5998 nt!MiGrowWsleHash+0x22
b6382c00 805a1e49 89b75b50 00000001 00000001 nt!MiCopyHeaderIfResident+0x36
b6382cb0 b6955e12 00000180 001b4000 001b4000 nt!IopNotifyTargetDeviceChange+0xad
WARNING: Stack unwind information not available. Following frames may be wrong.
b6382d50 8054086c 00000180 001b4000 001b4000 vsdatant+0x32e12
b6382d64 7c90eb94 badb0d00 0012f71c b5b07d98 nt!RtlIpv4StringToAddressExA+0x149
b6382d78 00000000 00000000 00000000 00000000 0x7c90eb94
==================================================================
BugCheck 1000000A, {1929e8, 2, 1, 804e838a}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromList+ed )
BugCheck 1000000A, {2bbc38, 1c, 0, 805021af}
Probably caused by : vsdatant.sys ( vsdatant+32e12 )
==================================================================
BugCheck 1000000A, {c0d6e4f0, 2, 0, 8051660a}
Probably caused by : ntoskrnl.exe ( nt!CcWaitForUninitializeCacheMap+5b )
STACK_TEXT:
b44d7bb8 805218e7 81e84380 0000003f 00000000 nt!CcWaitForUninitializeCacheMap+0x5b
b44d7bd0 80521efa eb6b95c0 8929f828 8905fbe8 nt!MmCleanProcessAddressSpace+0xf9
b44d7be8 80514af1 00000420 000004c0 8905fc18 nt!MiResolvePageFileFault+0x1e7
b44d7c18 8051568f 00008000 8929f88c 8929f898 nt!KeSetSystemTime+0x40
b44d7c5c 80515855 00000000 10798000 c0083cc0 nt!IoEnumerateDeviceObjectList+0x40
b44d7c78 b44d7d40 81e6f978 c0083cc0 eb6b95c0 nt!RotBarInit+0x8c
WARNING: Frame IP not in any known module. Following frames may be wrong.
b44d7ce0 8051fdca eb6b95c0 10798000 c0083cc0 0xb44d7d40
b44d7d4c 805437c8 00000000 10798000 00000001 nt!MiCleanSection+0x549
b44d7d64 10001934 badb0d00 0cbb2a00 00000000 nt!`string'
b44d7d68 badb0d00 0cbb2a00 00000000 00000000 0x10001934
b44d7d6c 0cbb2a00 00000000 00000000 00000000 0xbadb0d00
b44d7d70 00000000 00000000 00000000 00000000 0xcbb2a00
==================================================================
Login 
Windows NT/2000/XP 
