Re: Server Down Stop Error.
- From: Keith Schmeichel <KeithSchmeichel@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 27 Jul 2007 12:18:10 -0700
Claus
That's the impression I'm getting also. I'm going to reload SP2, but this
will have to be done from safemode. I've never tried that, do you know if it
is a problem to load SP2 from safemode?
"Claus" wrote:
If this was a result of applying SP2, the support call to MS would be free.
of charge.
Although I haven't seen a crash like this after SP2, have a look at this....
http://support.microsoft.com/kb/939421
--
Claus
"Keith Schmeichel" <KeithSchmeichel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:06A83CD1-9611-4CAA-B9D1-4F15E8D9536C@xxxxxxxxxxxxxxxx
Here is the entire Debbugging Report. I'm still not having much luck.
I'm
getting an impression that reloading Win 2003 SP2 may fix this. Any Ideas
are appreciated.
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and
Settings\Administrator.JSI\Desktop\Mini072707-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\Websymbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free
x86 compatible
Product: LanManNt, suite: SmallBusiness TerminalServer
SmallBusinessRestricted SingleUserTS
Built by: 3790.srv03_sp2_gdr.070304-2240
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Fri Jul 27 14:08:04.692 2007 (GMT-4)
System Uptime: 0 days 1:42:20.781
Loading Kernel Symbols
.................................................................................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 808bc9dd, b9e4a914, 0}
Probably caused by : ntkrpamp.exe ( nt!HvpGetCellMapped+97 )
Followup: MachineOwner
---------
0: 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: c0000005, The exception code that was not handled
Arg2: 808bc9dd, The address that the exception occurred at
Arg3: b9e4a914, Trap Frame
Arg4: 00000000
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!HvpGetCellMapped+97
808bc9dd 8b4604 mov eax,dword ptr [esi+4]
TRAP_FRAME: b9e4a914 -- (.trap 0xffffffffb9e4a914)
ErrCode = 00000000
eax=e1022000 ebx=e100a3c0 ecx=00000020 edx=8ad6b4e8 esi=00000600
edi=00000000
eip=808bc9dd esp=b9e4a988 ebp=b9e4a9fc iopl=0 nv up ei pl nz na pe
nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010206
nt!HvpGetCellMapped+0x97:
808bc9dd 8b4604 mov eax,dword ptr [esi+4]
ds:0023:00000604=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0x8E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 808d0c77 to 808bc9dd
STACK_TEXT:
b9e4a9fc 808d0c77 e100a3c0 04060400 e1354a44 nt!HvpGetCellMapped+0x97
b9e4aa18 808d4c94 e100a3c0 d01144cc e1354a44 nt!CmpMarkValueDataDirty+0x5f
b9e4aa64 808d4f7d e100a3c0 d01144cc d3ac28e4
nt!CmpMarkKeyValuesDirty+0x132
b9e4aa80 808d5047 e100a3c0 0032ba40 e1354a44 nt!CmpFreeKeyValues+0x17
b9e4aae8 808d5b38 e100a3c0 00008710 d00c9714 nt!CmpSyncKeyValues+0x37
b9e4ab2c 808d5d35 e5c9a000 00000400 00000003 nt!CmpCopySyncTree2+0x1fa
b9e4ab5c 808c9a9b e100a3c0 000001b8 e100a3c0 nt!CmpCopySyncTree+0x4f
b9e4accc 808ba7c6 00010003 b9e4ad64 b9e4ace8
nt!CmpSaveBootControlSet+0x2a7
b9e4acdc 8088978c 00000005 b9e4ad64 8082ed75 nt!NtInitializeRegistry+0x5e
b9e4acdc 8082ed75 00000005 b9e4ad64 8082ed75 nt!KiFastCallEntry+0xfc
b9e4ad58 8088978c 00000005 0074f8b8 7c8285ec nt!ZwInitializeRegistry+0x11
b9e4ad58 7c8285ec 00000005 0074f8b8 7c8285ec nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0074f8b8 00000000 00000000 00000000 00000000 0x7c8285ec
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!HvpGetCellMapped+97
808bc9dd 8b4604 mov eax,dword ptr [esi+4]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!HvpGetCellMapped+97
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 45ec0a19
FAILURE_BUCKET_ID: 0x8E_nt!HvpGetCellMapped+97
BUCKET_ID: 0x8E_nt!HvpGetCellMapped+97
Followup: MachineOwner
---------
0: kd> lmvm nt
start end module name
80800000 80a56000 nt # (pdb symbols)
C:\Websymbols\ntkrpamp.pdb\52A81696FB5B432AB0B1B46297F104D31\ntkrpamp.pdb
Loaded symbol image file: ntkrpamp.exe
Mapped memory image file:
C:\Websymbols\ntkrpamp.exe\45EC0A19256000\ntkrpamp.exe
Image path: ntkrpamp.exe
Image name: ntkrpamp.exe
Timestamp: Mon Mar 05 07:16:25 2007 (45EC0A19)
CheckSum: 0023FE7D
ImageSize: 00256000
File version: 5.2.3790.4035
Product version: 5.2.3790.4035
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0804.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft(R) Windows(R) Operating System
InternalName: ntkrpamp.exe
OriginalFilename: ntkrpamp.exe
ProductVersion: 5.2.3790.4035
FileVersion: 5.2.3790.4035 (srv03_sp2_gdr.070304-2240)
FileDescription: NT Kernel & System
LegalCopyright: (C) Microsoft Corporation. All rights reserved.
"Dave Nickason [SBS MVP]" wrote:
What I would do is from your desktop PC, Start -> Run -> \\<sbs>\c$ to
browse the C drive on the server without logging in (you'll need to be
logged into the network with a domain admin account). Browse to wherever
the server keeps the crash dumps, which by default should be
C:\WINDOWS\Minidump.
Copy the dump file to your desktop PC and see if you can debug it with
the
instructions from the link below. With any luck at all, you'll get a
pretty
obvious pointer to whatever's causing the blue screens. And, you'll
learn
something pretty useful : -)
http://blogs.technet.com/petergal/archive/2006/03/23/422993.aspx
"Keith Schmeichel" <KeithSchmeichel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:F819C6C6-F5CE-4274-97C9-B88A02671A2C@xxxxxxxxxxxxxxxx
I have an SBS Server 2003 that was hit by lightning. The result was a
scrambling of the raid drives. I now have the server up without having
to
reload, but I'm having a problem. When I boot my server and try to
login
I'm
getting a BSOD. The error is Stop: 0x0000008f (0xc0000005, 0x808bc9dd,
0xb8650914, 0x00000000). The funny thing is everyone can connect to
the
server and use it normally as long as you don't logon. I've even tried
to
RDP to it and it still crashes, but all is fine if I don't. I can boot
into
safe mode and I've reloaded all system drivers as most of the
information
I've found alludes to a driver issue. Still no change. I've tried
last
know
good configuration and I've run Chkdsk /r. I see some repair utilities
on
the web saying they can fix this but I'm wary of doing that on my
server.
Thanks
- Follow-Ups:
- Re: Server Down Stop Error.
- From: Claus
- Re: Server Down Stop Error.
- References:
- Re: Server Down Stop Error.
- From: Dave Nickason [SBS MVP]
- Re: Server Down Stop Error.
- From: Keith Schmeichel
- Re: Server Down Stop Error.
- From: Claus
- Re: Server Down Stop Error.
- Prev by Date: Re: Can't Reinstall companyweb
- Next by Date: Re: Can't Reinstall companyweb
- Previous by thread: Re: Server Down Stop Error.
- Next by thread: Re: Server Down Stop Error.
- Index(es):
Relevant Pages
|
