[FONT="Lucida Console"]
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\YUSRA\Downloads\ACER-V3-771-di_03-03-2015_170048,66\030315-41901-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
Machine Name:
Kernel base = 0xfffff800`0305a000 PsLoadedModuleList = 0xfffff800`0329e890
Debug session time: Tue Mar 3 18:02:12.787 2015 (UTC + 6:00)
System Uptime: 0 days 0:23:46.051
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffff2ea90209, 0, fffff800030c5056, 5}
*** WARNING: Unable to verify timestamp for avgidsdrivera.sys
*** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys
Could not read faulting driver name
Probably caused by : avgidsdrivera.sys ( avgidsdrivera+1180e )
Followup: MachineOwner
---------
2: 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: ffffffff2ea90209, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030c5056, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003308100
GetUlongFromAddress: unable to read from fffff800033081c0
ffffffff2ea90209
FAULTING_IP:
nt!ExpReleaseResourceForThreadLite+1b6
fffff800`030c5056 418b5108 mov edx,dword ptr [r9+8]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: ScanToPCActiva
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
TRAP_FRAME: fffff8800a6f34a0 -- (.trap 0xfffff8800a6f34a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa8009d9d010
rdx=fffffa8009ef5060 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030c5056 rsp=fffff8800a6f3630 rbp=fffffa8009ef5060
r8=0000000000000000 r9=ffffffff2ea90201 r10=000000000000005c
r11=000000200a3c032c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di ng nz na pe nc
nt!ExpReleaseResourceForThreadLite+0x1b6:
fffff800`030c5056 418b5108 mov edx,dword ptr [r9+8] ds:ffffffff`2ea90209=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000314c873 to fffff800030ceec0
STACK_TEXT:
fffff880`0a6f3338 fffff800`0314c873 : 00000000`00000050 ffffffff`2ea90209 00000000`00000000 fffff880`0a6f34a0 : nt!KeBugCheckEx
fffff880`0a6f3340 fffff800`030ccfee : 00000000`00000000 ffffffff`2ea90209 00000000`00000000 fffffa80`09d9d010 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`0a6f34a0 fffff800`030c5056 : fffff880`04835b10 fffff880`0a6f3680 fffff8a0`0eabf010 00000000`00000038 : nt!KiPageFault+0x16e
fffff880`0a6f3630 fffff880`0481180e : 00000000`00000001 00000000`00000001 00000000`00000000 fffff800`03204fcd : nt!ExpReleaseResourceForThreadLite+0x1b6
fffff880`0a6f3690 00000000`00000001 : 00000000`00000001 00000000`00000000 fffff800`03204fcd 00000000`000017b4 : avgidsdrivera+0x1180e
fffff880`0a6f3698 00000000`00000001 : 00000000`00000000 fffff800`03204fcd 00000000`000017b4 00000000`ffffffff : 0x1
fffff880`0a6f36a0 00000000`00000000 : fffff800`03204fcd 00000000`000017b4 00000000`ffffffff 00000000`00000614 : 0x1
STACK_COMMAND: kb
FOLLOWUP_IP:
avgidsdrivera+1180e
fffff880`0481180e ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: avgidsdrivera+1180e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: avgidsdrivera
IMAGE_NAME: avgidsdrivera.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 54e6470d
FAILURE_BUCKET_ID: X64_0x50_avgidsdrivera+1180e
BUCKET_ID: X64_0x50_avgidsdrivera+1180e
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x50_avgidsdrivera+1180e
FAILURE_ID_HASH: {6c14f21d-3b44-130e-0891-4bd9e442d56a}
Followup: MachineOwner
---------
2: kd> lmvm avgidsdrivera
start end module name
fffff880`04800000 fffff880`04847000 avgidsdrivera T (no symbols)
Loaded symbol image file: avgidsdrivera.sys
Image path: \SystemRoot\system32\DRIVERS\avgidsdrivera.sys
Image name: avgidsdrivera.sys
Timestamp: Fri Feb 20 02:26:53 2015 (54E6470D)
CheckSum: 00044E46
ImageSize: 00047000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
[/FONT]
