Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Memory dump in windows 2000 server


  • Please log in to reply

#1
vallirajan

vallirajan

    New Member

  • Member
  • Pip
  • 1 posts
hi,

we are getting frequent dump error in my Windows 2000 server with SP4 which leads to unexpected shutdown.

For this I tried to analyse with memory dump with windebugger and i got the below output for analyze -v

Please guide me what makes my system frequent reboot

Help me in this


Microsoft ® Windows Debugger Version 6.7.0005.0
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\rss-admin.SNRMCG155904\Desktop\Mini060107-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\winnt\system32
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 2000 Kernel Version 2195 (Service Pack 4) MP (8 procs) Free x86 compatible
Kernel base = 0xdd400000 PsLoadedModuleList = 0xdd485ac0
Debug session time: Fri Jun 1 18:35:51.017 2007 (GMT-4)
System Uptime: not available
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
................................................................................................................
Loading User Symbols
Loading unloaded module list
...........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {4c494600, 2, 0, f643c932}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for SCSIPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SCSIPORT.SYS
Probably caused by : SCSIPORT.SYS ( SCSIPORT+3932 )

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

3: kd> !analyze 0v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {4c494600, 2, 0, f643c932}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Probably caused by : SCSIPORT.SYS ( SCSIPORT+3932 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 4c494600, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f643c932, address which referenced memory

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.


FAULTING_MODULE: dd400000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 3ec58c26

READ_ADDRESS: unable to get nt!MmPoolCodeEnd
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSpecialPoolStart
unable to get nt!MmPagedPoolStart
unable to get nt!MmNonPagedPoolExpansionStart
unable to get nt!MmPoolCodeStart
4c494600

CURRENT_IRQL: 2

FAULTING_IP:
SCSIPORT+3932
f643c932 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 00000000 to dd46b11c

STACK_TEXT:
ef473058 00000000 4c494600 00000002 00000000 nt+0x6b11c


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
SCSIPORT+3932
f643c932 ?? ???

SYMBOL_NAME: SCSIPORT+3932

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: SCSIPORT

IMAGE_NAME: SCSIPORT.SYS

BUCKET_ID: WRONG_SYMBOLS

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

  • 0

Advertisements







Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP