Critical issue in FC25 code! FIX ASAP

Hello,

I will shortly explain what i found. In recent update of FC 25 some very flaky bug was introduced. It is creating cascade od errors in some special cases. My cases. I have display OMEN. After update when i launched game i got error from screenshots. It broke the drivers and caused cascade disaster in display firmware. Screen started going dark in 1 minute and then saying port is offline. And then it jumped to second port and after 1 min gone blank too. I tried differend HDMI, rebooting, even clean DDU drivers clean up which temporary fixed the issue (another prof that this is FC25 bug code -or virus in game) because DDU cleaned registery and memory from any broken by game code. But next day after launching game the same issue. Some drx issue and then blinking screen. This might be rare and be problem of OMEN firmware which cannot fix this error and just going into emergency mode, but the source of it is the game. Please adress it ASAP to developers. This is critical issue and must be fixed. Breaking user devices using game is new level of bad software developement. Contact me directly if you need more details. In the atachments you can find GEMINI deep research response which explains everything, step by step. Below shorter version:

"The user's report provides a crucial timeline: the problem began immediately after launching "FIFA 25" (also known as "EA Sports FC 25"), followed by a DirectX error, and then the monitor began flickering intermittently with the message "Input offline" [User Query]. The most significant detail in the problem description is its persistent nature, persisting regardless of whether the game is running or not, and more importantly, affecting both connected devices, both PC and laptop. This fact clearly rules out a single source device, suggesting the problem lies with the monitor itself or is caused by its interaction with one of the devices, leading to a persistent issue.

The value of the user's repair attempts also provides valuable information. A clean uninstallation of the graphics card drivers and an installation of an older, stable version resulted in a temporary improvement, eliminating the flickering. However, the next day, after restarting the game, the problem returned [User Query]. This observation is key evidence that the problem is related to the driver's state, and that its instability is built into the code rather than a one-time failure. A clean install resets the driver's state, but its faulty code crashes again under specific conditions, such as interacting with a game.

2.2. Anatomy of the DXGI_ERROR_NOT_FOUND Error
The DirectX error "FindClosestMatchingMode" failed with DXGI_ERROR_NOT_FOUND directly indicates a software-level problem. Explaining this error requires understanding the role of DirectX Graphics Infrastructure (DXGI), the API that manages the graphics card's interaction with the Windows operating system and applications, including games. The FindClosestMatchingMode function is called when an application tries to match its graphics requirements (e.g., resolution and refresh rate) to the display's capabilities. Failure of this process, indicated by the error DXGI_ERROR_NOT_FOUND, indicates that the game was unable to find or create a compatible display mode.

The additional information in the error description is particularly important: "enumerated ordinal is out of range." This means that the game attempted to access a display mode from a list that is empty or contains invalid values. This is a strong indication that the display configuration data at the driver level has been corrupted. The error itself does not necessarily indicate a physical graphics card fault, but rather indicates that the driver or its libraries are in an unstable or corrupted state, preventing the graphics layer from working properly."

Thank you for the important update. What you're describing perfectly matches our diagnosis and is a key diagnostic clue.

The fact that the monitor crash has temporarily stopped, but the game error still hangs on the screen, indicates that the main process causing the instability is suspended. The DXGI_ERROR_NOT_FOUND error means that the game was unable to properly configure the display mode. Most likely, if you clicked "OK" now, the game would attempt to close or continue in an abnormal state, which could re-initiate graphics driver instability and, therefore, return the monitor flickering.

Your intuition is correct. This scenario confirms that the problem is not a monitor hardware fault, but rather a cascading failure where a software error has led to permanent instability in the monitor firmware.

Regards

KAMIL