Page 1 of 1
Primocache 3.0.1 prevents sleep
Posted: Sun Dec 17, 2017 7:21 pm
by jussssx1
Hello,
I tried primocache 3.0.1 and the speed is incredible!!
However,
the system immediately returns from sleep when Primocache is installed.
Is this a known bug and is there some workaround?
thank you in advance!
Re: Primocache 3.0.1 prevents sleep
Posted: Mon Dec 18, 2017 9:25 pm
by minhgi
try teh option flush L1 cache on sleep or hibernation
Re: Primocache 3.0.1 prevents sleep
Posted: Tue Dec 19, 2017 5:28 am
by jussssx1
Yes, already tried that but it does not help. Thanks for the tip though!
Re: Primocache 3.0.1 prevents sleep
Posted: Tue Dec 19, 2017 1:41 pm
by Support
Your Windows OS? And cache configuration?
Thanks.
Re: Primocache 3.0.1 prevents sleep
Posted: Tue Dec 19, 2017 6:03 pm
by jussssx1
My Windows version is Win 10 Pro, build 16299.125; cache configuration is
16 gt reserved for L1 cache for C, D and E drives
Re: Primocache 3.0.1 prevents sleep
Posted: Wed Dec 20, 2017 2:26 am
by Support
Is the PrimoCache GUI program open when you sleep the computer?
Re: Primocache 3.0.1 prevents sleep
Posted: Wed Dec 20, 2017 7:23 am
by jussssx1
Hmm.. no. But I did run powercfg -systemsleepdiagnostics and something peculiar is there. Entering the sleep mode (while primocache is active) results the following:
TIME USER WENT IDLE IDLE DURATION SLEEP STATE ENTERED
6 2017-12-17 19:30:27 0:29:21 Invalid
and then
The system idle time was reset because: An application has indicated the user is present. 0:42:39 2017-12-17 19:59:47
while the application mentioned is
START TIME DURATION TYPE TOKEN
2017-12-17T19:39:06 0:00:00 System 0xffff8f0213460bf0
Re: Primocache 3.0.1 prevents sleep
Posted: Wed Dec 20, 2017 7:28 am
by Support
Thanks for the information!
Re: Primocache 3.0.1 prevents sleep
Posted: Thu Dec 21, 2017 7:00 pm
by jussssx1
This problem seems to be fixed in version 3.0.2! Thanks
Re: Primocache 3.0.1 prevents sleep
Posted: Fri Dec 22, 2017 2:52 am
by Support
3.0.2 fixed the bug that GUI program prevents computer logoff/shutdown. It seems that here the problem was also caused by the GUI program.
Anyway, I'm glad that the problem is solved now!
