CTO error message when doing total recovery of HP laptop

May 5, 2017 at 20:39:03
Specs: Win 10
Using hp recovery kit. Following instructions. Error message says unexpected reboot during (win setup) causing cto panic. Image might mot be normal.

See More: CTO error message when doing total recovery of HP laptop

Report •

#1
May 5, 2017 at 21:22:55
HP restoration incomplete error "fix"
http://emergencytech.blogspot.com.a...


Report •

#2
May 6, 2017 at 14:35:51
unfortunately that is not the same error I got Mine is as follows :

[C:\SYSTEM.SAV\ExitProc\ErrorChk\ChkError.cmd] has started...
[21:53:13.02] --------------------------------------------------
[21:53:13.02] Check SW Error...
[21:53:13.04] --------------------------------------------------
[21:53:13.05]
[21:53:13.07] Create ["C:\system.sav\ChkError.cmd.FAILURE.flg"] file...
[21:53:13.09]
[21:53:13.10] Logfile [C:\system.sav\Logs\CheckLog\ChkErr_PASS2_FUpdate_END.log]...
[21:53:13.10]
[21:53:13.12] Check 2nd parameter [PASS2FU]
[21:53:13.15]
[21:53:13.15] Error Checking items : [MEMDUMP,REGDEV,TIMEOUT,BADLINE]
[21:53:13.18] --------------------------------------------------
[21:53:13.18] Checking : Memory Dump
[21:53:13.19] Could not find memory dump...
[21:53:13.21]
[21:53:13.23] [DumpFile]
[21:53:13.24] Result=PASSED
[21:53:13.26] --------------------------------------------------
[21:53:13.27] Checking : Yellow-Bang
[21:53:13.29]
[21:53:13.30] This is under WinPE environment...
[21:53:13.30] Skip Yellow-bang checking...
[21:53:13.32] [RegistryDevicesCheck]
[21:53:13.34] Result=IGNORED_BECAUSE_WINPE_ENV
[21:53:13.35] --------------------------------------------------
[21:53:13.37] Checking : Timeout in INSTALL.log
[21:53:13.37]
[21:53:13.38] Run [FIND.exe /I 'timeout with' C:\System.sav\Util\Install.log]
[21:53:13.90] Run [FIND.exe /I 'timeout wait' C:\System.sav\Util\Install.log]
[21:53:14.34] There is NO timeout in install.log file.
[21:53:14.35]
[21:53:14.35] [TIMEOUT]
[21:53:14.37] Result=PASSED
[21:53:14.38] --------------------------------------------------
[21:53:14.40] Checking : Bad Line in INSTALL.log
[21:53:14.41]
[21:53:14.43] Run [cscript.exe c:\System.sav\ExitProc\ErrorChk\BadLine.vbs]
FAILED : DATA CORRUPTION
FBI was terminated in INSTALL.LOG at line(s):
=> [20:37:25.242] NOTICE: **** if running a Service Pack -- DO NOT DO A PROCESS INFORMATION DUMP ****

RESULT=FAILED

[21:53:14.67] There is Bad Line in install.log file.
[21:53:14.67]
[21:53:14.69] [BADLINE]
[21:53:14.70] Result=FAILED
[21:53:14.72]
[21:53:14.72] --------------------------------------------------
[21:53:14.73] Some error detected...
[21:53:14.76]
[21:53:14.76] --------------------------------------------------
[21:53:14.78] [C:\SYSTEM.SAV\ExitProc\ErrorChk\ChkError.cmd]
[21:53:14.80] [PASS2_FUpdate_END][PIN_ERROR_MSG][ChkError.cmd] found [1] SW issue[s]...
[21:53:14.81] --------------------------------------------------
[21:53:14.83] [PASS2_FUpdate_END][PIN_ERROR_MSG][ChkError.cmd] Refer the following file[s] if exists to see detail.
[21:53:14.84] [PASS2_FUpdate_END][PIN_ERROR_MSG][ChkError.cmd] C:\CTOERROR.flg , C:\System.sav\*FAILURE.flg, or C:\system.sav\Logs\AllFailure.log
[21:53:14.86]
[21:53:14.86] --------------------------------------------------
[21:53:14.87]
[21:53:14.89] This is for customer image...
[21:53:14.91]
[21:53:14.91] Trigger CTO panic...
[21:53:14.92]
[21:53:14.94] This is Recovery image...
[21:53:14.95]
[21:53:14.95] --------------------------------------------------
[21:53:14.97] [ChkError.cmd] has completed...
[21:53:14.98] **************************************************


Report •
Related Solutions


Ask Question