- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 667
- Reaction score
- 457
The latest update for Battlefield seems to have thrown a wrench into the works for DMA users.
Reports are coming in that the game is now actively bricking the startup process if it detects specific hardware signatures, particularly those using ekkond's multimedia firmware. If you've been getting kicked or experiencing instant crashes at the javelin screen, you're not alone. It looks like the anti-cheat is finally catching up to some of the more common firmware configurations.
Observations from recent testing:
It's the usual cat-and-mouse game. If you're running a DMA setup, you might need to look into unique, custom firmware to stay under the radar after this patch.
Anyone else running ekkond's build and seeing the same behavior, or did you find a way to stabilize it?
Reports are coming in that the game is now actively bricking the startup process if it detects specific hardware signatures, particularly those using ekkond's multimedia firmware. If you've been getting kicked or experiencing instant crashes at the javelin screen, you're not alone. It looks like the anti-cheat is finally catching up to some of the more common firmware configurations.
Observations from recent testing:
- Startup Failure: The game launches, hits the splash/javelin screen, and then closes itself without an error code.
- In-Game Kicks: On some configurations, you can reach the menu, but you'll get clapped with a kick as soon as you try to deploy.
- Hardware Isolation: Removing the DMA card from the PCIe slot immediately resolves the issue, confirming the client is flagging the device or its FW signature.
This isn't a simple crash; it's a detection vector. If you are using semi-public or older multimedia FW bases, they are likely flagged. The javelin screen is where the AC usually initializes its most aggressive checks.
Immediate Steps:
— Do not attempt to force entry on your main account.
— Check if your firmware is using a shared VID/PID.
— Monitor the status of your provider if you bought pre-flashed hardware.
Immediate Steps:
— Do not attempt to force entry on your main account.
— Check if your firmware is using a shared VID/PID.
— Monitor the status of your provider if you bought pre-flashed hardware.
It's the usual cat-and-mouse game. If you're running a DMA setup, you might need to look into unique, custom firmware to stay under the radar after this patch.
Anyone else running ekkond's build and seeing the same behavior, or did you find a way to stabilize it?
