Random Crashes using FF14

I posting this in hopes it helps others who are experiencing similar issues running Windows 11

There has not been much response, or instruction on how to resolve these issues; I submitted a ticket for this quite some time ago. I have asked AI to look into the specifics of these current crash reports, one of which I did submit to you all recently.

Potential Fixes and Workarounds suggested by AI (some of which I applied)

1. Upd ate Filter Forge to Version 15. But I question FF developers as to whether or not they have addressed these issues with Windows 11 in Version 15
2. Update Graphics Drivers -->I did update my Nvidea RTX 4070 laptop driver
3. Adjust Display Settings: -->I se t my display to 100% - recommended settings
*Try setting your display scaling to 100% or 200% (Settings > System > Display). Some crashes tie to fractional scaling (e.g., 125% or 150%) messing with UI repaints. If using multiple monitors, test on a single screen or match DPI settings across them.
4. Editor Workarounds: -->I began using the in app zoom to fit and this has reduced the amount of crashes
*Keep your filter layouts compact—avoid spreading components too far, as this triggers navigation crashes.
*Use the "Zoom to Fit" button instead of manual zooming/scrolling.
*Save frequently (Ctrl+S) and work in smaller groups/snippets to minimize loss.
*If possible, test simpler filters first to isolate if complexity is a factor.
5. Other Troubleshooting: -->closed and disabled some processes
*Close background apps/processes before launching Filter Forge, especially anything telemetry-heavy (more on that below).
*Run a system file check: Open Command Prompt as admin, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth.
*If crashes persist, generate a new error report and send it to their support again, referencing your past reports and this exact stack trace. Mention the OS misdetection—it might prompt them to investigate Win11 24H2 compatibility.

Other information that AI included with workaround steps:
"Windows 11's telemetry can be aggressive, spiking CPU/RAM and potentially interfering with resource-intensive apps like Filter Forge"

**Check Task Manager
**Change advanced power settings, and disable wake timers or fast startup -->(I did go through some processes for my unique setup and apps running with AI and se t some parameters in Group Policy for unnecessary processes and apps to cut back on resources)

And finally a detailed answer by AI regarding my specific initial crash report which led me to complete steps above:

It looks like you're dealing with a frustrating, recurring crash in Filter Forge 14's filter editor, specifically tied to UI rendering (the WM_PAINT message handles painting/redrawing the window, and exceptions there often point to graphics or compatibility glitches during actions like scrolling, zooming, or moving components). The "kernel" references in the stack trace (e.g., KERNELBASE.dll) are indeed part of Windows' core system components, but they don't necessarily mean an OS-level failure—more often, they're catching unhandled errors from the app itself, like access violations during drawing operations.Your system's specs (i9-13900HX, 65GB RAM, 32 cores) are plenty beefy for Filter Forge, so hardware overload seems unlikely unless there's a GPU bottleneck or driver conflict. Note that the error log misidentifies your OS as Windows 10 (build 26100 is actually Windows 11 24H2), which could hint at a compatibility detection issue in the app.From digging into similar reports on Filter Forge's forums and elsewhere, this type of crash (XFW::Exception during WM_PAINT in the filter editor) has been reported across versions 5 through 14, often during navigation in complex filters. It's not isolated to you—users on Windows 11 (including 24H2) describe the same symptoms: random terminations when spreading out modules, scrolling, or zooming. Developers have acknowledged it in some threads but haven't released a targeted fix; they sometimes request filter files to reproduce it, but resolutions are spotty.

------------
Today, after having some success with these suggestions, I received another crash.
I sent it to the AI and its response was as follows:

This new crash is different: it's triggered by mouse interactions (WM_LBUTTONUP = left mouse button release, likely after clicking/dragging a component, connection, or button), and the core error is ::CreateFontW(Segoe UI, 14, 0) failed. That's a Windows GDI call to create a font object for UI text (Segoe UI at 14pt is common for labels/tooltips in the editor).
Failures here usually mean a low-level graphics/resource issue, like:
*Temporary exhaustion of GDI handles (rare on your beefy system, but possible if many apps open or a leak).
*Corrupted font cache.
*Graphics driver glitch when allocating font resources during UI updates.
*Compatibility quirk on Windows 11 24H2 (the app still misdetects it as Win10).
It's not as common as the paint-related crashes, but similar editor instability has been reported.

Potential Fixes and Workarounds suggested by AI (for second crash report) :

1. Rebuild Font Cache (since it's a font creation failure):
*Close Filter Forge.
*Open Services (services.msc), stop "Windows Font Cache Service" if running.
*Delete the font cache files: Navigate to C:\Windows\System32\FNTCACHE.DAT (delete it—admin rights needed) and/or C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache (delete contents).
*Reboot—Windows will rebuild the cache.
*Test Filter Forge.
2. Graphics Driver Refresh:
*Download and run Intel's Driver & Support Assistant (intel.com) for your i9-13900HX integrated graphics.
*If you have a discrete NVIDIA/AMD GPU, update that too.
*After update, reboot and test.
3. GDI Handle Check (unlikely issue, but easy to rule out):
*In Task Manager > Details > Look for high GDI Objects on Filter Forge process (normal is <500; if spiking to 10,000+, that's a leak—but doubtful here).
4. Continue Safe Habits:
*Keep scaling at 100% for now (or test the high-DPI override I mentioned before).
*Avoid rapid clicking/dragging if possible—use keyboard shortcuts more (e.g., Ctrl+C/V for copy-paste components, arrow keys for nudge).
*Save often!

One theme that keeps coming up within these crash reports are that the app seems to be pointing to "Windows 10" when, clearly, I am running Windows 11 Pro version 24H2. AI Response: "Note that the error log misidentifies your OS as Windows 10 (build 26100 is actually Windows 11 24H2), which could hint at a compatibility detection issue in the app."

And again, for the second crash report, it suggested upgraded to Filter Forge 15, however, please address whether or not the developers have upgraded Filter Forge 15 to be compatible with Windows 11. I just upgraded to Filter Forge 14 in Spring of 2025. I don't want to upgrade until I can see these compatibility issues are addressed. In the meantime I am going to try using FF 14 in Windows 10 compatibility mode.