First Post! Hello Everyone, Dump File

[matt3681]

Just looking for more opinions here.......does this appear to be a memory issue?

Thanks in advance!!


Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Mini080907-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS2003
Executable search path is:
Unable to load image \WINDOWS\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: LanManNt, suite: Enterprise TerminalServer SingleUserTS
Kernel base = 0x80800000 PsLoadedModuleList = 0x808af988
Debug session time: Thu Aug 9 06:00:08.225 2007 (GMT-4)
System Uptime: 63 days 10:48:44.398
Unable to load image \WINDOWS\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
..............................................................................................................
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 58f42001, 3c8d1, c0502000}

Probably caused by : ntoskrnl.exe ( nt!`string'+121 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041284, A PTE or the working set list is corrupt.
Arg2: 58f42001
Arg3: 0003c8d1
Arg4: c0502000

Debugging Details:
------------------


BUGCHECK_STR: 0x1a_41284

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

PROCESS_NAME: lsass.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8086b211 to 8087b6be

STACK_TEXT:
b7474c04 8086b211 0000001a 00041284 58f42001 nt!MmAdvanceMdl+0x137
b7474c40 80853246 0003c8d1 00000000 8993f500 nt!`string'+0x121
b7474c60 8082d64c 00740061 0012be24 8993f500 nt!IoFreeController+0x19
b7474c80 8082da1f 00163d08 8993f500 89ffec98 nt!MmUnlockPages+0x383
b7474d44 80834d3f 00000174 58f41000 00000000 nt!MiSegmentDelete+0x1b4
b7474d64 7c82ed54 badb0d00 0012bde8 00000000 nt!ObpTraceDepth+0x3b
WARNING: Frame IP not in any known module. Following frames may be wrong.
b7474d68 badb0d00 0012bde8 00000000 00000000 0x7c82ed54
b7474d6c 0012bde8 00000000 00000000 00000000 0xbadb0d00
b7474d70 00000000 00000000 00000000 00000000 0x12bde8


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!`string'+121
8086b211 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!`string'+121

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42435e60

FAILURE_BUCKET_ID: 0x1a_41284_nt!_string_+121

BUCKET_ID: 0x1a_41284_nt!_string_+121

Followup: MachineOwner
---------

 

[Tedster]

learn how to read your own minidumps: https://www.techspot.com/vb/topic31341.html

 

[EZ123]

it may be a memory problem but you did not gave us enough information.

are you experiencing many blue screens ? what is the scenario that you generated the blue screen ?

give as much information you can. from just looking at this mini dump no-body can tell you what is the cause.

EZ