TechSpot

BCCode Error

By fantom
Sep 18, 2005
  1. My new pc has been rebooting randomly about 5 times since I put it together.
    The crash code is

    BCCode : a BCP1 : DE5918D4 BCP2 : 00000001 BCP3 : 00000000

    BCP4 : 804EEF61 OSVer : 5_1_2600 SP : 1_0 Product : 256_1

    Event Viewer Details are:

    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 9/17/2005
    Time: 4:45:32 PM
    User: N/A
    Computer: MOUNTAIN-F1PGYT
    Description:
    Error code 00000024, parameter1 001902fa, parameter2 f785a734, parameter3 f785a434, parameter4 f8355365.
    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 32 0000002
    0020: 34 20 20 50 61 72 61 6d 4 Param
    0028: 65 74 65 72 73 20 30 30 eters 00
    0030: 31 39 30 32 66 61 2c 20 1902fa,
    0038: 66 37 38 35 61 37 33 34 f785a734
    0040: 2c 20 66 37 38 35 61 34 , f785a4
    0048: 33 34 2c 20 66 38 33 35 34, f835
    0050: 35 33 36 35 5365

    Also attached is the minidump file and an xml file which was included in the error.

    I'm guessing faulty RAM or voltage problem..possibly the RAM.
    Any help would be greatly appreciated.

    Fantom
     

    Attached Files:

  2. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    I've studied your problem and the culprit maybe faulty ram. Usually I require 5 to 6 minidumps to confirm my finding.

    Suggestion
    1. Upgrade to XP SP1 to latest patch as your XP SP1 is three years behind
    2. Diagnsostic which memory stick is faulty if you have more than one memory stick.
     
  3. fantom

    fantom TS Rookie Topic Starter

    Attn cpc2004,

    There are about 5-6 minidumps in my event viewer. PC will not turn on at all now. I was upgrading to Windows XP SP2 when the crash occurred. PC only has one memory stick and that is it.

    Thx,
    Fantom
     
  4. fantom

    fantom TS Rookie Topic Starter

    ok i took a memory module out of another working pc and it still doing the same rebooting problem. Could it be the CPU or power supply? I dont think its the mobo. Need to see if i have another PSU laying around.
     
  5. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi,

    You only mention you cannot boot up the PC. There have thousand of reason why your PC cannot be boot up. It maybe some cables are loosen, faulty Power supply unit, motherboard, CPU, RAM and etc. Take your PC to Computer hardware shop.
     
  6. fantom

    fantom TS Rookie Topic Starter

    Checked PSU..its fine..wires are fine. narrowing it down to CPU or mobo but now im thinking its a voltage issue. Anything i can check on the system regarding voltage in the BIOS?
     
  7. jrmjunior

    jrmjunior TS Rookie

    Please, I am new here and my pc has been rebooting randomly after I instaled a Sound card Creative Live 7.1. The error is:

    BCCode : f4 BCP1 : 00000003 BCP2 : 8202DA20 BCP3 : 8202DB94
    BCP4 : 805FA7A8 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

    I atached the minidump files. I don't have any idea about what is happening, any help would be greatly appreciated. Many thanks.
     
  8. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi jrmjunior,

    The culprit is bad paging space.

    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 and second arguments are 0, 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: 0076c000, offset into page file

    Debugging Details:
    ------------------
    ERROR_CODE: (NTSTATUS) 0xc0000185 - I/O
    DISK_HARDWARE_ERROR: There was error with disk hardware <--
    BUGCHECK_STR: 0x77_c0000185
    CUSTOMER_CRASH_COUNT: 2
    DEFAULT_BUCKET_ID: DRIVER_FAULT
    LAST_CONTROL_TRANSFER: from 80521361 to 805339ae
     
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...