KERNEL_STACK_INPAGE_ERROR

Discussion in 'Windows Small Business Server' started by George, Jun 24, 2009.

  1. George

    George Guest

    Recently my SBS 2003 Server system hangs and crashes and show the following
    error

    A problem has been detected and windows has been shut down to prevent
    damage to your computer.

    KERNEL_STACK_INPAGE_ERROR

    If this is the first time you've seen this stop error screen restart
    your computer. If this screen appears again follow these steps

    Check to make sure any new Hardware or software is properly installed
    If this is a new installation ask your hardware or software
    manufacturer for any windows updates you might need.

    If problems continue, disable or remove any newly installed hardware
    or software. Disable BIOS memory options such as caching or
    shadowing. If you need to use safe mode to remove or disable
    components, restart your computer. press f8 to select Advanced start-
    up Options, and then select Safe Mode.

    Technical Information:

    ***STOP: 0X00000077 (0xC00000185,0xC00000185, 0x00000000,0x013B700

    Beginning Dump of physical memory

    Can anybody suggest , what the problem .is my server board is intel S3000AH
    with 4GB DDR2 (667) Memory (4 *1) with 320GB samsung HDD
    George, Jun 24, 2009
    #1
    1. Advertising

  2. If it's your lucky day, you might be able to figure out something from the
    logs, or if you can figure out what triggers the blue screen. Otherwise,
    you'll probably have to debug. Here's how (title does not match your issue,
    but the procedure is the same):

    Stop 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
    http://blogs.technet.com/petergal/archive/2006/03/23/422993.aspx


    "George" <> wrote in message
    news:D...
    > Recently my SBS 2003 Server system hangs and crashes and show the
    > following
    > error
    >
    > A problem has been detected and windows has been shut down to prevent
    > damage to your computer.
    >
    > KERNEL_STACK_INPAGE_ERROR
    >
    > If this is the first time you've seen this stop error screen restart
    > your computer. If this screen appears again follow these steps
    >
    > Check to make sure any new Hardware or software is properly installed
    > If this is a new installation ask your hardware or software
    > manufacturer for any windows updates you might need.
    >
    > If problems continue, disable or remove any newly installed hardware
    > or software. Disable BIOS memory options such as caching or
    > shadowing. If you need to use safe mode to remove or disable
    > components, restart your computer. press f8 to select Advanced start-
    > up Options, and then select Safe Mode.
    >
    > Technical Information:
    >
    > ***STOP: 0X00000077 (0xC00000185,0xC00000185, 0x00000000,0x013B700
    >
    > Beginning Dump of physical memory
    >
    > Can anybody suggest , what the problem .is my server board is intel
    > S3000AH
    > with 4GB DDR2 (667) Memory (4 *1) with 320GB samsung HDD
    >
    >
    Dave Nickason [SBS MVP], Jun 24, 2009
    #2
    1. Advertising

  3. You should have a look into this document:

    <a
    href="http://support.microsoft.com/default.aspx/kb/228753">http://support.microsoft.com/default.aspx/kb/228753</a>

    It seems that you hit the problem:

    0xC0000185, or STATUS_IO_DEVICE_ERROR: improper termination or defective
    cabling of SCSI-based devices, or two devices attempting to use the same IRQ.

    With kind regards
    Krystian Zieja

    "George" wrote:

    > Recently my SBS 2003 Server system hangs and crashes and show the following
    > error
    >
    > A problem has been detected and windows has been shut down to prevent
    > damage to your computer.
    >
    > KERNEL_STACK_INPAGE_ERROR
    >
    > If this is the first time you've seen this stop error screen restart
    > your computer. If this screen appears again follow these steps
    >
    > Check to make sure any new Hardware or software is properly installed
    > If this is a new installation ask your hardware or software
    > manufacturer for any windows updates you might need.
    >
    > If problems continue, disable or remove any newly installed hardware
    > or software. Disable BIOS memory options such as caching or
    > shadowing. If you need to use safe mode to remove or disable
    > components, restart your computer. press f8 to select Advanced start-
    > up Options, and then select Safe Mode.
    >
    > Technical Information:
    >
    > ***STOP: 0X00000077 (0xC00000185,0xC00000185, 0x00000000,0x013B700
    >
    > Beginning Dump of physical memory
    >
    > Can anybody suggest , what the problem .is my server board is intel S3000AH
    > with 4GB DDR2 (667) Memory (4 *1) with 320GB samsung HDD
    >
    >
    Krystian Zieja, Jun 24, 2009
    #3
  4. George

    George Guest

    Thank you for the information.

    I loaded the DMP and the output i got is below.

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


    Loading Dump File [C:\Documents and Settings\George\Desktop\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is:
    SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    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_rtm.070216-1710
    Machine Name:
    Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
    Debug session time: Wed Jun 24 13:57:30.011 2009 (GMT+5)
    System Uptime: 0 days 1:56:06.046
    Loading Kernel Symbols
    ................................................................
    .......................................
    Loading User Symbols

    Loading unloaded module list
    ..
    *******************************************************************************
    *
    *
    * Bugcheck Analysis
    *
    *
    *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 77, {c000000e, c000000e, 0, 2539000}

    Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+5c1 )

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

    0: 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: c000000e, status code
    Arg2: c000000e, i/o status code
    Arg3: 00000000, page file number
    Arg4: 02539000, offset into page file

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


    ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was
    specified.

    DISK_HARDWARE_ERROR: There was error with disk hardware

    BUGCHECK_STR: 0x77_c000000e

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from 8084ae6d to 80827c63

    STACK_TEXT:
    f7912cbc 8084ae6d 00000077 c000000e c000000e nt!KeBugCheckEx+0x1b
    f7912d34 8084bd11 c07bc750 0006d5fe 00000001
    nt!MiMakeOutswappedPageResident+0x5c1
    f7912d68 8084bda7 8b17fdb0 f7912d78 f78eb000
    nt!MiInPageSingleKernelStack+0x14b
    f7912d8c 80887d6e 8b17fdb0 00000000 8b1755b0 nt!MmInPageKernelStack+0x39
    f7912da4 8088837e 8b17fe10 80949b7c 00000000 nt!KiInSwapKernelStacks+0x16
    f7912dac 80949b7c 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x7c
    f7912ddc 8088e062 80888302 00000000 00000000 nt!PspSystemThreadStartup+0x2e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiMakeOutswappedPageResident+5c1
    8084ae6d cc int 3

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!MiMakeOutswappedPageResident+5c1

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 45d69710

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+5c1

    BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+5c1

    Followup: MachineOwner


    IS the Memory Correction Error Caused by Virtual Memory,

    Coz in my Machine which has an hdd capacity of 320 GB, Partions are divided
    like this
    c : 99GB
    D: 40GB
    E: 20 GB
    F: 99GB
    G: 44GB

    The machine memory Capacity is 2G DRR2 (667) * 2 = 4GB

    FOR BETTER PERFORMANCE I HAVE INCREASSED VIRTUAL MEMMORY SETTINGS TO IN

    C: INTIAL 12000MB - MAX 18000MB
    D: INTIAL 6500MB - MAX 9000MB
    F: INTIAL 12000MB - MAX 18000MB

    IS THIS THE REASON FOR THE CRASH AND WHAT IS THE SOLUTIONS




    "Dave Nickason [SBS MVP]" wrote:

    > If it's your lucky day, you might be able to figure out something from the
    > logs, or if you can figure out what triggers the blue screen. Otherwise,
    > you'll probably have to debug. Here's how (title does not match your issue,
    > but the procedure is the same):
    >
    > Stop 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
    > http://blogs.technet.com/petergal/archive/2006/03/23/422993.aspx
    >
    >
    > "George" <> wrote in message
    > news:D...
    > > Recently my SBS 2003 Server system hangs and crashes and show the
    > > following
    > > error
    > >
    > > A problem has been detected and windows has been shut down to prevent
    > > damage to your computer.
    > >
    > > KERNEL_STACK_INPAGE_ERROR
    > >
    > > If this is the first time you've seen this stop error screen restart
    > > your computer. If this screen appears again follow these steps
    > >
    > > Check to make sure any new Hardware or software is properly installed
    > > If this is a new installation ask your hardware or software
    > > manufacturer for any windows updates you might need.
    > >
    > > If problems continue, disable or remove any newly installed hardware
    > > or software. Disable BIOS memory options such as caching or
    > > shadowing. If you need to use safe mode to remove or disable
    > > components, restart your computer. press f8 to select Advanced start-
    > > up Options, and then select Safe Mode.
    > >
    > > Technical Information:
    > >
    > > ***STOP: 0X00000077 (0xC00000185,0xC00000185, 0x00000000,0x013B700
    > >
    > > Beginning Dump of physical memory
    > >
    > > Can anybody suggest , what the problem .is my server board is intel
    > > S3000AH
    > > with 4GB DDR2 (667) Memory (4 *1) with 320GB samsung HDD
    > >
    > >

    >
    >
    George, Jun 24, 2009
    #4
  5. I would look at all the hardware - if you have diagnostic tools from the
    server manufacturer, I'd run whatever you can on the disk controller and
    hard drives. And, I'd run a chkdsk /r on all the drives. You can probably
    run it on all the drives other than C, then have it run on C during a
    reboot. I don't claim to be an expert on this, but I've found that
    generally when something says it's hardware, that's what it ends up being.
    If you've recently upgraded or added a driver, you could undo that just in
    case, but otherwise I'd focus on the hardware.


    "George" <> wrote in message
    news:...
    > Thank you for the information.
    >
    > I loaded the DMP and the output i got is below.
    >
    > Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    > Copyright (c) Microsoft Corporation. All rights reserved.
    >
    >
    > Loading Dump File [C:\Documents and Settings\George\Desktop\MEMORY.DMP]
    > Kernel Summary Dump File: Only kernel address space is available
    >
    > Symbol search path is:
    > SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    > 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_rtm.070216-1710
    > Machine Name:
    > Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
    > Debug session time: Wed Jun 24 13:57:30.011 2009 (GMT+5)
    > System Uptime: 0 days 1:56:06.046
    > Loading Kernel Symbols
    > ...............................................................
    > ......................................
    > Loading User Symbols
    >
    > Loading unloaded module list
    > .
    > *******************************************************************************
    > *
    > *
    > * Bugcheck Analysis
    > *
    > *
    > *
    > *******************************************************************************
    >
    > Use !analyze -v to get detailed debugging information.
    >
    > BugCheck 77, {c000000e, c000000e, 0, 2539000}
    >
    > Probably caused by : memory_corruption (
    > nt!MiMakeOutswappedPageResident+5c1 )
    >
    > Followup: MachineOwner
    > ---------
    >
    > 0: 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: c000000e, status code
    > Arg2: c000000e, i/o status code
    > Arg3: 00000000, page file number
    > Arg4: 02539000, offset into page file
    >
    > Debugging Details:
    > ------------------
    >
    >
    > ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was
    > specified.
    >
    > DISK_HARDWARE_ERROR: There was error with disk hardware
    >
    > BUGCHECK_STR: 0x77_c000000e
    >
    > DEFAULT_BUCKET_ID: DRIVER_FAULT
    >
    > PROCESS_NAME: System
    >
    > CURRENT_IRQL: 0
    >
    > LAST_CONTROL_TRANSFER: from 8084ae6d to 80827c63
    >
    > STACK_TEXT:
    > f7912cbc 8084ae6d 00000077 c000000e c000000e nt!KeBugCheckEx+0x1b
    > f7912d34 8084bd11 c07bc750 0006d5fe 00000001
    > nt!MiMakeOutswappedPageResident+0x5c1
    > f7912d68 8084bda7 8b17fdb0 f7912d78 f78eb000
    > nt!MiInPageSingleKernelStack+0x14b
    > f7912d8c 80887d6e 8b17fdb0 00000000 8b1755b0 nt!MmInPageKernelStack+0x39
    > f7912da4 8088837e 8b17fe10 80949b7c 00000000 nt!KiInSwapKernelStacks+0x16
    > f7912dac 80949b7c 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x7c
    > f7912ddc 8088e062 80888302 00000000 00000000
    > nt!PspSystemThreadStartup+0x2e
    > 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
    >
    >
    > STACK_COMMAND: kb
    >
    > FOLLOWUP_IP:
    > nt!MiMakeOutswappedPageResident+5c1
    > 8084ae6d cc int 3
    >
    > SYMBOL_STACK_INDEX: 1
    >
    > SYMBOL_NAME: nt!MiMakeOutswappedPageResident+5c1
    >
    > FOLLOWUP_NAME: MachineOwner
    >
    > MODULE_NAME: nt
    >
    > DEBUG_FLR_IMAGE_TIMESTAMP: 45d69710
    >
    > IMAGE_NAME: memory_corruption
    >
    > FAILURE_BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+5c1
    >
    > BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+5c1
    >
    > Followup: MachineOwner
    >
    >
    > IS the Memory Correction Error Caused by Virtual Memory,
    >
    > Coz in my Machine which has an hdd capacity of 320 GB, Partions are
    > divided
    > like this
    > c : 99GB
    > D: 40GB
    > E: 20 GB
    > F: 99GB
    > G: 44GB
    >
    > The machine memory Capacity is 2G DRR2 (667) * 2 = 4GB
    >
    > FOR BETTER PERFORMANCE I HAVE INCREASSED VIRTUAL MEMMORY SETTINGS TO IN
    >
    > C: INTIAL 12000MB - MAX 18000MB
    > D: INTIAL 6500MB - MAX 9000MB
    > F: INTIAL 12000MB - MAX 18000MB
    >
    > IS THIS THE REASON FOR THE CRASH AND WHAT IS THE SOLUTIONS
    >
    >
    >
    >
    > "Dave Nickason [SBS MVP]" wrote:
    >
    >> If it's your lucky day, you might be able to figure out something from
    >> the
    >> logs, or if you can figure out what triggers the blue screen. Otherwise,
    >> you'll probably have to debug. Here's how (title does not match your
    >> issue,
    >> but the procedure is the same):
    >>
    >> Stop 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
    >> http://blogs.technet.com/petergal/archive/2006/03/23/422993.aspx
    >>
    >>
    >> "George" <> wrote in message
    >> news:D...
    >> > Recently my SBS 2003 Server system hangs and crashes and show the
    >> > following
    >> > error
    >> >
    >> > A problem has been detected and windows has been shut down to prevent
    >> > damage to your computer.
    >> >
    >> > KERNEL_STACK_INPAGE_ERROR
    >> >
    >> > If this is the first time you've seen this stop error screen restart
    >> > your computer. If this screen appears again follow these steps
    >> >
    >> > Check to make sure any new Hardware or software is properly installed
    >> > If this is a new installation ask your hardware or software
    >> > manufacturer for any windows updates you might need.
    >> >
    >> > If problems continue, disable or remove any newly installed hardware
    >> > or software. Disable BIOS memory options such as caching or
    >> > shadowing. If you need to use safe mode to remove or disable
    >> > components, restart your computer. press f8 to select Advanced start-
    >> > up Options, and then select Safe Mode.
    >> >
    >> > Technical Information:
    >> >
    >> > ***STOP: 0X00000077 (0xC00000185,0xC00000185, 0x00000000,0x013B700
    >> >
    >> > Beginning Dump of physical memory
    >> >
    >> > Can anybody suggest , what the problem .is my server board is intel
    >> > S3000AH
    >> > with 4GB DDR2 (667) Memory (4 *1) with 320GB samsung HDD
    >> >
    >> >

    >>
    >>
    Dave Nickason [SBS MVP], Jun 24, 2009
    #5
  6. George

    George Guest

    Is there a chance that this is happeining because i have installed system
    restore in windows 2003.

    i have installed it from a ref on
    http://www.windowsreference.com/win...tallenable-system-restore-on-win-server-2003/

    Is this slowing the system or taking memory space. Also is there any tech
    issuse if system retore in installed in windows 2003

    Thanks


    "Dave Nickason [SBS MVP]" wrote:

    > I would look at all the hardware - if you have diagnostic tools from the
    > server manufacturer, I'd run whatever you can on the disk controller and
    > hard drives. And, I'd run a chkdsk /r on all the drives. You can probably
    > run it on all the drives other than C, then have it run on C during a
    > reboot. I don't claim to be an expert on this, but I've found that
    > generally when something says it's hardware, that's what it ends up being.
    > If you've recently upgraded or added a driver, you could undo that just in
    > case, but otherwise I'd focus on the hardware.
    >
    >
    > "George" <> wrote in message
    > news:...
    > > Thank you for the information.
    > >
    > > I loaded the DMP and the output i got is below.
    > >
    > > Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    > > Copyright (c) Microsoft Corporation. All rights reserved.
    > >
    > >
    > > Loading Dump File [C:\Documents and Settings\George\Desktop\MEMORY.DMP]
    > > Kernel Summary Dump File: Only kernel address space is available
    > >
    > > Symbol search path is:
    > > SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    > > 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_rtm.070216-1710
    > > Machine Name:
    > > Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
    > > Debug session time: Wed Jun 24 13:57:30.011 2009 (GMT+5)
    > > System Uptime: 0 days 1:56:06.046
    > > Loading Kernel Symbols
    > > ...............................................................
    > > ......................................
    > > Loading User Symbols
    > >
    > > Loading unloaded module list
    > > .
    > > *******************************************************************************
    > > *
    > > *
    > > * Bugcheck Analysis
    > > *
    > > *
    > > *
    > > *******************************************************************************
    > >
    > > Use !analyze -v to get detailed debugging information.
    > >
    > > BugCheck 77, {c000000e, c000000e, 0, 2539000}
    > >
    > > Probably caused by : memory_corruption (
    > > nt!MiMakeOutswappedPageResident+5c1 )
    > >
    > > Followup: MachineOwner
    > > ---------
    > >
    > > 0: 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: c000000e, status code
    > > Arg2: c000000e, i/o status code
    > > Arg3: 00000000, page file number
    > > Arg4: 02539000, offset into page file
    > >
    > > Debugging Details:
    > > ------------------
    > >
    > >
    > > ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was
    > > specified.
    > >
    > > DISK_HARDWARE_ERROR: There was error with disk hardware
    > >
    > > BUGCHECK_STR: 0x77_c000000e
    > >
    > > DEFAULT_BUCKET_ID: DRIVER_FAULT
    > >
    > > PROCESS_NAME: System
    > >
    > > CURRENT_IRQL: 0
    > >
    > > LAST_CONTROL_TRANSFER: from 8084ae6d to 80827c63
    > >
    > > STACK_TEXT:
    > > f7912cbc 8084ae6d 00000077 c000000e c000000e nt!KeBugCheckEx+0x1b
    > > f7912d34 8084bd11 c07bc750 0006d5fe 00000001
    > > nt!MiMakeOutswappedPageResident+0x5c1
    > > f7912d68 8084bda7 8b17fdb0 f7912d78 f78eb000
    > > nt!MiInPageSingleKernelStack+0x14b
    > > f7912d8c 80887d6e 8b17fdb0 00000000 8b1755b0 nt!MmInPageKernelStack+0x39
    > > f7912da4 8088837e 8b17fe10 80949b7c 00000000 nt!KiInSwapKernelStacks+0x16
    > > f7912dac 80949b7c 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x7c
    > > f7912ddc 8088e062 80888302 00000000 00000000
    > > nt!PspSystemThreadStartup+0x2e
    > > 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
    > >
    > >
    > > STACK_COMMAND: kb
    > >
    > > FOLLOWUP_IP:
    > > nt!MiMakeOutswappedPageResident+5c1
    > > 8084ae6d cc int 3
    > >
    > > SYMBOL_STACK_INDEX: 1
    > >
    > > SYMBOL_NAME: nt!MiMakeOutswappedPageResident+5c1
    > >
    > > FOLLOWUP_NAME: MachineOwner
    > >
    > > MODULE_NAME: nt
    > >
    > > DEBUG_FLR_IMAGE_TIMESTAMP: 45d69710
    > >
    > > IMAGE_NAME: memory_corruption
    > >
    > > FAILURE_BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+5c1
    > >
    > > BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+5c1
    > >
    > > Followup: MachineOwner
    > >
    > >
    > > IS the Memory Correction Error Caused by Virtual Memory,
    > >
    > > Coz in my Machine which has an hdd capacity of 320 GB, Partions are
    > > divided
    > > like this
    > > c : 99GB
    > > D: 40GB
    > > E: 20 GB
    > > F: 99GB
    > > G: 44GB
    > >
    > > The machine memory Capacity is 2G DRR2 (667) * 2 = 4GB
    > >
    > > FOR BETTER PERFORMANCE I HAVE INCREASSED VIRTUAL MEMMORY SETTINGS TO IN
    > >
    > > C: INTIAL 12000MB - MAX 18000MB
    > > D: INTIAL 6500MB - MAX 9000MB
    > > F: INTIAL 12000MB - MAX 18000MB
    > >
    > > IS THIS THE REASON FOR THE CRASH AND WHAT IS THE SOLUTIONS
    > >
    > >
    > >
    > >
    > > "Dave Nickason [SBS MVP]" wrote:
    > >
    > >> If it's your lucky day, you might be able to figure out something from
    > >> the
    > >> logs, or if you can figure out what triggers the blue screen. Otherwise,
    > >> you'll probably have to debug. Here's how (title does not match your
    > >> issue,
    > >> but the procedure is the same):
    > >>
    > >> Stop 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
    > >> http://blogs.technet.com/petergal/archive/2006/03/23/422993.aspx
    > >>
    > >>
    > >> "George" <> wrote in message
    > >> news:D...
    > >> > Recently my SBS 2003 Server system hangs and crashes and show the
    > >> > following
    > >> > error
    > >> >
    > >> > A problem has been detected and windows has been shut down to prevent
    > >> > damage to your computer.
    > >> >
    > >> > KERNEL_STACK_INPAGE_ERROR
    > >> >
    > >> > If this is the first time you've seen this stop error screen restart
    > >> > your computer. If this screen appears again follow these steps
    > >> >
    > >> > Check to make sure any new Hardware or software is properly installed
    > >> > If this is a new installation ask your hardware or software
    > >> > manufacturer for any windows updates you might need.
    > >> >
    > >> > If problems continue, disable or remove any newly installed hardware
    > >> > or software. Disable BIOS memory options such as caching or
    > >> > shadowing. If you need to use safe mode to remove or disable
    > >> > components, restart your computer. press f8 to select Advanced start-
    > >> > up Options, and then select Safe Mode.
    > >> >
    > >> > Technical Information:
    > >> >
    > >> > ***STOP: 0X00000077 (0xC00000185,0xC00000185, 0x00000000,0x013B700
    > >> >
    > >> > Beginning Dump of physical memory
    > >> >
    > >> > Can anybody suggest , what the problem .is my server board is intel
    > >> > S3000AH
    > >> > with 4GB DDR2 (667) Memory (4 *1) with 320GB samsung HDD
    > >> >
    > >> >
    > >>
    > >>

    >
    >
    George, Jun 25, 2009
    #6
  7. I don't have any experience with installing or using system restore on a
    server, but I doubt it's the cause of the blue screen errors. The only
    thing that would cause me to question that is if the blue screens were
    happening when system restore was doing something (like creating a restore
    point). I still think the blue screens are hardware related.


    "George" <> wrote in message
    news:...
    > Is there a chance that this is happeining because i have installed system
    > restore in windows 2003.
    >
    > i have installed it from a ref on
    > http://www.windowsreference.com/win...tallenable-system-restore-on-win-server-2003/
    >
    > Is this slowing the system or taking memory space. Also is there any tech
    > issuse if system retore in installed in windows 2003
    >
    > Thanks
    >
    >
    > "Dave Nickason [SBS MVP]" wrote:
    >
    >> I would look at all the hardware - if you have diagnostic tools from the
    >> server manufacturer, I'd run whatever you can on the disk controller and
    >> hard drives. And, I'd run a chkdsk /r on all the drives. You can
    >> probably
    >> run it on all the drives other than C, then have it run on C during a
    >> reboot. I don't claim to be an expert on this, but I've found that
    >> generally when something says it's hardware, that's what it ends up
    >> being.
    >> If you've recently upgraded or added a driver, you could undo that just
    >> in
    >> case, but otherwise I'd focus on the hardware.
    >>
    >>
    >> "George" <> wrote in message
    >> news:...
    >> > Thank you for the information.
    >> >
    >> > I loaded the DMP and the output i got is below.
    >> >
    >> > Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    >> > Copyright (c) Microsoft Corporation. All rights reserved.
    >> >
    >> >
    >> > Loading Dump File [C:\Documents and Settings\George\Desktop\MEMORY.DMP]
    >> > Kernel Summary Dump File: Only kernel address space is available
    >> >
    >> > Symbol search path is:
    >> > SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    >> > 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_rtm.070216-1710
    >> > Machine Name:
    >> > Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
    >> > Debug session time: Wed Jun 24 13:57:30.011 2009 (GMT+5)
    >> > System Uptime: 0 days 1:56:06.046
    >> > Loading Kernel Symbols
    >> > ...............................................................
    >> > ......................................
    >> > Loading User Symbols
    >> >
    >> > Loading unloaded module list
    >> > .
    >> > *******************************************************************************
    >> > *
    >> > *
    >> > * Bugcheck Analysis
    >> > *
    >> > *
    >> > *
    >> > *******************************************************************************
    >> >
    >> > Use !analyze -v to get detailed debugging information.
    >> >
    >> > BugCheck 77, {c000000e, c000000e, 0, 2539000}
    >> >
    >> > Probably caused by : memory_corruption (
    >> > nt!MiMakeOutswappedPageResident+5c1 )
    >> >
    >> > Followup: MachineOwner
    >> > ---------
    >> >
    >> > 0: 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: c000000e, status code
    >> > Arg2: c000000e, i/o status code
    >> > Arg3: 00000000, page file number
    >> > Arg4: 02539000, offset into page file
    >> >
    >> > Debugging Details:
    >> > ------------------
    >> >
    >> >
    >> > ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was
    >> > specified.
    >> >
    >> > DISK_HARDWARE_ERROR: There was error with disk hardware
    >> >
    >> > BUGCHECK_STR: 0x77_c000000e
    >> >
    >> > DEFAULT_BUCKET_ID: DRIVER_FAULT
    >> >
    >> > PROCESS_NAME: System
    >> >
    >> > CURRENT_IRQL: 0
    >> >
    >> > LAST_CONTROL_TRANSFER: from 8084ae6d to 80827c63
    >> >
    >> > STACK_TEXT:
    >> > f7912cbc 8084ae6d 00000077 c000000e c000000e nt!KeBugCheckEx+0x1b
    >> > f7912d34 8084bd11 c07bc750 0006d5fe 00000001
    >> > nt!MiMakeOutswappedPageResident+0x5c1
    >> > f7912d68 8084bda7 8b17fdb0 f7912d78 f78eb000
    >> > nt!MiInPageSingleKernelStack+0x14b
    >> > f7912d8c 80887d6e 8b17fdb0 00000000 8b1755b0
    >> > nt!MmInPageKernelStack+0x39
    >> > f7912da4 8088837e 8b17fe10 80949b7c 00000000
    >> > nt!KiInSwapKernelStacks+0x16
    >> > f7912dac 80949b7c 00000000 00000000 00000000
    >> > nt!KeSwapProcessOrStack+0x7c
    >> > f7912ddc 8088e062 80888302 00000000 00000000
    >> > nt!PspSystemThreadStartup+0x2e
    >> > 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
    >> >
    >> >
    >> > STACK_COMMAND: kb
    >> >
    >> > FOLLOWUP_IP:
    >> > nt!MiMakeOutswappedPageResident+5c1
    >> > 8084ae6d cc int 3
    >> >
    >> > SYMBOL_STACK_INDEX: 1
    >> >
    >> > SYMBOL_NAME: nt!MiMakeOutswappedPageResident+5c1
    >> >
    >> > FOLLOWUP_NAME: MachineOwner
    >> >
    >> > MODULE_NAME: nt
    >> >
    >> > DEBUG_FLR_IMAGE_TIMESTAMP: 45d69710
    >> >
    >> > IMAGE_NAME: memory_corruption
    >> >
    >> > FAILURE_BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+5c1
    >> >
    >> > BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+5c1
    >> >
    >> > Followup: MachineOwner
    >> >
    >> >
    >> > IS the Memory Correction Error Caused by Virtual Memory,
    >> >
    >> > Coz in my Machine which has an hdd capacity of 320 GB, Partions are
    >> > divided
    >> > like this
    >> > c : 99GB
    >> > D: 40GB
    >> > E: 20 GB
    >> > F: 99GB
    >> > G: 44GB
    >> >
    >> > The machine memory Capacity is 2G DRR2 (667) * 2 = 4GB
    >> >
    >> > FOR BETTER PERFORMANCE I HAVE INCREASSED VIRTUAL MEMMORY SETTINGS TO IN
    >> >
    >> > C: INTIAL 12000MB - MAX 18000MB
    >> > D: INTIAL 6500MB - MAX 9000MB
    >> > F: INTIAL 12000MB - MAX 18000MB
    >> >
    >> > IS THIS THE REASON FOR THE CRASH AND WHAT IS THE SOLUTIONS
    >> >
    >> >
    >> >
    >> >
    >> > "Dave Nickason [SBS MVP]" wrote:
    >> >
    >> >> If it's your lucky day, you might be able to figure out something from
    >> >> the
    >> >> logs, or if you can figure out what triggers the blue screen.
    >> >> Otherwise,
    >> >> you'll probably have to debug. Here's how (title does not match your
    >> >> issue,
    >> >> but the procedure is the same):
    >> >>
    >> >> Stop 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
    >> >> http://blogs.technet.com/petergal/archive/2006/03/23/422993.aspx
    >> >>
    >> >>
    >> >> "George" <> wrote in message
    >> >> news:D...
    >> >> > Recently my SBS 2003 Server system hangs and crashes and show the
    >> >> > following
    >> >> > error
    >> >> >
    >> >> > A problem has been detected and windows has been shut down to
    >> >> > prevent
    >> >> > damage to your computer.
    >> >> >
    >> >> > KERNEL_STACK_INPAGE_ERROR
    >> >> >
    >> >> > If this is the first time you've seen this stop error screen restart
    >> >> > your computer. If this screen appears again follow these steps
    >> >> >
    >> >> > Check to make sure any new Hardware or software is properly
    >> >> > installed
    >> >> > If this is a new installation ask your hardware or software
    >> >> > manufacturer for any windows updates you might need.
    >> >> >
    >> >> > If problems continue, disable or remove any newly installed hardware
    >> >> > or software. Disable BIOS memory options such as caching or
    >> >> > shadowing. If you need to use safe mode to remove or disable
    >> >> > components, restart your computer. press f8 to select Advanced
    >> >> > start-
    >> >> > up Options, and then select Safe Mode.
    >> >> >
    >> >> > Technical Information:
    >> >> >
    >> >> > ***STOP: 0X00000077 (0xC00000185,0xC00000185, 0x00000000,0x013B700
    >> >> >
    >> >> > Beginning Dump of physical memory
    >> >> >
    >> >> > Can anybody suggest , what the problem .is my server board is intel
    >> >> > S3000AH
    >> >> > with 4GB DDR2 (667) Memory (4 *1) with 320GB samsung HDD
    >> >> >
    >> >> >
    >> >>
    >> >>

    >>
    >>
    Dave Nickason [SBS MVP], Jun 25, 2009
    #7
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Raj

    KERNEL_STACK_INPAGE_ERROR

    Raj, Feb 6, 2004, in forum: Windows Vista Drivers
    Replies:
    0
    Views:
    525
  2. Doug
    Replies:
    3
    Views:
    379
    Scott Baker
    Jul 1, 2004
  3. Korman
    Replies:
    2
    Views:
    302
    Mike Rosado [MSFT]
    Mar 10, 2005
  4. Noor Motani

    Error 77 Kernel_Stack_Inpage_error

    Noor Motani, Nov 26, 2009, in forum: Windows Vista General Discussion
    Replies:
    2
    Views:
    229
    Peter Foldes
    Nov 26, 2009
Loading...

Share This Page