Windows 10: Restorehealth parado no 62.3% e diversas Reinicializações

Meu pc andou tendo diversas reinicializações por motivos diferentes como por exemplo "IRQL NOT LESS OR EQUAL", "PAGE FAULT IN NONPAGED AREA", "MEMORY MANAGEMENT", "BUGCODE USB DRIVER" e alguns outros. Decidi fazer o processo de Restorehealth no cmd e ele ficou preso por bastante tempo no 62.3%. Queria alguma ajuda pra identificar o problema nessas reinicializações.

:)

 

About to buy Xeon ES CPU, Which stepping would be safest

Im gonna have a duel xeon cpu setup, was looking to get couple of E5 ES models since the retails are so expensive, PC will be used for work, obviously
Just need to know what stepping are safe to deal with

Any ideas, suggestions let me know !

Thanks !

 

Error DISM restorehealth

Hello i just registered after i read all the pages...so opencl.dll is a problem of a windows update? Because i had no issues running sfc/scannow last month
**UPDATE**
Thanks it worked perfectly fine and it fixed any corrupted files.This worked perfectly...it was giving me a headache.Step 3 option 2 converted .esd file to .wim...! Thanks again guys.
step 1 delete current dism and cbs log files
step 2 run Image_Health.cmd - option 1 = scanhealth
step 3 run Image health - option 2 = restorehealth
step 4 run image health - option 3 = restorehealth /source (OPTIONAL because step 3 already fixed the issue)

 

Error DISM restorehealth


twp things..

Executing command line: Dism /Online /Cleanup-Image /RestoreHealth /Source:"D:\Users\Hali\Downloads\IMAGE_HEALTH\IMAGE_HEALTH_SXS\Temp\Mount\windows\winsxs" /LimitAccess

Place the "Image_health" folder on C - you are running the command 9 folders deep...
Place Image_health-sxs.cmd inside "image_health" folder
Image health sxs cmd was and is only a TEST cmd
Image-health is the normal cmd...

[removed]

"C:\Windows\Logs\CBS\CBS.log" post the CBS.log

Also dism /scanhealth gives a better file report in the dism.log

Your damaged files appear to be that from a windows update, as windows update files are not on setup media..

step 1 delete current dism and cbs log files
step 2 run Image_Health.cmd - option 1 = scanhealth
step 3 run Image health - option 2 = restorehealth
step 4 run image health - option 3 = restorehealth /source
step 5 post dism.log and cbs.log (note: you can post logs as .txt > cbs.txt dism.txt)