TechSpot

Reboot on standby, Error code 000000f4

By marcp1967
Aug 13, 2007
  1. Reboot on standby, Error code 000000f4 - Please Help!!

    Hi all.

    My computer reboots when waking up from stanby mode with the above error.

    My specs are:

    Pentium IV 2.53GHz (533 FSB/512kb cache)
    1 Gb Samsung DDR 333 RAM
    200 Gb Samsung HDD (IDE master)
    80 Gb Seagate HDD (IDE slave)
    LG DVD-RW
    CD-RW
    450W PSU
    nVidia Geforce 4 MX440 64MB AGP

    Windows XP SP2 with all latest patches

    nVidia drivers are updated.

    I have tested my computer with memtest86+ with no errors.

    I have run HDDlife which says all HDD status at 100%

    I have run chkdsk /f /r on all patitions

    I have set the pagefile to 0 and defgraged, and reset to 1.5Gb.

    I get the following in Event Viewer on crash:
    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 13/08/2007
    Time: 16:55:14
    User: N/A
    Computer: FAMILY
    Description:
    Error code 000000f4, parameter1 00000003, parameter2 8669ba78, parameter3 8669bbec, parameter4 805fa160.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 53 79 73 74 65 6d 20 45 System E
    0008: 72 72 6f 72 20 20 45 72 rror Er
    0010: 72 6f 72 20 63 6f 64 65 ror code
    0018: 20 30 30 30 30 30 30 66 000000f
    0020: 34 20 20 50 61 72 61 6d 4 Param
    0028: 65 74 65 72 73 20 30 30 eters 00
    0030: 30 30 30 30 30 33 2c 20 000003,
    0038: 38 36 36 39 62 61 37 38 8669ba78
    0040: 2c 20 38 36 36 39 62 62 , 8669bb
    0048: 65 63 2c 20 38 30 35 66 ec, 805f
    0050: 61 31 36 30 a160

    Debugging information:

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck F4, {3, 8669ba78, 8669bbec, 805fa160}

    Probably caused by : csrss.exe

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

    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 00000003, Process
    Arg2: 8669ba78, Terminating object
    Arg3: 8669bbec, Process image file name
    Arg4: 805fa160, Explanatory message (ascii)

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


    PROCESS_OBJECT: 8669ba78

    IMAGE_NAME: csrss.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MODULE_NAME: csrss

    FAULTING_MODULE: 00000000

    PROCESS_NAME: csrss.exe

    EXCEPTION_RECORD: f55669d8 -- (.exr fffffffff55669d8)
    ExceptionAddress: 75b7b399
    ExceptionCode: c0000006 (In-page I/O error)
    ExceptionFlags: 00000000
    NumberParameters: 3
    Parameter[0]: 00000000
    Parameter[1]: 75b7b399
    Parameter[2]: c000000e
    Inpage operation failed at 75b7b399, due to I/O error c000000e

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

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The required data was not placed into memory because of an I/O error status of "0x%08lx".

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

    EXCEPTION_STR: 0xc0000006_c000000e

    FAULTING_IP:
    +75b7b399
    75b7b399 ?? ???

    BUGCHECK_STR: 0xF4_IOERR_C000000E

    STACK_TEXT:
    f5566520 8062c623 000000f4 00000003 8669ba78 nt!KeBugCheckEx+0x1b
    f5566544 805fa11e 805fa160 8669ba78 8669bbec nt!PspCatchCriticalBreak+0x75
    f5566574 804de7ec 8669bcc0 c0000006 f55669b0 nt!NtTerminateProcess+0x7d
    f5566574 804ddae1 8669bcc0 c0000006 f55669b0 nt!KiFastCallEntry+0xf8
    f55665f4 8051d6de ffffffff c0000006 f55669f8 nt!ZwTerminateProcess+0x11
    f55669b0 804fc864 f55669d8 00000000 f5566d64 nt!KiDispatchException+0x3a0
    f5566d34 804e206b 0069fbe8 0069fc08 00000000 nt!KiRaiseException+0x175
    f5566d50 804de7ec 0069fbe8 0069fc08 00000000 nt!NtRaiseException+0x31
    f5566d50 75b7b399 0069fbe8 0069fc08 00000000 nt!KiFastCallEntry+0xf8
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0069fff4 00000000 00000000 00000000 00000000 0x75b7b399


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    FAILURE_BUCKET_ID: 0xF4_IOERR_C000000E_IMAGE_csrss.exe

    BUCKET_ID: 0xF4_IOERR_C000000E_IMAGE_csrss.exe

    Followup: MachineOwner


    Any help would greatfully received.
     
  2. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    The crash is caused by paging I/O error. The paging space may be corrupted or the hard disk error. Re-create the paging space and run chkdsk /r.
     
  3. marcp1967

    marcp1967 TS Rookie Topic Starter

    Many thanks for your reply :grinthumb

    I take it by paging space you mean the windows pagefile?

    I have set the pagefile to zero, degfraged the drive and reset to 1.5x RAM size and the error still presents. It even presented when virtual memory was switched off.

    I will try the steps you outline to see if it makes any difference.

    Thanks again
     
  4. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Maybe disk cable problem

    Re-plug disk cable and make sure it is tightly plug.
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...