Navigation: FAQ & Troubleshooting >

High CPU usage

Send comments on this topic.

Home Page





High CPU usage.

You have a file (or files) that is causing MysticThumbs to run a process (usually rundll.exe or Explorer.exe) at 100% that never seems to quit, OR Explorer crashes when opening specific folders to view.


Some files are written differently by various applications and sometimes there are also other parts written into files that are not handled well when parsing the file. This can lead to erroneous problems like crashes or processes getting stuck when trying to decode them.


Any number of variations on files or even half written files from applications crashing when writing can cause files to be internally different from the format specification that MysticThumbs expects in order to decode and display the file.



In order to track down what files are causing problems follow the following steps to try to pinpoint the specific file format/extension and possibly the specific files themselves.


1.Think about which folders are causing problems specifically and check which file formats are in those folders. The folders to look for are ones you just opened when you get a 100% CPU task or Explorer crash when opening.

2.Close all Explorer folder windows and all open applications.

3.Disable all file formats thumbnails and small icons and apply.

4.Enable just one file format you decided on in step 1 thumbnail mode only and apply.

5.Open a folder with possible problematic files / formats in it and see if the problem persists or the folder generates and displays files normally.

6.If there is a problem with the folder opening and displaying files, and you get a 100% task, this folder likely has a problem file.

Hover the mouse pointer over the MysticThumbs tray/notification icon, usually at bottom right of screen, to see what file is currently being processed. The tooltip should display a file name. This file name should be the problem file. You can then send this file attached to a support request to us to investigate and optionally move it to another folder that you are not going to use for safe keeping to prevent the problem for the time being.


Copyright © MysticCoder Pty Ltd