By default, the L2 cache retains its cached data across computer restarts. If your L2 cache content gets cleared from time to time, you can first check whether it is caused by the following reasons.
-
Ungraceful shutdown or startup failureSince the index data of the L2 cache may be corrupted or cannot be updated during ungraceful shutdown, in order to avoid serious problems caused by index errors, PrimoCache will actively clear the L2 cache content when it detects an ungraceful shutdown or startup failure.
Note: Starting with version 4.0, PrimoCache will validate L2 cache data by comparing it to source disk data when an ungraceful shutdown is detected, rather than simply resetting the L2 cache.
-
Are using cracked software or have ever installed cracked software
If you have ever installed a crack program for Romex software, your computer may have been running the crack program in the background, causing various problems such as resetting the L2 cache. Please refer to this article for the removal method of cracked software.
-
Windows system partition or registry is write-protected
PrimoCache determines if there was an ungraceful shutdown by tracking and updating data saved in the Windows registry. If data cannot be updated, PrimoCache will assume an ungraceful shutdown and will reset the L2 cache.
- "Volatile Cache Contents" option is checked
When configuring the cache task, if the "Volatile Cache Contents" option in the Advanced Level-2 Cache Options dialog is checked, PrimoCache will reset the L2 cache every time the computer restarts.
- PrimoCache version is too old
-
L2 cache disk or accelerated disk disconnectedWhen the L2 disk or the accelerated disk is disconnected from the computer due to physical connection failure or system software error, PrimoCache will clear the corresponding cached data. Common situations include loose cable connection, loose USB port, accidentally unplugged USB disk, accidentally disconnected iSCSI disk, etc.
-
Windows Fast Startup is enabled
If none of the above reasons work, you can try turning off Windows Fast Startup. The Fast Startup feature is prone to failure of fast startup. On startup failure, PrimoCache resets the L2 cache, as mentioned in the first reason. To disable Windows Fast Startup, open the PrimoCache options dialog, and then click the "Turn Off" button next to the "Windows Fast Startup" item.