Server Reboots every once in a while.

[Joe]

I have a windows 2003 server and every once in a while the server does a
dump and reboots. I used windbg to debug the Minidump and this is what i
got.

Loading Dump File [C:\Mini030105-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available



**** AddRegion: Empty region being added.

Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows Server 2003 Kernel Version 3790 MP (4 procs) Free x86 compatible

Product: LanManNt, suite: TerminalServer SingleUserTS

Built by: 3790.srv03_gdr.040410-1234

Kernel base = 0x804de000 PsLoadedModuleList = 0x8057b6a8

Debug session time: Tue Mar 1 15:44:35.390 2005 (GMT-6)

System Uptime: 2 days 0:33:46.421

Loading Kernel Symbols

.............................................................................................................

Loading unloaded module list

...

Loading User Symbols

*******************************************************************************

*
*

* Bugcheck Analysis
*

*
*

*******************************************************************************



Use !analyze -v to get detailed debugging information.



BugCheck 1000008E, {80000003, 804df1c0, f7757904, 0}



Probably caused by : Unknown_Image ( nt!RtlpBreakWithStatusInstruction+1 )



Followup: MachineOwner

---------



1: kd> !analyze -v

*******************************************************************************

*
*

* Bugcheck Analysis
*

*
*

*******************************************************************************



KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)

This is a very common bugcheck. Usually the exception address pinpoints

the driver/function that caused the problem. Always note this address

as well as the link date of the driver/image that contains this address.

Some common problems are exception code 0x80000003. This means a hard

coded breakpoint or assertion was hit, but this system was booted

/NODEBUG. This is not supposed to happen as developers should never have

hardcoded breakpoints in retail code, but ...

If this happens, make sure a debugger gets connected, and the

system is booted /DEBUG. This will let us see why this breakpoint is

happening.

Arguments:

Arg1: 80000003, The exception code that was not handled

Arg2: 804df1c0, The address that the exception occurred at

Arg3: f7757904, Trap Frame

Arg4: 00000000



Debugging Details:

------------------





EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments
are invalid



FAULTING_IP:

nt!RtlpBreakWithStatusInstruction+0

804df1c0 cc int 3



TRAP_FRAME: f7757904 -- (.trap fffffffff7757904)

ErrCode = 865c0023

eax=00000004 ebx=00000000 ecx=80542f0d edx=00000000 esi=00000023
edi=80000023

eip=804df1c1 esp=00000000 ebp=80000003 iopl=0 nv up di pl nz ac pe
nc

cs=0003 ss=0003 ds=0023 es=0023 fs=0000 gs=0000
efl=00000030

nt!RtlpBreakWithStatusInstruction+0x1:

804df1c1 c20400 ret 0x4

Resetting default scope



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP



BUGCHECK_STR: 0x8E



CURRENT_IRQL: 0



LAST_CONTROL_TRANSFER: from 00000000 to 804df1c1



STACK_TEXT:

80000003 00000000 00000000 00000000 00000000
nt!RtlpBreakWithStatusInstruction+0x1





FOLLOWUP_IP:

nt!RtlpBreakWithStatusInstruction+1

804df1c1 c20400 ret 0x4



FOLLOWUP_NAME: MachineOwner



SYMBOL_NAME: nt!RtlpBreakWithStatusInstruction+1



IMAGE_NAME: Unknown_Image



DEBUG_FLR_IMAGE_TIMESTAMP: 0



STACK_COMMAND: kb



BUCKET_ID: INVALID_KERNEL_CONTEXT



MODULE_NAME: Unknown_Module



Followup: MachineOwner

---------





any suggestions on what is the issue.

 

[Lanwench [MVP - Exchange]]

I have a windows 2003 server and every once in a while the server
does a dump and reboots. I used windbg to debug the Minidump and this
is what i got.

any suggestions on what is the issue.

Did you already check your event logs?
Have you changed your startup/recovery settings so that the computer doesn't
reboot after a blue screen?
Given that you're running Win2k3 server, you should also consider posting in
microsoft.public.windows.server.general (MS is moving away from
version-specific NGs for server products).