EHB
This is from today. I assume you were playing a java game in the browser ntkrnmp.exe was the probable culprit and java was running and died with it.. How much memory do you have? at some point you ran out of memory and a page call was made thats when java died. I have the feeling that you have 4 gigs on 64bit, right?
The earlier dump also was caused by ntkrmlmp and svchost was running at that time.
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Mini092309-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*
Symbol information
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0xfffff800`02002000 PsLoadedModuleList = 0xfffff800`021c6dd0
Debug session time: Wed Sep 23 18:19:27.918 2009 (GMT-4)
System Uptime: 0 days 10:34:18.872
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800020b0ab3, fffffa60090790b0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+a5f3 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800020b0ab3, Address of the exception record for the exception that caused the bugcheck
Arg3: fffffa60090790b0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt! ?? ::FNODOBFM::`string'+a5f3
fffff800`020b0ab3 488b03 mov rax,qword ptr [rbx]
CONTEXT: fffffa60090790b0 -- (.cxr 0xfffffa60090790b0)
rax=0000000000000001 rbx=0000000000000000 rcx=00000000ffffffff
rdx=00000000ffffffff rsi=fffffa80082bd388 rdi=fffffa8007306bb0
rip=fffff800020b0ab3 rsp=fffffa6009079910 rbp=fffffa800348dc50
r8=0000000000000000 r9=0000000000000000 r10=fffffa80050ab3e0
r11=0000000000118497 r12=0000000000000000 r13=0000000000000000
r14=0000000000000011 r15=0000000000000001
iopl=0 nv up ei pl zr ac po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010256
nt! ?? ::FNODOBFM::`string'+0xa5f3:
fffff800`020b0ab3 488b03 mov rax,qword ptr [rbx] ds:002b:00000000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: java.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002092735 to fffff800020b0ab3
STACK_TEXT:
fffffa60`09079910 fffff800`02092735 : 00000000`128a4000 fffff680`00094548 00000000`128a3000 fffffa80`050ab3e0 : nt! ?? ::FNODOBFM::`string'+0xa5f3
fffffa60`09079960 fffff800`022d028e : fffffa80`050ab3e0 00000000`00000001 fffffa60`00000000 00000000`00000004 : nt!MiCommitExistingVad+0x2d5
fffffa60`09079a00 fffff800`0205bef3 : ffffffff`ffffffff 00000000`07fee808 00000000`00000000 00000000`07fee800 : nt!NtAllocateVirtualMemory+0x41e
fffffa60`09079bb0 00000000`775a6e9a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`07fee7c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775a6e9a
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+a5f3
fffff800`020b0ab3 488b03 mov rax,qword ptr [rbx]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+a5f3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 49e0237f
STACK_COMMAND: .cxr 0xfffffa60090790b0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!_??_::FNODOBFM::_string_+a5f3
BUCKET_ID: X64_0x3B_nt!_??_::FNODOBFM::_string_+a5f3
Followup: MachineOwner
---------
Since both dumps seem to ave been caused by a system file I would first run a system file check by going to start>search> type cmd >type sfc /scannow
It will run and tell you if you have damaged files and if they were able to be repaired.
Hope this helps
Ken
