Romex Software Forum

We have had a shuffling of computers among household members lately, and this involved some tedious preparation. One system -- configured with PrimoCache RAM caching -- had been set up with sleep and hibernate disabled for a span of years. I discovered that I could not get that system to hibernate, but hadn't discovered why. Now, it's interesting that since I moved the PrimoCache license from that machine to my newest system, the hibernation problems with that machine disappeared.

The new system is set-up as dual-boot Win7 and Win10. I went through some hoops to get this all to work reliably and -- especially -- to back up the image of the entire disk storing both OSes, so that a system restore would result in flawless operation. After that, I attended to testing sleep and hibernate functions.

The system would sleep and wake properly, but it would not go into hibernation. Selecting hibernate would sleep the monitor, but the computer would remain running. Clicking the mouse, I discover the system at the logon screen. Also, I think this was a problem I first saw in Windows 10, but on the older system it had occurred in Windows 7. So I should also test it again to my satisfaction in the latter OS for the new computer.

Also, but as far as I can tell at this moment, the problem arises with RAM-caching exclusively, or it only requires active RAM-caching to defeat hibernation.

Is this something that has a remedy? Am I mistaken? Is it something that Romex software engineers may have overlooked?

You might want to try the release L1 cache on fast-shutdown or hibernation. That what I think you are looking for. My computer have issue and that option allowed my computer to sleep and hibernated as normal.

Just as a heads up in response or to anyone, I think I have this partially figured out, but no less "significantly" figured out.

The system in question was set up with two 2,048MB Ram-caches respectively for NVMe boot and SATA HDD. Sometimes, I check these to save and load back at the next boot-time. The SSD-caching would not likely cause a hibernation problem for what I've discovered.

Deleting the boot-drive caching of the NVMe drive, the other drive's cache was left active without change. That situation allows for reliable hibernate.

I'll post more about this after I've discovered more, running some tests. Meanwhile, with Ram caching absent for the NVMe "3,500MB/s seq-read" drive, I have good feelings about making further tweaks.

Did you try the option "release L1 cache on fast-shutdown/hibernation" in the advanced L1 settings as minhgi mentioned? Will this option work for the problem? Thanks.

I'm going to find out. It took me a while poking around to discover this "release L1" feature as a button that had been right in front of me all this time. Will give it a try.

BACK AGAIN.

Yes -- that seems to work. But is it possible to make it work and still set "Prefetch Cache on startup" or however it's phrased? That question is just "off the top of my head," but it was a feature I liked and could use. I should probably poke through the manual some more, but insights would help.

And -- thanks again for the pointer.

BonzaiDuck wrote: But is it possible to make it work and still set "Prefetch Cache on startup" or however it's phrased?

"Prefetch" only works on restart or fully cold boot (I mean, not fast-startup in Win8+). So far, Prefetch doesn't run when resuming from the hibernate state or fast-shutdown.

Thanks for the guidance.