SBS Server crash Unexpected - Error ID 6008
- From: AbrarKhan <AbrarKhan@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 11 Jun 2006 13:06:02 -0700
Dear Support,
My SBS Server crash on daily bases, I get the following error.
The previous system shutdown at 1:18:44 AM on 6/11/2006 was unexpected.
Since three week back I use to get the following error message. Now the
system just crash.
Error code 00000077, parameter1 c0000185, parameter2 c0000185, parameter3
00000000, parameter4 01d25000.
Error code 0000000a, parameter1 0003afda, parameter2 00000002, parameter3
00000001, parameter4 80a5702a.
Error code 0000000a, parameter1 0001afd8, parameter2 00000002, parameter3
00000001, parameter4 80a5702a.
Error code 1000007e, parameter1 c0000005, parameter2 b7f3aa9e, parameter3
f7906c38, parameter4 f7906934.
Please advice, any can assist me in solving the this problem. The Server
Hard ware vendor has check hardware log, Raid Controller Log, but no hardware
problem found.
The problem started, when I have uninstalled the SP2 of ISA Server and than
I have uninstalled the ISA Server application two months back.
Below is the memory dump records.
Loading Dump File [C:\Users\Abrark\MEMORY.DMP] Kernel Summary Dump File:
Only kernel address space is available
Symbol search path is: C:\WINDOWS\Symbols Executable search path is:
C:\WINDOWS Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (4
procs) Free x86 compatible
Product: LanManNt, suite: SmallBusiness TerminalServer
SmallBusinessRestricted SingleUserTS Built by: 3790.srv03_sp1_rtm.050324-1447
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8 Debug session time:
Sun May 21 23:04:09.370 2006 (GMT+3) System Uptime: 3 days 11:05:32.109
Loading Kernel Symbols
................................................................................................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 77, {c0000185, c0000185, 0, 1d25000}
Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+5c1 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by bad block
in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature in the
kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or C000016AL
(STATUS_DISK_OPERATION_FAILED) normally indicates the data could not be read
from the disk due to a bad block. Upon reboot autocheck will run and attempt
to map out the bad sector. If the status is C0000185
(STATUS_IO_DEVICE_ERROR) and the paging file is on a SCSI disk device, then
the cabling and termination should be checked. See the knowledge base
article on SCSI termination.
Arguments:
Arg1: c0000185, status code
Arg2: c0000185, i/o status code
Arg3: 00000000, page file number
Arg4: 01d25000, offset into page file
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x77_c0000185
DEFAULT_BUCKET_ID: DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8084a89b to 80827451
STACK_TEXT:
f7922cbc 8084a89b 00000077 c0000185 c0000185 nt!KeBugCheckEx+0x1b
f7922d34 8084b73f c05d2bd0 000b7885 00000001
nt!MiMakeOutswappedPageResident+0x5c1
f7922d68 8084b7d5 8a73ec20 f7922d78 ba57b000
nt!MiInPageSingleKernelStack+0x14b
f7922d8c 8088724e 8a73ec20 00000000 8ab836c0 nt!MmInPageKernelStack+0x39
f7922da4 8088785e 8a73ec80 80948bb2 00000000 nt!KiInSwapKernelStacks+0x16
f7922dac 80948bb2 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x7c
f7922ddc 8088d4d2 808877e2 00000000 00000000 nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiMakeOutswappedPageResident+5c1
8084a89b cc int 3
FAULTING_SOURCE_CODE:
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!MiMakeOutswappedPageResident+5c1
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 42435b14
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x77_c0000185_nt!MiMakeOutswappedPageResident+5c1
BUCKET_ID: 0x77_c0000185_nt!MiMakeOutswappedPageResident+5c1
.
- Follow-Ups:
- Re: SBS Server crash Unexpected - Error ID 6008
- From: Cris Hanna \(SBS-MVP\)
- Re: SBS Server crash Unexpected - Error ID 6008
- Prev by Date: Re: Can't connect to server with RWW but can connect workstations
- Next by Date: Re: Can't connect to server with RWW but can connect workstations
- Previous by thread: Can't connect to server with RWW but can connect workstations
- Next by thread: Re: SBS Server crash Unexpected - Error ID 6008
- Index(es):
Relevant Pages
|
