Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Yusra\Downloads\imnsu\imnsu\091212-23712-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*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.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02e1e000 PsLoadedModuleList = 0xfffff800`03062670
Debug session time: Wed Sep 12 15:07:00.463 2012 (UTC + 6:00)
System Uptime: 1 days 4:28:22.993
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {2d10050, 1, 7feef98f5db, 8}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+45ea5 )
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: 0000000002d10050, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: 000007feef98f5db, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000008, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030cc100
0000000002d10050
FAULTING_IP:
+3261613139356131
000007fe`ef98f5db ?? ???
MM_INTERNAL_CODE: 8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: MsMpEng.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002e2d7bb to fffff80002e9d1c0
STACK_TEXT:
fffff880`066a2ab8 fffff800`02e2d7bb : 00000000`00000050 00000000`02d10050 00000000`00000001 fffff880`066a2c20 : nt!KeBugCheckEx
fffff880`066a2ac0 fffff800`02e9b2ee : 00000000`00000001 00000000`02d10050 00000000`00000001 00000000`112f35d0 : nt! ?? ::FNODOBFM::`string'+0x45ea5
fffff880`066a2c20 000007fe`ef98f5db : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`01f5e170 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ef98f5db
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+45ea5
fffff800`02e2d7bb cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+45ea5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4fa390f3
FAILURE_BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+45ea5
BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+45ea5
Followup: MachineOwner
---------