BSOD (CACHE_MANAGER) on running Ext2Mgr after installation

[robinhood2014]

This program seems to be totally broken. When I finish installing Ext4Fsd and run Ext2Mgr afterwards, Windows panics with a BSOD saying "CACHE_MANAGER". The result, after rebooting, is an Ext4Fsd service that will not start.

[bobranten]

Please share the memory dump in \windows\minidump\ it will help us analyze the problem.

[theAeon]

042025-12718-01.dmp

Here's one. Triggered while system was under load and an ext4 drive was plugged in.

[Armel081]

this happened to me with Ext2Fsd while doing a quick format because of an unfixed bug with CCPurge in cleanup.c which is apparently still present in this fork.

[jithatsonei]

050625-10078-01.dmp
050625-10109-01.dmp
050525-9937-01.dmp
050525-10125-01.dmp
050525-10328-01.dmp

been encountering this one, pretty random in nature but always w/ no drives mounted.

[bobranten]

Thank you for sharing those memory dumps! I have analyzed them in WinDbg and the crash occurred on the same place in all of them: It is when CcUninitializeCacheMap is called in the end of Ext2InitializeVcb when it fails. This is around line 2750 in memory.c. However it remains to understand what the fix should be.

[bobranten]

In the middle (around line 2490 in memory.c) of Ext2InitializeVcb we create a stream file object and set SectionObjectPointer in it, however if the function fails before that, in the cleanup in the end it will always call CcUninitializeCacheMap. Perhaps we should change (around line 2750 in memory.c)
if (Vcb->Volume->PrivateCacheMap) {
Ext2SyncUninitializeCacheMap(Vcb->Volume);
}
to
if (Vcb->Volume->PrivateCacheMap && Vcb->Volume->SectionObjectPointer) {
Ext2SyncUninitializeCacheMap(Vcb->Volume);
}

[vovamod]

082325-7078-01.dmp

Confirm about BSOD caused by cache_manager. dump included:

• tried to run apps that rely on streaming or buffer
• tried to run cyberpunk 2077 (not redlauncher initiates the crash)

[vovamod]

In the middle (around line 2490 in memory.c) of Ext2InitializeVcb we create a stream file object and set SectionObjectPointer in it, however if the function fails before that, in the cleanup in the end it will always call CcUninitializeCacheMap. Perhaps we should change (around line 2750 in memory.c) if (Vcb->Volume->PrivateCacheMap) { Ext2SyncUninitializeCacheMap(Vcb->Volume); } to if (Vcb->Volume->PrivateCacheMap && Vcb->Volume->SectionObjectPointer) { Ext2SyncUninitializeCacheMap(Vcb->Volume); }

after trying that thing, when loading system with fresh service that include thy code my drive that was ext4 now said ext3 in ext2 volume manager and showed as full (when mounter to windows it suggested to format it) which... actually makes a bit of sense