Your device ran into a problem and needs to restart

[stefanjan2]

I'm getting frequent computer crashes and reboot when I open imatch with the error "Your device ran into a problem and needs to restart"

Every time I open imatch after a crash it adds loads of files to the database.

If I don't open imatch, then my Windows 11 computer seems stable.

I appreciate that this could be a problem not caused by imatch but more about heavy processing within imatch triggering a hardware issue.

In the log file, I'm seeing a few warning messages like this:

09.23 18:49:28+ 4953 [4F5C] 01  W> Failed to create cache image for [8210] 'E:\Photos\2012\05 Morocco\00027.MTS' => 'E:\imatch cache\C1B4B049-CF54-4238-978A-9B1F207DA12C\82\8210.jpg'. Check file system permissions and disk space.

There is plenty of disk space on the E drive and I don't seem to have a problem with any other files creating a cache.

I've attached the log file.

[Mario]

The error with the .MTS is probably just a "not a supported file format" issue. Can happen. There are many different variants in use and FFMPeg may not handle it. Or the file is corrupted.

IMatch is doing a lot of cache purging, removing between 50 and 250 files per purge. It seems the cache size you have set under Edit > Preferences > Cache has been reached.

That's all I can tell from this short log file.

When your computer crashes and reboots while IMatch is indexing images or performing face recognition, the system most likely has stability issues under prolonged heavy load. These issues may not show when you are browsing the web or watching videos or doing Office work.  But IMatch can max out your CPU, disk and GPU within the limits set by the Performance Profile and, sometimes, computers cannot handle heavy load for prolonged intervals.

Try to reduce the performance profile to Balanced or Low to see if this helps. If this avoids the computer crashes, there is definitely a stability issue. Check the Windows Event log for hardware-related errors logs. Clean the fans. Remove and re-add the RAM sticks (they may become "loose" and cause all kinds of issues under stress). If you a 3d party virus checker, check its logs.

[stefanjan2]

IMatch is doing a lot of cache purging, removing between 50 and 250 files per purge. It seems the cache size you have set under Edit > Preferences > Cache has been reached.

I've increased the cache from 100mb to 500mb. I have a 4TB Samsung 990 EVO Plus m.2 just for photos containing cache, database and images.

Try to reduce the performance profile to Balanced or Low to see if this helps.

Performance was set to Default, but as this was not the problem, changed it back to default.

If this avoids the computer crashes, there is definitely a stability issue. Check the Windows Event log for hardware-related errors logs. Clean the fans. Remove and re-add the RAM sticks (they may become "loose" and cause all kinds of issues under stress). If you a 3d party virus checker, check its logs.

Followed all these steps, but did not resolve issue. I wondered if I could run something other than imatch which would put the system under stress. Out of my depth here but ChatGPT to the rescue and the first thing I tried was OCCT https://www.ocbase.com. Ran various tests until "Memory" immediately flagged errors. Tested 1 of my sticks at a time and identified the faulty stick. Ordered new RAM which is arriving tomorrow.

I've attached the ChatGPT information which I found really great for someone who did not know any of this. I've attached this in case it helps someone else with a similar problem.

Many thanks Mario for once again giving amazing customer support and sending me in the right direction.

[Mario]

I've increased the cache from 100mb to 500mb.

That's the wrong setting. If IMatch is constantly purging cached files while you add new images, the Maximum Cache Size (GB) configured has been exceeded. 

A 100% JPG cache for a 12MP RAW image needs 1.5 to 2.5 MB on disk. This gives about 500 to 600 images per GB cache space. Depending how how large your "working set" is, use that as an indicator for a good setting that keeps images you access frequently in the cache, without wasting to much disk space.

Many thanks Mario for once again giving amazing customer support and sending me in the right direction.

You're welcome. Good to hear that you found a solution.

When IMatch is in full-flight indexing images, performing face recognition, it can utilize your system by 80% and in peaks 100%, depending on the power plan. This is a good thing because no resources are left idling, and the task at hand is processed as quickly as possible. I've spend weeks developing, testing and tuning the new background processing system for IMatch 2025.

Occasionally (rarely) this prolonged utilization reveals "hidden" issues with hardware. RAM cells may be used which normally lie fallow, but when IMatch peeks memory utilization to 85% or 90%, these cells get used, and fail. And a failing RAM chip can have all kinds of strange effects, from spontaneous reboots to application crashes. Good that you figured it out.

Good advice from ChatGPT for testing the hardware for faults under stress. 

[stefanjan2]

A 100% JPG cache for a 12MP RAW image needs 1.5 to 2.5 MB on disk. This gives about 500 to 600 images per GB cache space. Depending how how large your "working set" is, use that as an indicator for a good setting that keeps images you access frequently in the cache, without wasting to much disk space.

Trying to figure out from your explanation what I should set my maximum cache size to.
My main camera is 32.5MP and creates around 26.5MB CR3 files on disk.
What do you mean by "working set"? Does this mean the number of images I am currently culling, which could be say 3,000. Should the cache size be 3,000 x 26.5MB = 79.5GB
In which case my original maximum cache size of 100GB would not have been far off.

I attach a screen shot of my info panel in case that helps.

I could not find in help advice on setting maximum cache size

Occasionally (rarely) this prolonged utilization reveals "hidden" issues with hardware. RAM cells may be used which normally lie fallow, but when IMatch peeks memory utilization to 85% or 90%, these cells get used, and fail. And a failing RAM chip can have all kinds of strange effects, from spontaneous reboots to application crashes. Good that you figured it out.

I've been experiencing imatch shutting down every so often for quite a few months which was irritating due to reloading files but it did not occur to me that I had a hardware problem. This became serious over the last week or so. Now I know why. Very happy that I now have a stable system and imatch is working wonderfully .

[Mario]

You can look at the files in the cache folder (they are JPG images) and see their size. You can find the cache file name of an image using the  {File.CacheFileName} variable in VarToy.

The default 100GB size should work for most users. Purging files from the cache is a normal process, and it does not interfere with IMatch usage. If the maximum cache size is reached, and new images come in, older cache files must go.

I just mentioned it when analyzing your initial log file in case it was somehow related to the problem at hand.