Fail to start cache

[tkemp66]

I recently installed windows 10 fall creator and I believe it may have affected the cache on my ssd drive. I had to reformat the drive and create a new cache, but any time I try to create a new L1 and L2 cache, I get "Fail to start cache." Is there anything I can do to fix there error? Thanks

Troy

[tkemp66]

Is this the right place to report this problem I'm having?

[Support]

Did you try a bigger cache block size? I see current configure will cost additional 2.53GB memory which is quite big.

[tkemp66]

Did you try a bigger cache block size? I see current configure will cost additional 2.53GB memory which is quite big.

I did, and regardless of what size I choose, I get the same error. Nothing has changed from hardware or setup perspectives except a windows update. This is when I noticed the problem.

Troy

[tkemp66]

So I eventually got a BSOD trying to change things around in primocache. I have also been following this case: (https://www.romexsoftware.com/bbs2/en-u ... =33&t=4460) closely because it could be related to my issue. I believe recent updates in windows 10, for instance, Fall creators update, might have caused the issue with primocache. So I'm trying to find a way to see when the changes occurred in primocache. I know the fall creators update happened on 10/26/2017, but is there a way to see when and what changes actually occurred in primocahce? I was looking for a log file for primocache and could not find one. Maybe you can help?

[Support]

Could you go to Windows Event Viewer (right click on Windows Start and choose Event Viewer in the pop-up menu) and find an event issued by "FancyCcV". Every time PrimoCache failed to start a cache task, it will log an event. I'd like to see the event data (Event Viewer -> Custom Views -> Administrative Events -> Filter events by source "FancyCcV" -> Find and click on the event related to the creation failure -> Details -> Friendly View -> Binary data)
Thanks.

[tkemp66]

This is the last one recorded:
PrimoCache driver was not loaded correctly.

Binary data:

In Words

0000: 00080000 00000001 00000000 E0060001
0010: 00000001 00000000 00000000 00000000
0020: 00000000 00000000 4306C170 FFFFCF86

In Bytes

0000: 00 00 08 00 01 00 00 00 ........
0008: 00 00 00 00 01 00 06 E0 .......à
0010: 01 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 70 C1 06 43 86 CF FF FF pÁ.C†Ïÿÿ

[tkemp66]

This is another:
PrimoCache driver was not loaded correctly.

Binary data:


In Words

0000: 00080000 00000001 00000000 E0060001
0010: 00000001 00000000 00000000 00000000
0020: 00000000 00000000 9095CCC0 FFFF8A0C


In Bytes

0000: 00 00 08 00 01 00 00 00 ........
0008: 00 00 00 00 01 00 06 E0 .......à
0010: 01 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: C0 CC 95 90 0C 8A FF FF À̕.Šÿÿ

[tkemp66]

Hellooooo!!!

[RobF99]

Yes I have the same issue as per the topic you linked to. I have 32 Gb RAM and the largest L1 I can create is about 2 Gb. Higher than that I get the same type of errors and BSOD like you. I use Windows 7. Not sure what caused my problem but like you, it used to work fine and I had no limits to the L1 size that I could create. I've been using PCs for 30+ years and there is nothing in my bag of tricks that I tried that would work. Increasing block size does not fix the problem. I too, am awaiting help on this.