Hi,

So, in your previous question, you didn't share crash IDs as I asked. Please note that this makes it harder to understand your issue and help.

Also, if "not only firefox breaks, but also chrome, brave, etc.", why do you think it's a Firefox issue?

Talk normally, I didn't send the failure ID because I already scored on the problem and didn't see the message with the answer to the topic, now I provided everything, all the error codes and identifiers, I'm not saying that the problem is in firefox, the problem is in the engine on which it works, because for example, microsoft edge works, but I don't like it

First, please stay respectful, as I do.

Also, could you please point me to the error code in your message? Maybe I've missed it?

Note that Firefox and Chrome have different engines, but it's indeed weird that Edge is not affected (given that it shares its engine with Chrome).

Isn't that it? AvailablePageFile: 37469605888 AvailablePhysicalMemory: 32424693760 AvailableVirtualMemory: 138531310682112 BackgroundTaskMode: 0 BuildID: 20260403140140 CPUMicrocodeVersion: 0xa20120a CrashTime: 1775599624 DOMFissionEnabled: 0 DOMIPCEnabled: 0 HeadlessMode: 0 InstallTime: 1775587593 LastStartupWasCrash: 0 MinidumpSha256Hash: 89a8c6296c245dae30e1562163d1ec0d37df24dffa0a6e612f9294854213f8ff ModuleSignatureInfo: {"Mozilla Corporation":["firefox.exe","xul.dll","gkcodecs.dll","nss3.dll","mozglue.dll","lgpllibs.dll"],"Microsoft Windows":["dbgcore.dll","winrnr.dll","twinapi.dll","wshbth.dll","pnrpnsp.dll","NapiNSP.dll","netprofm.dll","npmproxy.dll","dhcpcsvc6.DLL","dhcpcsvc.dll","winnsi.dll","DWrite.dll","dbghelp.dll","winmm.dll","Windows.UI.Immersive.dll","twinapi.appcore.dll","InputHost.dll","WindowManagementAPI.dll","textinputframework.dll","Windows.UI.dll","ktmw32.dll","wsock32.dll","version.dll","propsys.dll","WinTypes.dll","CoreUIComponents.dll","CoreMessaging.dll","nlaapi.dll","uxtheme.dll","dwmapi.dll","kernel.appcore.dll","windows.storage.dll","ntmarta.dll","IPHLPAPI.DLL","dnsapi.dll","mswsock.dll","CRYPTBASE.dll","wldp.dll","ntasn1.dll","ncrypt.dll","msasn1.dll","profapi.dll","bcryptPrimitives.dll","msvcp_win.dll","ucrtbase.dll","cfgmgr32.dll","wintrust.dll","gdi32full.dll","crypt32.dll","KERNELBASE.dll","win32u.dll","bcrypt.dll","sechost.dll","SHCore.dll","user32.dll","advapi32.dll","kernel32.dll","nsi.dll","gdi32.dll","ws2_32.dll","rpcrt4.dll","shlwapi.dll","ole32.dll","shell32.dll","oleaut32.dll","msctf.dll","combase.dll","msvcrt.dll","psapi.dll","clbcatq.dll","imm32.dll","ntdll.dll"],"Microsoft Windows Software Compatibility Publisher":["msvcp140.dll","VCRUNTIME140.dll","VCRUNTIME140_1.dll"]} ProcessType: main ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384} ProductName: Firefox ReleaseChannel: release SafeMode: 0 SecondsSinceLastCrash: 12318 StartupCacheValid: 1 StartupCrash: 1 StartupTime: 1775599624 SubmittedFrom: Client SystemMemoryUsePercentage: 5 Throttleable: 1 TotalPageFile: 39652315136 TotalPhysicalMemory: 34283606016 TotalVirtualMemory: 140737488224256 UptimeTS: .2474393 Vendor: Mozilla Version: 149.0.2 Это сообщение также содержит техническую информацию о состоянии приложения в момент падения.

I'm afraid it's not. The lines you posted only contain some info about the state of Firefox when it crashed, but not the crash signature and other important details about the crash itself.

Please follow the steps from this reply to provide the crash report ID. Then, either I or other contributors will be able to take a look and hopefully tell more about what happened.

I didn't find the submitted folder, is that it?I went to the pending folder and in each extra file I found this ec8030f7-c20a-464f-9b0e-13a3a9e97384

Hi vaizer,

Denys is correct, and the log you provided actually explains exactly what is happening:

Regarding the Crash IDs, in your log, it says StartupCrash: 1. This means Firefox is dying the exact millisecond it tries to open. Because the crash is instant and violent, Firefox's crash reporter doesn't even get a chance to run and upload the data to our servers to generate a bp- ID. Τhe browser is just being choked out before it can even speak. Also, the code you found ec8030f7-c20a-464f-9b0e-13a3a9e97384 is actually just the generic Product ID for Firefox itself, not the ID of your specific crash.

The fact that Firefox, Chrome, and Brave are all crashing simultaneously is the ultimate proof that this is not a browser bug. Βrowsers use a heavy security feature called Sandboxing to isolate tabs in your system's memory.

When you enable IOMMU in your BIOS, the Faceit Anti-Cheat kernel-level driver initializes. For some reason the Anti-Cheat driver restricts memory access in a way that panics the browsers' sandboxing mechanisms. The moment they try to launch, the Anti-Cheat cuts their power. Edge likely survives only because it integrates differently with Windows security policies.

kernel-level driver conflict

I highly recommend copying exactly what you wrote here and opening a ticket with Faceit Support, or posting it on the r/FACEITcom Reddit. Tell them specifically: "When IOMMU is enabled for the Anti-Cheat, the kernel driver causes a Startup Crash on Firefox, Chrome, and Brave due to a sandboxing conflict."

Since you mentioned you just updated your BIOS, sharing your motherboard model and CPU details with them will help their devs patch this driver conflict.

I hope they get this sorted out for you quickly so you can get back to gaming!"

Thank you very much, I wanted to do it that way, 👍🏻