[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1375
  • Last Modified:

Windows SBS Pre 2003, STOP Erro 0x77

Dear Technical Support,

My Windows SBS Pre 2003 Server is crashing on daily bases with Stop Error 0x77.
I have enclosed the memory dump file log for your information, The Server Hardware vendor has confirmed that there is no problem in the hardware, and problem is coming from the software. Please read the memory dump log.
Microsoft (R) Windows Debugger  Version 6.6.0003.5 Copyright (c) Microsoft Corporation. All rights reserved.

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                                    *
*                                                                             *

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.
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



LAST_CONTROL_TRANSFER:  from 8084a89b to 80827451

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


8084a89b cc               int     3



FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  nt!MiMakeOutswappedPageResident+5c1



IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x77_c0000185_nt!MiMakeOutswappedPageResident+5c1

BUCKET_ID:  0x77_c0000185_nt!MiMakeOutswappedPageResident+5c1

Followup: MachineOwner
  • 2
1 Solution
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Who said the hardware was not the problem, and what hardware were they referring to?  Assuming that they knew something about hard drive health, then it really can only be one other thing...

Replace your IDE cables with more substantial ones than what came with the drives and you should be fine.

AbrarkAuthor Commented:

My Server is Fujitsu Siemens Primergy TX200 S2 Server, with SCSI U320 x 4 Hard disk Configured with hardware Raid 5.

Kindly advice, in my earlier email, i have attached print out from the Server Memory Crash Dump, please assist me in further investigating the memory log file, to pin point to the faulty hardware or device driver.

The Server had LSI MegaRaid Controller U320-0, I have checked each hard disk log, there is not error reported on each hard disk or in the controller.

The Raid controller is dual channel, on the second controller Tape Drive DDS5 is connected.

Kindly advice, if I should forword any other information.

Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I'm sorry, but I don't know how to analyze a memory log file more than just looking at the errors and then taking a look at what causes them.  If you don't feel that I've been able to provide you with enough information, I would suggest that you upload your memory dump file to Microsoft's Online Crash Analysis service, which is free.



Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now