Persistently STOP 0XC000021a

Discussion in 'Operating Systems' started by nemonavicusrino, May 13, 2020.

  1. nemonavicusrino

    nemonavicusrino New Member

    Messages:
    6
    Likes Received:
    0
    GPU:
    INTEGRATED HD4400 /
    Hello Guys and greetings from Romania.

    I read GURU 3D for almost ten years now but never encouner very big problem, that i need help anD because my enghlish is not very good.

    First thing i want to excuse for my english, is not my primary language.

    I need Your help with a computer that i tryed many recomandation, but to no avail.

    I am a litle service man in it, but this thing it has crayzed me.

    It is a desktop owned by my cusine, FUJITSU DESKTOP M13W, WITH WINDOWS 10 (SEEM TO BE ENTERPRISE licensed and installed), that he got from company, when company came to bankruptcy and dont bother to put a paralel, second os for home or to install a dual boot on same hdd.

    The problem is i cannot reinstall, because it has some accountability program that he need maintain data couple of years, data that can be exported only from program (when computer is working).


    Computer not log on to windows 10 after some update last month (Jeesus Microsoft, endless problem).

    Tryed every option, last, safe, enforcement signature, command prompt, nothing works.

    Computer loop in 0x21a, startup repair, 0x21a and loop again.

    What i have tried.

    Verified ram - 4 slot two stik, minim 10 pases - everything ok

    run chkddsk /f from recovery environment, no problem

    boot with live os and run hdd sentinel - health 100 % aprox 550 day worked, full hdd read test - absolutely no problem.

    Resized second partition, freed some space and baked up partition os in this state (cloned)

    Came in the recovery environment and run some dism comands, but all came with eror at about 83 % with an eror and no image source find . Here my knowledge is limited, my job is limited on basic test and repair /swap components



    After some time and comands, realized that it has enterprise not pro and canot use standard image downloaded with microsoft media tool. Downloaded enterprise edition, and pointed to location where i copyed on another partition , pointed some index, but in this stage my skills is unclear, because is not my daily context expertize. I am not very sure on comands given on dism, because is case senzitive, or depend on context, so...it is posibly that these comand not very corect and result unclear.

    Computer health is ok, it stay couple of days and night without to restart or anything other error in this state (permanent looping or stay in recovery environment day and night)



    Please help with some sugestion or direction. I am open with any sugestion or start from scratch with repair. Reinstall is excluded from start. If it was posible problem has ben resolved dozen of time now on.



    Atached eror dism command. Cannot update here dism log, but i have some csi payload eror (31) i will atach here an example :


    amd64_microsoft-windows-font-embedding_31bf3856ad364e35_10.0.17763.914_none_2aa82b07a48634f6\t2embed.dll
    2020-05-12 17:40:39, Info CBS Repair failed: Missing replacement payload.
    2020-05-12 17:40:39, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-gdi32full_31bf3856ad364e35_10.0.17763.914_none_cad37b30acd56437\gdi32full.dll
    2020-05-12 17:40:39, Info CBS Repair failed: Missing replacement payload.
    2020-05-12 17:40:39, Info CBS (p) CSI Payload Corrupt (n) wow64_microsoft-windows-data-pdf_31bf3856ad364e35_10.0.17763.914_none_759174fa4da212f7\Windows.Data.Pdf.dll
    2020-05-12 17:40:39, Info CBS Repair failed: Missing replacement payload.
    2020-05-12 17:40:39, Info CBS (p) CSI Payload Corrupt (n) wow64_microsoft-windows-gdi_31bf3856ad364e35_10.0.17763.1075_none_01dbc6396098dca1\fontsub.dll
    2020-05-12 17:40:39, Info CBS Repair failed: Missing replacement payload.
    2020-05-12 17:40:39, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_11.0.17763.914_none_00fa1f02dcee0825\vbscript.dll
    2020-05-12 17:40:39, Info CBS Repair failed: Missing replacement payload.
    2020-05-12 17:40:39, Info CBS (p) CSI Payload Corrupt (n)



    Thank you very much in advance
     

    Attached Files:

  2. mbk1969

    mbk1969 Ancient Guru

    Messages:
    10,035
    Likes Received:
    7,028
    GPU:
    GF RTX 2070 Super
    You should try DISM commands not in recovery environment but in live Windows session.
    Or try clean install of Windows.
     
  3. nemonavicusrino

    nemonavicusrino New Member

    Messages:
    6
    Likes Received:
    0
    GPU:
    INTEGRATED HD4400 /

    Thanks for your intervention, but as ai said clean instal is excluded momentarily. System not boot in live sesion, thats is the main and big problem.
     
  4. The Goose

    The Goose Ancient Guru

    Messages:
    2,556
    Likes Received:
    118
    GPU:
    MSIrtx2080 superXS
    Have you tried installing os on another drive and booting that to gain access to the other hardrive, or putting the drive in another system as a secondary drive.
     

  5. nemonavicusrino

    nemonavicusrino New Member

    Messages:
    6
    Likes Received:
    0
    GPU:
    INTEGRATED HD4400 /

    Thank for ideea. It is an easy task to do , I have plenty computers around, but i havent, because i dont know how it wil help me, as os is corupted. Can you please expand a litle this ideea and what to do after i move hard drive on another sytem healt and live?.

    I can evan instal a dual boot on same hardware to be sure that hardware is not a problem, and to easyly acces corupted os. that is sound promising. I wil instal an evaluation copy of w10 enterprise along the curent os. How i wil know for sure what version of os is instaled ? aftr some comand last week (i dont remember now) resulted that corupted os is enterprise.
     
  6. mbk1969

    mbk1969 Ancient Guru

    Messages:
    10,035
    Likes Received:
    7,028
    GPU:
    GF RTX 2070 Super
    386SX likes this.
  7. Astyanax

    Astyanax Ancient Guru

    Messages:
    8,356
    Likes Received:
    2,790
    GPU:
    GTX 1080ti
  8. mbk1969

    mbk1969 Ancient Guru

    Messages:
    10,035
    Likes Received:
    7,028
    GPU:
    GF RTX 2070 Super
    You boot from install media (DVD, USB) and start installation over the current instance. You can even specify login since boot media is not broken (and should it ask for login).
     
  9. Astyanax

    Astyanax Ancient Guru

    Messages:
    8,356
    Likes Received:
    2,790
    GPU:
    GTX 1080ti
    This is treated like a new install, existing data is lost
     
  10. mbk1969

    mbk1969 Ancient Guru

    Messages:
    10,035
    Likes Received:
    7,028
    GPU:
    GF RTX 2070 Super
    Google disagrees with you
    [​IMG]

    PS And event if it will be new installation it will not remove files from disk. So program he mentions can even work. Or it can work if he re-installs the program.
     
    Last edited: May 14, 2020

  11. mbk1969

    mbk1969 Ancient Guru

    Messages:
    10,035
    Likes Received:
    7,028
    GPU:
    GF RTX 2070 Super
    Last edited: May 14, 2020
  12. Astyanax

    Astyanax Ancient Guru

    Messages:
    8,356
    Likes Received:
    2,790
    GPU:
    GTX 1080ti

    That picture clearly demonstrates the opposite of your claim as that image is IN WINDOWS.

    Windows 10's equivalent of a repair install is the inplace upgrade which can only be performed as a logged in administrator

    Offline (Startup repair) is unable to begin an inplace upgrade, and the installer GUI for a bootdisk uses aero basic windows.

    https://answers.microsoft.com/en-us...ndows-10/ac3bbf05-9b08-47c6-a995-bc402c813b3b

    you would think that startup repair would have the ability to connect to network and perform a repair install via dism, but no.
     
    Last edited: May 14, 2020
  13. mbk1969

    mbk1969 Ancient Guru

    Messages:
    10,035
    Likes Received:
    7,028
    GPU:
    GF RTX 2070 Super
    @Astyanax

    I just misunderstood your "be within windows".
     
  14. nemonavicusrino

    nemonavicusrino New Member

    Messages:
    6
    Likes Received:
    0
    GPU:
    INTEGRATED HD4400 /
    Thanks, guys, sory for the delay response. I was very bussy at work with this pandemic virus, to prepare computers for online scholars. Wil try this week when i have some spare time, as this is a personal project to advance in "windows knowledge wisdom". If you have an ideea please throw here and i will happy try.
     
  15. nemonavicusrino

    nemonavicusrino New Member

    Messages:
    6
    Likes Received:
    0
    GPU:
    INTEGRATED HD4400 /
    Ok I came back with special microsoft news.... No joy.
    Verified hdd one time more.
    created apartition and instaled a paralel instalation (w10 pro). Everything works as espected, so i eliminated posibility to have an hardware eror.
    I find another solution and tryed. (Boot ofline with re or another live os and delete software distribution folder, cleanup.xml and pending xml). Same result,
    tryed revertpending, - 0x800f082f ereor.
    runing dism with reestore healt one mor time this night.
    Se you soon. If you have anothere idea please post !
     

  16. nemonavicusrino

    nemonavicusrino New Member

    Messages:
    6
    Likes Received:
    0
    GPU:
    INTEGRATED HD4400 /
    Is any body that can look at dism log or cbs log ?

    at one moment i deleted cbs log, in hope that wil produce one new , to see exct log per sesion, but it seem that in win re cbs log is not produced, is this true ?

    whatever will do i receive eror on 83 %
    i feel soon go madly. This edition of windows is fool of bugs. I have tree computers in similar situation, even personal notebook of my wife.

    Step i make



    i boot to computer

    strt diagnostic

    trublehoot

    command prompt

    come an X: - boot partition on recovery environment

    make comand from x: - did not work

    change to f: where is corupted os

    make comand from f: - did not work

    downloaded enterprise edition from microsoft and converted esd to wim (i read that is some problem with dism and esd)



    tried paramater with full path source (G:....etc)

    changed director to wim location

    tried here without fullpath

    What is wrong with comands ? What i am missing ?

    i see in dism some failed conect to provider, but i do not understand what it means

    is it some misisng in recovery environment ?

    can i run dism from coruped os ? maybe is somehow diferent from os file in system 32 ?

    questions, questions, questions ? i scratch my head above 1 month now...

    Please help !

    anyideas


    Nothing works, only comand prompt from recovery environment, booted with corupted computers
    Image Version: 10.0.17763.1098

    [===========================83.0%================ ]
    Error: 0x800f081f

    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

    The DISM log file can be found at X:\windows\Logs\DISM\dism.log

    G:\w10ent\1>dism /image:f:\ /Cleanup-Image /restorehealth /source:G:\w10ent\1\install.wim /scratchdir:f:\scratch

    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1

    Image Version: 10.0.17763.1098

    [===========================83.0%================ ]
    Error: 0x800f081f

    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

    The DISM log file can be found at X:\windows\Logs\DISM\dism.log

    G:\w10ent\1>notepad

    G:\w10ent\1>dism /image:f:\ /Cleanup-Image /scanhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1

    Image Version: 10.0.17763.1098

    The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior.
    Use the /ScratchDir option to point to a folder with sufficient scratch space. The recommended size is at least 1024 MB.

    [==========================100.0%==========================] The component store is repairable.
    The operation completed successfully.

    G:\w10ent\1>notepad

    G:\w10ent\1>dism /image:f:\ /Cleanup-Image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1

    Image Version: 10.0.17763.1098

    The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior.
    Use the /ScratchDir option to point to a folder with sufficient scratch space. The recommended size is at least 1024 MB.

    [===========================83.0%================ ]
    Error: 0x800f081f

    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

    The DISM log file can be found at X:\windows\Logs\DISM\dism.log

    G:\w10ent\1>dism /image:f:\ /Cleanup-Image /restorehealth /source:G:\w10ent\1\install.wim /scratchdir:f:/scratch

    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1

    Image Version: 10.0.17763.1098

    [===========================83.0%================ ]
    Error: 0x800f081f

    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

    The DISM log file can be found at X:\windows\Logs\DISM\dism.log

    G:\w10ent\1>dism /image:f:\ /Cleanup-Image /restorehealth /source:G:\w10ent\1\install.wim /scratchdir f:\scratch

    Error: 87

    DISM doesn't recognize the command-line option "f:\scratch".
    For more information, refer to the help by running DISM.exe /?.

    The DISM log file can be found at X:\windows\Logs\DISM\dism.log

    G:\w10ent\1>dism /image:f:\ /Cleanup-Image /restorehealth /source:G:\w10ent\1\install.wim /scratchdir: f:\scratch

    Error: 87

    The /scratchdir: option is missing a required argument.
    For more information, refer to the help for the /scratchdir: option.

    The DISM log file can be found at X:\windows\Logs\DISM\dism.log

    G:\w10ent\1>dism /image:f:\ /Cleanup-Image /restorehealth /source:install.wim /scratchdir:f:\scratch

    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1

    Image Version: 10.0.17763.1098

    [===========================83.0%================ ]
    Error: 0x800f081f

    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

    The DISM log file can be found at X:\windows\Logs\DISM\dism.log

    G:\w10ent\1>dir
    Volume in drive G has no label.
    Volume Serial Number is 1E88-C7AE

    Directory of G:\w10ent\1

    06/04/2020 06:38 AM <DIR> .
    06/04/2020 06:38 AM <DIR> ..
    04/27/2020 02:23 AM 3,518,513,484 install.esd
    06/04/2020 06:51 AM 4,101,703,078 install.wim
    2 File(s) 7,620,216,562 bytes
    2 Dir(s) 89,585,070,080 bytes free

    G:\w10ent\1>G:\w10ent\1>dism /image:f:\ /Cleanup-Image /scanhealth
    'G:\w10ent\1' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>Deployment Image Servicing and Management tool
    'Deployment' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>Version: 10.0.17763.1
    'Version:' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>Image Version: 10.0.17763.1098
    'Image' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior.
    'The' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>Use the /ScratchDir option to point to a folder with sufficient scratch space. The recommended size is at least 1024 MB.
    'Use' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>[==========================100.0%==========================] The component store is repairable.
    '[' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>The operation completed successfully.
    'The' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>G:\w10ent\1>notepad
    'G:\w10ent\1' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>G:\w10ent\1>dism /image:f:\ /Cleanup-Image /restorehealth
    'G:\w10ent\1' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>Deployment Image Servicing and Management tool
    'Deployment' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>Version: 10.0.17763.1
    'Version:' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>Image Version: 10.0.17763.1098
    'Image' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior.
    'The' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>Use the /ScratchDir option to point to a folder with sufficient scratch space. The recommended size is at least 1024 MB.
    'Use' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>[===========================83.0%================ ]
    '[' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>Error: 0x800f081f
    'Error:' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>The source files could not be found.
    'The' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
    'Use' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>The DISM log file can be found at X:\windows\Logs\DISM\dism.log
    'The' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>G:\w10ent\1>dism /image:f:\ /Cleanup-Image /restorehealth /source:G:\w10ent\1\install.wim /scratchdir:f:/scratch
    'G:\w10ent\1' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>Deployment Image Servicing and Management tool
    'Deployment' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>Version: 10.0.17763.1
    'Version:' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>Image Version: 10.0.17763.1098
    'Image' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>[===========================83.0%================ ]
    '[' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>Error: 0x800f081f
    'Error:' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>The source files could not be found.
    'The' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
    'Use' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>
    G:\w10ent\1>The DISM log file can be found at X:\windows\Logs\DISM\dism.log
    'The' is not recognized as an internal or external command,
    operable program or batch file.

    G:\w10ent\1>notepad

    G:\w10ent\1>f:

    F:\>f:

    F:\>dir
    Volume in drive F is WIN 10
    Volume Serial Number is 6A93-B81F

    Directory of F:\

    05/12/2020 03:51 PM <DIR> $Windows.~BT
    06/03/2019 03:01 AM <DIR> BILANT
    10/08/2019 12:08 AM <DIR> Brother
    08/24/2019 06:25 AM <DIR> D394
    08/19/2016 02:48 AM <DIR> Intel
    09/14/2018 11:33 PM <DIR> PerfLogs
    03/27/2020 04:22 AM <DIR> Program Files
    02/12/2020 06:27 AM <DIR> Program Files (x86)
    06/04/2020 04:02 AM 0 Recovery.txt
    06/04/2020 10:27 AM <DIR> SCRATCH
    05/20/2020 10:49 PM <DIR> stupid windows
    03/01/2018 08:18 AM <DIR> Temp
    05/02/2018 02:02 AM <DIR> totalcmd
    05/05/2019 07:32 AM <DIR> Users
    05/22/2020 12:08 PM <DIR> Windows
    1 File(s) 0 bytes
    14 Dir(s) 14,829,035,520 bytes free

    F:\>
    i atach here input & outpu in command prompt i(can see atach totxt file or zip file)
     

Share This Page