One could wonder why, when a user ran successfully as I did RAM Disk 3.4.2, would that user switch to 3.4.5.
In fact, Andrew, you proposed on another post of mine here, to stick to 3.4.2 if all was ok. This is logical.
Well, the point is I have been having very surprisingly (I'm very cautious about the computer) a few crashes mainly when a driver was modified. For instance yesterday I installed latest NVIDIA GeForce Driver 334.89 and, when I later on rebooted I had a crash : Microsoft repair detected nothing at all, I closed the computer, then booted cold, and all was fine. Similar crashes occurred previously, always on reboot (hot boot), never on cold boot.
I scoped possible causes without ever thinking of an issue with RAM Disk + CCleaner pair. Especially that these crashes started late after RAM Disk install.
But also, I imagined that it could be related to RAM Disk in particular, specific circumstances. This is why I switched to 3.4.5 (in fact I aborted install at this time).
Discovering the warning (good point for popping it on install), I now take into consideration a RAM Disk related issue, even if :
1- No proof (impossible to reproduce a reboot crash) ;
2- If, would be related to the RAM Disk + CCleaner pair.
I've tried to find on the Web testimonies of this binomial issue, found one but related obviously to the fact of having the TEMP folder set in the RAM Disk. That's why I mentioned this point.
Now, if CCleaner is really a troublemaker when RAM Disk is installed, I really don't have the start of the beginning of an understanding. In what could both be related to ? They seem to operate in totally uncommon grounds ...
One of those mysteries. I'll have to make a choice or to choose a volatile RAM Disk, not handy in my perspective.
Thanks Andrew for your quick information.