XP Locks Up While Encode Mpeg Too Avi

Discussion in 'Windows XP Help and Support' started by Arfer Daley, Jul 26, 2013.

  1. Arfer Daley

    Arfer Daley

    Joined:
    Jul 25, 2013
    Messages:
    12
    Likes Received:
    0
    Location:
    UK
    hi all
    have a weird fault developed
    i record tv programs thru windows media centre on win7pro 64bit too speed up things i use both machines XP & W7Pro to encode from mpeg too avi to squish down the size of the files
    done this for years now all of a sudden i am geting error on xp which reboots and throws up a
    The System has Recovered from a serious error box also get the info listed below :eek:

    Error Report
    C:\DOCUME~1\John\LOCALS~1\Temp\WER911e.dir00\Mini072613-01.dmp
    C:\DOCUME~1\John\LOCALS~1\Temp\WER911e.dir00\sysdata.xml

    Error Signature
    BCCode : 1000000a BCP1 : 00DFF980 BCP2 : 000000FF BCP3 : 00000000
    BCP4 : 80545F6D OSVer : 5_1_2600 SP : 3_0 Product : 256_1

    anyone come across this the machine seems to run ok otherwise sometimes it will encode 1 file or maybe two befor it throws up the above messages thanks for any input
    have a great day all
     

    Attached Files:

    Arfer Daley, Jul 26, 2013
    #1
  2. Arfer Daley

    Elizabeth23

    Joined:
    Dec 10, 2012
    Messages:
    5,847
    Likes Received:
    756
    Location:
    Florida
    hi, I have searched through google, and most say run memtest 86+ and/or run checkdisk with the /r parameter.

    http://www.geekstogo.com/forum/topic/246994-guide-to-using-memtest86/

    memtest86+

    ----------------------------------------

    burn a cd with recovery console:

    Here's how to make a bootable xp recovery console cd
    Courtesy of JoseIbarra
    You need to start by booting into the XP Recovery Console using a CD you can make (no XP media required) and run a chkdsk with error correction enough times until it runs clean and if that doesn't work, you can create a new boot.ini file (it is usually one of those two things).

    Here's how:

    Use the XP Recovery Console to verify the file system on your HDD and correct any problems and then try to boot your system - this may be all you need to do. Or, you are welcome to just start trying things that might work.

    Boot into the Windows Recovery Console using a bootable XP installation CD.
    If you have no bootable XP media (or are not sure what you have) create a bootable XP Recovery Console CD and be sure what you have (no XP media required).

    This is not the same as any recovery disks that might have come with a store bought system.

    You can make a bootable Recovery Console CD by downloading an ISO file and burning it to a CD.

    The bootable ISO image file you need to download is called:
    rc.iso

    Download the ISO file from here:
    http://www.thecomputerparamedic.com/?p=8 (courtesy of Daavee)

    Use a new CD and this free and easy program to burn your ISO file and create your bootable CD:
    http://www.imgburn.com/

    When installing ImgBurn, DO NOT install the Ask toolbar.

    Here are some instructions for ImgBurn:
    http://forum.imgburn.com/index.php?showtopic=61

    It would be a good idea to test your bootable CD on a computer that is working.
    You may need to adjust the computer BIOS settings to use the CD ROM drive as the first boot device instead of the hard disk. These adjustments are made before Windows tries to load. If you miss it, you will have to reboot the system again.

    When you boot on the CD, follow the prompts:

    Press any key to boot from CD...
    The Windows Setup... will proceed.
    Press 'R' to enter the Recovery Console.
    Select the installation you want to access (usually 1: C:\WINDOWS)
    You may be asked to enter the Administrator password (usually empty).
    You should be in the C:\WINDOWS folder. This is the same as the
    C:\WINDOWS folder you see in explorer.

    The Recovery Console allows basic file commands like: copy, rename, replace, delete, cd, chkdsk, fixboot, fixmbr, etc.

    For a list of Recovery Console commands, enter help at the prompt or read about the XP Recovery Console here:
    http://www.microsoft.com/resources/...ocs/en-us/recovery_console_cmds.mspx?mfr=true

    A good idea before starting things is to first verify the integrity of your file system using the chkdsk command.

    From the command prompt window run the chkdsk command on the drive where Windows is installed to try to repair any problems on the afflicted drive.
    Running chkdsk is fine even if it doesn't find any problems. It will not hurt anything to run it.

    Assuming your boot drive is C, run the following command:
    chkdsk C: /r

    Let chkdsk finish and correct any problems it might find.

    It may take a long time for chkdsk to complete or it may appear to be 'stuck'. Be patient. If the HDD light is still flashing, chkdsk is doing something. Keep an eye on the percentage amount to be sure it is still making progress. It may even appear to go backwards sometimes.

    You should run chkdsk /r again until it finds no errors to correct.

    Remove the CD and type 'exit' to leave the RC and restart the computer.

    You do not have to adjust the BIOS again to boot on the HDD since the CD will not be present.


    Hope this helps, I have not received this error so have no personal knowledge of solution.
     
    Elizabeth23, Jul 26, 2013
    #2
  3. Arfer Daley

    Arfer Daley

    Joined:
    Jul 25, 2013
    Messages:
    12
    Likes Received:
    0
    Location:
    UK
    hi Elizabeth
    thanks for your help and advice this weekend I tried all what you had posted also ran tests too eliminate memory /graphic card cpu etc u name it also ran windows file checker
    all to no avail so I dug out my trusted ghost image I made when I installed xp
    then ran into a load of updates but I am happy too report a fully functioning machine but none the wiser and yes people I could of used my image file sooner but wanted too try and find what caused the problem anyway thanks again for all your help
     
    Arfer Daley, Jul 30, 2013
    #3
  4. Arfer Daley

    Elizabeth23

    Joined:
    Dec 10, 2012
    Messages:
    5,847
    Likes Received:
    756
    Location:
    Florida
    You are welcome, and it was most likely a corrupted file. or possibly malware.
     
    Elizabeth23, Jul 30, 2013
    #4
Ask a Question

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

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.