computer bios core speed setting and failing backup
I had changed my cpu clock speed over-clocked from 4300 mhz to 4000mhz by changing the multiplier setting in the bios from 43 to 40. Then tried to do a backup. I got messages seen by others as "Failed to read data from the disk # (where # was either 1 or 2) " and "Failed to read the snapshot". In doing a internet search, I tried some suggested solutions. Chkdsk on the source (C drive) and destination drive (D or E) - to no avail (Chkdsk found no problems). I repaired True Image - again to no avail. I finally went back into the bios and change the multiplier setting back to 43. Now backups are working. Can someone explain why TI is cpu multiplier speed setting dependent? Note that the speed is not fixed. the multiplier varies from 16 to 43 automatically as reported by CPU-Z.


- Log in to post comments

Thanks Steve. Being new to the forum, I not sure how I can check with other posts with over-clocked problems. I would like to know if I have to eliminate the over-clocking and then do new backups. Mounting older backups form older computers have worked in the past. I was told by Acronis support that mounting is going away in the new 2020 TI; so now I just restore the archived disks to another disk. I wonder what other apps are clock dependent. TI must not be using Microsoft's supported API to write/read the disk as Chkdsk works just fine. As TI runs in the background, there is not much time dependency required.
I have been fairly happy with TI since I have bought multiple versions since version 6. But there are hidden situations like this that seem to be a gotcha. I remember reading about TI not backing up browser's bookmarks, but I lucked out by making a bookmark file to move between my browsers.
- Log in to post comments

Charles, do a search in Google using the phrase:
site:forum.acronis.com overclock
this will bring up a number of hits from the forums where overclocking has been involved.
Topic: ATIH 2016 and Overclocking
Topic: ATIH 2019, Overclocking and AVX
plus others are shown in the results.
- Log in to post comments

Thanks, Steve. I looked at the links and found some interesting information. Didn't find anything directly pertaining to my situation. So I set the computer back to non-turbo mode at 3400 mhz and did some incremental backups and verified the backups. Then turbo-ed by to 4300 mhz and did the same. Everything seems to work going between them :>) So I will stay away from 4000 mhz. Note that my cpu is an Intel I7-2600K, which supports over-clocking.
- Log in to post comments

Charles, thanks for the update. I suspect that any over-clocking is going to require a time of trial & error testing given that not all computer components are created 100% identical and some will work better than others in different scenarios.
- Log in to post comments