Romex Software Forum

Microsoft Patch Tuesday triggered a set of patches ... that I thought nothing of... until I got a BSOD loop.

Message is
PAGE_FAULT_IN_NONPAGED?AREA?
what failed: rxfcv.sys

which a quick google search indicated is Primocache which I was running successfully without issue.

I haven't upgrade Primocache in probably at least a year.
the rxfcv.sys file was dated from 2021.

How do I fix this?
I tried renaming rxfcv.sys in System32 from an emergency boot disk; that got me further; but now I'm seeing Inaccessable boot device.

What is the PROPER way to force disable Primocache with regedit?
I've tried booting safemode; but that gives the same stop message.

I really don't want to reset my pc. HELP!

Ok. Fixed this myself...unorthodox solution probably.

Problem config:
PrimoCache 4.1.0
Likely Winblows Patch: 2025-03 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5053602)

Hacky Fix:
1) boot a laptop/system doesn't have latest PrimoCache installed.
2) Install trial version of latest PrimoCache. In my case 4.4.1.
3) don't reboot system after installation complete.
4) go to Windows/System32/drivers and copy rxfcv.sys to a usb stick.
5) eject usb stick

6) Boot emergency disk and mount the Windows Partition of the problem installation.
7) copy rxfcv.sys from usb stick; replacing it on the faulty Windows/System32/drivers installation.
Mine went from 2021 to a 12/2024 date on rxfcv.sys.
8) eject and uninstall usb stick.
9) exit command prompt and reboot device.
10) System should boot into windows.
11) Exit primocache in the system tray.
12) download and install the latest version of primocache.
13) restart windows.

Windows boots with correct drivers and Primocache should launch automatically.

Another way to fix the boot BSOD:
viewtopic.php?p=14537#p14537

Cool. Maybe put this somewhere obvious in the FAQ section of PrimoCache.
Admittedly I didn't look thru every entry; but, this "fix"/workaround didn't jump out at me.