Solved

Server reboots automatically

Posted on 2008-10-13
3
608 Views
Last Modified: 2013-12-05
i got this information from Memory dump file


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


Loading Dump File [C:\Documents and Settings\pradeepk\Desktop\New Folder\Mini092608-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows 2000 Kernel Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x80484520
Debug session time: Fri Sep 26 11:32:18.875 2008 (GMT+8)
System Uptime: not available
Unable to load image 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 50, {fec8e020, 0, f86ba47e, 0}


Could not read faulting driver name
Unable to load image ofant.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ofant.sys
*** ERROR: Module load completed but symbols could not be loaded for ofant.sys
Probably caused by : ofant.sys ( ofant+247e )

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: fec8e020, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: f86ba47e, If non-zero, the instruction address which referenced the bad memory
      address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: unable to read from 80483b80
unable to read from 80483804
unable to read from 80483794
unable to read from 8047a158
unable to read from 80483798
unable to read from 80483808
unable to read from 8047a15c
unable to read from 804838e0
unable to read from 80483b84
 fec8e020

FAULTING_IP:
ofant+247e
f86ba47e ??              ???

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR:  0x50

LAST_CONTROL_TRANSFER:  from 804696bf to 8044a99a

STACK_TEXT:  
f776f62c 804696bf 00000000 fec8e020 00000000 nt!MmCleanProcessAddressSpace+0x367
f776f644 00000000 00000000 00000000 00000000 nt!RtlIpv4StringToAddressA+0x1b0


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP:
ofant+247e
f86ba47e ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ofant

IMAGE_NAME:  ofant.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  39294207

SYMBOL_NAME:  ofant+247e

FAILURE_BUCKET_ID:  0x50_ofant+247e

BUCKET_ID:  0x50_ofant+247e

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

This is error message when i try to get from Memory dump file .it cause to Ofant.sys.how to solve this error.
0
Comment
Question by:Pirasanna
  • 2
3 Comments
 
LVL 95

Accepted Solution

by:
Lee W, MVP earned 50 total points
ID: 22708882
ofant.sys appears to be a key file in the Open File Agent for Arcserve - I would suggest reviewing this article:
http://support.microsoft.com/?kbid=330962

Then make sure you have the current version of the open file agent installed.  If you do, it could be a bug that, if you report it to CA, they may have a hotfix for OR they may be able to come up with one.
0
 
LVL 95

Expert Comment

by:Lee W, MVP
ID: 24145315
I object because this person NEVER responded to my comment.  If that wasn't the problem, then a response should have been posted.  Lacking a response, ID 22708882 should be selected as the answer.
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This is my 3rd article on SCCM in recent weeks, the 1st (http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/A_4466-A-beginners-guide-to-installing-SCCM2007-on-Windows-2008-R2-Server.html) dealing with installat…
Know what services you can and cannot, should and should not combine on your server.
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question