SD 3.2 - using more than 90% of CPU

[Whiplash]

After I updated to the newest SD, it started to behave weirdly. I guess every time it needs to do an auto defrag, my PC is almost frozen because SD is using more than 90% of CPU suddenly. Previous (SD 3.1) was just perfect.

[Cicely]

Hi Whiplash,

 

Sorry for my late reply.

 

For the situation you mentioned, does Smart Defrag always take up 90% CPU? Or does it just happen when you defrag several disks together?

 

If you did not defrag several disks together the CPU is high, please download the tool from http://testdemo.iobit.com/SDInfoHelper.exe

 

Then double click to run this tool and click “Save report to Desktop”. You will get a zipped file IObit_Debug_Info.zip on your desktop. Please send it to us so that we can get the detailed information to look into.

 

Looking forward to hearing from you.

[Whiplash]

It's starting to use over 90% at a random moment - at least I understood it like that. I actually turned back to 3.1 and wanted to stay there since I already reinstalled 3.2 twice.

But in order to help you, I decided to install it again today. And, it was working nicely for few hours, but I wanted to catch it up at the moment when it consume more than 90% of CPU and use your tool right at that time. And finally, it happened again while I was browsing the Internet. I noticed that something is wrong when the browser (Opera 23) didn't want to load a web page. So, it obviously also cause the Internet disconnection (one of my programs for chatting -Miranda NG - lost connection too).

Anyway, I'm having an quite old PC: 1 HD with 2 partitions. And here are the zipped files. I hope they will help you. I decided to make 2 of them: one is when cpu is consumed by over 90% - the other is when SD was working normally. I did it like that because I didn't know there will be any important difference.

http://xtreame-team.game.ba/other-downloads/IObit_Debug_Info-over90cpu.zip

 

http://xtreame-team.game.ba/other-downloads/IObit_Debug_Info-normal.zip

 

I'll now go back to 3.1 because I don't want my PC experience this again when I'm not close to it.