Skip to main content

True Image home 2010 chaos

Thread needs solution

XP SP3, 2gig of memory.

Been using TI for years, but I had to re-install, on using the CD, got the latest build, installed fine.

On running a basic disk image backup the program uses up to 900,000K of memory and 100% CPU bringing my system to almost a halt.

Monitoring with the Task Manager, when the program is closed, under the Process Tab... it is still there and using 833,000k of memory...and 100% CPU.... can only kill it with End Task.

Uninstalled, rebooted, reinstalled, same problem.

Never before did I have these kind of problems.
any ideas?

0 Users found this helpful

As a follow-up, when TI is closed it remained using about 800,000k of memory for about 20 minutes before it released the memory.

And, when TI starts up it will be at about 75,000k of memory used.
THEN, doing nothing.... it starts consuming more and more memory,no backup running,
nothing... just the opening desktop screen.... non-stop backup is not turned on.

Downloaded 7154 (again)... did a Repair, re-booted, same results... 100% CPU and all
available memory used (1.2 gig)

Strangely, my scheduled tasks appear to be working fine

not sure how to monitor Priority setting.

AMD Sempron 2600+ is the CPU

Since this posting I got Grover's Cleanup Utility, ran it to remove TI Home, rebooted,
edited the Registry and removed anything that was Acronis, rebooted, re-installed (build 7154)
..... same results= 100% CPU and TI opening at about 78k and continually "growing"
to finally consume 1.3 gigs (all my free memory)
When TI is closed it stays in memory (monitored with Task Manager) constantly going
up and down in memory usage... finally has to be "Killed"

Strange happenings here

The Backup priority options can be found in the Backup options section of TI's options. There are default options you can set in TI and options for each task. The default setting is Low.

You can also check what Priority is being used the TI by looking in the Task Manager. Click the Processes tab and then right-click TrueImageHomeService.exe. Select Set Priority and see if it's on Low.

What build were you using before that didn't cause this problem? What was the CPU and RAM usage with it (if you remember)?

I need to clarify something...
When I open TI and do absolutely nothing the pgm starts to eat up memory.
There is no job running, constant backup is Off....

since i never had a problem before I cannot answer your question about prior CPU/memory usage.
Probably the version was the one before 7154 as I try to keep my software up to date.

I'm seeing a problem like this, but under Win7x64. My processor is an AMD also, if that has anything to do with it. I have Avast anti-virus, not Avira. There have been some problems reported with Avira. I ran TI2009 under WinXP and it usually ran fine.. I just opened up my own post. Following is what I put in that post.

I’m trying to get any version of Acronis True Image Home to run under a Win7 Home Premium x64 running on a new HP p6710f AMD Athlon II quad core desktop computer with 4 GB of RAM.

When I run Acronis TI Home it just keeps on asking for more and more memory until it gets up to 2GB and then windows closes the program. I can see this using the task manager. I’m actually trying to get any version of Acronis True Image to run under Win7 on this machine. I’ve tried Acronis TI2011 which is supposedly made to run under Win7x64 but it quits with a C++ runtime error. A lot of people talk about this problem on these forums.

Then I tried TI2009 in every compatibility mode from WinXP SP2 to Vista SP2 and native Win7 mode and keep on getting the same result. Then I put on a trial version of TI 2010 Backup and Security and when I ran it the same thing happens. The program just keeps on eating memory until it closes. Does anyone have any ideas what is causing this and how to fix it?

Thanks,
Roger

this is getting spooky... all problems have gone away.
TIH starts, loads fairly quick, uses about 71,000k of memory and that is it..
No longer does it eat up all my available memory.
NO software changes... nothing....

"IF is ain't broke don't fix it"